cstine @ cstine @lemmy.uncomfortable.business Posts 1Comments 81Joined 2 yr. ago
Three words: creepy anime porn.
I'm probably going to get mega canceled here but I think a good portion of it is that the Holocaust is history.
A lot of what we don't talk about is how we treated the Native Americans because we're STILL shitting on them from on high. For example, the Dakota Access Pipeline is the same old shit, different century.
Also talking about how we've treated people of color, and any discussion around chattel slavery, ends up being "uncomfortable" because an awful lot of people in this country don't seem to see any problem with it and would be perfectly happy if we could toss out the civil rights acts and go back to having separate water fountains.
TLDR: it's 'history' in Germany because ya'll arrest people giving nazi salutes, but in the US wearing a KKK robe is "free speech".
Yeah in that case I'd agree; if you're on a giant public server that anyone can sign up to, I'm not sure there's any particular value to be found in defederating anyone, other than places with uh, questionable content.
Yeah, I just mentioned it because OCI is kinda wonky and requires some static routing stuff in the iptables on the host to have the platform work as intended (which, as far as I'm aware, no other hyperscaler does), which strikes me as really really lazy engineering, but I'm just a simple computer janitor so maybe I'm wrong there.
The most infuriating thing at my last job was people sending in a ticket freaked out that their database was stolen and ransomed, and us going 'Well, we sent you 15 emails over the last 3 months telling you that you had the database open and improperly secured, so what exactly are you wanting us to do now?'
I think that defederation is the middle ground.
One extreme is The Algorithm tells you who you're going to talk to, and shoves junk at you nonstop, and the other is that you have to just accept and filter through whatever gets posted with no filtering at all.
Defederation puts the control back in the hands of, if not the users, then at least the administrators and mods of a community; if you can control who can see your content, and what posts you see then and only then do you own the platform instead of being a faceless number that's only there to be shoved into a dashboard to calculate your revenue value.
A lot of it is people wanting to avoid another Eternal September .
If you have a community you've built, and like, a flood of people who don't understand the culture and behavioral expectations swarming in can be viewed as, frankly, an unwanted invasion.
I also think if this was some new startup (say, Bluesky) instead of Meta, there'd be a different tune, but that's because a good portion of the people who run the communities and invest their time and money into building the community they want were burned by the aggressive enshittification that Meta is basically synonymous with at this point.
TLDR: this has happened before, and it's absolutely destroyed communities just due to the sheer volume of people who don't understand how to behave swarming in and drowning out everyone who the community originally belonged to.
That's not really the right approach on OCI, unfortunately: if you just flush the rules you also break a lot of their management plane.
You'd want to modify the /etc/iptables/rules.v4 and rules.v6 files to add any rules you want to load on boot (and, of course, if you just flush the rules without saving them, then it won't persist and a reboot will break things, again).
It's an arguable benefit: I'm a fan of having the security policies AND iptables sitting between me and doing something stupid, but I also spent most of the last decade dealing with literally thousands and thousands of compromised hosts that just whoopsie oopsed redis/jenkins/their database/a ftp service in a publicly accessible state, got hacked, then had the customer come crying to us asking why we didn't keep them from blowing their foot off - which, basically, is what the OCI defaults do.
As a product of American eduation, I can say resolutely that no, that was absolutely not taught.
Of course, this is partially because American education sucks and partially because we never HAD common land here: everything was privately owned, after it was stolen from the people who already lived here, and then most of it had people who had no say in the matter enslaved to work on it for the people who stole the land.
Of course, this is ALSO not really taught, because it'd make people feel sad and make the US look kinda bad, so it's always talked about but you get like, a week of coverage on both subjects, at most.
Yep, you'll only get content that someone on your instance has subscribed to, so if that's the only subscription that's the only content that'll show up.
Nope, assuming the default settings - that is, they've not explicitly decided to allowlist selected servers or block yours - there's nothing that instance has to do if you subscribe to a community on it.
They'll push content to you and it just magically works.
TLDR: federation is basically a push from the origin server (the one the community belongs to) to any server that subscribes to that community.
The media was something I didn’t consider, but yeah the original image is served from the original posting server.
That’s probably trivial to fix, given other fediverse software locally caches and serves images, though yeah, that requires an extra level of trust and more work for admins in the far too likely case of CSAM or other illegal content.
One minor correction: if lemmy.there has users subscribed to blargh@lemmy.here, the content that is federated to lemmy.there won't vanish if lemmy.here does: that copy is more or less independent once it's federated out.
It's not a 100% complete clone, but it's also not at risk of totally vanishing off the face of the earth, either.
There are issues with further interaction with that group (since the host instance is gone and it won't federate back up and then out to other subscribers), but the content does still exist anywhere it was subscribed to.
If you go old PC and use it for Jellyfin, you probably want hardware that can do accelerated video transcoding so you probably want to aim for 8th gen or newer Intel CPUs (with integrated graphics), because that gets you 10bit h265 transcoding, which I'd say is probably the bare minimum you should aim for these days.
Granted that's 5 or 6-year-old hardware, so it's hardly new, but it took me a bit to figure out why in the world the transcoding performance and quality sucked and what's supported where and at what gen of hardware is... hilariously unclear.
Data this app collects: yes.
This feels like the same anti-FOSS FUD that was there 20 years ago against linux: 'it's not ready!' and 'who will provide support?' and 'it's too hard for people to figure out!' and 'how can you make money if it's free?' and so on.
Of course, the whole world runs on Linux now and it's eaten the lunch of every single proprietary competitor... it just took more than a week to do it, which is far too long of a cycle if you're a clickbait "journalist" on corpo-owned media.
The IBM name, build quality, warranty and whole nobody-got-fired-buying-IBM helped, but don't undersell 80 column text mode: if you wanted to do Real Business Stuff, 40 column just didn't cut it, which wrote off a LOT of the cheaper competition. CP/M machines could be 80 column, but they also weren't required to as there was no default terminal expectation. You'd end up with close-but-not-quites pretty often, even on the upper-end of the price scale.
And yes, the Apple II had 80 column mode, but again, it wasn't exactly the cheaper option.
IBM entered the market at exactly the right time, with the right machine, with the right features, at a price that wasn't incredibly outside of reality and sold an awful lot of them.
The real risk isn't really Meta, or Reddit, or whatever coming in and shitting on everything, but rather the same thing that happened on Reddit: upvote bots, bought and paid for mods, communities that get astroturfed by corporations with fake reviews/"questions" about if a cool new product is, in fact, cool/"hey i just found this thing!" posts and so on.
Those aren't as immediately obviously toxic as lemmy.facebook.com would be, but they're still a corrupting influence that degrades the experience for everyone, and they do it in a way that's less obvious to a lot of people because I mean, is it just a random person, or is it a paid-for shillbot?
Still, have to be careful of Meta federating their piles of users, but it's not really the risk that's likely to happen in the short term as much as "social media marketers" shitting things up the way they shit up everything they get anywhere near.
I'm paying Google for their enterprise gSuite which is still "unlimited", and using rclone's encrypted drive target to back up everything. Have a couple of scripts that make tarballs of each service's files, and do a full backup daily.
It's probably excessive, but nobody was ever mad about the fact they had too many backups if they needed them, so whatever.
For anyone who doesn't know what 'registering for DMCA notification' means, you're after https://www.copyright.gov/dmca-directory/
That said, there's no particular requirement that a DMCA notice be sent to you even if you have a registered agent and some reporters will send it to the abuse contact for the IP netblock you're hosted on regardless of registration, so you may want to make sure you understand what steps your provider may or may not take when they get a DMCA notice before you actually get a notice.
One other option is the "Always Free" tier on Oracle Cloud. You get some potato EPYC instances and some Altera ARM ones that are quite nice.
There are people who have issues with their accounts getting banned with no recourse, but I've used OCI free for over a year with no issues (and run a Mastodon instance on some of the ARM stuff), and know a good number of people who have various services running on it with no issue long-term, so YMMV.
The price is right, though, and you should keep current backups regardless.