I don’t know about firstest, but he was definitely firster. That’s why they call him a founding father, not a founding fathest.

Silicone isn’t what makes parchment paper heat-resistant (and isn’t even used on most standard parchment papers). Cellulose pulp is treated with sulfuric acid to cross-link the cellulose molecules, making them more chemically and thermally resistant, and the result is parchment paper.

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.

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.