Yup, nothin’ like a little buckshot in the mornin’.

Yup, this is why I shoot fallen tree limbs with a shotgun.

Really? That’s so odd, I thought as long as you’re not running an exit node, you should be fine. TIL, I’ll have to check my ISP’s policies before setting one up then.

Yeah, 100M is a no-go for me since my ISP provides much more than 100M, and streaming full-res videos would bottleneck that pretty quick.

1G is probably fine for us, but we’ll probably go 2.5G minimum the next time I need to swap out switches, maybe 10G.

Yeah, I trust Mikrotik much more than Trendnet, though I’m happy to use Trendnet for internal switches.

the manufacture published a firmware patch for before any public disclosure was made

They were pretty quick for the stable branch, so I guess the miss is prioritizing it for LTS. But if it’s just the one time, I’m completely fine with that.

Do be aware that Backblaze drive access patterns will probably be quite different from yours. So if there’s a really good deal on something with a bit higher failure rate, but your usage pattern is pretty tame, it may be worth taking the gamble.

But at least you mean well.

I don’t think you even need to try very hard…

One that I wasn’t sure about asked about a NAS. It seemed the question was about dedicated NAS devices, and I built my own NAS (desktop PC + drives + btrfs + samba, etc).

I answered “no,” but I think it would be interesting to capture that distinction in the next one. I.e. Do you use a NAS product?

• Yes (commercial)
• Yes (DIY)
• No

And then a follow-up about what that NAS offers (i.e. just NAS stuff, or can it host apps?).

Yeah, I don’t need transcoding, I just need NAS, some random services, and occasional compiles.

Yeah, I’m just disappointed, because I’d love a low-power DIY NAS and I really don’t need need anything x86-specific on it. My main limitation with current ARM SOCs is limited RAM, I really want 16GB RAM, and many SOCs only go to 4GB.

I know why they don’t do it, I was just hoping they’d make an option to use the same socket for ARM and x86 so I could pull a low-end server chip and put it into a higher-end consumer board and have my cake and eat it too.

Which is a major bummer. I remember Project SkyBridge, but that never happened. If it did, I’d probably be running an AMD ARM chip right now.

Then you’re all clear.

I personally want my Jellyfin to be on the WAN, and I have certain devices on my internal network VPN’d to my VPS, which exposes the services I want to access remotely. But if you don’t need that, using the local addr in your DNS config totally works. Getting TLS certs will be complicated, but you don’t need that anyway if everything is local or over a VPN.

I suppose, but then you’re kind of screwed if you want to access Jellyfin outside of your network. I suppose you could use a VPN, but it’s probably easier to just not use the Chromecast (or just accept that it’s going to hit the WAN regardless).

Can confirm, I do this as well for my local services (especially important for Jellyfin), I just point my local DNS server at my local IP and everything works perfectly.

He has cheaper ones too, so check around the shop and find one that fits your requirements.

Hmm, I learned that from lemmy.ml.

And that’s enough.

Good point, I’ll consider MOCA. The main problem is that we have three sets (OTA antenna, satellite, and internet), and I’m not sure which are which, but figuring that out should be quite a bit easier than running cable. :)

I’m not planning on getting anything more than gigabit in the near future, though my city is rolling out fiber and claims to support up to 10gbit.