If there's one issue, ever, that you should be at least a little "both sides" on, it's this one.

There's no way you can honestly argue only one side of this.

If you do, do it for Jordan Klepper's wit. It's truly impressive how fast he comes up with these and how deft he is at it.

I could do it in writing over an hour. He does it on the fly in seconds and is able to manage the conversation at the same time. It's incredible.

I was in M2-XFE. That whole experience certainly taught a lot about the power of narrative and propaganda. And the later blockade showed what leadership failures look like.

We always had the advantage in that blockade, and could have stayed there for another year had the allies stuck together. Or we could have executed real plans to break them and end the war. Instead we did the worst of both.

the land they stole.

Do you consider that all of Israel?

Haven't they done it twice before? Something like 2006 and 2014?

They refused to respond to an Australian government investigation. (Because Elon fired the two people who interfaced with Australia.)

The fine is not directly because they haven't cracked down*, but because they couldn't competently answer if they're handling it at all.

(* and they've probably fired enough trust and safety people that they're also having trouble there, but that's not exactly what the fine is for.)

Wanna bet? There are ways to frog in a boiling pot this. And chrome isn't the only browser that will support blocking Firefox. (They'll argue Chromium is not Google, only Chrome).

As a software dev, I don't think there really is a better way. One thing you could do to avoid this is to install a second drive and boot to completely different OSes. You could boot to a Linux drive for personal stuff, and only use Windows for gaming.

These gaming companies are pretty aware that they go bankrupt if they either get a reputation for abusing anti-chrst data OR are full of cheaters. They have some incentive to use data ethically. But it's still a good thing to keep an eye on.

Probably Netflix, YouTube, and streaming apps first. I'd say banks, but banks are slow. Games won't take long. If there's not enough blowback it'll spread to every website that uses captchas today.

I'm not really in favor of a wealth tax. Maybe, if we really need to claw back our mistakes, but I think there are better approaches.

A tax on loans based on wealth seems great though. If you have the wealth, why are you borrowing? What are the legitimate uses of secured loans?

Capital gains taxes should be higher than payroll taxes. Always and forever.

Marginal tax rates exist for a reason, and it's absurd that we stop progressive taxation after $700k. The difference between making $800k/year and making $15m/year is ridiculous. At $800k/year you at least want to make the business last for a decade. After you cash out for $15m in a year, are you really accountable to anyone?

https://takeout.google.com

Download your data while you still can.

You can get an old version of the software without the features blocked.

On the Fediverse, you can go to a different instance.

Yet.

https://nebula.tv/videos/legaleagle-why-trump-hires-terrible-lawyers-a-ranking

Documentation tends to be "you take what you can get" on both sides. Are you going to turn down a PR because there aren't supporting docs? That's a good way to drive off developers too.

Generally someone who is annoyed with having to figure it out is the one who writes the documentation.

I forgot to mention Mumble as an example. It was many years ago, so hopefully things have improved by now, but the dependencies and setup for that were insane. I felt like I'd made a mess of my primary OS by the time I was done.

He forgot some of the biggest reasons.

• A larger codebase is generally just harder to work on. A more established product with more users tends to be larger.
• More popular projects with many users tend to have developers that don't welcome new contributions. The investment required for a new developer to make an initial contribution is huge. Things like setting up the development environment and the stack of technologies and understanding the basic architecture are significant barriers to entry. Existing developers tend to not care about reducing that burden. After all, everyone who's *actually *contributing to the project is already over that barrier, right?

Developers, open source or otherwise, should generally be excited about people "taking their jobs". Because you're going to have churn of developers over time, and if you're not bringing in fresh blood, then your project is eventually going to die. Do you really want to maintain every project you work on for the rest of your life? Encourage new blood. Do what you can to accept new ideas and directions unless you have very good and explicit reasons not to. If someone has a sightly different vision and is willing to hop that initial barrier and is willing to put in more work than you, don't undervalue that. Be willing to compromise a little to bring in a new developer. Sometimes you have to say no, but consider that you're saying no to a person who wants to volunteer their time to do work for you.

On the other hand, there are tons of people who say they're eager to work on your project. You invest a little time into them, they provide nothing, and then vanish. It's easy to get jaded when you keep running into people who are more words than action. Be very careful what you promise you'll do, and if someone invests their time to help you, try to actually do what you said you would.