is there a science fiction novel where there are many parallel worlds but people in some of them use this knowledge to covertly A/B test major decisions (eg policy) across worlds
answer: a whole lot
i guess a bunch of these are more “personal choice” whereas i’m thinking more like meta-world scientists being able to run controlled experiments and write papers about the parallel worlds
whereas from the perspective of the controlled worlds it’s more as if they’re being run by the “lizard people”. where lizard people are the corresponding people from the world “advising” themselves what to do. like origin boris johnson’s avatar advising the forked boris johnson
forked worlds always eventually develop conspiracies about being run by a secret cabal of outsiders because it’s true — they’re run by the origin world. unlike TVA, forked worlds don’t get destroyed and just keep living in mayhem forever. the protagonist is in one of such worlds
they protagonist manages to sneak into the origin world and secretly kills their origin self, stealing their life to bring down the system from within. they organize resistance by orchestrating similar replacements. more and more people in the origin world are from forked worlds.
as the hijackers spend more time organizing in the origin world, they witness effectiveness of the approach. diseases are cured. catastrophes averted. all thanks to the info gathered from the parallel world experiments. after some infighting they stay and keep status quo.
naturally, they find out that the origin selves they killed were not the true origin world selves, but themselves from the forked worlds who already had the same exact realization and decided to uphold the existing order. or at least that’s what the origin world conspiracies say.
i’m probably describing some really wacky doctor who episode
this thread was inspired by reading about the filibuster
• • •
Missing some Tweet in this thread? You can try to
force a refresh
if you’re curious, i’m trying to fix this bug in react. it comes up when using code splitting with react router <Switch> and other cases. it’s been reported a while ago. it’s easy to work around so it wasn’t urgent but i wanted to look into it for a while. github.com/facebook/react…
the submitter of the issue was kind enough to send a pull request with a minimal failing test encapsulating the issue. this alone has significantly increased the chances that i would be able to find the bug. (when in doubt, send a failing test!) github.com/facebook/react…
one of the most obnoxious traits of the “web3” community is labeling existing web experts as “web2 people”. it’s disingenuous because web expertise is usually related to frontend, and “web3” apps, from what i understand, still build UI the same way — HTML, CSS, and JS.
from what i can tell, “web3” is a different approach to building the backend and a different set of values/philosophies. if y’all hope to attract the frontend expertise you desperately need to make your stuff usable, consider not making asses of yourselves by labeling outsiders.
the “web3” branding is, in my opinion, genius and designed to be polarizing. it implies obsolescence and induces FOMO. but it’s just that, a branding. unless you literally reinvent the browser, don’t get too carried away excluding people :)
i have questions about crypto, web3, and the surrounding ecosystem. i’m gonna thread these. please feel free to reply! but don’t start arguments and fights with other people who reply or i’ll use the banhammer.
1. what is bitcoin’s plan to solve its energy consumption problem? is that on the radar of the team/community? is that considered a non-problem / “worth it”? asking specifically about bitcoin
2. why is there a lot of skepticism around ethereum’s move to PoS? is it because it’s been continually pushed back, or is there skepticism that it will work at all? both?
properly trying VR for more than a few minutes. got myself a quest 2. what is the coolest/whackiest shit i can do with it? i like music, trippy stuff, idk
maaaaan the whole setup process with a virtual “boundary” and a lo-fi see-through of the room in black and white is already trippy as hell and i am here for it
i am surprised to the degree to which the “slightly wrong” virtual ghost fingers don’t bother me. i believe this
a hundred things i learned working on the react team @threadapalooza
1. every few years your audience changes. new users don’t appreciate problems of the past bc never seen them. old users burn out or lose excitement. new users have different reference frame, learned in diff ways, you might be their first programming env. plan accordingly.
2. when you fix a problem you better really really understand the problem you’re fixing. take a few steps back and reintegrate new knowledge into the design. should it change the design? it’s like fighting a hydra: solving a problem in the wrong spot spawns 10 new problems.