database schema improvements, which is a particularly tricky thing to work on
Not, if you know what you're doing.
I dont like AI, I wish I could go back to the world before it, but I cant.
You do know that you can use LLMs to get inspiration and suggestions but then still implement those things by hand? Which is also a great way to make sure it doesn't change something else in the background. Also, if you use Claude like you've used StackOverflow and Google before, you don't even have to mention it as a Co-Author.
[!NOTE]
Upgrading to Paperless-ngx v3 can only be performed from version 2.20.15. If you are running an older version, please upgrade to v2.20.15 before proceeding with the v3 upgrade.
EDIT: Two advantages of this setup for me: I can easily drag&drop emails from my other email accounts to this "archive" account in Thunderbird. And once I want to "seal" an archive folder, I can gzip the underlying mbox file and make it read-only (dovecot needs to be configured to store mails in mbox files).
Eh, there's not really a better/worse between Gitea and ForgeJo. Gitea is targeting business customers, ForgeJo is targeting the open source community.
And yes, it's often slower than commercially available search engines - but it's completely free, without trackers, and it's combining results from various different engines. I can live with that.
Do you know about the MAILTO= lines in crontabs? That's exactly what they're there for. (And your script needs to output error messages on failure, of course.) You'll need a local mail forwarder like ssmtp or exa, though.
That's what I settled for as well. Keeping my *.kdbx file in iCloud, doing nightly backups to my NAS, and using Strongbox as a client (there's also KeePassium with similar features) - which beautifully integrates into Apple's AutoFill API, so it feels native - i.e. as if you're using Apple's Passwords app. And I can access all passwords from Windows using KeePassXC as well.
If you host it on a VPS and stop paying the invoices, it'll go down anyway. However, AFAIK, Bitwarden client apps cache all passwords - so your family would still be able to access them, but there would be no sync back, of course.
Have you considered using something like a KeePass database on a shared drive? Most modern client apps can sync changes seamlessly and there are browser plugins for all the major browsers.
Samsung will, at its option, either: (1) repair or replace the Product with new or refurbished Product of equal or greater capacity and functionality; or (2) refund the then current market value of the Product at the time the warranty claim is made to Samsung if Samsung is unable to repair or replace the Product.
Yeah, probably. But this doesn't help much when the damage is already done, i.e. people have already commented bad things. And might even entice people (that might've downloaded it) to upload it again. Also, not sure whether this works as easy on e.g. TikTok.
Filming by itself isn't illegal in Germany, but publishing the footage without consent of everyone in the video is. ("Recht am eigenen Bild") Don't know how this applies if the perpetrator is from the USA and publishes the recording there, though.
And even if - good luck in suing someone from the US while you're still in Germany.
Two things that aren’t changing: every Strava athlete can still access and download their data for free, at any time – and wearable and device integrations are not affected.
Tell that to some states in the US where there's a thing called "one-party consent", i.e. if one party knows about the recording (which the wearer obviously would), it's legal.
Not, if you know what you're doing.
You do know that you can use LLMs to get inspiration and suggestions but then still implement those things by hand? Which is also a great way to make sure it doesn't change something else in the background. Also, if you use Claude like you've used StackOverflow and Google before, you don't even have to mention it as a Co-Author.