skysight-inc/HackerNews huggingface dataset:
That's exactly what I'm saying. I recognize it's not practical, but that doesn't mean I'm going to change the criterion -- it's also why I chose not to upload data to 23andMe.

In Google and everyone else's case, I would argue it's a bit different. Google remunerates me with the best search engine in the world, excellent free email, etc. Other services improve the product, which I (generally) reap the benefits of.

On the other hand, your genetics are what they are -- I don't believe 23andMe is sending every participant a coupon for this new drug, although I might be wrong. Instead, all you get is a small sample of the 600k SNPs available, some shaky genetic inferences, and tabloid level ethnic data. You give up valuable data with huge upside for analysis of questionable integrity and limited actionability.
We can do that some places where it's an issue (bed, for example) but other places like cabinets that's not possible. The house I'm in now has foundation issues (it's a lease), so in spots it won't get under the cabinets, but a couple of feet down it gets wedged in as the height varies by a few millimeters.
compare memory / callcounts / time spent with thunking turned on vs. off would give a good idea of it.

i can say for my side of things thunking is a super huge performance gain as it allows for quick gathering of expression intent and then the computation side on the other side of a cache.
Well, he says

> It was always more of a buzzword than anything else, I feel, and the licensing issues just make it a non-starter for me.

So presumably the licensing problem mentioned by your parent's comment is weighing heavily here. I think this "don't use ZFS" statement is most accurately targeted at distro maintainers. Anyone not actually redistributing Linux and ZFS in a way that would (maybe) violate the GPL is not at any risk. That means even large enterprises can get away with using ZoL.
I think it is besides the point for the risks of merging anything into Linux. He's right on that topic of course.

But it is a separate point he made about using zfs in general, and it's certainly not correct if you take one look at the activity in the zfsonlinux project on GitHub.
This study suggests that from DNA evidence that natural human lifespan is 38 years old, the same age that was the life expectancy during Wunderlich's 1851 survey.

https://elifesciences.org/articles/49555

Additionally, our heating systems were vastly less sophisticated, and we were outdoors more.

Together I think that these suggest that we get a sort of genetic gift of our bodies in our prime, but the growth program kind of peters out in our late 30's. After that it's a genetic maintenance program, with which, in concert with modern society, we have a good chance to keep the machine going for quite a long time.
yeah, it would actually decrease the number of employees if employee cost is significant enough to not be absorbed by raising the price. It might also decrease it by forcing a robustness check on existing businesses. A lot of them manage but couldn't absorb a financial hit; this would be a minor crisis but one that could just push marginal businesses over the edge.
Or take both like I do. Berberine is not as effective as metformin, but every bit helps when lowering blood sugar levels go.
Why should there ever be a just and equitable society? If there never will be one, a safe space is not a substitute but your best option.
I agree, there should be a legislative intervention here. These devices come out semi-regularly with no regard to security.
Your confusion is around where the end is in this case. E2E would be encryption from the ring device to your other device being used to view the feed (your cellphone for instance). Part of the difficulty in that case is getting the encryption key securely transferred between the two devices without exposing it to anyone else (a non-trivial problem). Assuming that was done in this case Ring employees would only have access to the encrypted videos with no access to the decryption keys to actually view them.

E2E Encryption is usually referenced in messaging applications where the ends are understood to be the two communicating parties, while in this scenario it's a little more nebulous.
If it is taking you 20 minutes to go a dozen blocks on a motorized scooter then maybe it is the wrong tool for the job.
I went on a similar journey but for OpenID Connect. While the spec is fantastic https://openid.net/specs/openid-connect-core-1_0.html#Overvi..., I found the same thing to be true - very little explanation of why. For example, it's very clear how each flow works and therefore how to implement, but not clear why there are so many of them. While researching and building my own implementation I eventually ran into IdentityServer3 https://identityserver.github.io/Documentation/ which had a nice intro video explaining things clearly. I also quit building my own at that point, since their offering is very well done and using the same stack as the rest of our software. I wouldn't say the docs are a good resource, but they helped a bit. There's also a version 4 now, though the documentation looks about the same.

Also not a good resource, but acceptable: Pluralsight. There is one straight up OAuth course to go over all the basics and then quite a few language/framework specific ones, e.g. how to implement OAuth in Node/ASP.NET/etc. The OAuth course was dry but had some decent information - but I did quit halfway through it because of IdentityServer, so take that with a grain of salt.

And yes, it sure does feel more complicated than it has any right to be. There's a good read here https://hueniverse.com/oauth-2-0-and-the-road-to-hell-8eec45... by the once-lead-author.

I really do recommend checking out IdentityServer4 though, unless you're implementing this specifically to learn / have fun / etc. And if you don't care for the Microsoft ecosystem, I've heard nice things about Hydra https://github.com/ory/hydra which is a similar Go offering.
> allows for "any modification of the source code that is contributed back to an open source fork to then be reapplied to the proprietary product."

That’s not an additional permission. That is granting yourself a right; i.e. a requirement imposed (on the legal author of the contribution) to give you this permission.

> Do you disagree?

Yes, I disagree. The author of a patch owns the copyright on that patch. You can’t reasonably believe that requiring this author to give you permission to do something constitutes an “additional permission” which you are giving to that author. It is obviously a restriction imposed on that author, since they would not otherwise be required to give you this permission.

A “permission” can only be something which you grant someone which 1. You are in a position to grant and 2. They would otherwise be not permitted to do. In the case of a software license like the AGPL, you the copyright holder have the sole right to copy the software. The license you give to others to copy the software under certain conditions is a thing which they would not otherwise be permitted to do under copyright law. Therefore, this “permission” that you want to give yourself, regarding copying the code authored by other people, does not qualify as such, since you are not in a position to give this permission, since you do not hold the copyright to the patch.

> From a principle perspective, I think as long as developers know up front (based on the licensing) that when they contribute code to and open source project that the code could be incorporated back into the original product, then they would be okay with that.

Maybe, but you’d have to find some legal way to accomplish this.

> As I'm writing this, I had the thought that perhaps a simpler approach is simply to just open source it as AGPL from the beginning with the additional restriction to remove the Plyint trademarks from the code. That is fairly clearly spelled out in section 7 as a valid additional term.

Oh, I agree completely. This would probably be the best for all involved.
Amazon Takes a Swipe at Paypal's $4B Acquisition
Considering the amount of people that end up with medical issues because they can't afford basic medication, I'd say no.

We're overmedicated in opiates because of the corrupt drug industry and corporations pushing pills for profit (see: the various articles and stories detailing the rampant corruption behind Purdue) and likely undermedicated in everything else.
I was going through boxes of old CDs and DVDs the other day and throwing out a lot of crap, I found my old BeOS5 disk. Didn't throw out that one. I really enjoyed using that OS back in 2000.
We have a newer one that returns to base to recharge, and it seems to do well about knowing when to "return home"
"Don't use ZFS. It's that simple. It was always more of a buzzword than anything else, I feel, and the licensing issues just make it a non-starter for me."

When he says that, I think on the $500 million Sun spent on advertising java.
GP is refuting the idea that public transit is inherently the slowest mode of transportation by providing an instructive counter-example. If the vast majority of the population cannot relate, that's a product of policy choices that favor sparse development in most of the country.
quite a few Canadians, as reported by NPR
https://www.npr.org/2020/01/09/794863678/we-will-surely-find...
Yep that's me :) The Bao project evolved into BLAKE3, and the latest version -- which I literally just released -- is now based on BLAKE3.
It looks like the speedup is coming from two main changes.

The first change is reducing the number of rounds from 10 to 7. Think of it like making a smoothie - you add bits of fruit to the drink (the input data), then pulse the blades to blend it up (making the output hash). This change basically runs the blades for 7 seconds instead of 10 seconds each time they add fruit. They cite evidence that the extra 3 seconds aren't doing much - once the fruit's fully liquid, extra blending doesn't help - but I worry that this reduces the security margin. Maybe those extra 3 rounds aren't useful against current attacks, but they may be useful against unknown future attacks.

The other change they make is to break the input into 1KiB chunks, then hash each chunk independently. Finally, they combine the individual chunk hashes into a single big hash using a binary tree. The benefit is that if you have 4KiB of data, you can use 4-way SIMD instructions to process all four chunks simultaneously. The more data you have, the more parallelism you can unlock, unlike traditional hash functions that process everything sequentially. On the flip side, modern SIMD instructions can handle 2 x 32-bit instructions just as fast as 1 x 64-bit instructions, so building the algorithm out of 32-bit arithmetic doesn't cost anything, but gives a big boost to low-end 32-bit CPU's that struggle with 64-bit arithmetic. The tree structure is a big win overall.
What about people who lose their jobs or don't get hired in the first place?
New US building codes will make every home ready for electric cars
Thank you for the nice feedback, much appreciated!

> Ad using native bookmark sources, such as HN/Twitter/...

You are right, this is not ideal and it also happens to me that I am no longer sure where to look first. On the plus side, I do find it eventually, even if it's only the second native source I check. Atm, it seems to me that this is still better than duplicating everything in my other bookmarking layers. I will read your posts to find out more about your system, honestly don't know much about org-mode yet.

PS: Very glad to hear that! Especially, since I don't do much frontend work usually. I will think of a way to include a ToC also on small screens. Please, feel free to steal any idea you like. Then I don't have to feel as bad for looking into some of yours. I really like the pilcrows next to the headings and the dotted lines for highlighting sections on your site.
Even if you make an apples to apples comparison (cost of renting a scooter vs cost of buying one outright), renting doesn't really make sense if it's something you want to use regularly.

For a 10 minute commute daily commute, the break even point for buying a scooter vs renting one comes in less than 60 days.
Thank you. Could you box up my discounted dopamine hit for carry-out, please? I might need some smug satisfaction later, possibly while driving, when it's not so easy to go online.
Unicode (1987-1991) predates URLs (1990-1994) but not DNS (1983)
I think a max wage totally makes sense, because nobody is more than a modest constant times more productive than anyone else, and anything created by a person is always built on existing knowledge and constructs created by society. Also, risk does not really exist anymore these days (with minimum wages, financial constructs around bankruptcy, etc.)
OpenJDK is on pretty solid legal ground, no?
I'm 52, not 36 however.
1) Think about who your customer base is.

2) Figure out where those people would be found.

3) Purchase ads there.
> "do the minimum and be rewarded?"

In my experience, the lower you are paid, the harder you are worked. Cooks, janitors, sanitation workers, mail(wo)men and amazon delivery workers, waiters, teachers, mechanics, construction workers, etc. all work longer hours in more emotionally and/or physically taxing jobs, with worse pay and work environments than any dentist, accountant, lawyer, CEO, sales person, or software engineer that I have ever met.

Wages are inversely correlated with how hard you actually have to work, perversely
Sorry, I meant the iMac (G3) in 1998 - maybe it's not the best pic then since it's an eMac that came later...

The iPod was 2001, 3 years after the first iMac.
It is because condition variables have no state, i.e. calling signal without waiters is equivalent to doing nothing and does not affect a future wait. The concern is that a thread is switched out after it checks the condition but before it calls wait, and in that moment the condition variable is signaled. The thread then calls wait and is not awoken (potentially never to be awoken). If the predicate is not altered without the mutex and the waiting thread has the mutex at the time it checks the predicate (this latter part is a must in all cases), then it is guaranteed the predicate will remain unmet at least until the thread has switched to a waiting state.

So simply using an atomic (even with a full release-acquire memory barrier) is not necessarily sufficient as that would only enforce the coherence but not prevent the scheduler from interrupting at the wrong moment.
>Has Linus not seen the work that the OpenZFS folks are doing?

That's what he meant by Oracle licensing issues. Java API infringement case against Google
An O/B system is a way to:

1. eliminate double frees
2. eliminate use-after-free
3. eliminate memory leaks
4. using undefined pointers

when using explicit memory management like malloc/free. Any D application, including DasBetterC, that uses explicit memory management can benefit from it.
For what? It's under the CDDL.
> Personally speaking, open sourcing something with no intention of responding to interested developers doesn't feel right.

Everyone is different :)

> When you open source though, aren't you making it significantly easier for people to build a product better than yours?

If the only benefit from you and a competitor is a particular feature or something else that you gain from proprietary code, you're gonna lose eventually anyway. You need something stronger if you are to survive. There needs to be something more between you and your competitors than something that can be easily copied (like most features in most products).

Some companies focuses on integrations/synergy (like Apple, easier the more stuff from them you have) while others on other things.
He also feels ZFS "was always more of a buzzword than anything else". Yikes.
Same, for at least 6 years in a 4 drive zraid array. It always reads and writes at full gigabit ethernet speeds and I haven't had any downtime other than maintaining FreeBSD updates which are trivial even when going from 10.x to 11 to 12.
Wait...did it throw an exception, yet still add the item to the list?

EDIT: Tried it myself. Sure enough, it throws the exception, but still adds the item. This seems like a bug.

EDIT Part 2: I understand now. `a[0] += [1]` is internally translated to `a[0] = a[0].__iadd__([1])`. The right-hand side is interpreted, mutating a[0] in-place as expected. But then the re-assignment happens, which throws the exception since you're trying to re-assign a value in a tuple, which is immutable.
My concern in these services is, at what point in the future does your DNA get weaponized against you? When do you get declined for health insurance, or have jacked up premiums, because the insurance company bought a report from 23andMe that says you have a predisposition to expensive disease?

My DNA isn't a secret, but I don't yet feel comfortable voluntarily handing it over to be indexed by a for profit company that has little to no regulation over what they can do with it.
Better link
https://news.ycombinator.com/item?id=22003315
The article is talking specifically about performing convolutions on higher dimensional manifolds. This is different from the more broad concept of data dimensionality typically associated with AI/ML.

Without repeating the article too much, this is important because it can be used to learn very complex systems from a series of lower dimensional projections. Such as, creating a 3d map of a dog from a collection of 2d images of dogs. The resulting system can better detect a dog in a position it's never seen because the CNN has built into it the relationship between 3d space and the 2d representation of that space.
I think there was some token POSIX compatibility in Windows NT back then. Probably for some government contracts.
I'd like to see a model like that adapted for vaccinations. So you can easily see the risk (for infants/elderly) dramatically increase as vaccination rates decrease a tiny bit.
I feel like modern OS's are in some(several?) ways, worse than these classic OS's... They just assume too much, impose too much, hide too much etc...
Is Entrepreneur Born or Made?
Do I want regulations that would prevent things that are illegal to say on one media form to apply to all? Sure. You can't just go buy a TV ad that says "blue cars cause cancer", knowing that it will drive business away from a guy you hate that makes blue cars. But I can go have that facebook ad up in 5 minutes.

As part of living in a society, I am happy to cede some freedoms for a better world.
Right, and even then, different doctors/specialties have different standards for what counts as low testosterone. My primary swore up and down that my 300 was fine (and even 200 would be) but men's clinics would insist I need to be at 900.
have you considered getting a job
Tech Podcast for the 1%
Quiet supersonic jet will halve the time it takes to get around the globe
Assuming wireguard hashes data shorter than 4k (i.e. most network packets), there is no reason to switch; BLAKE3 is only faster than BLAKE2 on data longer than 4k.
> What's the big deal if it's ring, or me with a bunch of chinese-made POE cameras and blue iris as a local server?

If it's just you with a local server, then I only have to worry about you. If it's going to someone else's server, then I have to worry about them as well. And in the case of Ring specifically, that someone else is Amazon -- which is even more concerning.

> shouldn't people have the right to set up surveillance on their own house for protection and deterrence?

Sure, I never said otherwise. I have a surveillance system myself (on my own local servers), but I take great pains to ensure that no cameras are capturing anything that isn't my property.

> It's a deterrent and doesn't necessarily mean high crime.

I never said that it automatically means a high crime area. It's just highly suggestive of it. If it's a low crime area, far fewer people would feel the need for this sort of thing.

> if you live in Major City like I have my whole life, it's just a fact of life that you're going to want stuff like this.

No, it's not. I've lived in a number of major cities, and have never felt the need to point cameras at my neighbor's houses or the street.
Or just take a Docker-like approach, where each app thinks it is the only user and intra-app communication is where you put the security functionality
Alright, Linus, I'll make you a deal: I'll consider dropping ZFS when you ship a production-grade BTRFS (or reiserfs or anything else with the same features).
That is much more rare than lime bikes on sidewalks, at least here. Also, cars on sidewalks don't tend to fall on people's feet by getting slightly knocked over.
They already do. These are advertisements and Facebook accepts money and approves them explicitly (and limits what advertisers can say/do already).

Random FB post - yeah maybe theres a 1st amendment argument there - but ads are already "Facebook authorized speech"
That is, in part, because many if not most nursing homes are understaffed. In Indiana, they always knew when they were getting inspected and forced overtime on folks those couple of weeks. Why the past month's payroll records aren't checked more often for staffing levels I never know.
A large volume of research shows depression/suicide/drug abuse/etc are directly related to economic stress, but that's a much harder topic to address so it's ignored in favor of easy scapegoats and bogeyman.
I can't remember which company it was, but I once read an article about a company who implemented their own version of `sudo`. Their version required another developer to approve your session before granting root privileges, and then allowed them to watch everything you did.
Wrong, profit is made. It can go to for profit hospitals who charge
for it, or at least the service if administrating it.
You seem to think that dairy is going away or something. That's not what's happening. Yes, dairy consumption is trending down a bit for various reasons, but hasn't changed a great deal.

What has changed is the consolidation of dairy herds into mega farms. Small and medium farms go bust while the mega farms increase their herd size (the overall milk production doesn't change a great deal).

So dairy will still be around, but as current trends continue, the milk will come from a Wal-Mart megafarm with requisite massive manure lagoons and high capacity water pumps, trucked by a Wal-Mart truck to a Wal-Mart creamery, and sent to a Wal-Mart distribution center and then Wal-Mart store for purchase. Instead of the traditional way of coming from independently-owned dairy farms, processed by cooperative creameries, etc.
If enough beacons have died such that it can no longer calculate it's position I bet it just stops. Should be a fairly easy thing to check just stop, send a notification, and power off or more likely since beacons are far more likely to die between runs just don't start if enough beacons aren't present.
Also, Maserati dealerships have 5 cars for every person who has no car. So?
I drive for Lyft and Uber and no one has ever said a word about it. I think it's just understood.
At least in the US, doing this would already be illegal.

https://en.wikipedia.org/wiki/Genetic_Information_Nondiscrim...
Not everyone on HN knows about C++11 threading. A "hello world" is of interest to some people.
I wouldn't be a fan of adding that kind of permissions to JWTs. Permission authorization should be stored in the server. JWTs should be for authentication.

Plus for some things you want to invalidate based on how recently they have interacted (IE bank logs you out if you haven't clicked/typed anything for 5 minutes) and you can't represent that without server state.