jeroenhd

Damn, I've never seen Anubis set up that aggressively, I wonder what kind of attack their web servers must be under to set their bot filters up this strictly.

Wero also isn't implemented EU-wide either, so it's still possible as long as the banks play ball.

UK politics has been quite isolationist, though, so I doubt the banks will see much in interoperating with the rest of Europe.

Wero is a payment provider technology, a money wallet, and a bank account integration technology under one single marketing name.

On the payment provider technology side, you're right, but the wallet feature uses phone numbers (and I think email addresses) so you can send each other money without sharing your IBAN (which is slightly longer and probably not in your contacts).

Does that matter? I don't care of Apple's thread scheduler is faster or slower than Windows' or if their throttling algorithm behaves differently, I just want to see how it performs in a given task.

We fixed the hole in the ozone layer. All the countries came together, worked together, and fixed the problem threatening to doom us all with skin cancer and worse. Humanity can come together.

Unfortunately, the threat of total annihilation of human civilisation is currently not outweighing the short-term profit incentives of those in power, and they've turned the issue into fuel for their culture war so I doubt we'll find a real solution before the current generation of politicians is dead.

I don't think websites block Google's VPN either, although that's not quite as popular as Apple's VPN solution.

Anthropic's Claude: own your things, for only 20 dollars per month!

I can only presume this regex is there because Google had to block various scammers trying to use email hosting donain names when novel TLDs came onto the market. You can try to manage gmail.zip or outlook.mov but Google will probably flag you as a scammer if you try to email from them. Just because web.de isn't well-known outside of German circles doesn't mean the risk doesn't exist. These email providers, especially the ones hosted by Microsoft, have a history of buying multiple TLDs to offer users a localised email domain.

Blocking a second level domain like the Ukranians tried to use is surprising, though. I guess it's to prevent domains like outlook.co.uk or something like that?

These regexes were put there for a reason so I doubt they'll get removed, but if they fix their frontend-only detection script you're going to be locked out of your domain some day if you force your way through their checks. Seems awfully risky.

A division of the Ukranian government seems to come pretty close to a "large enterprise".

Maybe there are politics involved, but fixing a broken regex seems well worth the time to convince a foreign government to rely on your tech.

Of course, the support request never reached anyone who knows what a regex is, so bugs get confused for policy and nobody cares to fix it.

TUIs run on any OS with minor patches to support quirks, GUI frameworks need a lot of work. TUIs don't need to follow any OS guidelines, cross-platform GUIs always look bad outside of the "main" platform.

If you're only targeting macOS/Windows/Gnome/KDE then the solution is easy: just grab a GUI control set and go ham.

Then there's remote access: you can spawn an X11 app through X forwarding and have a terrible laggy experience on Linux, you can use RemoteApps on Windows to have a good remote experience (but almost no other platform), you can use VNC to have an awful cross-platform experience, or you can use a TUI and have all the graphs and interactivity you need over a responsive, low-bandwidth connection on any combination of client+server.

China is strictly worse than the USA when it comes to border controls. That doesn't mean the USA is good or acceptable in any way; these laws are part of the reason why I don't plan on visiting the country. The USA also has much worse laws on the books, like having to give the authorities your social media passwords to check if you're secretly a terrorist (though that doesn't apply to citizens).

Excessive border patrol power has been around in the USA for ages now, it's all part of the post-9/11 package. I don't think many Americans even know they live in a zone where the border police can do shit like this, even if they haven't left the country, as international airports are usually near big cities, and they have a wide border zone around them. This stuff only really makes it into the news when it happens to one of the "good guys".

That shouldn't be too hard. Get someone from Google or someone with any tech knowledge to explain to the judge how phones normally work, what encryption keys are, the implications of wiping an encryption key, and then get someone to show the difference between entering a normal PIN wrong several times and entering the duress PIN. You just need to convince the jury (or judge, if there is no jury for whatever reason).

People have gone to jail or have been executed for less than a glitch. Theoretically a highly charged particle from space could've messed with exactly the right transistors exactly when entering the correct PIN and trigger the wipe process. There is no way to prove that didn't happen. But you don't need that kind of proof.

Whatever they claimed they needed access for his phone to. Probably nothing serious that would be worth more than a fine, if anything. But now they've got him for deleting evidence, which is pretty bad.

Knowingly providing a PIN that would erase evidence is going to get tough in court.

But the man was also hated by the cops because of his activism. They were going to catch him for something, some day. This incident just provided the necessary excuse to lock him up.

But their legal framework for being permitted to scan the books en masse (they are "transforming" the book from physical to digital) requires destruction of the original. Otherwise it wouldn't be transforming, it would be duplicating.

The piracy lawsuits have so far only deemed that obtaining books through pirating is a violation of copyright. Training the models on them and reselling model access has yet to be ruled illegal, from my understanding, even though there has been plenty of opportunity to.

Anthropic's crime wasn't stealing the contents of books and making a derivative work of it, but torrenting a shitload of books. Had they bought all the ebooks, I don't think the lawsuit would've gone anywhere.

> Like it or not, all publicly available information will inevitably become accessible to anyone and anything that has permission to access it. This is the baseline scenario people need to plan around.

And this will be the end of the internet as we had it, and as we have it right now. With no way to block AI scrapers and no hope of AI companies acting ethically, shutting down the free internet is the only end result.

I'll remember these fun, bespoke attempts to stop AI from ruining the world once the internet is gone. That alone makes them worth existing for me.

Lossily stuffing books into a model through a training process has so far been deemed legal. Enabling piracy by giving away digital copies is not. The internet archive tried to give away digital copies and they got sued to hell and back (which they should've seen coming from miles away).

I'm sure they have some repository available somewhere. They can even sell the digital copies down the line if they're done with them (only once, of course).

AI companies are buying the physical books, they can turn them into confetti if that's what they want to do. If the physical books are running out, the authors can print and sell more. Or they can sell digital copies so the information is not lost.

The law is currently forcing these companies to destroy the books after scanning them.

They want to have a digital copy and the judge ruled they can only keep one copy.

All of those can (and some do) wget source code from the internet and run it if you kick off their build pipeline. People just tend to use these tools differently.

Nothing is preventing anyone from distributing Rust crates as standard system packages, like some distros do with Python.

I think Debian is actually shipping rust libs in their repositories: https://wiki.debian.org/Rust Now Rust developers can also enjoy having to deal with popular packages that are years out of date/missing from popular repositories/getting deleted.

I really like "comics" like these. They're often well thought-out and can often get concepts across faster than plain documentation by using imagery that would stand out in a plain readme.

Unfortunately, I expect any company/project/product to produce these in the modern age to reach for AI.

A second hand pixel is a quarter of that. A four year old second hand phone being worth as much as a new midrange phone still makes these devices a bad deal, especially with the Z Fold 4 receiving no more security updates within a year.

I think there are plenty of people like me who would like to try one, but don't feel like spending multiple months of rent on the privilege of doing so.

I'm holding off for the coming while with the current RAM prices keeping phones incredibly expensive, but in five or six years when my current phone goes EOL I hope to see affordable options.

Not the links per se (those are subject to terms of service), but the contents downloaded for those links are free to share. Anyone can throw them up in their own git repository or upload them to Github.

> How did we get to the point where people feel they need to go to the length of embedding an ELF loader in their binary (!!) rather than just linking with glibc?

Most Linux distros have been built around the ability to compile their software together in a large repository, from source, so this was rarely ever an issue. Proprietary distribution or executing binaries from the internet like on Windows just wasn't really a common issue.

The problem arises when you start combining distros (glibc and MUSL for instance) or if you try to do the Windows model of sharing software. Historically, projects just compiled different versions for different distros.

When doing static compilation, just targetting an old version of glibc (which is generally forward compatible) also works.

You can hack your way into using software like this (or rather, have an LLM hack its way in) but I don't think any real distro actually cares. This issue exists in a quite small space where people are trying to use proprietary software built for glibc in MUSL environments for whatever reason, and the usual compatibility tricks don't work.

It's a niche use case for most Linux distros. It's not a "complete failure" of the GNU/Linux userland, it's the result of a couple of proprietary components not having MUSL builds available, or MUSL-based distributions not including libraries people want.

I'd like glibc to change so that these hacks aren't necessary for these use cases anymore, but it's not really a problem in practice for the vast majority of Linux use cases.

Luckily, modern cooling techniques like heat pumps are much more efficient than resistive heating, 300% to 500% efficiency is easily attainable. You can keep the inside of a data center nice and chilly at room temperature even in the middle of a heat wave.

Then there is also the heat island effect. Concrete boxes will heat up an area more than dirt or wood, even if those boxes are completely empty inside. If you build them near where people live, people are gonna notice. Houses have gardens, industrial complexes such as data centers and factories don't.

Also, the effect is more concentrated downwind, so the heat effect is not some kind of uniform distribution in all directions.

But only since the digital age did the government actually _succeed_ in controlling currency on a massive scale, right up until the point cryptocurrency took off (and even that can be tracked, most cryptocurrencies are based on a public ledger after all).

There are other hidden benefits as well. Tax evasion and money laundering become a lot harder in a system that tracks transactions. That can be massive benefit or a dystopian nightmare depending on the people in charge, but for many governments that's something worth throwing money at.

> in almost every devops or CI workflow

But that's the core of the problem, isn't it? People setting up devops environments are the reason these flows are so complicated. You can set up the same flows by having Jenkins call out to Jenkins to trigger chains of jobs that can conditionally fail.

People generally don't do it, because there are better alternatives out there for when you want those types of pipelines (which includes Github Actions and their counterparts). Setting up a four-step build+test+scan+tag+push+deploy pipeline in Jenkins is just as hard as it is with Github, if not harder. [Jenkinsfile](https://www.jenkins.io/doc/book/pipeline/jenkinsfile/) is just YAML with extra parentheses.

The modern YAML files are a simplification of the manual steps required to do it all in tools that predated the YAML files. There's nothing stopping you from having a Github runner configuration that's just a call to a single Docker image containing all the bash/perl/Makefile/Kotlinscript/Go/Ruby/etc. files you want to execute. Or you can forego the Docker part and run code directly inside of the repository, with all the security risks that come with it (not dissimilar to having a fully open Jenkins server).

Complicated YAML is a symptom. It's no better or worse than Bash or TOML or Makefile when you start adding conditional automation and multi-step CI/CD flows.