skysight-inc/HackerNews huggingface dataset:
I find your reasoning very strange, if anything, GPL ensures that the 'ideas' are instead made available for anyone to use, provided that they in turn do the same.

If anything would be a 'tumor' by your reasoning around ideas, it would be proprietary software, which is what GPL prevents.
Your link isn't working for me.
I recently used indico.io for a project, and I'm a huge fan of what they offer.

From my brief interactions, they seem like awesome people too.
There's a big difference between trolling and stalking. The problem is that what happens to pass as trolling today isn't even trolling it's just plain stalking. When you post someone's address, a photo of their house, or call someone's local PD to coax them to send the SWAT to their house then you're not a troll. A troll is all about flames and absurd reactions from people.
Perhaps doing this in DNS with DANE-EE TLSA records is a much better solution for all the reasons discussed here.
Yes, it is. This is an excessive level of caution which does not reflect the permissiveness of actual copyright law. However, there is the concept of "unintentional copying", which is effectively what you're describing, and which is still considered an infringement under copyright law, however it's very, very unlikely that such an argument would be used in court with regards to software, and even more unlikely that a jury would be convinced by it. It's really more of an argument for subjective and creative endeavours, such as hearing a music clip or seeing a logo design or piece of art, which leaves a strong impression.

Lawyers tend to fuel the FUD around this with "best practice" concepts such as "clean room", which is a drastic overreaction. It's akin to saying "if you want to be an author you should never read any books, in case you accidentally copy one of them". Sigh.
gizmodo's days are numbered now gawker media is broke.
Create Contact Lists Quickly with Slack
Don't you think there's difference between reading about surgeries and performing those surgeries (Or POC surgeries :))? I do get what you are saying, not trying to be mean. What I'm saying is the effort and time commitment to do weekend apps sometime end up taking whole weekends including nights...all because we love doing this.
Nice to hear
Nonsense.
Assuming the government intends to run something vaguely resembling a balanced budget, tax receipts (plus inflation away of govt debt) has to broadly, in the long term, equal money paid out (UBI + lots of other stuff). Which means (1) the government has to make up the portion of income tax revenues lost from high earners that spend relatively little by ensuring sales tax is sufficiently high to get the money back from lower earners that consume most of their monthly wage, and (2) every time the government puts the UBI up, they have to put taxes up [in the near future]
The customer support tools is a great idea. Twitter should optimize for how their users are actually using Twitter.

Other ideas:

- "Enterprise Twitter" for private communications and sharing status updates. Something like Yammer or Facebook at Work or even Slack, though big companies might not want a consumer brand associated with "goofing off" inside their enterprise.

- Flattr-like micropayments to let people "tip" a favorite tweet. This could encourage more people to tweet as a source of income. Like PayPal, Twitter could generate interest off people's tip accounts.
My money would be on the older person sticking around longer. It's very uncommon for anybody to work at the same company for decades any more, but older people tend to have children, mortgages, and other commitments that keep them from jumping around too much.

Besides that, younger people will require larger raises to keep around because the difference between 1 year of experience and 3 years of experience on a resume is significant, while 30 years vs 32 years isn't. The older person will ask for a higher initial salary, though.

I'm also skeptical the 25 year old and the 55 year old will have the same skill level, assuming the 55 year old has been in the industry for any significant amount of time.

Edit: I didn't see "junior" in your comment when I wrote my reply.
> That isn't a definition of "fast moving" that I would use. It sounds like slow moving.

Perhaps I didn't word it correctly.

When you want to write the next WhatsApp, you don't have to start from scratch. The OS has been taken care of for you, and you can expect it to "just work".

This solid foundation allows innovation to build on-top, at a rapid pace. If your foundation was constantly changing, you'd have to account for all sorts of weird intricacies, non-portable code, etc (like the old days).

A rapidly changing OS isn't really what you want for a production environment. In fact, you want it to be as constant as possible, so that you are free to do your work.

> Actually, Bell Labs had no problems with building their entire system front to back in their new unproven language C instead of using Fortran

You're right. But do remember it took a long time for it to propagate. Today, there's still systems not written in C (although they are in the minority). At the time, a lot of systems were written in pure assembler, and it took a long time to convince those guys that C was ready as a replacement for most tasks (and C changed dramatically in that time period).

I'm glad they went the way they did at the time -- but today with all these things built on top (financial markets, governments, big mega-corps, small ma n' pa shops, etc...), we need slower changes in order to keep the stability.
#2 is assuming UBI is a one-time cash injection to stimulate aggregate demand, similar to QE. I have a hard time seeing the path forward to the (substantially) higher taxation on the middle and upper classes needed to make UBI a reality with the current political and economic climate in the US. But this is subject to debate. You are correct that a redistribution of the tax burden, if feasible, would not lead to inflation.

#3 - yes, in agrarian societies poorer people have more children to help out with labor-intensive work. I think the situation would play out different in a services-based economy like the US.

The monetary aspect of UBI would not influence the wealthy, educated cohort's decision to have more children (usually capping out at 3). It would give lower-income individuals an incentive to have more children in order to claim more benefits, as is common for contemporary social services programs. If UBI was substantial enough to allow lower/middle income individuals to quit their jobs, they would also have much more time to have and raise children - not out of necessity, but out of ability.

Agreed that the effect on population size is uncertain and needs an actual study.
Ok, I think I understand the confusion now. You seem to be of the impression that shell scripts are like bytecode executed in a virtual machine. That is the only way I know of that you could write an application for a platform that doesn't exist and expect it to work. But even for that to work, it would need to be the same VM, and bytecode generated by & for it, or there's still no guarantee it will work.

Of course, you can already write a shell script for a particular shell, distribute that shell to that system, and depend on the shell to properly execute your script [by using internal functions only]. But that defeats the whole purpose of following a standard like POSIX, or caring at all how any given platform's 'echo' program works.

Bottom line, though: two independent implementations of a standard provide no guarantee they will work together. Practice over a couple decades shows this to be the case.
Terrorists kill very few people. People driving cars kill far more people.

9 people are killed in America every day related to distracted driving. In four days distracted and texting Americans kill more people than terrorists did in Belgium. Let's have an uproar about that.
> His argument is that achieving the level of quality that SQLite has requires verification (in a broad sense) after the compiler, and that's what he does.

> If you consider the goal to be producing quality-assured binaries, then you can treat UB, compiler bugs, and many other things as falling in a similar category, which are almost certainly eliminated by an MC/DC test suite.

I don't think that they're eliminated because dynamic testing can't eliminate everything—it only finds bugs given its test inputs.

Moreover, though, I'm also skeptical of the claim that binaries are all that matter. Lots of software projects (for example, Firefox) import SQLite as source into the project instead of using the binaries. They upgrade their compilers without running the SQLite test suite to catch regressions. (Firefox might, but I'm sure lots of other projects using SQLite from source don't.)

> But it does mean that rewriting SQLite in Rust wouldn't provide as much value as rewriting many other things where the binaries do not have such guarantees.

Sure; static analysis is more useful in systems that aren't as well dynamically tested. But static analysis still has value.
http://bokeh.pydata.org/en/latest/

"Bokeh is a Python interactive visualization library that targets modern web browsers for presentation."

(Of course, it works by generating JavaScript)
Less is more: our analysis of top logo redesigns
Well that is easy too. Even if you have cursory information about a problem stating that in terms in which you could get an answer is very easy these days.

You seem to be describing a situation which existed two decades back where a person's only portal to information was a library.
Newspeak, doublethink and thoughtcrimes
true, the machines in those days were much more limited and hence more understandable.... I'm a product of that era but what inspired me back then was hoping to create games similar to what I was then playing.

Don't get me wrong, I would love for kids to get into the MicroBit, I deal with similar systems all day long (embedded/realtime stuff on Cortex-Ms) but although its more accessible now due to the MicroBit and RPi, it seems to me that there is still a cognitive gap for kids to jump.
Much of the career advice I provide serves to counteract poor advice given by parents or university career counselors. Even most general career advice doesn't apply to the industry.
SandDance – Dynamic Visual Data Exploration
slacker hat: perspective is one of those words they use when they want something from you, like "duty" or "contribute". Doctors get so much more job security, prestige, and straight-up money than software developers. By the time we're in our 60s, many of our classmates who went into medicine will be living in neighborhoods and moving in social circles that are completely inaccessible to us.
Hi. I run a thing that uses a lot of bandwidth.

Repeat after me:

I can not safely use usage-based pricing clouds like AWS and GCS until they get serious about the DDoS problem.
I can not safely use usage-based pricing clouds like AWS and GCS until they get serious about the DDoS problem.
I can not safely use usage-based pricing clouds like AWS and GCS until they get serious about the DDoS problem.

I've brought this up before:
https://news.ycombinator.com/item?id=11261882
https://news.ycombinator.com/item?id=11000086

Many people that are in denial about this. This article is not an outlier, this is exactly how DDoS is now. DDoSes are cheap to execute and devastating to the host. Your competitor will chip in a little Bitcoin and get these people to attack your site. Or they'll just do it because they're bored and it's basically free for them. I knew a guy that worked on a site, he told me they always got DDoSed every time his site put on a sale. Guaranteed DDoS.

Who gets the $30,000+ bandwidth bill for the attack? Well, if you're using AWS or GCS, you do of course (it happened to Greatfire, why won't it happen to you?)

30x market bandwidth markups, zero DDoS mitigation. Good luck.

Edit: Oh, and VPS providers (DigitalOcean, Linode) that just null route servers for hours or days during a DDoS: you're not off the hook either.
No it really doesn't. Code which implements the same API is going to look pretty similar, for example ReactOS looks a hell of a lot like Windows. But it's not been copied.
The Chinese were aware of this risk when they banned Google.
Dennis you left the name of the Russian DDoS site in one of your images...you may want to consider cropping this.
also: bigger dishes are cheaper and you just might eat more cheap carbs like noodles.
The purpose of such a DSL isn't to let you write generic clojure faster. The DSL isn't even targetted at traditional programmers. The purpose is to enable training people who have no idea what Clojure or Lisp to get things done that are complicated (or expensive) to design graphical UX for. These people might have some excel experience or maybe a programming class in college, but are mostly reliant on examples and documentation to get things done. Why teach them things like how to create a function when they don't need to know or care? There is a huge usability difference for these people between (fn [age] (> age 18)) and (> age 18).
Domo Buzz – Collaboration platform for people that get things done
People have never liked the idea of being liable for their own actions.

What is strange is that people on this forum now thank that rich and powerful corporations shouldn't be liable for their actions either.

It's pretty clear that Apple should be liable to their customer's privacy. What seems to be forgotten is that Apple is also liable to the government's right to search and seizure.

We made the government agree to the 4th amendment to define not only our own individual rights but how they are balanced against the public good.

The judicial system has interpreted the constitution to state that these 4th amendment rights only cover what is contained within a person's private properties.

This is very important: There is no legal concept of an "authored work" that is non-public in nature. As soon as information that is attributed to you leaves your private property is is considered published.

We've structured our entire economy, legal, and political order on this concept. We have public marketplaces. We have public credit and criminal reports. We have public notices of lien. We have public courts that enforce private wrongs of all sorts. We have public records for land titles. We have public roads and public parks and anything that happens out there is considered freely published to the world. We have a public copyright regime that gives us financial entitlements to those published works.

There is no legal notion of "authored work that is private and non-public in nature" that leaves your physical property. Imagine what would happen to the above public infrastructure if this was the case. You can't because that's almost as fantastical as saying "imagine that we didn't have money and just bartered with bags of salt".

Clearly we have a need for some limited concepts of "authored work that is private and non-public in nature", or as I've been calling them, "privished works". Clearly this privished work is going to need to adhere to the existing notions of the constitution and we will need statutes that clearly outline the liabilities to both private citizens as well as public governments.

As I see it, Apple would need to be liable to both the government as well as to individuals. They would not be allowed to sell privished works to 3rd party marketers. They would not be allowed to let anyone other than the author decide who is authorized to read privished works. They would have to make sure the government could read privished works with a search warrant.

The deeper issue on this forum is that current software developers do not want to be liable for anyone else's privacy either. They just want to keep being able to make their apps without really being held responsible for their actions.
There's nothing wrong with reading the source code. You're allowed to read whatever you like! Just don't copy it.
Is Eclipse still growing exponentially? I remember Ganymede -> Helios increasing 2MM LOC, Helios -> Indigo 4MM LOC, and Indigo -> Juno 8MM LOC. I couldn't even get Luna to run, and haven't checked back in on it since then. The foundation started to bundle up too much stuff in the distributed versions.
> One is easy, the other is hard.

There are APIs and libraries for OCR, so that might not be so bad (even on a mobile device). A low-end phone is faster than the first PCs I did OCR on anyhow, and about 20 years more research has gone into algorithms.
Yep. It's a gentrification that has been chipping away at different aspects of the Internet for as long as I can remember. A struggle between the pioneers who have learned to live (and even flourish) within the chaos, and the rest of society who want the chaos eliminated.
You may be interested in linkerd (https://linkerd.io) -- we built it specifically to address the complexity of proper connection management at scale (service discovery, timeouts, loadbalancing, retry policies). Extends to routing and instrumentation as well.

The goal is to offload that logic out of your application.
Moderation is the best way to stop them. If you've got actual people going through posts and content and removing the low quality stuff, you'll maintain a much more well ordered and useful community than you would a mostly 'uncensored' platform.

Unfortunately, this has a few issues...

1. You need the manpower to actually check what's being posted on a regular basis. Or enough active members willing to help out that they'll do it for you on a voluntary basis as moderators. This is obviously easier for small sites like customer support forums and the average fan site.

2, You need to really, really limit bias as much as possible, so that you're booting out people or bots because of their behaviour rather than their political/social stances. This is what Twitter doesn't do at the moment, to the point being a 'progressive' troll is a good way to never get banned while being a conservative or having an unpopular opinion will get your account suspended for the smallest trangression.

3. A willingness to ban popular, rich or 'powerful' users as much as anyone else, if they break the rules. A good forum/community manager will just as easily kick out a troll with ten thousand posts as one with ten, but social media sites don't seem to have figured this out yet.

So for a community manager or site owner, moderation is the best way to stop internet trolls (and every other type of troublemaker or nuisance as well).

Making a user's post invisible to everyone but himself (shadowbanning or as vBulletin called it, Tachy goes to Coventry) and making their time on the site a nightmare due to fake errors (hell banning/miserable users) used to work. Note the word used to, since the internet is a lot more savvy about this sort of stuff and will usually figure out these systems pretty quickly now.

As for how to avoid internet trolls as a user? Well, stay off large social sites with few rules (or in some cases, extremely badly enforced ones) and go to places where the people tend to be a bit nicer to each other due to a shared interest or two. Less Twitter, more forums.

Stay fairly anonymous wherever possible. Seriously, trolls love knowing every detail about someone's offline existence and what annoys or upsets them. By giving less personal information, you force people to either REALLY dig for information to use or to attack your arguments rather than your background/appearance/personality.

Don't engage in arguments with trolls/idiots. The more you make it seem to affect you, the more pleasure a troll will get from their actions. If you've ever watched The Simpsons, you probably remember the scenes where Bart prank calls Moe's Tavern, right? Or how often, Moe would basically scream back down the phone in anger afterwards? That's what a troll wants to see. They want people who are easy to annoy.

So yeah. Moderated community platforms tend to be the best way to stop internet trolls, since they mean such users and comments are removed as quickly as possible.
Interview: John McAfee on FBI iPhone Hack
> At the time, a lot of systems were written in pure assembler, and it took a long time to convince those guys that C was ready as a replacement for most tasks (and C changed dramatically in that time period).

And they were wrong to resist C. They should have switched over sooner.

> today with all these things built on top (financial markets, governments, big mega-corps, small ma n' pa shops, etc...), we need slower changes in order to keep the stability.

Stuart Feldman, on why Makefiles insist on tabs:

"After getting myself snarled up with my first stab at Lex, I just did something simple with the pattern newline-tab. It worked, it stayed. And then a few weeks later I had a user population of about a dozen, most of them friends, and I didn't want to screw up my embedded base. The rest, sadly, is history…"

Stability is important, but eventually you do have to go back and fix things that are wrong for us to move forward.
Last time I looked in to this (many years ago) the only way you can use software that reboots an Android phone is to have that software signed with the same key that signed the firmware running on the phone. [0]

Sadly, it's not straightforward to make a remote reboot-phone button that's usable by the general public.

[0] IIRC, calling halt(8) from the shell didn't work, either.
What I like is that everyone has a solution on how twitter should run, but no twitter to run.
Well unlike fax machines though are protocol shifts over time. New tags and conventions are invented. A known shared dictionary seems a better method than a hard coded static dictionary.
True. Stuff like common functionality (regex engine, math functions, talk to postgres, etc) should be written once, and consumed with higher level interfaces from all other languages.

The problem is we don't have a safe, easy to build and package with everything else, and easy to consume (without performance penalty) language. The best we have is C, which is not enough.
I reserve a few down-votes each day just for people who rag on titles for being "click bait". I mean, really, why is everyone so obsessed with every article's title? Besides summarizing the content of the article (sometimes in a clever way), a good title gets you to click on it.
Completely understand the creativity bit... and I'm glad its working for you, but I think the hope of recreating the era of the Spectrum/BBC/AppleII/etc isn't going to work.

I'm a product of that era (as I suspect you are) and what inspired me was that I knew I was able to do whatever the professionals were able to do....
Thats a cognitive gap that I dont think has been bridged with this type of device.
The only difference between today and say 2500 years ago is the speed of dissemination and little fear of being run through with a sword.

I think, though, that it's a pretty huge difference. The speed with which someone can crap all over a discussion is instantaneous and psychologically a lot easier due to not being "in person". Trolling in the form that it would have existed a couple of centuries ago[1] still exists today (without the sword, perhaps, but the threat of violence in retaliation to trolling still exists today -- we just have better technology and better enforcement). I would use Donald Trump as an example. He gets his share of trolling (and non-trolling protesting) at his in-person events, however, I'd hazard a guess that the amount of such activity during his entire campaign would be about as much as is seen in an hour on Reddit.

[1] We don't have a lot of historical evidence that dates back 2500 years, so I'm assuming that was a typo or an embellishment used to make a point (or, perhaps, something I missed in my speed reading of the article).
I think that's called DDoS, not trolling.

Who is targeted by that and why? Who organizes that - I mean, why would thousands of people suddenly have reason to hate you?