Replication is not the same as reproduction; I can replicate an API without violating someone's license or copyright (which I would by reproducing their work).
There is code I gift to the world that I license as MIT or similar and there is code I publish as a means for furthering what I perceive as a advanced society which I license as GPL or similar.
I don't ask anyone to share my ideals but conflating these two is dishonest.
The shifts between flags will correlate with date of birth though, or do you think someone turning 16 or 18 will wait a year or two to switch to more adult content for privacy? Also I'd guess the tech industry would push for more specific age buckets.
Games already have PG ratings and similar in different countries, I don't see the issue there. Web content could set a age appropriateness header and let browsers deal with it, either for specific content or for the whole website if it relies on e.g. addictive mechanics.
Applications is a wide field, but I'd be interested in specific examples where you think it wouldn't work.
> Applications is a wide field, but I'd be interested in specific examples where you think it wouldn't work.
Sure. Take a game with voice chat. Child mode disables voice chat. How does the game, which presumably uses a load of telemetry, avoid incidentally leaking which users are children via the lack of voice telemetry data coming from the client? It's probably possible, but the fact is we're talking about third party code running on a computer, and the computer running different code paths based on some value. The third party code knows that value, and if it has internet access can exfiltrate it. In that sense, if there's an internet connection, there's not a meaningful difference between "the OS tells the service/app your age rating preference" and "the OS changes what it displays based on your age rating preference."
Though while I'm throwing out fantasy policies we could solve this by banning pervasive surveillance outright.
You're assuming that everything not mandatory is prohibited. If the device is required to provide every service with the flag, every service gets the flag, even if it contains no adult content or adult content that the user agent could display or not without the service having a way to know about it.
The service would then have to deduce the information instead of getting it explicitly and may be able to do that some of the time instead of all of the time, which is an improvement. And then people can work on anti-fingerprinting technologies with the premise that if they succeed it actually does something, instead of the information being required by law to leak to the service.
I honestly think the answer is tax money. It should be clear by now, that a browser is (critical) infrastructure and it should be funded as such. Ideally by multiple, non-aligned states.
"Gzip only provides a compression ratio of a little over 1000: If I want a file that expands to 100 GB, I’ve got to serve a 100 MB asset. Worse, when I tried it, the bots just shrugged it off, with some even coming back for more."
Modern browsers support brotli or zstd, which is a lot better in terms of compression. Perhaps not as good for on-the-fly compression, but static assets can get a nice compression benefit out of it.
With toxic AI scrapers like Perplexity moving more and more to headless web browsers to bypass bot blocks, I think a brotli bomb (100GB of \0 can be compressed to about 78KiB with Brotli) would be quite effective.
Which do you consider as being under better control: a technology that we exhaustively create reports on even in the face of incidents like this where the only real chance of harm was that the guy couldn't swim and might have drowned; or a technology where we don't report on anything at all whatsoever and thus have no idea what's actually going on?
Reports don't mean danger, and they don't mean lack of control. Reports are information.
Of the eight reports I only see one that relates to a guy being able to swim or not (and I suspect the same is true for the estimated 1400 reports so far this year). Also having transparency is obviously good and I don't understand what you want to prove with arguing that a worse situation would be worse. It clearly would be worse.
I'm also not totally against nuclear, in case you are suspecting that. I do think though, that we as a society aren't at the point where we have the ability to completely control such technology, contrary to what proponents of much higher utilization of nuclear like to claim. Reports of fuses seemingly without failover or stolen equipment seem to support that argument.
I'd argue that most people like knowing that what they receive is what the original server sent(and vice versa) but maybe you enjoy ads enough to prefer having your ISP put more of it on the websites you use?
Jokes aside https is as much about privacy as is is about reducing the chance you receive data that has been tampered. You shouldn't only not use FTP because credentials but also because embedded malware you didn't put there yourself.
I tried to open different themes in tabs for comparison, but I would have to first open each one and then manually copy the URL into a new tab because you implemented your links as <button> (which prevents both middle-click and 'open in new tab' context menu option to work).
Yup, this is the incompetence that we see all over the place since these new frameworks have come and front end devs have no idea what HTML actually is or how it works.
Buttons are for submitting forms and nothing else.
In HTML a link is created using an <a> element.
React has a <Link> element for this purpose, it will be rendered as <a>.
Please OP, at least try to learn a little bit about the underlying technologies.
reply