I’m often surprised how little people talk about the iOS Orion browser on here and it’s ability to let you use both Firefox and chrome extensions. I’ve been using it for a while now and it’s been great. It’s a little bit buggy sometimes, but nothing that would make me switch.
My dad was diagnosed with multiple myeloma 2 years ago. His bone marrow transplant failed (frequent first line of defense) and he just finished CAR-T therapy a couple months ago. The initial side effects from the treatment were _bad_, but everything is looking good right now. CAR-T is really mindbogglingly insane cyberpunk stuff.
I had a close relative diagnosed with multiple myeloma 25+ years ago (I don't remember the exact year) who only lived for a couple more years. It was rough back then. I'm really glad to hear that there is much better treatment these days.
They don't detect if you're a bot or not; it just makes it more expensive, the idea being that doing $action 10,000 (or more) times becomes much more costly for the attacker, preferably to the point where doing $action (posting spam, creating accounts, etc.) is no longer profitable. It's probably more useful to see it as a ratelimiter than a bot detection mechanism.
Until, of course, the attackers reprogram their FPGAs and can solve challenges 10,000 times faster than a legitimate user. And since you can't request a user to have their phone toast itself at 100% load for 10 seconds, the attackers can solve it in micro/milliseconds for a sip of power.
Actually, this just uses SHA-256 hashing, which already has specialized CPU instructions (that browser WASM can't use) and ASICs.
They don't detect if you're a human exactly. What they do is they create a calculation expense that is negligible if there's one of you but adds up quickly if you're running a bot farm that needs to send out 10,000 requests a second.
So I click the button, my browser does a quick proof-of-work, no big deal.
But an automated script will have to complete that proof-of-work every time it encounters it, skyrocketing the cpu costs for the server.
This could be incredibly useful for me. Currently struggling to complete jobs with massive amounts of shuffle with Spark on EMR (large joins yielding 150+ billion rows). We use Glue currently, but it has become cost prohibitive.
Then mount FSX for Lustre on all of your EMR nodes and have it write shuffle data there. It will massively improve performance and shuffle issues will disappear.
Is expensive though. But you can offset the cost now because you can run entirely Spot instances for your workers as if you lose a node there's no recomputation of the shuffle data.
Is the shuffle the biggest issue? Not too sure about joins but one of the datasets we're currently dealing with has a couple trillion rows. Would love to chat about this!
Curious on this: "Atuin's sync keeps my history on all of them"
I just checked on their GitHub and it says "Additionally, it provides optional and fully encrypted synchronisation of your history between machines, via an Atuin server."
So you trust all of your shell commands to be stored on a server that you don't control?
