You don’t need a car in Singapore. Very good public transport and affordable taxis.

For more brain flipping try looking into hardware description languages (Verilog) or proof assistants (Coq).

Is this a new project that was intentionally started in PHP or something legacy? Any interesting benchmarks? Like minimal wire to wire network processing time and where the bottleneck is?

I saw md5 checksum implemented in scratch.

I would like to hear more

Canonical make it hard not to use snaps so only those who took extra steps are not using them.

Yea, not with firefox, at least not without switching to some third party repo.

a handful of states that require porn sites

A handful of states can require that, sure, but requiring is not enough. All the browsers and all the porn sites need to follow that and this is not going to happen

So, again, I don’t know why you’re thinking these solutions are the bad ones

If the goal is to make sure there’s age verification for users of some porn sites with some web browsers - yea, you can totally achieve that. A workaround is a) switch the website or b) switch the browser. That’s security theater though. Wastes time and money, fails to achieve the goal. If the goal is to make sure age is tested for users of all the porn sites for users of all browsers - this goal cannot be achieved without massive effort.

they’re just trying to roll it out nationwide now.

They have internet with porn in it in other nations :)

The option of “I don’t want to do it” may not be on the table anymore.

For this to be on the table you need to convince all the browser manufacturers to implement it and close the sources so it cannot be undone by the users or forked. And remove all the earlier copies and sources Next you need to ban tools like curl or wget because they can pretend to be browsers. If you want something that can’t be removed in reasonable time realistically you have to demand full web drm a-la Google but this means a bunch of older computers needs to be thrown away just because they can’t use newer browsers and/or newer OS.

Now that we figured out what needs to be done on the client site - let’s talk about server side. You need to convince every porn site out there to perform this check. A few more interesting things to think about - how many porn sites are out there? What to do with those that won’t follow your proposal?

In short - from technical point of view if you really want to achieve “enforced age verification” - internet must become a very different, much more closed system.

So it’s not your browser that checks your age but a third party. This raises a few questions:

1. What kind of IDs are accepted? Say I have one issued by Singapore…
2. How often should it check that a person that uses my browser is still me?

the browser decides if you can see it or

Yea, no. I decide, not the browser.

(the best one so far is that the browser itself checks your age

How? As a user I want to have total control over my browser and Internet is an open platform - any browser should be able to view any website even though google is trying to change that with their DRM.

Did twitter consider to affiliate with @musicfan, @musicmusic, @music123, or @musiclover instead?

Do they agree on the definition of the false information?

Let’s say we know how to do better than cmake now.