You could use tailscale or netbird. Alternatively, you can use a dynamic DNS provider which usually provide free subdomains, if you don’t want to pay for a domain. And even with all of that, Jellyfin doesn’t require HTTPS, although there may be clients that do (make sure you’re behind a VPN in this case).
I had a quick look and the AI features that are added:
They do look to be optional at least. I’d probably be a bit more concerned if the code was largely written with LLMs, given the large number of commits in what looks to be only a few months.
Effective as of the end of this sentence. This sentence I’m speaking right now. Period.
Almost as annoying is if they give you a single /64. Here’s an absurd amount of IPs but you only get one subnet. Thankfully, I’ve had nothing smaller than a /56.
Not the OP but:
FreshRSS interface is kind of ugly (probably can be tweaked). You can use third party RSS readers, but that ends up being almost as much work as installing readeck and the like.
FreshRSS doesn’t support OPDS or have any koreader integration, unlike readeck. These are essential features for reading on an e-ink reader, which is my preferred way to read longer articles in particular.
I think country TLDs don’t have WHOIS privacy protection if you care about that.
The risks of auto-updating now include “devs losing their shit” which has become increasingly common.
I like that matter provisioning requires verification of their certificate, but I don’t like that certificates can expire or the certificate authority can shut down. Although maybe that’s all taken care of by the DCL? In which case that’d be fine.
It’s also pretty obnoxious that it requires an Android phone with Google play services enabled (and even a Google login IIRC) or an iOS phone. There are ways around this, but they are pretty complex and not well documented.
If any ai Ia involved they will dismiss not only it but you and it’s a really irritating habit that is starting to emerge.
It’s perfectly understandable. It used to be that a project that had the appearance of a significant amount of work and polish put into it could be reasonably trusted. With the rise of LLMs, that assumption has gone completely out the window as people can churn out appealing looking slop in record time. In addition, LLMs are dominated by the most transparently evil tech companies in existence, and the fully open models aren’t yet good enough, and are still built on the backs of the absurd amount of energy usage used to train the models.
That all being said, I don’t think the OP is being malicious and I appreciate the disclosure but I’d give this project a year of maintenance before I would reasonably trust it.
Not FOSS or open source in any sense. You could still say it’s self-hosted, but I suspect most people self-hosting care about this.
Snikket is essentially just prosody but more of an all in one package.
Endurain, a self hosted fitness app, may get gadgetbridge integration once the network helper is finished.
This one is nicer than uptime-kuma if you prefer declarative config.
Probably need a bit more detail for this like caddy logs and your caddy config. I did a similar thing on NixOS with services.acme getting the certs and then configuring the cert files to include caddy group access (I didn’t use caddy directly either for those reading as the DNS challenge approach requires third party plugins which is a bit annoying on NixOS).
Sunshine and moonlight. Or just ssh if it’s for administrative tasks.
It looks similar to tailscale and netbird, in that it offers NAT traversal, relays, and proper authentication and access control. Whether or not you need that depends on your circumstances (how many users and their technical proficiency, CG-NAT prevalence, whether you need mesh support, etc).
If you’re just hosting for yourself and you have public ipv4 and ipv6 there’s not much benefit.
Some will let you pay for up to 10 years at the 1 year price, so if you get a deal on a particular tld (as long as it’s not an abused one like .xyz) you can pay upfront and save a decent amount of money.
From memory you should try and avoid 10 year renewals since you can’t transfer to a new registrar for the first year of the new renewal.
You’ll probably want WHOIS privacy support, so make sure the tld supports it.
I didn’t follow a guide, but this guide is probably the closest to how I’d do things.
I’d say if you don’t care that much about the data then either snapraid or RAID-5 is okay; I use snapraid because even if the data is replaceable, I’d prefer to lose only 1 or 2 drives instead of all of them. You should of course have proper 3-2-1 backups for essential/irreplaceable data in any case.
Because modern arrays are often in the multi-TB size recovery can take a significant amount of time (days and weeks potentially) and since RAID-5 only allows one drive to fail, if a second drive fails during that time you’re cooked.
I like to use snapraid combined with mergerfs which technically has the same problem, but because it works on the file level, if a second drive became corrupted, you’d only lose the data on the drive that failed, not the entire array. I combine it with snapraid-btrfs which operates on read-only snapshots instead of raw data, avoiding write hole issues (data changing during sync) and also btrfs itself on each drive gives an additional layer of integrity checking, and rollback support from the snapshots themselves.
I integrate Miniflux with readeck, which is then combined with a readeck plugin for koreader, allowing me to easily read articles on my ereader, without relying on a paid service.
I’m also one of those people that still uses custom ROMs on Android, and since the backup and restore situation is still kind of dire if you don’t use Google (and sometimes even with) it’s easier to have most of my configuration and state stored on a server, and so I can wipe a phone with relatively little risk.