skysight-inc/HackerNews huggingface dataset:
Sure, I'm not saying this is the only solution, or that it's foolproof. But this should be a wake up call for everyone in the OSS community to do better.

Projects that end up with a single maintainer should raise some flags, and depending on their importance, help and resources should be made available. We've all seen that xkcd, and found it more amusing than scary.

One idea to raise awareness: a service that scans projects on GitHub and elsewhere, and assigns maintenance scores, depending on various factors. The bus factor should be a primary one. Make a scoreboard, badges, integrate it into package managers and IDEs, etc. GitHub itself would be the ideal company to implement this, if they cared about OSS as much as they claim to do.
> Google has their "was this you?" built into the OS.

Not only that, but it's completely impossible to disable or remove that functionality or even make TOTP the primary option. Every single time I try to sign in, Google prompts my phone first, giving me a useless notification for later, and I have to manually click a couple of buttons to say "no I am not getting up to grab my phone and unlock it for this bullshit, let me enter my TOTP code". Every single time.
There's no way that's a good idea without a AZ-5 style wax+paper seal and flip cap on the steering wheel to turn it off. You want to be able to use your car in emergency situations.
""Wiretap" without additonal context is a bit misleading since it conjures an image of listening to phone conversations between employees of the competitor."

What is the context. Litigation. The submission comes from courtlistener.com "Wiretap" here has a specific meaning. The definition is provided in the citation in footnote 1: 18 USC 2511(1)(a) and (d).

"intentionally intercepts, endeavors to intercept, or procures any other person to intercept or endeavor to intercept, any wire, oral, or electronic communication;"

What's perplexing about the HN fixation on the term "wiretap" in this case is that the criminal offence of wiretapping is not a claim in this particular litigation. The case is concerned with anticompetitive conduct. The plaintiffs are proceding on a "monopoly broth" theory. The issue is whether Facebook's conduct re: the VPN is anti-competitive. Why would Facebook do something it knows is illegal or even might be illegal.

In the plaintiffs first amended complaint, they cite a quote from a US senator who specifically referred to the Onavo situation as "wiretapping teenagers". Even if the term was not being used to refer to the specific federal crime of wiretapping, it was already being used to refer to what Facebook was doing.

Meta is going bananas to try to keep the facts revleaed in this litigation from seeing the light of day. Why. Let the reader decide.

Pretending that the word "wiretapping" is misleading is like SBF refusing to acknowledge that he has committed any crime. Being evasive, trying to redefine words will not work. The definition is provided via citation in the document. This is an antitrust case, not a wiretapping case. Judge Donato is all too familiar with the unethical conduct of so-called "tech" companies. This "tech company" nonsense is occupying an increasing portion of the court's time.

A computer user MITM'ing apps on her own computer is not wiretapping. Facebook is MITM'ing apps on someone else's computer.
> Yes. The "record" part, is beside the point.

If it's besides the point why make it the headline?

> Most people are unaware of the scale of disproportionality at all

The biggest issue is that the top 1% is not a static group! People move into it and out of it all the time - the churn is quite high.

There was an analysis of US tax payers and most people will only enter the top 1% for one year out of their entire life.
Well said. I was annoyed by the lack of specific information for exactly the reasons you mentioned

More specific estimates of safe distances versus collider power would be helpful, same too about the nature and type of radioactive byproducts in soil (what elements would be expected to become radioactive along with their half-lifes, etc.).

Sometimes I think it ought to compulsory for scientists to study philosophy—at least its parts that deal with logic, language and semantics.

Philosophy defines near —like good— as a 'simple notion' that cannot be subdivided into simpler terms. The word needs qualifiers/quantifiers (figures, distances, amounts) for it to be useful—info that the paper was overly vague about or omitted to specify.
Agree. I’m a Tesla owner and I bought it only for the super charger network. Living in Europe, every country I travel to can have different charging networks and so the Tesla network is one of the few that lets me drive on road trips without a worry. I don’t care about FSD.
mkfs(8):

> This mkfs frontend is deprecated in favour of filesystem specific mkfs.<type> utils.
I've done work with non-profits.... they are really about bottom line for their DEI staff. There is nothing more important that paying people that are on the extreme side of virtue signalling. Hopefully that era is ending soon. The sooner people stop virtue signalling, and actually just start doing the work - the better this world will be.
You're thinking of hardware-backed attestation, which provides a hardware root of trust. I believe passkeys are just challenge-response (using public key cryptography). You could probably add some sort of root of trust (for example, have the public key signed by the HSM that generated it) but that would be entirely additional to the passkey itself.
Venezuela and Iran have service
Google paid for it
If by techies they refer to IT, then just about everything.

I have seen many, many cases over the decades where OT was confused for IT by management and the extensive OT considerations were ignored or had to be re-learned when an IT approach was taken to OT problems.

Often the IT based solution in OT world never ended up working at all and had to be discarded, or re-engineered from the ground up.

Just because you have boxes with screens connected by blue cables, history has proven many times that this does not make IT the best people to architect and implement your OT system, by a long, long way.
Honestly, I don't have a lot of hope that we can fix this problem for C on linux. There's just so much historical cruft in present, spread between autotools, configure, make, glibc, gcc and C itself that would need to be modified to support capabilities.

The rule we need is "If I pull in library X with some capability set, then X can't do anything not explicitly allowed by the passed set of capabilities". The problem in C is that there is currently no straightforward way to firewall off different parts of a linux process from each other. And dynamic linking on linux is done by gluing together compiled artifacts - with no way to check or understand what assembly instructions any of those parts contain.

I see two ways to solve this generally:

- Statically - ie at compile time, the compiler annotates every method with a set of permissions it (recursively) requires. The program fails to compile if a method is called which requires permissions that the caller does not pass it. In rust for example, I could imagine cargo enforcing this for rust programs. But I think it would require some changes to the C language itself if we want to add capabilities there. Maybe some compiler extensions would be enough - but probably not given a C program could obfuscate which functions call which other functions.

- Dynamically. In this case, every linux system call is replaced with a new version which takes a capability object as a parameter. When the program starts, it is given a capability by the OS and it can then use that to make child capabilities passed to different libraries. I could imagine this working in python or javascript. But for this to work in C, we need to stop libraries from just scanning the process's memory and stealing capabilities from elsewhere in the program.
Thanks for sharing! I've bookmarked the book.
Rejecting media is next door to rejecting science, society, any and all rational argument etc. It’s not an immune reaction per se, it’s a preamble to shutdown. Basically we want people to choose what they believe judiciously, not to get overwhelmed and believe nothing.
That's why I always raise concerns about JEP 411 - removal of SecurityManager from Java without any replacement.
The roller ship was not an effective way to cross the high seas
The fraudulent author must have enjoyed the 'in joke' -- He's the one create vulnerabilities..
Modern coders have been conditioned to import random libs to save 30mins work.
I have no clue, so I've asked, where is the difference?
Thanks for your feedback! Initially, I thought it would be a good idea, mainly if a description were too long. But, after reading your feedback and trying again on a few pages, it's never practical.

I just pushed an update to remove the "Show more" button.
I once had a discussion with a friend where we hypothesized that the universe is God, discovering Him/Itself through the experiences of its constituent systems, like atoms, cells, humans, solar systems, galaxies, etc. it’s all one consciousness, and it’s omnipresent because it is literally existence, all knowing because it’s knowledge is the sum of all other knowledge. So religious people aren’t wrong, but neither is everyone else.
Is there an actual "right to use the sea"? ! My city dumps dozens of wild dogs on beach, they attack people in large packs, and everyone is told to use beach at their own risk. No right to swim on public beach!

Or environmentalists dumps dangerous bears into public forrest. They routinely kill people, even roam city streets [1]. But there is no "right to safely use forest".

1] https://www.bbc.com/news/world-europe-68675794
Well, the worst drivers are those that just keep their brights on, because they have no fucking clue you're supposed to lower them when another car is approaching. Fucking idiots.
When I remember right, Paint.net has this funny origin story: someone wanted to proof that .NET was not suitable for delivering a paint application. He proofed himself otherwise and made a permanent job out of it.
Um, what? This incident is turning into such a big deal because xz is deeply ingrained as a core dependency in the software ecosystem. It's not an obscure tool for "pirates."
Buy a boat
searched for best yoga mat, got strange video about sunscreen...
It has been on the agenda for years to identify FOSS contributors with an id… Wet dream for authoritarians like you.

What would it solve when identity theft happens on a mass scale on a day to day basis?

It'd just ruin the life of some random person whose identity got stolen to create the account…
the actual paper: https://link.springer.com/article/10.1007/s10508-023-02798-x

see also Morgan, "What Part of 'No' Don't You Understand?" (1992)
9 comments on it when it was posted August 31 last year: https://news.ycombinator.com/item?id=37340361
Absolutely false. It is not a skill issue to write safe c code. It is simple impossible. As in every humans makes mistakes and we know by know that statistically it must happen. There are also other issues as tooling. We need better languages for system programming. If your are sower because you don't whant to change, than the world will move on without you.
Which is also why radio stations never play complete songs any more, because everybody would just record them.
> Is it really aspirational if you do it?

No, aspirational means that you aspire to do it, which is probably why most people buy most cars, at least in the US. One exception does not disprove that theory.

If you only need the range 4 times, let alone once, a year, why not rent a car for that rare and buy something more optimal for your daily needs? That's what we do, and our daily need is no car at all.
Give us more money.
Nope, I read The Register (UK based) and they've had scandals from celebrities having their confidential SMS messages leaked; SMS spoofing; I think they even have SIM cloning going on every now and then in UK and some European countries. (since The Register is a tech site, my recollection is some carriers took technical measures to prevent these issues while quite a few didn't.)

I don't think it's a thing that happens that often in UK etc.; but, it doesn't happen that frequently in the US either. It's just a thing that can potentially happen.
Good points. Although, having worked on many high scale architectures before, I always err on the side of thinking that any technical solution of this magnitude would have far too many nuances for a blog post to capture. And I believe Figma’s post also talks mainly about the common denominator that’s easier to communicate to the external world.

For me to understand their choices, I’ll first have to understand their system, which can be a task in itself. Without that, I’d not become aware of the nuances, only general patterns.
It's my idea... I've been writing about it for over a decade. I hope to get a small version of it made via tiny tapeout later this year once I'm out of the precariat.

The idea is that you can decompose any non-cyclic code, for example, a matrix multiply, FFT, etc.. into a directed graph of bitwise operations, then map those operations out into the grid of LUTs. Pipe inputs in one side of the grid, and get the outputs out the other side, and all of the bitwise operations happen in lock step parallelism. (Unlike an FPGA which is asyncronous)

If you can decompose one stage of an LLM down into a bitwise graph of computation, you can easily map it into the grid. If there's a bad cell in the grid, you can map around it.

Because all of the high speed logic lines are short (to the neighbors) you don't have the long lines / high capacitance issues driving signals all the way across an FPGA or ASIC, thus you can really crank up the clock rate (and/or it's very power efficient).

It should be trivial, design wise, to scale from a 16x16 grid up through chips that could crank out Petaflops.

Here's a simulator for the thing, written in Pascal.

https://github.com/mikewarot/Bitgrid
Wonderful.

Made more so by the music that has been combined with the recording!
Meet my friend “it’s what you know for sure that it isn’t so (…)”

We are clueless of our ignorance, and of how much there is still to discover in all domains of science.

IMHO I think we are accelerating discovery and we do not know yet what to do with all the things we invent and discover.
If we down to naming things - my Apple products are inedible, AI personal assistants do not assist in most cases, footlong subs are 6”, SuperCruise is SomeplaceCruise…
There’s been sewage in the seas and oceans for as long as there’s been sewage in proximity to those places. Long before caring for the environment as it’s now understood was even a concept. I’d hazard a guess that on a population density normalized comparison for developed countries there has never been a better time for responsible sewage handling. That’s not to say that there aren’t plenty of problems like this article highlights, just that it probably has not been better in the past. Hopefully the UK courts will hand this lady a decisive win and reinforce the idea that industry does have responsibility.
I mean, when you're dealing with a barbarian driving 130 mph you're probably saving someone's life
Can I run awesome-wm on Wayland yet? That's what keeps me on X.
Bunch of bu... rather unsubstantial claims. Just installed fresh KDE 5 + Plasma , running Wayland session, with two displays having different DPIs (96 and 185), and Plasma menus on HiDPI display are blurry until I'm moving a mouse over them, then they magically are getting refreshed with proper resolution. Tell me about how Wayland is great and works out of the box, sure
The answer is obvious: they invented their own sharding solution because it's a really really cool problem to work on and they have more engineers than they really need to develop their actual product. A more resource-constrained team would have found a solution that sharded their backend using one of the existing solutions out there.

I have seen this several times before and it's always a symptom of having too many engineers working below the waterline. Rather than work on the actual customer-facing problem, let's port the backend to do event-sourcing/cqrs, move all our infrastructure to k8s, change language from x to y etc.

These are all what I would call "internal goals" (ie they may or may not be necessary or even essential to progress but are not directly customer-visible in their outcomes even if they may enable customer features to be built or indirectly improve the customer experience later) and need to be held to an extremely high level of scrutiny.

If you're amazon/google/meta and you need to do this because of extreme user scale I might believe you. If you're CERN or someone and you need to do this because of absolutely ridiculous data scale I might believe you. The idea that it's better for figma to write their own sharding solution than it is to port to one of the existing ones just doesn't pass even the most basic sniff test.
The problem we have right now is that any linked code can do anything, both at build time and at runtime. A good capability system should be able to stop xz from issuing network requests even if other parts of the process do interact with the network. It certainly shouldn't have permission to replace crc32_resolve() and crc64_resolve() via ifunc.

Another way of thinking about the problem is that right now every line of code within a process runs with the same permissions. If we could restrict what 3rd party libraries can do - via checks either at build time or runtime - then supply chain attacks like this would be much harder to pull off.
This should be the final word on the issue. Please don't comment about how your X desktop is fine, or how Wayland doesn't work for your obscure, niche little use case. If X isn't broken already for you, it will soon be broken, not least by some "here's a quarter, go buy yourself a real window system" patch that lands in critical user space or even kernel components or libraries. Ex.: the Asahi Linux video driver simply dies if it detects that it's being called from X, because neither marcan nor Alyssa (who in her early twenties has forgotten more than you know about graphics) can be bothered to support X.

So kindly shut the fuck up, use Wayland, and let the adults in the room chart the future for graphics on your Linux system.
Booo hooo Mr BeyondMeat TotalCommander
Offering "pie in the sky" is nothing new; the difference is that in the old days it was the manifestly untestable "pie in the sky when you die".

see https://www.acityonmars.com
> People need cars that can handle the longest distances they would need to travel.

No they don't, it's much more optimal to buy something that is geared towards your daily needs, and then if you need to drive cross country a few times a year you can rent a big car, that's almost always going to be cheaper, even before taking fuel costs into account.
My bank gave me an hardware token to protect my 5k€ account.

Get better banks people :)
Development of Selfheating Concrete Using Low-Temperature Phase Change Materials
It is really shocking that X has been on life support for like a decade, but it is still necessary to write essays to try and convince people to switch away from it.

Maybe it is just a really good design.

I like i3, so I can switch to Sway easily, there’s just no reason to.
Manipulation always involves diminishment.

Abuse always involves isolation.

Coercion always involves fatigue.

Symptom; method; cause; tool; good ends or bad; doesn’t matter. If X is present, Y is also present.
In this case, the project is using Git submodules for its vendored dependencies, so you can trivially cryptographically verify that they have vendored the correct dependency just by checking the commit hash. It looks really crazy on Github but in most git clients it will just display the commit hash change.
I've been very, very happy with Sway WM, which is a near-replica of i3 WM ans uses Wayland under the hood. It's close to the peak of personal computing for me. Thank you, Wayland.
Such a positive, wholesome attitude, really makes me eager to switch.
Oh no, actually I cannot be bothered because for now my X desktop is fine.
Quite a solid project and approach. Both founders seem smart and to know the problem well. I can see their new framework (Pear runtime) getting huge in the future.
Hereditary peerage was ended with the House of Lords Act 1999.
Who is bragging more online? A large scale analysis of bragging in social media
Study finds $1000 Ozempic appetite suppressant can be made for just $5
"Bison" is an European word (with several variants like "Wisent"), so it makes sense that originally it was the name of an European animal. It became applied to the American bison when the American colonists have encountered an animal similar to the one known by them in Europe.

The European bison is a distinct species from the American bison. In the more distant past bisons were widespread all over the Northern Eurasia and Northern America. They have been preferentially hunted everywhere, so their populations have dwindled and fragmented, becoming isolated, then they have become differentiated.

The European bison is somewhat smaller (because it had been mainly a forest animal) and it had become completely extinct in the wild a century ago.

Fortunately, there were enough captive, which have been bred and then reintroduced in the wild in some of their former territories, e.g. in Poland and Romania.
>> the average trip in the US is less than 20km

> I don't buy my car for my 50th percentile drive.

For most people the average is more like the 95th percentile.
You really think “Steam on nvidia” is a obscure, niche use case?
I don't have a read on this - do we know that Figma isn't doing difficult stuff that warrants proprietary solutions?
It's another species, wisent, zubr, zimbru:

https://en.m.wikipedia.org/wiki/European_bison
https://way-cooler.org/
It’s a good thing it’s a divestment bill and not a ban bill . Americans have good taste
Everything you quote is Musk's goals for the future he wants to implement.

The website where you buy the car never said it was capable of that.

Nobody thought it was a robotaxi when they bought it.
"My reading is that "in the plane" literally means in the plane, +- a couple or tens of meters, depending."

What wad said was so vague as to be practically useless.

"...they give examples of accelerators buried at 300 meters which would create a radiation hazard at a radius of 62 kilometers"

Again, this is overly vague and unhelpful. As I replied to LegitShady, no specific mention is made about the type of radiation dangers or how long radiation would be expected to linger in soils etc.
I don't disagree - fair point there definitely is a latency transfer overhead. I would suspect one had prefetch it by calling `.to("cuda", non_blocking = True)` say 2 layers ahead, so you can in theory hide the movement.

I think somewhere the blog did mention HQQ for 1 bit is slower for now, maybe due to the transfer overhead, although I couldn't exactly remember where
The old James Woods film
True believer is based on Tony Serra.
It seems more straightforward to fix your data-in-files layout than to implement a novel in-GPU filesystem, though.

I think the main benefit here is not having to do memory copies through the CPU, which frees up memory bandwidth for other things.
The business owners have no right to keep people from dumping sewage on them in public
But at least you can see why you shouldn't use lzip in addition to xz, which has been my position for a long time.
Antidotes to Cynicism Creep in Academia
X window managers cannot run on Wayland and that's not something that can change in the future.

There are many awesome-like Wayland compositors though, I've used sway, hyprland and river.