jeroenhd

The Dutch newspaper participating in this article (https://www.trouw.nl/duurzaamheid-economie/nederland-weet-am...) states that a quarter of the statistics are public, but also that within Europe, that's one of the more transparent numbers.

It looks like nobody is really enforcing these laws anywhere.

It's also the reference OS for tons of free software out there.

The Linux implementation I've seen is the Freedesktop implementation that just responds to a user profile flag. There's no cryptography involved, it's just like asking for a room number like the adduser command does.

Edit: well except American states don't flag your operating system as illegal unless they ask for your room number. Canonical and all the other Linux companies really like being able to make money and not spend all of their earnings on lawyers.

The Rust compile cycle will probably generate a gigabyte of files locally as well, but at least they can be `rm`'d out of `target/` once it's done.

It should be said that for this project that's entirely irrelevant of course, but seeing PyTorch has made me skip over projects on the HN homepage before and probably will again in the future.

Murdering people on international waters is not even the latest war crime, IIRC the Hague Invasion Act was created because of the war crimes they were comitting in the Middle East 25 years ago.

A dependency on code you can't read reaching out to servers you don't control is a recipe for disaster. If you can control the server, you can try to add fixes, redirect DNS to a backup cluster, you name it. If you implement the client, you can write the code in a way that doesn't cause full crashes when the remote server does something weird. If you can do neither, you're handing over your business flow and uptime to a third party that doesn't care about you in the slightest.

Tor amplifies the problems caused by badly written websites that do a billion HTTP calls (unless you have HTTPS enabled on Tor) which does make it noticeably slower in a few edge cases, but I don't think it's as bad as its reputation suggests. For this particular blog, the Tor version loads maybe a couple hundred milliseconds slower, mostly because of images coming in slower (content is ready almost immediately).

Lots of hidden services seem to be under constant DDoS attack, though.

There are still plenty of issues with TOR (my main gripe is the "domain names" being practically impossible to recognize/trust or tell anyone about in the real world), but I don't think speed is the biggest factor anymore.

Onionshare runs on basically every device out there (for obscure devices like Linux ARM phones you may need to compile it manually). Install the app, point it at a directory with an index.html file inside, and you're done.

You can monkey-patch scripts around Tor service activation, but I haven't been able to get my Tor+nginx setup to work reliably after updates/service restarts when using unix sockets.

I've tried intentionally answering the prompts wrong and correctness is definitely a factor here (although low bot scores seem to permit you more mistakes). That doesn't mean fingerprinting is not happening while you're solving the puzzles, but it's more than just a distraction.

That said, there was an entire industry out there cranking out these """fun""" explainer videos, so there must be some market for it out there.

The insane part is launching a DDoS attack because some guy online insulted your favorite toy.

Usability is one thing, but with Apple hiding scrollbars by default, loads of macOS-designed websites spawn scrollbars all over the place on other platforms because of 1px overflows.

If the developer behind ShotAPI had started letting the ShotAPI code take shots at the Austrlian government then yes, ShotAPI (or rather, the people behind it) would be responsible.

Blaming ShotAPI would be like blaming OpenAI for what its users are doing. That's not what's happening here. And if ShotAPI did knowingly let its users somehow hack the Australian government, then maybe they should be investigated.

This isn't even "an openai customer tried to hack someone", which can be defended. This is the AI companies themselves fucking around.

In this case, it's not even about the people driving self-driving cars. It's like someone launching a car into traffic just to see what would happen. Even Tesla puts a human in the car when they do their self-driving trials, it's almost impressive that AI companies have somehow managed to out-neglige Tesla.

Price-wise, you're still often better off with amd64. People like to compare the top-end chips, but the competition for a huge slab of amd64 is a small laptop running an iPhone CPU, not the M6 Ultra or whatever the latest and greatest is today. After Apple followed the rest of the industry, the launch price advantage of the Neo quickly grew smaller, especially outside of the USA. If you want a 15 inch laptop, you're pretty deep into high end prices the moment you consider a Macbook.

In practice, getting the M series to run Linux takes longer than it takes Qualcomm to release a Linux build that works, and amd64 takes a few months of actual vendor support rather than enthusiasts hacking away for free, so in that sense the M series is still behind.

If you run WordPress, you should be aware of this already. Either upgrade to the latest versions, constantly and quickly, or have extremely restrictive WAFs up and ready. Especially if you have any plugins installed (as those are usually where the WordPress exploits are coming from).

I'd recommend everyone unhappy only finding out about WordPress' long-standing support policy to ask their money back.

Not saying he had anything to do with this particular hack, but I doubt the ones within reach of the American justice department would be dumb enough to actually threaten the FBI like this.

That's a problem regular companies need to write up a plan for (but most of them probably don't put too much effort into it).

Even with the descend into incompetence the USA has been pulling for the past few years, I still expect the FBI to have a plan for exactly that sort of compromise.

If they're just a bunch of common crimimals from China or Russia, I doubt they'll appear in court.

American courts are real scary when you live in a country that works together with the USA, but if you don't, all you need is to make sure your crimes aren't worth starting another invasion over.

Although, if you count EPYC, which you might as well with the prices Apple charges for their top-end models, AMD still beats Apple with ease at multi-processing.

It's a real shame that these processors are made by Apple (and Qualcomm, I suppose). They'd be my go-to chip if they weren't.

Yet, the five seconds you save by not plugging in a USB cable have led to charging coils being added to nearly every phone to the market these days.

It's a flashy convenience feature, but this is Porsche we're talking about. People interested in buying these cars are all about flashy features without any practical use, because if they wanted a practical car, they wouldn't be buying a Porsche.

Pretty much everything supports SAML. If you decide not to support one of the standard protocols for SSO, you'll lose out on customers. Your tool has to bring in a lot of benefit (and have no competition) to warrant upending a company's entire auth system for.

OAuth/OIDC is a problem if you're trying to shove a bot-shaped peg into a browser-shaped hole, but we don't need a new protocol to solve that.

You can try this copy: https://web.archive.org/web/20260921054500/https://libroot.o...

In practice, those caches were all done for malicious purposes, usually for injecting ads and selling tracking information through injected headers.

Those shared caches were monitored just as strongly, if not stronger, by the people doing internet surveillance.