You mentioned AB1856 which seems waaaaay broader than emitting an age bracket header based on user settings. It puts the onus on the website operator to not only prevent presenting content to wrong age bracket users, but also to determine the age bracket of the user.

Websites are shutting down wholesale because they cannot reasonably afford the CYA, or dont want to out of principle.

In echelons scheme the parent would be voluntarily setting the age bracket on the childs device right, so if a 12 year old is more mature, then go ahead and set their device to emit the 13-16 age bracket header. If you as a parent dont believe in this, then leave the bracket unset.

For a website operator it would be trivial to block the user from accessing the site if the suggested age bracket is too low (as long as we can agree on a single way of doing things, of course). Larger operators can do more heavy content moderation and present a filtered view to those same age bracketed users.

It is true you are adding more tracking signals, and I am sensitive to the free speech issues, but children are not fully emancipated members of society yet and parents need tools to deal with the difficulties of raising children in a digital society. The alternative now seems to be OSA-like, which is even more intrusive and a risk to privacy and perhaps free society as a whole.

Of course, OSA is really the goal and not the method, and we have to remember it is never about the children. Would children have been protected from e.g. andrew mountbatten if OSA had been around at that time?

So lawmakers do know how to make legally binding preferences based on device settings? What a crazy innovation.. now if only parents were given these options to indicate their child is using a device.. we could do away with all this Online Safety Act nonsense...

Simply reducing the complexity of the standard to "pure ML-KEM" could already be considered enough "NOBUS" to be workable, such that the focus of attacks can be only on it (and bonus NOBUS if weaknesses are already known).

Sure, it's not completely free, but the hardware and implementation points seem relatively minor. Once CRQC exists the capacity will certainly not be unlimited, so there will surely still be use for encryption using ECC and "dragging it around" is not so bad.

Are you sure you did not mean Unsloth?

A new instruction by the user will be appended at the end if it done in the same conversation. Thus only has influence on the cacheability of the original agent prompt, but not of subsequent tool calls.

https://www.nayuki.io/page/creating-a-qr-code-step-by-step

This is an interactive guide that will break down the process for your specific QR-code.

In the basis we seem to agree. Note that I am not trying to discourage helmet wearing (nor for governments to do it), just arguing against making it mandatory or even officially advised (for healthy adults) to wear them. Actual cycling safety is in numbers, more than in individually taken measures. This is all discussed in way more depth on reddit btw [0].

> but as a simple thought exercise on your argument

I realize could have written the sentence you respond to better, I should have written "and [mandatory helmet wearing] reduces perceived safety", also I said "should" in the sentence preceding the one you quoted, but I should've said that the NL ones ARE against making helmets mandatory for exactly the reasons I specify (and that my opinion is that other rights' organizations SHOULD be against it). Quoted directly from tbe website of the, quite well-regarded and not off their rocker, Fietsersbond [1] (under the header "Veilig gevoel?", translated by kagi):

    The Fietsersbond (Cyclists' Union) isn't against wearing a bike helmet. If you feel confident, you cycle more safely. It can be wise to wear a helmet in high-risk situations, for example, for seniors on e-bikes. Unfortunately, it has been proven multiple times that forcing people to wear a helmet actually backfires. People start cycling less.
    A helmet mandate makes cycling feel more like a dangerous activity—something you should be afraid of. Getting around by bike also becomes more complicated. After all, what do you do with that helmet when you're not wearing it? And what happens if you forget the helmet or if it gets stolen? These are all factors—whether justified or not—that make choosing a bike less convenient.

I wanted to react to your car/seatbelt point, but I realize now you are the same person arguing about what constitutes starting points in the sibling thread. I don't mean to spread FUD and I also disagree that this is indeed FUD. I'm sorry that Austria is not as nice a place for cyclists as you would like it to be. I hope with this oil crisis you will find a way to foment some change re the emancipation of cyclists in your locality or even country.

[0] https://old.reddit.com/r/fuckcars/comments/ut5fcx/why_is_thi...

[1] https://www.fietsersbond.nl/helmplicht/

This is btw also why cyclist's rights organizations (e.g. fietsersbond in NL) should be _against_ mandatory use of helmets. Helmets make it less convenient to cycle and reduces perceived safety, in turn reducing the amount of cyclists and as a result _actually_ making cycling less safe (and the vicious circle ensues).

Even only suggesting that it would be beneficial to use a helmet has this effect apparently, hence the organizations are only willing to state that they are "not against the use of helmets".

Just an interesting second order effect I think. You want to always be careful to optimize for the absolute number of safe rides, and not solely for the relative number of safe rides that might significantly reduce the absolute number of safe rides.