WhyNotHugo

I'm don't see "allow GrapheneOS" as a great difference: the bank is still only permitting transactions on devices controlled by a third party and not by the owner. I don't want to change the third party that controls the device. I want to use my own device.

People who work at Facebook and complain about this strike me as incredible naive. They work for the devil in exchange for huge sums of money, but are then shocked that the devil partakes in devious acts.

Neither leaving in protest nor staying would really change much. As long as someone is willing to do the dirty work, it'll continue to get done.

A lot of banks are dropping support for making transfers from their regular webapp. AFAIK, in some countries a total of zero banks support this.

I dislike the idea of these separate tools being blended like this. ty is currently perfectly usable on non-uv projects. uv has *a lot* of opinionated quirks, its custom lockfile lockfile, and other nuances which many of us dislike — ty being a separate tool works fine with plain pip plus any other dependency manager (e.g.: pip-tools).

Of note though, ty doesn't NEED to be integrated into uv, nor vice-versa; keeping them as standalone tools seems most natural.

While I agree in spirit, this also makes the resolver away from being able to claim they're just a neutral service which just delivers existing records without being opinionated

DANE is actually what you want.

A domain owner can publish DANE DNS records with details on the certificate and/or CA used for the domain. With DANE, if a misbehaving CA emits a certificate for your domain, it won't be valid since that certificate doesn't match what you're declared as permitted. This is further solidified with DNSSEC.

Regrettably, none of the major browsers implement DANE, so if any CA emits a certificate for your domain, they'll trust it implicitly.

> Amazon's Fair Pricing Policy lets it remove the Buy Box (the "Add to Cart" button), or even suspend a seller, if they're offering their item cheaper elsewhere.

This kind of abusive practice needs to be banned in whichever countries it's still legal.

You can't really aspire to improve the situation if such things continue to be legal.

mkdocs still uses "web fonts" for icons. This hack was required for compatibility with Internet Explorer, but is just cargo-culting these days. It's an accessibility issue in that users who disable web fonts (for readability) don't see icons, they just see unicode placeholders everywhere ("tofu").

Goguma is an IRC client which runs on Linux Mobile, iOS and Android.

You can use a bouncer on IRC to retain messages while you were offline. In reality, it's the same with every other network: you need a server which receives and retains messages while you're offline.

With WhatsApp, Discord, etc, that server is provided by Facebook, Discard respectively. With XMPP, Matrix, that server is the instance in which you have an account or where the channel is hosted.

With IRC, you use a bouncer. What makes IRC unique is that a bouncer is _optional_. You can even join a channel without an account and without a server which keeps logs while you're offline. This ephemeral level of joining doesn't exist in WhatsApp, Discord, XMPP, Matrix, etc.

And, btw, this is not a new thing: I first saw bouncers 15 years ago and they weren't even new back then.

Rather than claim a Discord-esque feel, you should point out the features you're referring to explicitly. Discord is infamous for its absolutely awful UX and hostility to open source ecosystem. I'm sure you're referring to neither of those aspects, but consider that those reading your reference might be entirely unfamiliar with the (presumably) positive aspects that you're actually imitating.

There's a zeroth step missing from both the Quickstart and Full Set Up: install php-fpm, configure it, and configure your http server to serve using it as a backend.

It seems to be taken for granted — that's something you'd already have in place if you're already serving applications in PHP, but would have to figure out on your own if you haven't served anything in PHP so far in your life.

It's a really dangerous precedent that we say "a rogue computer did X". Especially when the police does so.

We don't say "a rogue knife stabbed someone", or "a rogue scalpel botched a surgery". There's a human behind this, who set everything up. They might have lost control at some point, but when someone loses control while driving, we don't say that "a rogue car crashed into some kids" and call it a day. When a surgeon "loses control of their scalpel" we question whether they're qualified to perform surgeries.

The person responsible who lost control is still responsible for losing control, and it's dangerous precedent that we pretend otherwise for these cases.

Meanwhile, the EU is working on further entrenching payment and identity into American service providers (mainly: Apple and Google).

Do these sanctions also affect anyone working at the ICC?