schizo @ schizo @forum.uncomfortable.business

Posts

6

Comments

1,240

Joined

1 yr. ago

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.

contrast to their desktop offerings

That's because server offerings are real money, which is why Intel isn't fucking those up.

AMD is in the same boat: they make pennies on client and gaming (including gpu), but dumptrucks of cash from selling Epycs.

IMO, the Zen 5(%) and Arrow Lake bad-for-gaming results are because uarch development from Intel and AMD are entirely focused on the customers that pay them: datacenter and enterprise.

Both of those CPU families clearly show that efficiency and a focus on extremely threaded workloads were the priorities, and what do you know, that's enterprise workloads!

end of the x86 era

I think it's less the era of x86 is ended and more the era of the x86 duopoly putting consumer/gaming workloads first has ended because, well, there's just no money there relative to other things they could invest their time and design resources in.

I also expect this to happen with GPUs: AMD has already given up, and Intel is absolutely going to do that as soon as they possibly can without it being a catastrophic self-inflicted wound (since they want an iGPU to use). nVidia has also clearly stopped giving a shit about gaming - gamers get a GPU a year or two after enterprise has cards based on the same chip, and now they charge $2000* for them - and they're often crippled in firmware/software so that they won't compete with the enterprise cards as well as legally not being allowed to use the drivers in a situation like that.

ARM is probably the consumer future, but we'll see who and with what: I desperately hope that nVidia and MediaTek end up competitive so we don't end up in a Qualcomm oops-your-cpu-is-two-years-old-no-more-support-for-you hellscape, but well, nVidia has made ARM SOCs for like, decades, and at no point would I call any of the ones they've ever shipped high performance desktop replacements.

• Yes, I know there's a down-stack option that shows up later, but that's also kinda the point: the ones you can afford will show up for you... eventually. Very much designed to push purchasers into the top end.

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.

I mean, recovery from parity data is how all of this works, this just doesn't require you to have a controller, use a specific filesystem, have matching sized drives or anything else. Recovery is mostly like any other raid option I've ever used.

The only drawback is that the parity data is mostly equivalent in size to the actual data you're making parity data of, and you need to keep a couple copies of indexes since if you lose the index or the parity data, no recovery for you.

In my case, I didn't care: I'm using the oldest drives I've got as the parity drives, and the newer, larger drives for the data.

If i were doing the build now and not 5 years ago, I might pick a different solution but there's something to be said for an option that's dead simple (looking at you, zfs) and likely to be reliable because it's not doing anything fancy (looking at you, btrfs).

From a usage (not technical) standpoint, the most equivalent commercial/prefabbed solution would probably be something like unraid.

A tool I've actually found way more useful than actual raid is snapraid.

It just makes a giant parity file which can be used to validate, repair, and/or restore your data in the array without needing to rely on any hardware or filesystem magic. The validation bit being a big deal, because I can scrub all the data in the array and it'll happily tell me if something funky has happened.

It's been super useful on my NAS, where it's the only thing standing between my pile of random drives and data loss.

There's a very long list of caveats as to why this may not be the right choice for any particular use case, but for someone wanting to keep their picture and linux iso collection somewhat protected (use a 321 backup strategy, for the love of god), it's a fairly viable option.

Yeah, I noticed that.

It's on my to-do list for next week since I should have time to sort that out/file a bug if it's something that's not a configuration error.

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.)

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.

thought more than 2%

What confuses me is a survey earlier this year was 2.32%, so why the actual regression?

I'd have expected it to go up with more time to sell steam decks and whatnot, not regress by 15%.

Hell, maybe not since 1997!

Office 2000 was peak office: it had the definitive version of Clippit, and every actually useful feature you'll probably ever need to type and edit any sort of document.

...I will say, though, that Excel has improved for the weirdos that want 100,000 row spreadsheets since then, but I mean, that's a small group of people who need serious help.

This has nothing to do with anything, but whatever.

As a FunFact(TM), 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.

Hell I almost got snagged by one recently, and a goodly portion of my last job was dealing with phishing sites all day.

They've gotten good with making things look like a proper email from a business that would be sending that kind of email, and if you're distracted and expecting something you can have at least a moment of 'oh this is probably legitimate'.

The giveaway was, hilariously, a case of using 'please kindly' and 'needful' which uh, aren't something this particular company would have actually used as phraseology in an email, so saved by scammers not realizing that americans at least don't actually use those two phrases in conversation.

I just uh, wrote a bash script that does it.

It dumps databases as needed, and then makes a single tarball of each service. Or a couple depending on what needs doing to ensure a full backup of the data.

Once all the services are backed up, I just push all the data to a S3 bucket, but you could use rclone or whatever instead.

It's not some fancy cool toy kids these days love like any of the dozens of other backup options, but I'm a fan of simple and well, a couple of tarballs in a S3 bucket is about as simple as it gets since restoring doesn't require any tools or configuration or anything: just snag the tarballs you need, unarchive them, done.

I also use a couple of tools for monitoring the progress and a separate script that can do a full restore to make sure shit works, but that's mostly just doing what you did to make and upload the tarballs backwards.

I'm finding 8 years to be pretty realistic for when I have drive failures, and I did the math when I was buying drives and came to the same conclusion about buying used.

For example, I'm using 16tb drives, and for the Exos ones I'm using, a new drive is like $300 and the used pricing seems to be $180.

If you assume the used drive is 3 years old, and that the expected lifespan is 8 years, then the used drive is very slightly cheaper than the new one.

But the 'very slight' is literally just about a dollar-per-year less ($36/drive/year for used and $37.50/drive/year for new), which doesn't really feel like it's worth dealing with essentially unwarrantied, unknown, used and possibly abused drives.

You could of course get very lucky and get more than 8 years out of the used, or the new one could fail earlier or whatever but, statistically, they're more or less equally likely to happen to the drives so I didn't really bother with factoring in those scenarios.

And, frankly, at 8 years it's time to yank the drives and replace them anyways because you're so far down the bathtub curve it's more like a slip n' slide of death at that point.

My read was 'we need to make more communities, AND we need more users' and I'm not sure why more communities solves anything since I've shown Lemmy to several actual real touch-grass kind of friends and they're all like 'but why? there's nothing there.'

Which is both very wrong, and completely understandable because if you go searching for a community about something, you'll find a whole lot of no activity ones and that's just a misleading and confusing presentation which they're taking the wrong impression away from.

I don't think there's a group of users who are just sitting out there waiting for a community about Longaberger baskets to make the jump off reddit, but there are a LOT of people who would move if it looks like it's not just another "reddit killer" with lots of empty zones of nothingness.

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.

Read up on the saga of /r/jailbait sometime if you want to be utterly confused how the FBI didn't show up and arrest everyone involved with Reddit.

Yeah I've been noticing that. It's probably a case of it being cheaper for them than games, but I've also noticed they've not yet done a cycle where it's ONLY freemium stuff, at least.

Next week, for example, is an Apex skin and a game. If it was JUST the skin I'd probably be less gruntled, but as it is, I find it hard to get too upset that I'm only getting 1 free game instead of 2.

Well, shit.

Hopeful that Apple doesn't wreck anything, but I mean, they've not always bought software and NOT wrecked it horribly.

Guess we'll see.