99.999% of the population of Earth will never be directly affected by either of those two things, so at the very least you're going to have to expand on how eroding the privacy of those 8 billion people will make their life better.
No we can't have nice things because of fascist lackies who use any excuse. If terrorists and pedophiles somehow didn't exist it would be spying or organized crime.
The Online Safety Act provides for Ofcom to develop its own codes of practice and guidelines based on the provisions of the act and public consultation (including with the platforms). It has an enormous amount of leeway in deciding how to implement the Act.
Ofcom has operational independence. Neither its investigations nor its enforcement actions are directly controlled by the Government. The Government does approve Codes of Practice but if it doesn't approve, it can only request modifications. It's still up to Ofcom to decide how to interpret and implement. Secretary of State interventions are, by convention, rare and subject to Parliamentary scrutiny.
I'd say that, at least with Tibetan Buddhism, there are things like deity yoga, wrathful and peaceful manifestations, Dakinis and Dharma protectors, Bodhisattvas, all are essentially theistic in nature. Adi-Buddha in the Vajrayana tradition is also a "primordial" Buddha, so it has many of the hallmarks of theistic religion.
This gives big bikeshedding vibes. I always liked the idea of semantic markup, but humans are messy and complex and we will always find ways to bring that chaos to utopian systems. Classes and IDs work fine most of the time. Documenting your styles is good practice. Using BEM or Tailwind has the benefit of adhering to a system and base classes that others can make sense of without much effort. CSS is OK. Our energies are better spent on more important things.
Tailwind solves this but not in the way you think!
The rise of React and SSG/SSR means there is a world where the classes are React components and the attributes are props.
Even for static pages, for DX you can use the same tooling as you are used to for dynamic pages. And something like NextJS can generate the static html.
And this makes even more sense for dynamic stuff like date pickers.
In this world you use utility classes because tags are too granular and components are the logical unit.
But if you are hand crafting the html then tailwind might be more of a pain. I am a bit undecided on that. I still have a soft spot for CSS Zen Garden.
It's schizophrenic. I have a shortcut called "What's the spa temperature" that ran fine for years. Of a sudden, now it can't match to it.
"Hey Siri, what's the spa temperature?" => "The temperature outside is 75°"
"Hey Siri, run the shortcut 'What's the spa temperature'" => "I'm sorry, I didn't quite get that!" (x3 repeat, of course, because I can't believe what's happening)
=> rename to: "spa status"
"Hey Siri, spa status" => "...yada yada... it's currently 81 and set to 93, please check back in 15 minutes" (that's the original shortcut that I'd put together).
Suuuuper basic stuff throughout HomeKit, Siri, are horrible. Renaming things doesn't always take, "I'm sorry, I'm having trouble connecting to the internet." Can't properly set an Airplay target by voice.
"Hey Siri, turn off the light!" => (iPhone hears it instead of HomePod) => "Did you mean master bedroom? Kids room? Guest room? Kitchen? Living room? Family room? Office? Dining room?" => cancel, cancel, cancel! :-(
I like that userland is kept separate from base as much as possible, but agree it could be even better. I do think the BSDs have more coherency than Linux on the whole. Would be nice if we could simplify things down even further, but I suspect it just becomes one giant bikeshedding exercise, which is probably why it's easier to just cling on to hier https://man.freebsd.org/cgi/man.cgi?hier
This attempts to hide inter-keystroke timings by sending interactive
traffic at fixed intervals (default: every 20ms) when there is only a
small amount of data being sent. It also sends fake "chaff" keystrokes
for a random interval after the last real keystroke. These are
controlled by a new ssh_config ObscureKeystrokeTiming keyword.
reply