Restarts in a server between dB updates that in a sane world would be txns I meant (e.g update A, crash so don't update B). Anyway, in postgres they're pretty cheap in the absence of actual conflict -- more expensive if you have actual cinflicts, obvs.
Well you might also need to run some arcane incantation to remove quarantine bits, too. And it'll only work if it's actually been ported to the m-series chips, of course. And sometimes you just need to compile the whole god damn app yourself anyway. But sure, caveats side, you can run anything you want on macos that runs on macos. As long as you're not using a company-issued device and are forbidden.
Yeah but majoras mask earned that right
Actually transactions can be a secomd-layer safety-net for single-responsibility writers to ensure rollback on eg restarts and consistency on loadbalancer redecisions without having much of an impact on performance, and data integrity is usually quite important.
Oh hey I do this in jwts too.
I need to encode a lot of permissions
Don't ask
Have you tried disabling all local Trojans and seeing if that helps?
Because it's absolutely not a real paper lol, it's a bait
They absolutely do give wrong answers, as in this classic meme that's way off because of floating point: 
I have never understood how a dev can be comfortable pasting a valid jtw Auth token into a random website to decode it, when there are several very good cli tools that will do this for you locally, faster, and much more securely
One huge advantage of a rolling distro is that generally only one thing can break at a time :)
It was a good thread here too: https://lemmy.world/post/43447694
I guess the nature of the fediverse means that some post duplication is necessary for exposure coverage, lol, so who am I to accuse a repost of not suitably linking the source.
Depends on your magical mythos, I was thinking more Earthsea than D&D