CocaineShrimp

They're already making suggestions. Got one this morning telling me I can ask it for updates on Amazon packages.

Speaking of which, anyone have any suggestions for better smart speakers?

She's a liability to them. She holds so much power over them; and all she has to do is run to the media and give them "the truth" ("the truth" being what everyone suspects anyway. Doesn't matter if it's actually true or not)

We all wish you and your country the best of luck 🫡. I know Canada will be there to help

I don't even need to read the article. Yes - capitalism hijacks everything for the sake of more money

Next headline at the end of this quarter:

"Procter and Gamble sees record profits for the billionth year in a row!"

Probably image. They don't want to be associated with something they think the public will perceive as negative. Bitcoin was vilified initially because "criminals were using it" (but let's forget about the part where cash is also untraceable). So they prob don't want to be the "credit card company that supports pedophiles and rapists"

Looking through the docs n' stuff, this is what I found:

• Updating Guide. Just basic steps, similar to what I explained above; but with commands to run.
• Backing up and restoring
• 2.0.0 Change Log. Unfortunately they don't include any notes about how to upgrade

I wasn't able to find any additional instructions on how to update other than the expected generic steps (docker pull or pip install -r requirements.txt). So my guess at this point is that they have scripts built in to check the version and run upgrade scripts as needed

I haven't gone through your specific case, but generally what I do when doing a major update with potentially breaking changes:

• Read the upgrade guides, if they have them. Some devs will put them out if they know their users will encounter issues when upgrading. If they don't have an upgrade guide, there might be some in the change logs. Going from 1.17.1 to (assuming) 2.x.y, check the change logs at 2.0.0.
• Backup everything. I'd recommend doing this on a regular basis anyway.
• (If you're running it in a docker container) Setup a second instance, restore the backup, then run the upgrade. You'll be able to check to see if it breaks at all. If it works, you can just destroy the old one and use the new one
• (if you're not running it in a container) with the backup, try upgrading. If it breaks, you should be able to uninstall & reinstall the old version, then restore the backup

~~What's the difference between Lemmy and Piefed?~~

Nvm. Found exactly what I was looking for here

Just let it die already....