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.
take a few extra taps and swipes than they would on Android
I’ve swapped from iOS to Android and I very much have the opposite experience.
Everything in Android feels just a little bit like someone somewhere went ‘well we have to put this option SOMEWHERE’ and just shoved it in, which leads to me fiddling in apps and system settings a lot more than I was on iOS.
I’m happy to chalk it up to much more experience in iOS than modern Android, but it’s been kinda a pervasive experience.
And, also related and annoying: googling ‘how do I change a thing’ routinely makes me nuts because how you do something seems to vary from manufacturer to manufacturer and even like, model to model.
I guess it’s just… maybe iOS needs more button presses, but Android is utterly inconsistent as to where something might be which means you spend a little more time digging for a specific thing than you might on iOS which leads to the impression that you’re hitting a lot more buttons to do something, even if maybe the actual number of presses would be lower if you knew exactly how to do it.
Give me a new version of the 5c, but use the G3 iMac colors as your color options, including a transparent look into the guts of the phone.
Would buy at least one.
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.
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.
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.
Excessively patient. I’ve noticed there’s basically a 50/50 chance of any game I find interesting showing up for free on Epic eventually, so I mean, fine, I’ll wait a couple of years to save $60. Why pay for something that’ll eventually be given to you, paid for by some vulture capitalist’s dragon horde?
I take some of their money, get a free game: win/win.
…at this point, I’m pretty sure my Epic games library is way bigger than my Steam library, simply from the 3-5 free games a month that Epic tosses at you, of which like 1/3rd are actually pretty good.
I mean, I can understand why he’d think that, given that he’s certainly never caused one.
Sure, but it’s redundant. You can easily infer that simply from the ‘conservative commentator’ bit.
My immediate reaction is ‘because they don’t have to be’. Laptops are very very bright these days because the expectation you’ll be using them outside and thus need to be able to overwhelm the sun.
Desktop monitors don’t have to/aren’t used like that, and so there’s no reason to have them be as bright.
Also, the brighter the monitor the more color will start deviating from being completely accurate, and something like a studio display is aimed at creators who want it to be perfectly accurate, so that’s likely another part of it.
I don’t think I’d buy an Apple monitor mostly due to them being priced in a way that really makes no sense: for what your wife is doing I’d look at the ASUS ProArt monitors. They’re focused on accuracy and creator workflows, come calibrated, and for the price difference you could buy three or four of them instead…
The M4 lineup is kinda confusing mess.
I’d take a look at the chart at https://arstechnica.com/apple/2024/10/apples-m4-m4-pro-and-m4-max-compared-to-past-generations-and-to-each-other/
If it were me, and this was the main workload, I’d seriously look at the $1600 Mac Mini with the 10 performance core variant.
But that said, ANY M4 is going to be so much faster than that 2016 laptop that she’ll be happy.
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.