Could you say a few things on your plans to develop the community and ecosystem then as requested?

That's the significant part of Wordpress after all, not the mediocre code.

This holds true until you pass to the next age bracket for the first time.

It being Linux those would obviously be seconds so they are roughly half a year old.

Unless it represents seconds since the epoch which would make it a birthday - May 31st 1970.

I fail to see how mass scale reproduction of copyrighted code isn't a form of distribution.

Reproduce is a definition of replicate. And LLMs reproduced code.

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.

You can do it by using a feed reader and subscribing to the channels rss feeds. Keeps you better isolated from dark patterns as well.

edit: has the added benefit that there are different feeds for All/Videos/Shorts/Live/Specific Playlists, so this is another way to avoid shorts

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."

https://maurycyz.com/misc/the_cost_of_trash/#:~:text=throw%2...

You could try different compression methods supported by browsers like brotli.

Otherwise you can also chain compression methods like: "Content-Encoding: gzip gzip".

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.

Ah cool that site's robots.txt is still broken, just like it was when it first came up on HN...

How do they even know that?