skysight-inc/HackerNews huggingface dataset:
HN: would you please help me explain something to BrightCloud?
tl;dr: please visit http://beta.brightcloud.com/tools/url-ip-lookup.php and explain to them why they should label jupyter.org as only "Computer and Internet Info" and they should remove the category "Shareware and Freeware".

Longer version:
I'm on a sort of moderately high security network, but I also do research with the data on that network. So access to sites like GitHub and Jupyter.org is super helpful.

My network admins use BrightCloud (we can debate the merit of that decision later), and, for good reason, decline sites categorized as "Shareware and Freeware". Uninspectable binaries are not something we want on the network. Seems reasonable.

The problem is that BrightCloud has seen fit to classify jupyter.org as "Shareware and Freeware". And after a bunch of email, they feel I don't know enough about classifying things (my job is classifying things) to provide input.

So, as it happens, I'm just trying to do clinical cancer research in a hospital. See why uninspectable freeware binaries aren't popular, but the research needs to happen?

So, my request: would you kindly visit http://beta.brightcloud.com/tools/url-ip-lookup.php and explain to them why they should label jupyter.org as only "Computer and Internet Info", just like github, and they should remove the category "Shareware and Freeware"?

Thank you.
Containers may solve some problems, but they're hardly the only solution and the others seem (note: personal bias) simpler to me.

> common baseline

"Here is the standard image with standard packages; if you need something else, add it to Chef/Ansible/whatever-we-use"

> responsibility boundary

"Ah, this binary is in /opt/$COMPANY - go ask the devs why it's broken"

> which is identical

So use configuration management (Chef, Ansible, whatever) for the system and tarballs/packages for your stuff, rather than shipping whole system images per-project?
This is interesting to me, because I've recently gotten into mechanical watches as a hobby. If you don't know how a mechanical watch works, I recommend taking a look at some of these links:

https://www.youtube.com/watch?v=uGcoIue1Bs8

https://www.youtube.com/watch?v=Fh_8BFDcEkg&feature=youtu.be

https://torgoen.com/blogs/blog/mechanical-vs-quartz-watch-mo...
If you have enough knowledge of quantum computation to be annoyed by that sentence, you will not get anything out of the rest of the article.
Then I don't know. You normally have around one hour to edit, IIRC.
remember, just ship it. doesn't work? ship it and let the users tell us what's wrong. maintenance nightmare? ship it and then ship it's replacement later. not designed for security? just get bob's cousin, who says he's a hacker to try it, then ship it.
> Why not both?

Because it costs too much right now. SpaceX is providing NASA with rockets, I'm not sure they'll have a sustainable business model to get to Mars. I hope they do find a way but until costs come way down it's going to be tough.
Cool. Call me when I don't have to calculate capital gains taxes every time I spend Bitcoin.
I think it's awesome that you can become a software engineer without any engineering schooling. Where I live you have to take software engineering in University to be a software engineer. Bootcamps and certs usually only get you dev jobs.
How do you know the people interviewing you are rich kids? I work at a big 4 company and I grew up in a low-middle class household.
This doesn't address the coming problem of automation in which unemployment numbers are likely to rise. It is also ends up basically being a regressive tax as those who make the least receive the least benefit while those who are already living comfortably receive the full benefit.
Good article, but I personally hate Take-Home coding challenge:

Some people spend an entire week on the coding challenge, which really set the bar unrealistically high. Once I turned in a project 2 hours after receiving the assignment and got rejected because they think I didn't even try. Every functionality worked flawlessly, but they want tests and for me to treat it like a real production work. But how do you motivate yourself to treat such a trivial take-home (which will never be maintained because its a take-home assignment) with the perfection you would in production code? In production you have much better insights like how your component impact others, how users will be using your app, etc.
The effective US corporate tax rate is more median. Our headline tax rates were higher, but we also had larger deductions and tax credits.
https://github.com/solid/solid#about-solid

this should answer all of these questions
I have no idea what they are planing but my simple approach to the problem would be, to let browsers offer an API to store their users data in the cloud.

That might sound a little abstract, so I will give an example: A year ago I built an PWA which had the ability to use a WebDAV server as a backend to store data and sync multiple clients. While some might argue that WebDAV is not the perfect protocol, most of its disadvantages can be worked around. The real issue is that the user has to enter his credentials to every app which wants to store some data for him.

In my opinion, that is something browsers could make a lot easier and just let the user grant/refuse access to the 'cloud-storage'. That cloud storage would need a standardized protocol (e.g. WebDAV) to manage its access, but that way browsers could offer web apps a large storage and the user could select its own storage provider (in the browser settings).

Most users would probably stay with Google Drive or Dropbox, but at least their data would not be stuck in the walled gardens of the various web app providers and some might even choose to store their data in a Nextcloud (at least that is what I do with my PWA).
Another option, once you have some cash built up and are otherwise diversified, is to occasionally request that the loan be recast.

https://www.bankrate.com/finance/mortgages/what-is-mortgage-...

Recasting works sort of like refinancing .. but your rate doesn't change and neither does your mortgage term.

Instead, a lump sum that you provide is deducted directly from your principal. Your monthly payment is then recalculated based on that reduced principal amount.

The financial institutions usually impose limits (minimum lump-sum amount, how many times per year you can do it, etc.) And they don't advertise it or make it easy, because there's no money in it for them.

And since the principal/interest ratio is front-loaded (so that much of the money that they make from you is in the first seven years or so of a 30-year loan), then if you can recast early in the life of the loan, the benefit is increased. (And that's the real reason why the industry advises upgrading every seven years - that 30-year, front-loaded clock gets reset in their favor.)
Introducing the POAP (the Principal of Applying Principals)
V-model is great. For other folks reading this thread, a few things it lets you do:

1) You can still use v-model with Vuex: https://vuex.vuejs.org/en/forms.html

2) You can easily distribute custom components that provide `v-model` to users

3) You can dynamically accept 3rd party components that implement `v-model`. E.g., I have a component that incorporates standard form fields, but can also be used with any custom components that properly implement `v-model`.[1]

[1] - Vue Query Builder (https://dabernathy89.github.io/vue-query-builder/) - try adding a 'Range' rule to see this in action
> so there's not a single number that can be given here, you pay for what you use.

While true, in practice as soon as you use, for example, `List`, `Map`, and `Option`, along with various basic collection operations (`flatMap`, `map`, `zip`, ...) you've pulled in basically the entire standard lib*

Wind up paying about a 160KB baseline "tax" to use Scala in the browser, which is well worth it considering that you can ditch jQuery and related plugins (DataTables, Validation, etc.), shedding far more weight than Scala.js in the process. I find it to be a huge win, wish I could use it in current bloated Angular 5 + TypeScript project :\

* This is due in part to existing collections library that is not so amenable to dead code elimination (or at least google closure compiler can't track the full reach of CanBuildFrom's tentacles :)) Maybe this will change in Scala 2.13 collections overhaul, have my doubts, doesn't sound like the new design is radically different than the current one.
I took the 11-week Coursera course last year (and even paid for the 'verified' certificate). It was worth it, I think. I may not have a deep understanding of the different ML algorithms that were presented, but at least I know of their existence, and to what problems they are suited (and then I can look up the details when needed).

Granted, that's not enough to actually find work doing anything ML-related, as there are now plenty of experts with years of experience out there on the job market, but hey, I like learning stuff for the sake of it. I'm thinking of taking one of the follow-up courses on NN.
> Only because we are going to allow it. We could, you know, keep it in orbit and continue to use it.

I'm not sure if it's safe to operate much longer than the 2020's without some major work and the running costs are astronomical. I'd love to see the ISS live longer but with limited resources going to the moon instead seems like a solid plan. At least on the Moon we might be able to get some practice in at harvesting resources off world. That's really going to be the economic key to kicking off a non war related space race.
Highland Park and Dobb's Ferry have public schools though:

https://www.dfsd.org/

http://www.hipark.org/

Median incomes in Highland Park are lower than Detroit and the school system there basically failed a few years ago.

I think there's probably a pretty good argument to be made about how schools are funded. Just pointing out that not all properties are inside of large cities isn't it.
Some thoughts on asynchronous API design in a post-async/await world (2016)
how's that fair if you have person a working in a callcenter for slightly better pay than person b working at McDonalds.

Person A makes 20k, person B makes 10k. Both work pretty shitty jobs -- I wouldn't want either.. Both work the same hours. No more jobs exist for Person A's job, so Person B couldn't rise up to their level if they wanted to.

GBI works because everybody gets it -- so nobody feels like they're getting special treatment, nobody feels like they're on welfare (which causes a mental stigma to begin with) and the goal is simply to cover average rents and maybe some food. Everyone should have food and a roof.

Your plan also doesn't account for what happens when all the jobs for both A and B close down because of automation which is the whole point for why we're discussing GBI more and more anyways.
I think that’s different, and the response to that sort of company, especially for a senior employee is to resign.

If the founders are behaving unethically or illegally, the board has already failed to fulfill its duty. “Don’t kill the messenger” is rarely reality.
I don’t know what else to add to this. Slack is a bad idea, implemented poorly, and I can think of no redeeming qualities to it.

Edit: Looks like Slack’s employees decided to swarm to the thread and downvote anything critical about their shitty product.
I'm very comfortable typing /mute in noisy channels and coming back later. I'm also happy to close slack when I need to be in the zone.

IMHO Don't blame the tools, it's about discipline, you need to own your time, calendar time for yourself and get stuff done. If management doesn't understand this then time to find a new team.
See: Earned Income Tax Credit https://en.wikipedia.org/wiki/Earned_income_tax_credit
To create, you must de-story
I wonder if disabling search and restricting chat rooms to a limited buffer would help encourage people to see Slack as a lossy chat service and not an appropriate data store. You would be forced to decide what's important to keep and keep it somewhere.

I especially don't like when Slack is used as an official record.
As time has wore on our organization has relied on slack less for team collaboration and more for monitoring.

Admittedly, the slack client is great at cross platform notifications and we leverage those in our monitoring processes, where alerts are sent via zabbix to pagerduty and slack simultaneously via webhooks.

In a real sense the responders have “any activity creates a notification” which enables them to react and others to view a record of what happened. This eliminates the casual “what happened?” conversations.

We’ve yet to have an oncall event fall through the cracks.
They're having a few issues with it right now it seems.

https://github.com/angular/angular.js/issues/16432
You're right, there are volatile hedge funds, although it might be accurate to say that there are more and less volatile funds than indices. Moreover, there are plenty of bad funds that only exist to dupe clueless retail investors into giving them their money. I wouldn't say that all hedge funds are good, and in fact regular people are probably screwed when it comes to picking a good one (in part because some hedge funds are what I like to call "20/20 funds" and are just statistical testaments to the fact that some fraction of poorly managed funds will still do well).

Volatility isn't a binary thing. Although the less-volatile more-return funds are out of reach for regular people, the less-volatile less-return funds are not, and these still have a lot of value for people who are less tolerant of risk.
Show HN: A bittrex crypto currency trading bot using Node.js/Redis/Matlab
There are a few issues on Github that would explain this. It seems that they tried migrating to FireBase and are ironing out some things still.

https://github.com/angular/angular.js/issues/16432

https://github.com/angular/angular.js/issues/16447
Still true globally at the high school level. Found some quora answers with perspectives on IOI(programming olympiad) and IMO(math olympiad) which both have low single digit percentage female participants:

https://www.quora.com/Why-are-there-few-females-in-competiti...

https://www.quora.com/Why-do-boys-outperform-girls-in-math-c...
I'm pretty sure the person you replied to was being satirical.
You may know this already, but using Vue Dev Tools you can easily export & import Vuex state.
I heard a funny story once about an interaction between Tim Berners-Lee and Ryan Shea. Woulda been about 4 years ago and I can see how it might have prompted TBL to take a crack at the same problem. Maybe you're right?
One issue my team is dealing with is how to store our large models. We are using git lfs at the moment but it feels woefully inadequate. It is trivial for a team member to accidentally commit the 500mb file to git and completely destroy our repo size.

Not to derail the post, but what does everyone else use?
Violation of privacy?
It widely varies for me. For general contract work I shoot for $40-80/hr for Ruby on Rails or Angular 4 / React / Vue work. I tend to charge less for some languages that I am less adept with such as Python. I have about 4 years of experience now.
>How is he proposing to pay for UBI aged 18-64? The only way I would support a UBI is to completely eliminate social programs like welfare, food stamps, and housing assistance. It may then be cost-neutral.

That won't do it. $1,000 a month for every working age adult would cost over $2 trillion a year. That is roughly equal to what the Federal government spends on Social Security, Medicare, Medicaid, and Defense combined. There is no way this plan can ever be cost neutral. For it to even be financially feasible it would need to come with a rewriting of the entire Federal tax system and budget (which would probably be a good thing, but it would be a political impossibility at this point).
How do you embrace an era where there will be no jobs. Even doctors, lawyers, accountants and callcenters will be automated -- let's plan for the automation era send everyone to med school if they want to... oh shit... we don't need doctors anymore, oh well - you still have to pay your student loans...

I'm a web developer, and learning ml/ai so I can automate myself out of one of the last existing careers.

We can move to a post-scarcity world where all menial tasks are done by collectives of robots who work for all mankind... it is possible and would be cool, I just don't know how we begin to get there.

By the way most academics/economists agree that in 12 years there will be a minimum of 40% of the current jobs gone. Not replaced by new jobs in ai/ml - completely just gone. As in those 40% of people have no use for society at all.
I wouldn't even be sure skipping that part makes it an better, because that sensation might actually distract from all the others, and while it wears of, the others don't in the same way.
> The ability to smile is not necessarily connected to the meaning of a smile, though.

Pediatricians call it a "social smile", and it is an important milestone in newborn development. See https://www.webmd.com/parenting/baby/babys-first-social-smil....

Evolutionary, I think the intention is to bring parents further under the baby's spell, since otherwise they might give up because taking care of a baby is a lot of work!
That's fair.. it really depends on the situation. Too many feature flags can get complicated in the same way too many open, long running branches can. It's nice to have the option of either. Feature flags I think are a bit easier to forget about and leave in the code; branches are obtrusive and you constantly have to merge new code in to keep them updated, pushing dev to get rid of them ASAP.

All my work lately has been done in branches, which then merge to master, and master gets deployed to production as needed: sometimes immediately with a single bug/feature, sometimes several bundled together after a week or two. Depends on severity, other work occupying the team (especially QA), and which software/system(s) are affected (eg. core software, infrastructure, or internal tooling). I am pretty sure we've only used feature flags in the core software, and only a couple times. Of course, that software is hybrid cloud/on premise, and as such we have strong version numbering for every release, so features/changes naturally tie to the customer-facing release numbers.
There is no sustainable business model to go to Mars. Unlike LEO, GEO, or maybe even Moon, there's no business opportunity on Mars.

The only way to go there is to accumulate resources from real business, and to improve efficiency.
As Helena Cronin noted of men: "more dumbbells but more Nobels" [1].

[1] https://www.edge.org/annual-question/2008/response/10670
if you want to fast, go alone.
if you want to go far, go with others.
Folha stops publishing content on Facebook [portuguese]
The problem I have with large group chats like Slack, Riot, IRC is that it's hard to get information from them when you've been "out of the loop" for a while. Much better to read a bunch of forum threads or tickets, then trying to make sense of a long scrollback.
Mass transit is clearly the solution we need, but it is tricky to convince people since they are so used to private transport.
Ai yai yai. People need to stop adopting tools thinking it'll be the panacea of communication and organization. Insofar as the author says that I agree.

But I think it is equally short sited to blame the tool.

Whatever tool you choose, you have to FULLY adopt. Everyone has to be bought in, learning the features (like do not disturb), setting ground rules which make sense for your company and how people within it like to get things done.

Seriously, I never felt more productive than when I used Trac, I don't think issue tracking has really evolved much more than that save useful social features and code review (essentially what killed Trac because the Git integration was never very good).

When I look back as to why that was, I realize it was because the WHOLE COMPANY was bought in. We all used it, we all used it well and respectfully.

This is the madness of the agile world. Viewing the tool as the solution rather than just that, an implement, a ways to a means that starts before its usage and and ends after its usage.

> Remote work culture is a defense mechanism against the distracting open office

Disagree as to the reason remote work has become a thing, but I do think it's largely because video conferencing works better every year, tools like Slack exist, and code review tools can be done line-for-line remotely.

But, has anyone seen the Slack diagram for whether or not to send a message? It is extremely well thought out, but settings can't be useful if you don't set them.

> Chat, at least on slack, isn’t grouped or threaded.

Yes they are, now.

> ...non-trivial to know what the current topics of conversation are in a slack channel or to assign one of those topics to any given message.

Then speak up and tell people to stick to the topic, change it, or open a new room.

> ctrl-f, the one constant of web interaction, is broken in channels if you’re searching more than one page up.

Use the Slack client

> Middle managers will make deliverables....

And here is where I stop reading. This is an organizational problem you see manifesting on the tool and you are incorrectly assigning blame to the tool.

--

You have to be committed to using whatever tool is chosen. Just choose one and actually use it.

These tools are a discipline not a freedom from discipline.
My impression is that this is basically Urbit. Am I wrong?
Another interesting link that puts together a timeline of events: https://www.reddit.com/r/CryptoCurrency/comments/7wp334/the_...
What are these jobs that you think will resist robotic automation, and how many of them will there be? Realistically a small percentage of people will ever be programmers in our society; we just don't need that many.

Look, we're entering a period of history where the number of tasks requiring human labor will only keep decreasing. This will lead to a growing class of people for whom the labor market cannot provide a basic standard of living.

If a stronger welfare state isn't the answer to that problem, I've yet to hear what is, exactly.
For most people, a house payment also represents a direct impact to their ongoing cash flow. If your house payment is $2000 a month, paying off your house automatically increases your cash flow by that amount.

What else could you do right now with that cash flow - not only in direct alternative financial investments, but in indirect investments in your own well-being and quality of life?
My comment isn’t disingenuous. I’m neutrally presenting the reality that it is possible to beat the market. I’m not saying most people should try it, and in fact I specifically stated most people should stick to index funds. I also specifically admitted most people who beat the market are outliers, just like professional athletes.

The point here is that it’s dogmatic to continually say, “you won’t beat the market, don’t even try, look what Buffett says about it”. I have laid out, in this thread and others I’ve linked to, how it is possible to beat the market in principle. No, not everyone will do it, but people will want to try anyway, so in my opinion they may as well be equipped for success, insofar as they can be.

I haven’t tried to undermine the position that index funds are the best option for most investors. I’m just providing perspective for those who understand that and want to try actively trading anyway. I dislike the blind advocation of index funds in a matter of fact manner - it doesn’t actually improve financial education as poignantly as discussions such as this one do. A complete presentation should include the subject in entirety, not the, “We know what’s best for you” version.
i don't have a real account, haven't had one for years, because eventually i say something the mods don't like.

cheers.