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?

Removed by mod

Removed by mod

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.

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.

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.

It’s something like

Help > About > Check for updates

My 7.6.0.3 won’t auto update. Says there are no updates available. I’m trying a manual install.

Advertise. And Geocaching is a great way to do it.

I’d recommend a post in the community encouraging people to put a url and/or QR code into some geocaches. Maybe with a sticky at the top of the community that explains what Lemmy is.

Consider the point of view of a person who finds the QR code in the geocache.

https://old.reddit.com/user/serinus

They can sell colors and themes as DLC! Cosmetics for your home!

If you can open it, they can open it. There’s not much of a point if it’s something you can undo.

I would make sure the firmware can’t be updated. Uninstall the Hue app for sure.

After they make the change, someone with an old Hue bulb should go to the Consumer Financial Protection Bureau.

Making this decision retroactive is clearly false advertising and anti-consumer. I don’t really give a shit what their terms of use were.

They can do what they want with their future bulbs. The old ones need to be grandfathered in.