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.

Also, if you like htop, youre going to love btop.

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.

Yeah DNS is, in general, just goofy and weird and a lot of the interactions I wouldn’t expect someone who’s done it for years to necessarily know.

And besides, the round-robin thing is my favorite weird DNS fact so any excuse to share it is great.

Uh, don’t do that if you expect your mail to be delivered.

Multiple PTRs, depending on how the DNS service is set up, may be returned in round-robin fashion, and if you return a PTR that doesn’t match what your HELO claims you are, then congrats on your mail being likely tossed in the trash.

Pick the most accurate name (that is, match your HELO domain), and only set one PTR.

(Useless fact of the day: multiple A records behave the same way and you can use that as a poverty-spec version of a load balancer.)

people’s literal existence are now being political and sensitive

Insert always has been meme here.

The major difference between the 1920s or 30s or 40s or 50s or 60s or etc. and now is simply which people’s existence is being pushed as a political issue and that we’ve ceded control of the media to giant corporations who have an overriding incentive to make nobody mad ever because if they don’t, they’ll lose advertiser money because you can’t do anything without half the population disliking you.

That, and we have allowed fascists to control the discussion for decades, rather than stomping them like they rightfully deserve.

Twitch is very much in the wrong here, but let’s not pretend that telling people they’re not allowed to talk about one minority group or another is somehow new.

sudo smartctl -a /dev/yourssd

You’re looking for the Media_Wearout_Indicator which is a percentage starting at 100% and going to 0%, with 0% being no more spare sectors available and thus “failed”. A very important note here, though, is that a 0% drive isn’t going to always result in data loss.

Unless you have the shittiest SSD I’ve ever heard of or seen, it’ll almost certainly just go read-only and all your data will be there, you just won’t be able to write more data to the drive.

Also you’ll probably be interested in the Total_LBAs_Written variable, which is (usually) going to be converted to gigabytes and will tell you how much data has been written to the drive.

I had a similar issue (different media types but) where Jellyfin would not, for any bleeping reason, update the metadata to reflect changes in the media.

After an annoying amount of fiddling I just yanked the library in it’s entirety (as in, it was deleted) and then re-added it and on the new-library-scan everything updated.

Annoying, and maybe not entirely viable depending on how your library is structured - I have ~6 libraries for different things, so it wasn’t that big of an issue - but it did resolve it.

As a FunFact™, you’re more likely to have the SSD controller die than the flash wear out at this point.

Even really cheap SSDs will do hundreds and hundreds of TB written these days, and on a normal consumer workload we’re talking years and years and years and years of expected lifespan.

Even the cheap SSDs in my home server have been fine: they’re pushing 5 years on this specific build, and about 200 TBW on the drives and they’re still claiming 90% life left.

At that rate, I’ll be dead well before those drives fail, lol.

The real pro move is to learn to just roll your eyes, and walk away.

Or block them, and walk away.

It makes certain angry-on-the-internet types so so SO mad when you just shrug and ignore them, but alas, it’s a lost art since everyone likes being mad about everything all the time now.

It’s usable-ish, but still kinda crashy and prone to occasionally imploding.

I wouldn’t really use it as my sole daily driver, but for certain people doing certain things, it’s probably fine.

(It needs another year, honestly.)

Well, I know what I’m doing this weekend.

I went and whacked the scan library button on a 30tb library collection and it didn’t read all that much data (looks like under 100gb) and seemed to be pretty quick - maybe 45 seconds. Local drives and all that, so the speed of the scan doesn’t matter as much as the relatively small amount of data. If all you had was 1tb of media, I’d expect it to just be a couple of gigabytes, not huge amounts of data.

I’d probably double-check that however you’ve mounted the WebDAV share is supporting partial reads, since that really feels to me like the first place that something could be wrong that would cause excessive amounts of file transfers.

I mean, WebDAV is basically just HTTP.

Accessing a file over WebDAV will result in the file being downloaded, so it makes sense that trying to scan terrabytes of files will result in terrabytes of downloads.

You probably want to use nfs/smb instead, since that’s more designed for random-access type situations, though you’d STILL end up pulling all the data down since iirc jellyfin scans the entire file so you’d still be in the situation of having to download all the data even there.

If you kept the same case, I’d call it the same computer.

It’s like a car: if you replace the seat covers, add a new air freshener, and replace the transmission, well, it’s still the same car because the outside shell didn’t change, just the bits inside it.

Private APIs that “trusted sites” have access to that can make all sorts of browser-level changes?

So many questions:

1. Why in the hell? No, seriously what big-brain was involved in the idea that some site needs that level of access to my browser?

2. Who didn’t see this coming? I mean if you make basically a secret back door, of COURSE your shit’s getting pwnt as soon as someone else notices it.

Also note to self: don’t install Opera I guess.

Crap title: it’s a lot of ‘if’.

If they’re being honest with performance.

If they don’t have any development issues they might have a next generation in a year or two, that might be on par with current CPUs, maybe.

I don’t really believe any manufacturer’s benchmarks, and I especially don’t believe it about a product that doesn’t exist yet.

Maybe?

It depends on if the added functions are software-based, or if there’s some hardware funkery going on.

Given it’s a consumer product, I’d wager it’s just a drive in an enclosure that does all their mirroring/backups/encryption stuff in software, but their marketing material doesn’t seem to say one way or the other.

Google indicates older versions can be reformatted, so I’d bet that’s still true.

If I’m wrong it’s not my fault, etc.

Hey, if you can do it on a 4004…

(Yes yes, you’d have to write an x86 emulator and it’d be slow as heck but I mean, you could.)

Yeah, that wasn’t meant to be remotely comprehensive: there’s a lot of ways you can do this ranging from the filesystem to what kind of archives you’re storing, to programs that make parity data for validation.

…also, since I haven’t started a flamewar yet today, I don’t think I’d personally use BTRFS. It’s still too new, has had data consistency issues too recently, and just plain doesn’t have the kind of historical performance record for something I’d want to use for archival purposes.

Come back in another decade and we’ll see how it’s been going.