I gather that’s a meme that’s older than you are?

By linux ISOs I meant any content you’re torrenting: movies, software, audio, my little pony porn, whatever.

Frankly, it probably means absolutely nothing.

Even when captain coffee cup was the FCC chairman, did you lose the ability to torrent linux isos? Did usenet stop working?

I wouldn’t expect anything different this time, either.

https://www.microsoft.com/en-us/evalcenter/evaluate-windows-11-iot-enterprise-ltsc

Keep in mind, though, that you’ll still have to do some activation and KMS hackery to make them usable, but you can at least use an installer that’s going to be clean.

From Microsoft. They actually provide ISO downloads for the 11 LTSC versions, so there’s not really any reason to go grab some random one off totally-legit-software-and-totatlly-not-malware.com or whatever.

Not in a way you’re probably going to like.

You could set up a bare metal hypervisor on the system and set up a VM for your NAS, Windows, and Linux and swap between them as needed, but uh, that’s not really an exceedingly pleasant desktop use case, for a number of reasons, one of which is that you really won’t have the normal ‘sit down, and use the computer’ desktop experience.

Alternate option: run the NAS and either the Linux or Windows install in a VM, and keep it booted into, say, the desktop Linux environment with everything else being a virtualized setup.

Also if you’ve never seen it, lazydocker might be something up your alley.

It’s a TUI, but it provides easy access to docker containers, logs, updating/restarting/stopping/etc them and so on.

My comment was more FDM vs resin support removal, and that it’s not like resin is all sunshine and rainbows.

If anything, modern tree supports for FDM have fixed the giant-blob-of-plastic problem with supports you’d previously get on smaller models, where you’d end up with, uh, well, a giant blob of plastic stuck to an arm or a sword or whatever.

Still not fantastic, but until someone figures out antigravity, it’s what it is.

print with supports, but removing supports from such thin, fragile bits of a model is nigh impossible without doing damage

Removing resin supports is worse, if anything.

They leave little bumps where they’re cut off that you have to then try to VERY VERY gently sand off without bending or breaking said fiddly models.

You could also use nginx if you wanted; it’ll do arbitrary tcp data with the stream plugin.

Hard disagree.

A million empty communities simply makes all of lemmy look like a barren wasteland nobody uses.

We, if anything, need to stop making a community for every single edgecase that someone might ever one day want to talk about, and focus on the basics, until there’s enough people interested in some random niche thing to justify adding the community.

That is to say, it should be organic community growth led by users making a more specific community from a larger community, and not server admins making, for example, 421,000 different sports team communities hoping users will somehow magically appear and use any of them.

Lemmy is still at the scale that a single /c/NFL could more than adequately handle the entire volume of people talking about NFL games, and we don’t really need a /c/ for each league, team, player, and coach or whatever.

You forgot both ‘Don’t send too much email’ and ‘Fail to send enough email’ as qualifiers, as well.

Which I think is the big thing that hits more people than anything else, since ‘too much traffic’ and ‘not enough traffic’ are not defined and so you can easily be caught by one, then the other, then end up in purgatory.

(This is mostly a Microsoft problem rather than a Google problem, but still.)

unmoderated

Fun fact: that’s not strictly true.

You could have moderated groups, where a moderator/group of moderators would get sent every post via email, and they’d only be posted into the group if approved.

The vast, vast, vast majority of groups were not moderated, but that’s not to say you couldn’t do so.

100%: anyone complaining that the mods are mean are not old enough to remember when the people in the moderator positions had actual real power.

If you pissed off a BBS sysop, they had the power to ban your ass, block your phone number, and tell you to fuck off and never come back. And if you really pissed them off, they’d call/netmail all their local BBS friends and you’d be tossed out of everywhere.

Shitposting on Usenet? You’d find your usenet provider would tell you to stop it, and if you didn’t, they would revoke your account and that was that.

Doing abusive things on someone’s FTP server with your actual email address? Your email provider would delete your shit and tell you to go fuck yourself.

Doing an abusive thing with your connection? (Winnuke, any sort of hacking, whatever) Your ISP would yank your connection and tell you to go fuck yourself.

And, of course, in a LOT of cases these were things provided by your work and/or school, which means you could have even more actual consequences for being a fuckstain.

There’s no longer any painful enforcement of any norms (oh no, i have to spend 8 seconds making a new account!) because there’s no longer any real gatekeepers with actual enforcement power.

Or, if they have it, they’re too scared to use it, because they’re too fussed with what someone might angry-tweet if they do.

Yeah it was NAS -> DAC -> Switch -> endpoints and for whatever reason, for some use cases, it would just randomly hiccup and break shit.

I could never figure out what the problem was and as far as I could tell there was nothing in the network path that stopped working or flapped or whatever unless it did it so fast it didn’t trigger any monitoring stuff, yet somehow still broke NFS (and only NFS).

Figured after a bit that since everything else seemed fine, and the data was being exported via like 6 other methods, that meh, I’ll just use something else.

I’m going to have to cut up my nerd card here, but I had similar issues with NFS exports from my roll-your-own build.

After a month of troubleshooting I decided that working is better than purity so I just mounted the SMB shares instead and everything just worked going forward.

Best I can tell, NFS is just very very finnicky when it comes to hardware accessibility (drive spun down, etc.), network reliability, and is just a lot less robust than other options. I never was able to trace why NFS was the one and only thing that never seemed to work right, but at least there’s other options as a workaround?

So I came across something that might be a partial solution: https://github.com/LumePart/Explo

Figured I should update the thread in case it helps you/someone else.

I’d also bet against not hardware failure.

Traditional RAID5 (and others) is subject to data loss in the middle of a write that can break entire arrays if it happens.

Seen it on various LSI controllers, mdraid in Linux, and even a Windows implementation in Storage Spaces. I mean it’s rare and mostly won’t, but if you get unlucky and lose just enough data from just the right places, well…

Wouldn’t imagine that any particular NAS appliance is using some magic sauce that prevents it from happening if you get unlucky as to a crash/power outage.

From what I understand running high bandwidth things like video streaming through cloudflare tunnels

Not at present; section 2.8 is gone.

It is true they frown very bigly on doing stuff like that through the normal cached CDN, but that’s mostly because the CDN is vastly vastly more expensive than some traffic through a tunnel and is still pretty much enterprise-or-you-can’t territory.

The bigger issue is the tunnels are relatively slow, and the performance for real-time stuff like streaming really sucks.

So probably won’t get banned, but it’s also not going to work very well.

I mean, for a $15 thing that does 4k your options are pretty much a Roku, or whatever Amazon’s thing is called.

I’d MUCH rather have the Roku. And the Plex and Jellyfin apps work great, so what else do you need ;)

‘slow and clunky’ part might be a Roku specific issue

Almost certainly. I have a couple of them and they’re like, fine, but the app quality is uneven AF. They’re written by the provider and/or some random 3rd party, so some apps work well, some work poorly, and some are flaming piles of crap.

The Disney app being a flaming pile does not, however, surprise me in the least.