You did 200k years. You need to do 200k years as seconds (the 6.311e12 they mentioned). Their math is right.

Not sure why you’re acting like they claimed to invent the logarithm, either…

There’s a lot of common patterns, but you have to understand how URLs work. You have to recognize which URL parameters are tracking ones or even just might be tracking. And that means you have to know how they work and that takes a moment.

In brief, URL parameters start after a ? in the URL and are formatted like key1=values&key2=value2. You can’t usually remove all parameters because not all are tracking. To further complicate things, URLs can also have an anchor starting with a # character which will be after the URL parameters. You often don’t want to remove that (though theoretically the anchor could in fact contain tracking details).

It’s often trial and error to see which parameters you can remove. I do this a lot since I write a lot of technical documentation. Clean URLs make the documentation more compact and less likely to break. It’s not just tracking stuff, but sometimes you need to remove temporal data that makes a page display data from a specific time when you want it to just default to the current time (etc).

Some of these I get, but I don’t get the T9 thing. T9 was so bad! It took ages to type many words. Today’s predictive keyboards are miles better.

Also, no software updates? Sure, every now and then there’s a shitty update, but most updates are great. New features and especially bug fixes are amazing. Used to be that if something had a bug, you just had to deal with it. There’s no guarantees it’ll be fixed today, but many companies do fix their bugs at least eventually. The ability to iteratively develop is huge for software quality. These days, unless you’re developing something that absolutely cannot fail (like a mars prober or radiation therapy machine), it’s widely agreed upon that iterative design is superior to “waterfall” design of trying to plan it out all ahead of time. Part of why is so you can get feedback continuously instead of only after you’ve committed to months of tech debt.

Not to mention that this sub is unapologetically pro LGBT while practically every authoritarian government (including particularly those that tankies support) has been anti LGBT. eg, China prohibits same sex marriage and adoption, while forcing trans people to get permission from their family to transition (spoiler alert: they ain’t progressive).

Democratic socialism with actual equality for all (which goes hand in hand with the root issue socialism is supposed to solve) makes sense and is reasonable. But that’s not what tankies support. They’re defined by support for authoritarian states that have nothing to do with equality except pretending that they care about it.

I don’t think that makes sense if you’re worried about defederation. Porn instances are particularly at risk of being defederated from (and thus you potentially can’t interact with large communities).

Let’s not pretend people acknowledge warnings, though. It’s a popular meme that projects will have hundreds of warnings and that devs will ignore them all.

There’s a perfectly valid use case for opinionated languages that don’t let you get away with that. It’s also similar to how go has gofmt to enforce a consistent formatting.

Honestly, I’ve been using Go for years and this unused variable error rarely comes up. When it does, it’s trivial to resolve. But the error has saved me from bugs more often than it has wasted my time. Most commonly when you declare a new variable in a narrower scope when you intended to assign to the variable of the same name (since Go has separate declare vs assign operators).

That’s misleading because that’s not that often. Most of the cops are beating up innocent black people, shooting your beloved dog, and performing no knock warrants on the wrong house.

And I’m upvoting you because while I completely disagree with your comment, I’m in gratitude of your effort and we will always need new comments.