skysight-inc/HackerNews huggingface dataset:
Signing is definitely part of the answer but there's still the question of trust.

A signed package doesn't really tell you that much. In the best case scenario it tells you the package you're installing in fact came from developer X and contains code Y (which you kinda already know since you have the source code). This works as long as you know and trust developer X, or did your due diligence reading through the code (which you can already do today).

I can't think of an end solution that wouldn't have to rely on network effects and social proof, which strikes me as rather fragile. Maybe formal verification and AI can help, but that's a long way off (?)
Basic income is a great way to test that, yes.
Wristify: Thermoelectric Wearable Would Reduce Energy Consumption
NYC rents
> This is why markets are a bad thing.

... well, that's extreme. The ownership of the company should be working to avoid long term disaster. In most industries this happens all the time.

Actually, some of the main instances they don't (financial industry) is because of government support. If you're allowed to fail and get bailed out, then there's no reason to avoid disaster.
This should firmly cement law enforcement's status as thieves rather than civi servants. As if civil asset forfeiture didn't do that already, already making police the #1 class of thieves in the US: https://www.washingtonpost.com/news/wonk/wp/2015/11/23/cops-...

To steal and murder! The correct police motto.
He's referring to plain-old civil asset forfeiture.
Just because the party in power calls itself "socialists" doesn't make them socialists. Their current plans to gut worker's rights are antithetical to socialism.
With the added wrinkle in this particular case that the patent troll is also suing a bunch of little guys who decided to use Google Play Store.
> anonymous testimony

Okay then, how about these:

https://hypatia.ca/2016/06/07/he-said-they-said/

https://medium.com/@nickf4rr/hi-im-nick-farr-nickf4rr-35c32f...

https://twitter.com/quinnnorton/status/739937558533021697

And just to make sure this tweet isn't missed... https://twitter.com/quinnnorton/status/739939420183400449

Quinn Norton:

> I do hope Jake has enough sense that trying to accuse me of being part of a vast gov conspiracy to take him down would catch in his throat.
Wat?

> To "reinvent" the "web" (or what I call the Intercloud), business models must be removed from the equation.

This goes into my "and everyone gets a pony" set of solutions.
Wonder if they know each other, seems like they would have something to talk about.
It won't though. The supply of people willing to sell their soul to make easy money contains more than one person.
I regularly use non-printable ASCII characters as delimiters. I just confirm first that they are not in the input. I am going to start using the ones you mentioned. This solution is one I rarely if ever see used. The other solution which I have seen in practice is to encode the comma character. The problem really IMO is that people who make CSV place no limits on what range of characters is stored in the tables. Certain characters can safely be removed. In most cases the input is still comprehensible without commas. Commas can be deleted, freeing up their use exclusively as record separators.
Many BLE devices do not advertise with random addresses. iOS and Android do, but last I checked Fitbit and Tile do not.
The success, or failure, of OpenOffice itself says little-to-nothing about the success of the ASF itself. Why OpenOffice was not as successful as hoped is a long and drawn out story, and Apache suffered from the ill-will that the OpenOffice community accumulated over the years, due to mismanagement by Oracle. By the time it was donated to the ASF, maybe it was unwise to think that those dynamics could be changed, but it was worth it to try. Even so, the donation of OpenOffice to Apache, and the subsequent relicensing of that codebase to ALv2 was a MAJOR benefit for the entire OpenOffice eco-system, especially LibreOffice which, as soon as the ASF did the relicensing, consumed those changes to their benefit. Which is one benefit of permissive licenses in general.

I would encourage people to look at the (open and public) discussions when the incubation of OpenOffice was debated; I would also encourage people to read the tons of other communications about it as it progressed. Instead of having "nothing to say", as this clueless poster suggests, there is/was a LOT to say, which WAS said, and done so in an open, public, and transparent fashion. Maybe all that is uncomfortable for people to admit, since it goes against their misleading and incorrect narrative to paint the ASF and OpenOffice so negatively, and for this reason it is good when real journalists keep the facts straight.
The people who are "anti-socialism" see road building, national defense, and policing as "the government's job" and see healthcare and other social services as "not the government's job". Hence national defense is not considered socialist, whereas single-payer healthcare is considered socialist.

I get that you think this definition is wrong, but you're in the minority here. Both self-identified socialists and anti-socialists in the US consider social welfare programs to be socialist.

https://berniesanders.com/democratic-socialism-in-the-united...

"Social Security, which transformed life for the elderly in this country was “socialist.” The concept of the “minimum wage” was seen as a radical intrusion into the marketplace and was described as “socialist.” Unemployment insurance, abolishing child labor, the 40-hour work week, collective bargaining, strong banking regulations, deposit insurance, and job programs that put millions of people to work were all described, in one way or another, as “socialist.” Yet, these programs have become the fabric of our nation and the foundation of the middle class."
That doesn't really save you from typos
I think you're missing the point. Unix tools like `cut` are really effective ways to deal with plain text data, who cares if it's CSV.
> Why restrict yourself to Gazan software engineers?

Cause that's what I thought we were talking about?

https://electronicintifada.net/content/sodastream-treats-us-...
With scale its not about key exhustation, its the ability to be able to create a key in multiple servers without having to consult a central location.
This was probably the weakest suggestion in the article.

That said, the default SERIAL type in postgres is 32-bit signed integer so it can be surprising when you exceed 2B items.
Piazza insights 2016
I'm going to go against the JS ecosystem grain and say that boilerplates are a total anti-pattern. And not because you should be doing this stuff by hand either, which is probably the second most popular answer.

"Boilerplate" implies copying a bunch of code into your project that should be library code but isn't because it's too poorly designed to have an API cleaner than "just fork it, YOLO". It's dramatically harder to update than something with well-designed API boundaries.

Your web app really isn't a unique snowflake. Shared, standardized toolchains are harder to build but once you do they're a dramatically better long-term investment.

In Javascript it's really just ember-cli that operates this way, which started in the Ember community and has now also been adopted by Angular.
And 'npmjs.org' is misspelled as 'npmsjs.org' in the introduction. Nice.
It's autonomous but now the term "drone" is also becoming synonymous with consumer-grade "UAVs" which are controlled from the ground. Thus not autonomous. Thus while this is autonomous and does fit with the "drone" term in common parlance, it's also overlapping with the notion of "drone" that can be controlled from the ground.

I'd much prefer to just call it an "Unpiloted Passenger Vehicle" or "UPV" which only appears to be used by the Coast Guard as a term for "Uninspected Passenger Vessel" and could be reasonably co-opted.

Or "Autonomous Passenger Vehicle" which could apply to both flying and non-flying vehicles, of which both are seemingly in advanced development stages.
Yes, that kind. I have a cable modem router that has no buttons or controls on it whatsoever, separate from the pc, obviously. Then, I have the actual wireless router attached to that. I could have bought a single cable modem/wireless router. Regardless, depending upon the application there are essentially all one and the same in intent.
I agree that taking extremes is a useful tool, but this isn't the best example.

What if you took away 100% of people's time off? No weekends, no evenings? Nobody is coming back to that either.
And here's the related paper, "Unifying Count-Based Exploration and Intrinsic Motivation": https://arxiv.org/abs/1606.01868

Tech journalism isn't at its best when it can't distinguish between WOPR and a team of researchers.
The missing scruples are what make the people responsible for this valuable. You don't want someone who might have a moral crisis working on a product that can and will be easily wielded for abuse.
Not every action by a country must be taken by the government. Being un-American is in fact something that the government must tolerate under the First Amendment. However, if you believe that American culture and values creates a good society, and that freedom of speech is a cornerstone of that culture and values, then you can use your freedom of association to boycott Facebook for being un-American.
If you use the "suggestion" sorting, it will recommend some links it thinks you should look at again. It bases this on several factors, like the interest level, tags, creation date, last visited date, and last modified date. It does a lot of time decay. I'm still tuning the algorithm, so it should improve as time goes on.
Yea they could in multiple ways. They could sue to the troll for a declaratory judgement of invalidity and non infringement. Or they just indemnify their app stor developers for any patent liability caused by using their product.
> do data consistency in your code, moving data logic into solid models that are tested and versioned from day one

So your consistency check code is more reliable that that which has been built and tested over many years, people and projects?

And your code is guaranteed to be deployed into any project that need to access that database later?
In the same way police corruption would be fixed if the good eggs didn't protect the bad ones.
I come from an Asian country, we are used to bribes, crooked politicians, government workers etc etc.

To me the USA was the place where Neil Armstrong lived, it was the country that gave me so much that I was thankful for, it was a country where the words "Freedom of speech" ruled above everything. To me it was the country I wanted to be in if I had a wish.

Little by little, that idea I had of the united states is being changed, may be its my fault since I idealised the USA too much. May be its the news I read about, large scale surveillance, government officials who has no regard for civil liberties, people more powerful than the FBI, people above the law, power crazed security guards at airports etc etc.

I really really dislike this, wish I would once again get to believe that there is a place where people are treated right.
Thinking Machine 6: Play chess against a transparent intelligence
IMO normalizing up front is rarely ever a mistake. The primary advantage of normalization is it makes your schema amenable to changes in requirements. What if category ends up needing a description, and an id for a permalink-able page with links to each post in a category, etc.? Normalize up front and then denormalize where you need to when the requirements crystalize and your focus becomes responsiveness.
Isn't the difference there that in your example the person clearly did not intend to kill anyone?
Ok monopoly was absolutely the wrong characterization. They are a cartel. ("an association of manufacturers or suppliers with the purpose of maintaining prices at a high level and restricting competition.") Which is a difference of degree.

But your analogy doesn't make sense to me. There's not political or regulatory reason there exists one coffee shop.

And because of this fact, if they abuse their position as the sole coffee shop (raise prices, provide bad customer service, etc.) they will open themselves up to a challenge from another entrant into the (open and free) market.

This is exactly why taxis are a different beast. They are protected from competition. Explain to me how taxi cartels operate in a free market? Or conversely, if you agree that they don't, explain how coffee shops operate under the same conditions?
The LGPL thing is not really the issue here. It's how Trolltech/Nokia/Digia/QtCo approached the payment of a commercial license.

It's always been explained to me by the sales people that "you cannot switch licensing models mid-stream". So if you're planning to go commercial, you start commercial.

It's not really about closing the deal as much as making sure the Trolltech developers were paid during the time you needed their support.
Yes, it was harder than it probably should be but now that I've written a book
in it I've got it down by heart. Probably needs to be more prominent in the
docs:

# doc1, the destination

.. _introduction:

Introduction
---------------

asdf asdf…

Then in the source document:

# doc2, the source

In the :ref:`Intro <introduction>` or
simply :ref:`introduction`,
blah blah blah.

I made snippets in my editor to help with common tasks such as this.
Q&A with YC Partners
That's the kind of thing laymen always say. Whenever I read reports of what the social scientists say it sounds like intelligence testing is one of the few sub fields with consistently reproducible and meaningful results. Even in this short article they contradict your point by stating the military finds it correlates with success. The military filters out those with developmental disabilities.
If that was true, then QT would violate this principle itself and could not sell you a commercial license.
Yeah, the guide is kind of hidden away at https://mochimarks.com/info/api
Pension funds in many cases operate similarly; their finances improve if beneficiaries die early, and in some cases they are required to pay out surplus returns above a certain level. The difference seems to be that pensions operate continuously (ie, they'd only see a demographic effect on payouts if there were a global decline in life expectancy) rather than on a defined batch of customers.
Why not? Central repositories could require that all names are within a certain Levenshtein distance of one another.

This could get mildly annoying every once in a while when there are legitimate non-clashing names. A better metric/typo recognition technique is probably possible. Or else some manual process for requesting exceptions (maybe with a tiny fee to help fund the overall project) would also address this problem.

EDIT: Just downloaded and read the thesis abstract. The author actually suggests the first idea: "The analytical part generates ideas
for countermeasures that allow repository maintainers or users to detect typosquatting attacks
in the future. For this purpose potential typosquatting candidates could be generated for each
legitimate package name with the help of the Levenshtein distance algorithms or Bayesian
networks. Another option that can be considered is the Metaphone algorithm."
Neil Gaiman on “What is Genre?”
Actually, uuid4 as a pkey will cause pathological insertion performance on a b-tree since you are randomly inserting across the tree (having to constantly split pages) rather than appending to a far extent.

If you want to use uuids, uuid1 may be a better bet.
We've banned this account. Personal attacks, name-calling, and flamewars, all of which you've made an egregious hash of in this thread, are not allowed on Hacker News.

We detached this subthread from https://news.ycombinator.com/item?id=11861023 and marked it off-topic.
They are not a monopoly, you are correct. They are a cartel.
During the discussion of the security hole last year, you conspicuously had plenty of time to comment at length on how unfair it was for people to note Apache's utter inability to maintain a secure desktop application, as did several of Apache OpenOffice's alleged developers.

However, neither you nor they apparently had any time to fix the security hole. The fix being, literally: remove one file from the download. Well done.
> why would that be a reason to not use it?

Mostly because you can't expect many new features or the product evolving particularly fast. Which is exactly the case for Cloak -- the feature-set was basically frozen for years. It's not a crime: if a product works fine, why mess with it? But I wanted new stuff and it didn't feel like I'd ever get it.
Yeah. I think it's becoming a reflex for programmers when they get an import error like:

Error: Cannot find module 'x'

to quickly type:

npm install x
> In the thesis itself, several powerful methods to defend against typo squatting attacks are discussed. Therefore they are not included in this blog post.

http://incolumitas.com/data/thesis.pdf section 5 "Practical implications". Just wanted to point out that in case you skipped it it's worth a read, some interesting proposals there that are worth discussing with package manager maintainers.

I particularly like the preemptive approach of auto-blacklisting common typos by simply monitoring the number of times a specific unexisting package is requested over time (5.10). So if a lot of people regularly attempt to install the unexisting package "reqeusts", it could signal that it's a common typo and should be blacklisted to prevent malicious use in the future. False positives could always be sorted out manually by communicating with the package manager maintainers.
consuming
“The web is already decentralized,” Mr. Berners-Lee said.
“The problem is the dominance of one search engine, one
big social network, one Twitter for microblogging. We
don’t have a technology problem, we have a social
problem.”

One that can, perhaps, be solved by more technology.

This is a very confused article. It's a social problem! But we're going to solve it with technology!

I'm sure Tim Berners-Lee has a great understanding of the situation, but since it didn't come across in the article let's try to build our own description of the problem here in the comments. To do this we'll go through the most interesting projects in the "fix the web" space and steal their key insights.

# Camlistore - All Your Data Should Be in One Place

I probably have important data in two dozen different places. Google, FB, Dropbox, Reddit, GitHub, Mint, Stack Exchange, Amazon, etc. This is crazy!

All my personal data should go into a personal data store. I'm not sure how we'll ever approach a sane system without this step. Camlistore is all about making that data store.

More info here:

https://camlistore.org/doc/overview
" Camlistore is your personal storage system for life. "

# Urbit - Everyone Should Have a Name

Right now only techies own their names. We do it in two ways -- the total ownership way where we make a private key and identify ourselves with it, and the "technically renting but basically ownership" way where we buy a domain. You can reach me at <myname>@<mydomain> today, tomorrow, and probably for the rest of my life.

Most non-techies get by with Gmail and a FB page. This isn't the worst, but it's not ideal.

And for every different service we use we get a different name. I don't want 20 names! I want to use my name! (Or sometimes one of my pseudonyms, which Urbit has first-class support for).

In Urbit everyone has a name[1]. Even better, this name maps to their computer, so if I know my friends name I can connect to their computer -- the foundation of getting an actual peer-to-peer network back from the current mess.

[1] Connected to a private key and human readable! But often silly, eg: ~gumdob-tumlub

# Sandstorm - Everyone Needs a Server

Servers are necessary to be real internet citizens. I think this is basically self-explanatory. If your entire internet presence disappears when you close your laptop lid you're basically beyond helping, and will always need some kind of walled-garden to watch out for you.

The problem is that Linux servers are a pain to host. With Sandstorm you can set up a server with one click. You can install apps with one click. This is . . . basically such an obviously good idea it's hard to find more to say about it.

If there are more interesting projects in this space please mention them, I'm going back to coding:)

EDIT: I wasn't really sure what to write for a conclusion, but now I've thought of one: The web evolved, what we get next will be _built_. This is very exciting.
You make a good point. If we were to understand how intelligence works and if it were to be heritable, it may be possible to ensure that everyone had some baseline of intelligence. That may be beneficial.

Maybe I've lived in the United States for too long, but it seems inevitable to me that we'll end up with a tiered system. Perhaps there will be some baseline intelligence level everyone is entitled to, but the very wealthy will surely be able to pay for even more intelligence. Likewise, if intelligence was this well understood, a measure would be applied to everyone. Perhaps it would be like your credit rating and this could easily be used to discriminate in a wide variety of ways.

IMHO, some people like to box others off and say: these are lesser than me. Should science support this opinion, this will only encourage the behavior. To me, this is the basis of the argument we're seeing on this post. Some see intelligence as heritable and, inevitably, somehow favoring one or more ethnic backgrounds.

In terms of the "just feels right", I think that the science on this issue is less than clear. Some things point towards heritability, others do not. The idea that some ethnic backgrounds may engender more intelligence than others is to me an idea so poisonous that I simply reject it on moral grounds.
Just because the garbage collector is optional and the slightly higher emphasis on performance. Also the way it compiles to C. I have using Nim to program a microcontroller on my todo list but I'm not sure how I'd go about doing that in Go. It's weird though because Nim is certainly more expressive than Go is and usually that goes with being higher level.
> I actually see more socialists trying to claim that the capitalist economies of the Western Civilization socialist than anyone else.

That's because socialists (who, after all, are the heirs to the tradition that invented the term "capitalism" to refer to the then-dominant system in the developed world of the late 19th Century that they were criticizing) are more likely to recognize that the so-called "capitalist" societies of Western Europe (and even, though less so, the United States) are quite far from the system that "capitalism" was coined to refer to, specifically as a result of reforms to the system designed to address the same problems with it that were identified by 19th Century socialists (and, often, reforms specifically championed by socialists, though often watered down somewhat.)

The now-dominant system in the developed world -- the modern mixed economy -- has a lot in common with capitalism, but it also has a lot of elements of socialism. Its at least as wrong to call it the former as it is to call it the latter (especially since socialism has been, stretching back to its origins, often seen as an evolutionary step building on the experience of capitalism, not a diametrically opposed system, even if the proponents of the two systems would end up politically opposed.)
> "using serializable in their systems is the ability to enforce arbitrary constraints under parallelism"

That's a funny way to say that. :-) Because what it really means is, "wanting to enforce a total lack of parallelism when under parallelism." I mean I get what you're saying, it was just funny to read.