skysight-inc/HackerNews huggingface dataset:
Does anyone else find it strange that threads on Mozilla articles submitted to HN are filled with privacy-absolutists while articles about Google/Chromium are disproportionately commented on by Google apologists?

Are there two radically divergent subsets of HN users who hardly comment on articles about the other major browser?
Use and share your clipboard in the cli by simply piping to and from it
Perhaps that's due to my terrible English... However I see few "downvote trends" not against me but against certain "families of arguments", normally without zero accompany comments to explain why, counterargument etc

Perhaps it can be a nice analysis to made on whole HN comments to "track" the trend and discover why...
Germany has a good rate.

My cable provider uses IPv6.

But yes. When I did an internship in 2001 my co-workers told me that I had to learn IPv6 because it will replace v4 in the next years, hehe.
Several ways to get noticed in the application process:
* Go to Kaggle and participate in some of their competitions. * Build an ML program from the ground up to help build your portfolio (something like a dog door that only opens to your dog).
* Implement a paper from arxiv - try to understand what the paper is about, then download the data set and implement the model they are talking about and see if you get similar results. Then, write a blog post about what you did....
it was the LICENSE file at the top level of the source archive. if that didn't apply to the whole of the source archive then it should have specified that.

it could of course be that the source archive is not complete and there are non-free dependencies, or that there are exceptions in some subdirectories

EDIT: the README contains this:

Use of original work by Vivaldi Technologies contained in this source code package is governed by a BSD-style license that can be found in the LICENSE file. Other works are governed by their original licensing terms.

those other works are chromium and a few other things, all on FOSS licenses. there is also no mention of other dependencies.
1. my objection was to it being opt-out. "Turn it off" is not a valid solution to that. I'm wondering if you read my comment fully?

And it's not just me. You're saying that Mozilla is expecting all users to opt-out to protect themselves... from Mozilla itself. By Mozilla claims to be protecting those users...

2. you say it's not the antithesis of what they stand for but you've given no reasoning. Why is Mozilla compiling a personal profile of my browsing preferences not the antithesis of what they stand for? What have I said that isn't in line with the technicalities of how Pocket works? Does Pocket not compile a personal profile of my browsing preferences?

I'm sorry, I normally try to avoid combative tone on hn, but you've written quite a substantive comment all of which simply states that the points in my comment are incorrect with no reasoning behind those statements. It's not really logically cohesive...
I assume they're referring to the 3-month certificate lifetimes, which all but force you to automate certificate renewal, whereas the 1+-year certificates of the past let you treat it as manual sysadmin work. This was based on a belief that automating certificate renewals is the right thing to do.

Still, LE seems to be wildly more successful than IPv6. I suspect in part that's because they were more technically right - or at least it's more feasible to add the automation than to rearchitect an IPv4 network - and in part because you can do manual certificate updates. (For complicated and entirely uninteresting reasons, I do manual certificate updates on my personal website every three months using certbot certonly --manual and scp, and it works.)

I'm also way more personally sympathetic to LE because they're pushing the change for security reasons (revocation doesn't work, so we need to move to very short-lived certs) and not mere elegance ones. Rolling out IPv6 as designed brings no security benefits either to the user or to the ecosystem, and carries quite a few potential security risks.
This is mostly a whiny article followed by an ad for the author's site which starts by wanting either your email or your money.

There are better advocates for stronger privacy. A good starting position is that the US needs something as strong as the EU's GDPR. With teeth. Might happen. See this Register article.[1]

We need a good event involving the privacy of some political official, preferably one on the right. The US got the Video Rental Privacy Act because Robert Bork's porno videotape rentals became public knowledge. Although that was weakened in 2013 due to Netflix lobbying.

[1] https://www.theregister.co.uk/2018/11/08/gdpr_usa_congressma...
Understanding the memcached Source Code
Looks like a scam. See their posting in the parallel thread https://news.ycombinator.com/item?id=18814051
Really nice work, and thank you for sharing! The attention to detail especially in Part II is inspiring!

I absolutely loved the tint change based on the view behind. That's the kind of extra care that makes a UI subtly feel completely natural and pleasant to use, even if it never consciously registers. (In fact, not consciously registering is probably part of the magic.)
With IPv6, there are mismatched incentives. There are parties that would have to do the investments and another parties would benefit.

For ISPs, it means investments with no benefits. They do it only once their CGNAT is too overloaded or on other sign of running out of IPv4. When they do it, in the simplest and cheapest way possible, which the informed customers see as worse service, so naturally they want to avoid it.

IPv6 would help network application developers, so they could do more or do what they do now with less, but they have no impact on investments ISPs would have to do.

Then there are parties, that have working IPv4 infrastructure, feel no pressure caused by lack of IPv4, and migration would mean just expenses with zero benefits. Exactly like companies that ran login forms over http, up until browsers started to warn users. That was the incentive, that caused them to switch to https.
> considering the problem is to fit the reals into 64/32/16 bits and have fast math

Floating-point numbers (and IEEE-754 in particular) are a good solution to this problem, but is it the right problem?

I think the "minimum of surprises" part isn't true. Many programmers develop incorrect mental models when starting to program, and get no feedback to correct them until much later (when they get surprised).

It is true that for the problem you mentioned, IEEE 754 is a good tradeoff (though Gustafson has some interesting ideas with “unums”: https://web.stanford.edu/class/ee380/Abstracts/170201-slides... / http://johngustafson.net/unums.html / https://en.wikipedia.org/w/index.php?title=Unum_(number_form... ). But many programmers do not realize how they are approximating, and the "fixed number of bits" may not be a strict requirement in many cases. (For example, languages that have arbitrary precision integers by default don't seem to suffer for it overall, relative to those that have 32-bit or 64-bit integers.)

Even without moving away from the IEEE-754 standard, there are ways languages could be designed to minimize surprises. A couple of crazy ideas: Imagine if typing the literal 0.1 into a program gave an error or warning saying it cannot be represented exactly and has been approximated to 0.100000000000000005551, and one had to type "~0.1" or "nearest(0.1)" or add something at the top of the program to suppress such errors/warnings. At a very slight cost, one gives more feedback to the user to either fix their mental model or switch to a more appropriate type for their application. Similarly if the default print/to-string on a float showed ranges (e.g. printing the single-precision float corresponding to 0.1, namely 0.100000001490116119385, would show "between 0.09999999776482582 and 0.10000000521540642" or whatever) and one had to do an extra step or add something to the top of the program to get the shortest approximation ("0.1").
Government employees aren't spending their own money. If you want to split hairs, we can say those employees spend "other entities money" instead of "other people's money", but the entire core of the points made remains. Similar problems of waste can happen with large corporations. (The smaller the company, the more likely such waste will actually impact your own paycheck, and the more market forces will make such waste painful.)

"Taxpayer's money" is useful rhetorical shorthand to remind people that creating government money requires either increasing taxes (taking money from taxpayers), printing more money ("taxing" holders of the currency through inflation), etcetera.

We have the notion of "for the people, by the people" - that the government should act in the interests of it's citizenry ("taxpayers", if sometimes quite indirectly), that the money should be spend wisely instead of wasted - both in the moral duty sense, and sometimes in the legal duty sense as well.

Can you give an example of a legal and moral use of government funds that doesn't benefit taxpayers or citizens? The closest I can come up with is foreign aid and other outwardly focused actions, which still aim to "benefit" the local citizenry through warm and fuzzy feelings, better international relationships, better access to oil and foreign markets, etc...
The US definitely has a problem with terror campaigns. But yes, I really really dislike it when media and general people start thinking the president is a king or something. I actually wish the media would lay off treating the president like royalty. I personally believe we need to get rid of the white house and treat the president more like we do the speaker of the house. More like a regular person that has a specific role.
Our health insurance system is inefficient, and some of that inefficiency does come from the way employer-provided private health insurance works. My point though is that the numbers suggest that there are larger structural factors that operate independently of that inefficiency.

It's possible that the pathologies of our system created those other structural flaws; like, if we had an NHS instead of private insurers, we wouldn't have built all these inefficient hospitals. But whatever the cause, we are where we are, and switching to single payer won't undo those problems.

Which sums up my concern about single-payer: it might be a good way to lock in a lot of structural problems for a long time. Meanwhile, if you just directly address the problems themselves --- stabilize the markets, enact strong price transparency rules, aggressively incentivize efficiency --- you might not need single-payer (an immense, disruptive change) in the first place.

Also, if we want cost outcomes approaching that of the NHS, we have to do more than simply enact single-payer. We also have to aggressively set rates, reduce compensation for doctors, fire a lot of nurses, and make people wait years for knee surgery.
Looks like a scam by "Jessica". See their posting the parallel thread https://news.ycombinator.com/item?id=18831711
You remind me of a business trip to Italy some 25 years ago, when I visited a factory outside Florence and was shocked to see small bottles of wine served in the employee lunchroom for the mid-day meal. I don't know if this practice is still common in Italy or other parts of Europe, but the thing that amazed me was that the plant was industrial, and most of the employees left the lunchroom and went back to operating moving machinery.
They want to donate to the general public not the government.
reddit slowly infecting HN
The Wisdom Hierarchy and Many-Model Thinking
I found that often when you want clean deep cloning of objects (e.g. for state data) and when you’re in control of creating the objects it’s better to build them out of Map and Array instances instead of the builtin object type. We use this extensively for config structures and state data, and it makes cloning or merging objects much easier (as you only need to differentiate between a map, array and everything else). This assumes that you will not clone any of the “object” types in your data structure though, so you might want to store immutable data types on there only (which often is possible and advisable for config and state data though). The downside is that the syntax for creating and working with maps is quite ugly (IMHO), I hope they will improve this in a future version of JS.
This is somewhat outdated.

Docker for Mac uses a relatively lightweight and largely-invisible virtualization layer now.
The general problem with this kind of criticism is that it can be leveled at any article citing a statistic.

No matter what value an article chooses to highlight they could have highlighted a different one. True... but so what?

Here I guess the root of your objection is that the article seems to conflate the ocean-sides with the entire ocean. That's fair: the article is really about ocean sides, but in a few places it refers generally to the ocean. It appears to be purposeful, too, since it's in the headline and lede while the rest of article is straight. Still, that the headline and lede is overly strong is, unfortunately, almost a universally applicable criticism these days. Headlines and ledes are written for attention-grabbing not accuracy. That's a problem not of individual articles, but of a system that lives on click-through.

A less superficial criticism would be to examine the degree to which the main point of the article -- that cigarette butt pollution is a problem that should be addressed -- is fair, or whether it's making this out to be a significantly more substantial problem than it really is. (Remember, the context here is activism to reduce pollution, where there was recently a lot of focus and traction on plastic drinking straws, for which there was some backlash, with people arguing that there was a lot of focus on a tiny part of the problem. So a really good question here is, is this just more plastic straw BS or is there a really issue here?)

And keep in mind that if cigarette butts are a coastal pollution problem it doesn't mean something else, like fishing nets in the ocean, isn't a problem.
This is awesome! I use pgcli everyday and love it so much. This is gonna be a great addition to my SQLite toolbelt!
What? How does one donate to the general public via tax receipts?
Imho IPV6 failed because of a failure to make DNS usable to non-specialists.

If every device on every network could be assigned a domain name, then we'd never have to know what underlying addressing scheme exists.

My ISP has a name. I have an account with them. Every device on my network has a name.

There's no good reason I don't have

Device.accountName.pub.ispName.tld

Bound to the phone I'm writing this on right now.

But because that doesn't exist, users are still used to screwing with MAC and IP addresses just to set up port forwarding and all that other nonsense.

And so we have to care about IP addresses. And so we're stuck on ipv4.
You would not be allowed to do any of this if you worked on my team. Do not put documentation in code, put it in documentation. Comments break up code, constantly flipping between reading the language and reading English.

Comments are failures on the part of the programmer to describe the implementation clearly in the language being used. The lesson you should have learned is to recognize that it's okay to fail in this way, but to still consider it a failure.
I understand that. Those features are not useful at all to me, that's why I said "my" data.
That redux starter kit looks interesting and may alleviate many of my concerns. I don't know if it will eliminate them, but thanks a lot for that.

[...edit...] Unfortunately, it looks brilliant with stuff like createSlice(), but it doesn't quite go far enough. If I have to deal with "action" and "payload" stuff then I am already polluting my code too much with stuff that I want to keep hidden in the machinery. My reducer functions should receive their actual parameters, not an "action" that they need to destructure into the actual parameters. And calling the actions in the slices should also wrap the store.dispatch() inside them. Ahhh feels so close to the ideal...
I can imagine some cypherpunks in this sci-fi world creating a crypto-system where the keying data is sent as media files (possibly requiring a new movie studio to be created as a cover story).

Unfortunately I can also imagine that the NSA give themselves backdoors that can even get past the legally-mandated DRM, and the media industries would accept this.
The DRM and unskippable portions were the same for DVDs when they launched and yet they were a bigger success in an equal timeframe. I do not think that most consumers care enough about these two points to actually influence their decisionmaking.

I'd be more interested in how the HD DVD as a very visible competitor blocked BluRay adoption because of consumers wanting to wait for a winner in that war.
If pay more in taxes then you end up paying less. If nothing else the government needs to borrow less money and thus pay less interest. Right now every year on average American taxpayer pays an extra ~3,000$ in taxes covering interest.

Changing the tax code is about who plays, it has ~zero impact on how much the government spends.
Ask HN: What is the earliest model ThinkPad that can drive a 4K monitor?
There's ungoogled-chromium, with every single telemetry code path patched out.
I'm happy that 23andMe is using my data for drug research.
I don't want companies to read my private messages, but drug companies are trying to fix things in me, and ask for a lot of money in return, which is more fair than what many other companies are doing.
This is also not perfect, as for example those with autoimmune conditions will not always work and can actually get worse under immunotherapy. My wife has stage 4 lung cancer due to Scleroderma immunosuppression medication and is struggling with the treatments due to the reactions ( immune system attacking non cancer cells ).
I often wonder the same thing.

Except that I'm envious of both their wealth of time, and ability; rather than dismissive of their desire to understand technology at its fundamental level.
The FSF used to use the term "semifree software" for this kind of thing, but they now prefer to just go with non-free ( https://www.gnu.org/philosophy/categories.en.html )
This is technically true but in practice Docker for Mac hides this from you and does not require a prohibitive amount of memory. 99% of the developers at my company have 16gb MBPs and we all build multiple Docker containers daily.
And for Apple, it just so happens that the market segment that likes touch-driven UI as their primary interface is as large or larger than those who like keyboard/mouse. Making mobile devices the computer for the masses widens the divide between users and developers.
This particular straw man argument comes up every time taxes are discussed.

Obviously the marginal effect of one person paying more in taxes is close to zero. There's no hypocrisy in advocating the group pay more collectively without unilaterally taking it upon oneself first.
The other side of the coin could be equally terrible though. No government employee regulates anything because their personal bank account can’t handle it.
>Commercialization of my data without consent or compensation is my fear.

I agree sort of, but how interesting is it that many people seem to really care when it’s their immutable genetic information to 23&Me - but when it’s their habitual and social information to Google or Facebook they seem care a lot less.
Comments are for when you do something that looks obviously stupid, and you need to justify your failure.

Way too many people here are confusing comments with documentation.
I understand your sentiment,and I doubt I could make the time to do this kind of exploration myself....but, and I don't think this is why they do it- I can imagine this skill could be quite valuable when someone had some data they absolutely have to get, and it is on an old set of floppies.
Would it be possible to embed an rf (or otherwise) ID into every single piece of non organic matter?

Some kind of code that gets assigned to you when you buy the items. And if those items are found in nature, then you are fined.

Possible?
I meant 3.1 Gen1 & Gen2, sorry, as mentioned by jwr.
DVD quality may be worse than you remember. The difference is really very clear on modern HD screens.
I would use FF if they had a decent Mac app. Still no TouchBar support, weak cpu and ram management, no native zoom like chrome implemented
Right now, millionaires and billionaires are building luxury bomb shelters and private islands, high end sanctuaries for the end of days.

Ouch.
It’s the data that is on them.
Life expectancy from the World Bank, 2016:

Norway: 82.51

Italy: 82.54

I doubt the difference is much from longer Italian lunches, but the same cultural differences may well be responsible for both longer lunches and higher life expectancy.
I'd strongly consider it, if any of the people in this comment section worked for me...
The obvious approach would be to generate adversarial examples.

https://blog.openai.com/adversarial-example-research/
Thanks for explaining, and I really don't mean to kick you while you're down here, but even if butts did degrade in 2 years, that means they're lying around a long time for birds or animals to eat or choke on them.
A successful solution would have pissed a lot of people off. Every faction that had just one little enhancement, that could by itself probably have been okay, would have to have been told no. That's a hard thing to do.

Sometimes you have to say "yes" to one powerful faction, regardless of whether their request is technically a great idea, in order to get enough political capital to fend off everyone else.
Apple's fineprint of disallowing third party app stores, and apps that directly compete with Apple's, needs to be litigated in court.

Clearly, in paid mobile apps, Apple's market share is 66% of the $40B market. The shtick of cowering behind unit sales to argue that the "app store" is not a separate business category, but merely an extension of iPhone unit sales, thereby avoiding monopoly regulation, has run its course.

AND, the restrictions placed by Apple further prevent a cross-platform app store to exist, reinforcing their monopoly, artificially linking OS to app store
I think it's helpful to know where our technology came from for multiple reasons. (It's also fun learning to me, too.)

Knowing what came before makes us better at building new (or, even better, recognizing that we might not need to build new). Our creations would frequently benefit from application of knowledge about the analogous systems that came before. There's nothing new under the sun. There is valuable analogy hiding in so many past technologies.

I want to know about trade-offs made during design, how that influenced implementation, and the lessons that were learned when the technology actually made it (or didn't make it) into use. Decisions made so many years ago shaped the technology we use today (von Neumann vs. Harvard architecture, the minutiae of compatibility in x86 and the IBM PC that dates back all the way to the early Intel 8-bit CPUs the IBM 5150, etc).

I think software, hardware, and protocol "archaeology" are going to become more necessary as more of the people who implemented early systems that are still in use today die. So, besides being interesting, I think there's a marketable skill in the act of being able to build understanding of past technology.
It's about dosage. 5 mg of amphetamines is really just a bit a boost. Of course if you start cutting lines and snort them to keep awake and dancing until noon the next day, it's a different story.
Understanding the BeagleBone’s built in microcontrollers (2016)
It's a great point about web first. As a side note, there's really no point to a college degree anymore for most people. You don't need a Stanford degree to make a leisure product.