Your guess is incorrect. I'm keeping well away from polarised politics as well as anti-scientific and anti-intellectual fringe views.

Please step away from the lathe

Because one kind of thing helps people and the other kind of thing inflicts pointless cruelty on the innocent.

And the regime loves pointless cruelty.

Garfield Minus Garfield has the same bleak sense of desolation as Goya's "The Dog". Just wonderful.

I doubt they think much, in general

OK, fun. What can we do to mitigate this until it gets patched?

Serious answer, don't use Safari. Use a browser that properly separates webpages into isolated processes so that this kind of cross-site read is not possible.

There’re no other browsers on iPhone. Every iPhone browser is a reskin of Safari. They’re in theory supposed to allow other browsers in the EU, but AFAIK it has not happened yet.

Then don't use an iPhone until it is patched.

What about turn JS off on your favourite iOS browser?

That wouldn't prevent possible malware apps using WKWebview from getting out of the jail they are running out right?

Yes, I agree.

However I also expect that Swift-compiled apps can do this without a web browser component.

It’s a different threat model though, having installed a malicious app vs browsing a malicious site.

Which is the reason alongside telemetry I tend to favor using websites over apps.

Having said that there are apps that are considered mainstream and not malicious by the general population but can become a convenient backdoor for, say, a state actor.

No need to turn JS off. Turn on Lockdown mode which disables Javascript JIT and WASM, which might be enough

It’s not.

Brave on iOS can limit Javascript to trusted sites.

So could this hypothetically open a mail client on your iPhone and read your emails?

No, it doesn’t do cross-address space attacks.

God I hate Apple sometimes

Will that work? Isn't memory treated in a unified way between processes, at some point?

Processors are not supposed to speculate across ASIDs

It will work unless someone forgets to add a public suffix into the public suffix list (as described in the FLOP paper). Both of these attacks target virtual memory pointers.

From the FAQ:

> While FLOP has an actionable mitigation, implementing it requires patches from software vendors and cannot be done by users. Apple has communicated to us that they plan to address these issues in an upcoming security update, hence it is important to enable automatic updates and ensure that your devices are running the latest operating system and applications.

I wonder if Lockdown Mode would help?

IIRC, it disables jit and webassembly, so i think yes

I'm generally in favour of the joycons as a concept. They make multiplayer party games a breeze.

But the execution in the Switch 1 is flawed. They're on the small side, and generally fiddly. If the joycons for the Switch 2 are larger and just more ergonomic then I think it'll be a win.

EDIT: the joycons also being little motion wands was also quite good. You don't need a separate accessory like on the other consoles. Overall the joycon is a neat little package of functionality, if imperfect.

> you'll quickly learn you can't use it to block political ideology from the DM

That's like, not true at all. The X card is exactly for that purpose, the GM doesn't get a special exception from the effect of the X card.

As a GM, if a player reaches for the X card for any reason I'm obliged to stop and listen.

I'm curious what exactly you mean by "political ideology" in this context. Can you give a concrete example of the kind of thing that makes you uncomfortable?

I believe you, but that's not the case everywhere. I've had DMs who have put drag shows in our game as part of tavern entertainment, for example. Even though I have no problem with them in real life, I have no desire to see them in my fantasy game because it just reminds me of contemporary culture war shenanigans. When questioned on it or asked if we could not do that, I've received nothing but pushback. Stuff like that.

Not every group is right for every person.

But the big thing is this: it's not your fantasy game. It's the shared fantasy game of you, the other players, and the DM.

> Not every group is right for every person.

In the context of an X-card discussion, that's hilarious.

"Touch the X-card, but only if the group agrees on why the X-card was touched. Otherwise, find new group"

turns out the real x-card was the group itself :)

This is true of every voluntary social thing.

yes, exactly, that's why the X-card thing is just useless performative theatre

I know it's a typo but this:

> what more could a shell?

Is quite good. It could almost be the tag line for fish shell.

My hot take is that the allure of parser-generators is mostly academic. If you're designing a language it's good practice to write out a formal grammar for it, and then it feels like it should be possible to just feed that grammar to a program and have it spit out a fully functional parser.

In practice, parser generators are always at least a little disappointing, but that nagging feeling that it _should_ work remains.

Edit: also the other sense of academic, if you have to teach students how to do parsing, and need to teach formal grammar, then getting two birds with one stone is very appealing.

It is not academic. It is very practical to actually have a grammar and thus the possibility to use any language that has a perser generator. It is very annoying to have a great format, but no parser and no official grammar for the format available and being stuck with whatever tooling exists, because you would have to come up with a completely new grammar to implement a parser.

> It is very practical to actually have a grammar

I fully agree that you need to have a grammar for your language.

> and thus the possibility to use any language that has a perser generator.

See, this is where it falls down in my experience. You can't just feed "the grammar" straight into each generator, and you need to account for the quirks of each generator anyway. So the practical, idk, "reusability"... is much lower than it seems like it should be.

If you could actually just write your grammar once and feed it to any parser generator and have it actually work then that would be cool. I just don't think it works out that way in practice.