But that's not what TypeScript does. The joke in the meme doesn't really even make sense.
A better analogy would be you have a basket that's explicitly labeled "Fruit" and TypeScript complains if you try to put laundry detergent in it because you said it's supposed to be a basket of fruit.
This meme was clearly made by someone who doesn't use or understand TypeScript.
I prefer just calling everything I eat the flesh of whatever it came from. Tomato? Flesh. Lettuce? Flesh. People? Flesh.
"Allegably"
I've tried to make this argument on the more extreme political communities and the arguments supporting a strike ranged from "everyone would blame the rail companies" to "the damage to unions is worse" to "all those people without jobs would rise up in protest to support the unions" to "it wouldn't be that bad, it's being exaggerated by the corporate media."
It shows just how privileged those people are to actually think that when people who are already living paycheck to paycheck, rationing insulin to survive, and barely managing to feed their families suddenly lose their income, can't get insulin, see food prices double, and can't even drink the tap water anymore because of a "rail strike", they're going to understand the nuance of the situation and blame rail companies for not giving the workers sick days.
That's not really a solid argument. Blocking is likely implemented as a very tiny piece of what is already very likely a massive table join operation. Computationally, it's likely to have as much an impact on their compute costs as the floor mats in your car have on fuel efficiency.
Everyone already sees different content. It's an inherent part of Twitter. It's not a static site where everyone sees the same thing. You see the tweets of who you're following, and don't see tweets of those you've muted. All that filtering is happening at the server level. Any new tweets or edited tweets or deleted tweets change that content too, which is happening potentially hundreds of times a second for some users.
Anyway, caching would be implemented after a query for what tweets the user sees is performed to reduce network traffic between a browser and the Twitter servers. There's some memoization that can be done at the server level, but the blocking feature is likely to have almost no impact on that given the fundamental functionality of Twitter.
But you can upvote and comment. OP didn't specifically say posts, just increases in upvotes and socialization
I had the Samsung Note 2 back in the day. I installed a custom bootloader and OS that worked fantastically. I had GPS issues, and all the guides I read said I have to reinstall Samsung's OS, get a GPS fix, then reinstall my custom OS.
I made the mistake of installing a newer version of the Samsung OS which installed Knox and locked down my bootloader. I was now locked into an old, insecure Android version with no possibility of ever upgrading because Samsung abandoned it.
From that day on, I vowed never to buy another Samsung product again. Screw them and their anti-choice bullshit.
That's what I said though.
Your ISP can't see what you're downloading if you encrypt, but the IP (intellectual property) enforcers still can if they're participating in the torrent. Then they find out which ISP that IP (address) belongs to and sends them a letter saying "we caught your subscriber downloading XYZ illegally."
However, at least one US district court has ruled that just catching an IP address downloading a torrent illegally isn't proof that any particular person illegally downloaded the IP (intellectual property). As a result, some ISPs simply ignore the letters the IP enforcers send, while some of the bigger ones count "strikes" against the subscriber with that IP address.
If you use encryption (I always change the settings from "prefer" to "require" encryption on every install), the ISPs literally can't identify what you're downloading.
So the IP enforcement companies send the ISP a letter saying "this IP was illegally downloading our stuff. We don't actually have proof, but trust us and punish them."
Big surprise, a ton of ISPs just ignore them.
Edit: to be clear, I'm only saying encryption prevents your ISP from seeing what you're downloading. IP (intellectual property) enforcers who participate in the torrent are the ones who inform your ISP, but their letters to the ISPs have no teeth. Some ISPs care, but a lot just ignore the letters. You still definitely want to use a VPN for all public trackers.
During computer learning in a computer lab 15 years ago, I figured out that the student passwords were sequential, so I could easily guess other students' passwords. If I logged in to their account while they were logged in, they would get booted and I'd hear the inevitable "Mrs Teacher! It says my session expired!"
I did that 2 or 3 times over the course of a few minutes before I got caught. The vice principal rambled on and on about how I was "disrupting learning" and how I "should be suspended for this" before finally telling me, "my mentor taught me a really important lesson. If your students don't hate you, you aren't doing your job."
What a horrible piece of shit.
But those "people" (i.e., the clones of Tuvok and Neelix) never existed in the first place.
The main issue in this episode is that two sentient beings were effectively destroyed against their will to create a new sentient being. To rectify the issue of two sentient beings being destroyed to create one new sentient being, the one was destroyed against his will.
But a clone of Tuvix would not come into existence at the expense of any sentient beings besides the original Neelix and Tuvok. It doesn't solve the original "we're killing a sentient being to bring back our friends" problem the original Tuvix caused, but it doesn't create new problems either.
We could just transporter-clone and combine Tuvok and Neelix into Tuvix in one shot. The net effect is one new being, Tuvix, at the expense of nobody. Doing it by cloning Tuvix is just an added intermediate step.