The year is 2025. A massive geomagnetic storm has fried all forms of technology, wiping out hard drives and solid-state drives alike, and scrambled all backup tapes. Coincidentally, a new plastic-eating bacterium has munched on all the compact discs without anyone noticing.
Humanity will rebuild…
The computer chip manufacturing pipeline has been restored, but there is no software to run them. In a dusty office previously owned by a lawyer from a long-defunct dotcom, a treasure trove is discovered. Five metal cabinets filled with paper: the printed Linux kernel source code, in 5-pt comic sans font. One brave soul will enter to transcribe. Mistakes are not an option. We all thank you for your sacrifice.
There was some scare in lemmy development circles recently about script injection vulnerabilities. The various apps and frontend developers “solved” the problem by peppering untrusted user input with escape sequences all over the place. User submits post? Escape title! Receive new post from a federated instance? Escape title!
Obviously if you escape the title twice and display once, it will show up weird. The problem is that the various devs haven’t agreed yet which parts of the messaging protocol are supposed to be already escaped and which are not. Ideally all user input should be stored and transmitted in raw form, and only escaped right before displaying. But due to various zealously-cautious devs we get this instead:
Yup yup! In a just world, if you have 100,000 workers at a factory, and then they get replaced by robots maintained by 1000 robot technicians, you should have ended up with a Star Trek utopia where 99,000 people now don’t have to work and can pursue culture and passions. In the real world, the factory product price gets halved, the technicians get paid 10x what a worker used to get (20% of total revenue), and the factory owner gets 80% of total. The former workers are now jobless, homeless, and penniless and can’t afford the product they used to make.
They tell us “Replacing jobs is OK! We’ll invent more new kinds of jobs, as old obsolete jobs free up labor. Everyone will be better off!” but the new jobs are mostly “telemarketer”, and “tech support scammer”, and “ornamental hermit” at factory owner’s mansion.
But all that still doesn’t convince me we should be smashing the robots as a job protection scheme. I wish there was a way to keep the automation and have the Star Trek utopia instead!
You are on the side track in scenario A. You die if you pull. Ironically, you’d be killing yourself. The dice are to make the two scenarios not equally likely.
Good question to ask, since specifics of selection process may affect the decision outcome! Other variants include growing humans in a vat from scratch on demand, using Star Trek transporter clones, or abducting the necessary number of people from a pre-selected list where your name happens to be the first one. For now, imagine the potential population as the 5 billion living cognizant adults.
as X approaches infinity, the difference becomes negligible
It may be negligible to the 4.999… billion adults sleeping comfortably and securely in their beds tonight, but the problem presupposed that you have already been abducted. It remains underdefined whether you refers to you the specific person reading this meme, or a more general you-the-unfortunate who has been chosen and is now listening to this on the headphones.
I want people to be able to report bugs without any trouble.
Thank you for being aware! I’ve experienced this on github.com. I’ve tried to submit issues several times to open source projects, complete with proposed code to solve a bug, but github shadowbans my account 6 hours after creating it (because I use a VPN? a third-party email provider? do not provide a phone number? who knows). I can see the issue and pull request when logged in, but they only see a 404 on their project page even if I give them a direct link. I ended up sending them a screenshot of the issue page just to convince them this was even possible. Sad to hear gitlab does it even worse now by making phone mandatory.
The paper doesn’t use an actual screen, they only have the detector D_S that they move up and down to record the coincidences. I simulated what the monkey would see had there been a screen in place for the purpose of the meme. I copied down the datapoints from the graph and simulated 100,000 photons hitting the screen with the probabilities indicated by those points. My javascript pastie is available here: html.cafe/xcd2a5ed3?k=19f51bff26c65bcf253ee5257a5… Importantly, the monkey can never see images 4 and 5 on the physical screen - those can only be displayed on the computer. The monkey will only ever see image 3, which is the sum of 4 and 5.
With distributed hash tables it is manageable. You do something like “store three copies on three peers” and as long as one of them is online the post is accessible. This is actually better than the way lemmy does it now. In principle each lemmy server stores the posts from its communities, and a copy of each post from communities its users are subscribed to. But since all instances are federated so well, in practice each of the 1000 lemmy instances stores a copy of almost every post ever made. That’s like 100GB x1000. With a DHT, the amount of space used on each user’s device is on average the amount of posts one user makes x3, no more.
The fractions don’t help me when I go to the grocery store and unit price of one bag of nuts is “per pound” and the unit price of another is “per ounce”. You’d better be good at dividing by 16 in your head if you want to price-compare! And you’d better be good at remembering how many fluid ounces are in a quart when you go to the olive oil aisle (hint: it’s not 16).
If 6 is rolled, then P(X|R=6) = (N-1 choose 9)/(N choose 10)
Might as well reduce that to 10/N to make the rest of the lines easier to read.
If you don’t flip it, you have a 2/3 chance of dying.
There is also a chance that your switch is not connected and someone else has control of the real one. So there is an implicit assumption that everyone else is equally logical as you and equally selfish/altruistic as you, such that whatever logic you use to arrive at a decision, they must have arrived at the same decision.
No matter what your goal is, given the information you have, flipping the switch is always the better choice.
That is my conclusion too! I was surprised to learn though in the comment thread with @pancake that the decision may be different depending on the percentage of altruism in the population. E.g. if you are the only selfish one in an altruistic society, you’d benefit from deliberately not flipping the switch. Being a selfish one in a selfish society reduces to the prisoner’s dilemma.