Bringing non-disposable technology to China is a mistake in most circumstances.
- 0 Posts
- 38 Comments
Ptsf@lemmy.worldto
Selfhosted@lemmy.world•What are your VPN recommendations for accessing self-hosted applications from the outside?English
6·1 year agoZero tier. I went tailscale originally, and they’re good, but their mdns support doesn’t exist and several services rely on it. (For me, the showstopper was time machine backups)
Tape drives will be expensive and likely beyond overkill for this. I’d recommend you grab a blue ray DVD writer and use that instead. The discs are generally shelf stable for 25 years and hold about 50-128GB depending on the disc. Duplicates are cheap, storage is relatively easy, and it doesn’t require constant upkeep/power like a hard drive would. Downsides? They just stopped making the discs, so they’ll grow in cost over time. That’s about it that I can think of.
Ptsf@lemmy.worldto
homeassistant@lemmy.world•IKEA moves to Thread (and away from Zigbee)English
17·1 year agoThey’re different in their implementation. Zigbee automesh is more of a centralized router-hub model with self healing relying on routing tables. This caused significant issues for me. Thread is true automesh with all devices acting as a hub in a hub/spoke model, so there’s no centralized routing table to act as a single point of failure.
Ptsf@lemmy.worldto
homeassistant@lemmy.world•IKEA moves to Thread (and away from Zigbee)English
324·1 year agoAn important difference between thread and zigbee/wi-fi I’m not seeing mentioned is that all thread devices automesh in a hub/spoke model as long as they’re not battery powered. So your light bulbs, plugs, etc all become extenders and part of a self healing mesh network without a single point of failure. For me it works better than Zigbee for this reason.
Depends on the drive too, I have some insanely loud Ironwolf drives and you would never guess they’re from the same manufacturer as my practically silent Exos X18s.
I think of it as a lab because it’s my sandbox for me to do crazy server stuff at home that I’d never do on my production network at work, and I think that’s why the name stuck, because back when systems were expensive as heck it was pretty much just us sysadmin guys hauling home old gear to mess with.
It’s difficult to say exactly what all a reverse proxy adds to the security conversation for a handful of reasons, so I won’t touch on that, but the realistic risk of exposing your jellyfin instance to the internet is about the same as handing your jellyfin api over to every stranger globally without giving them your user account or password and letting them do whatever they’d like for as long as they’d like. This means any undiscovered or unintentional vulnerability in the api implementation could easily allow for security bypass or full rce (remote code execution, real examples of this can be found by looking at the history of WordPress), but by siloing it behind a vpn you’re far far far more secure because the internet at large cannot access the apis even if there is a known vulnerability. I’m not saying exposing jellyfin to the raw web is so risky it shouldn’t be done, but don’t buy into the misconception that it’s even nearly as secure as running a vpn. They’re entirely different classes of security posture and it should be acknowledged that if you don’t have actual use for internet level access to jellyfin (external users, etc, etc) a vpn like tailscale or zero tier is 100% best practice.
Honestly you can usually just static ip the reverse proxy and open up a 1:1 port mapping directly to that box for 80/443. Generally not relevant to roll a whole DMZ for home use and port mapping will be supported by a higher % of home routing infrastructure than DMZs.
I hate having to run my own backups. That’s been a massively hidden cost behind self hosting that I did not originally account for. Anything sufficiently robust is expensive and anything cheap is unreliable (at least at the scales of data I have, 4k+ RAW videos and photos are massive).
Ptsf@lemmy.worldto
Selfhosted@lemmy.world•Jeff Geerling: Self-hosting your own media considered harmful (updated). Youtube removed his content, saying that self hosting content is "dangerous or harmful content"English
17·1 year agoHey kid… You wanna self host an api call? 😈
Ptsf@lemmy.worldto
Selfhosted@lemmy.world•What are the benefits of a server having multiple public IP addresses?English
2·1 year agoYou can run a service on the same port with less processing overhead than a reverse proxy. Additionally it provides you some benefit in domain separation. For $25 I’d pick up one or two, couldn’t hurt to have in the pocket and there are only so many of them afterall.
Gosh, after all the hacks I do to Windows I often forget how terrible the experience is for all my users our there raw dogging it. 🪦
Did you ever resolve this? I’m curious what it was.
The server caches your device ID at some point I believe, although I’m not a jellyfin developer so you’d need to look into their documentation for confirmation if you don’t already know yourself.
🤔 it’s probably something cache related or due to a clock offset then. Beyond that I’m not sure what I would investigate.
So there’s a change regarding reverse proxies in one of the recent updates that requires you to specify the approved ip of the reverse proxy. Are you using one? If so, it could be this.
Ptsf@lemmy.worldto
Selfhosted@lemmy.world•Would you use a self-hosted, AI-powered search engine for your favorite sites?English
43·1 year agoIndexing websites adds significant traffic to those sites. It’s not a good idea for the health of the internet for everyone to be Indexing, maybe you should search for a precompiled index you can train the lmm on and distribute it daily. Or do the crawling yourself and distribute that index.

Since you clearly plan on keeping this equipment for the long-term, you may be better served by a newer lower power option that will likely be more performant for less long term cost.