There really isn't any maintenance besides the occasional update. Setup was also effortless as I've got Caddy setup to reverse proxy containers in my network. I simply define what the subdomain should be for the container and where it can reach it and that's all there is to it.
I've got Vaultwarden setup on one of my servers via Docker and I've got nightly backups of my vault to Dropbox via docker-volume-backup[0], which works wonderfully.
I personally choose to self-host because I already have the infrastructure for it, so might as well put it to good use.
There are devices out there with vulnerable TEEs (trusted execution environments), where DRM operations commonly happen. You can then extract L1 keys from those environments - for example with the Nexus 6[0] NVIDIA Shield[1].
Hey HN! A few months ago I wrote Constellation to provide updates in my closed source tools. See more about why it exists and how it works in my blog post linked below.
I started on a Navidrome/Subsonic/Plex/Jellyfin replacement for my bachelors thesis this year - I haven't had the time to actively work on it since starting work but I really want to as I've been daily driving it for a while and it's lacking in quite a few areas.
Just as a warning, not even half of the stuff on the landing page are actually present in Coral but they absolutely will be future. The next thing on the plan is to re-write the UI in React Native so I can take Coral with me on the go.
https://coral.nectarine.sh (the download page is inactive, but you can grab a release from the GitHub page if you're so inclined)
I'm curious, what did you find lacking in Navidrome/...? I'm thinking about installing one of those pieces of software to serve my media and I'd love to know why you're building your own (if the answer isn't "for fun" :) )
0bin, another popular Pastebin alternative, solved this problem by encrypting the paste on the client and embedding the key in the paste URL - so the server had no idea about the data being posted.
Presumably they’re placing it in the # part of the url, which isn’t passed to servers by browsers. Now, of course, the client could still exfiltrate the key with client side JS, but that would be noticeable to anyone that wanted to check.
I honestly think we're going to see a lot less of this going forward. Recent generations were very hot and both AMD and Intel are now basically designing for the thermal limit (90-100 °C). I doubt there's going to be a lot of 13900Ks or 7950Xes that will last 10 years.
I moved away from NextDNS due to how slowly it picked up DNS changes, it would take hours for changes to propagate - and there wasn't any way to force it to update without manually creating DNS entries. I installed PiHole on one of my servers and Tailscale makes it available on all my devices - I couldn't be happier.
