I really, really doubt that this is going to be a concern. First, while technically Mastodon can interact with Lemmy, in practice how often does it happen? It’s not zero, but it’s not a lot, either, and I doubt that Threads will change that much because while it’s a neat technical feature, link aggregators and micro-blogging platforms are pretty incompatible culturally.

And then we have to remember that we’re talking about Threads normies. Do we really think that a bunch of Swifties and Kardasholes and other influencers are going to look at the absolute zoo of Marxist/Anarchist/Linuxist users on Lemmy and be like “this is the type of content I’ve been waiting for, I need to interact more with that community”? This reminds me a lot of neckbeards saying they wouldn’t date Megan Fox because she has weird thumbs.

And then we have the whole thing with the actual fediverse and the tech behind it. There is still going to be no algorithm artificially inflating the popularity of what are thinly veiled ads. Meta has no mechanism for introducing ads into the Fedi. Lemmy is not suddenly going to be massively interested in the vast majority of content on threads and start upvoting to the moon.

And the dev team behind the fedi I would wager is going to prevent any sort of real technical takeover, so that means that at any point defederating is possible, and with basically no loss to the fedi.

Serious question though - how would you? Meta can’t push content in your feed. The only reason you’re going to see Meta in your feed is if the community here (or people you follow on mastodon) decide they want to show it.

I think it’s even slightly different in that Firefox has some dependence on Google (a scary level, actual, if Google ends that deal Mozilla is pretty much fucked) that the fediverse doesn’t - the people on the fediverse right now are enough to keep Fedi alive and moving, and I’d find it really, really hard to argue that they aren’t there deliberately to avoid being subject to the whims of Meta/Twitter/Reddit, etc. Like, in a lot of ways, it’s a sacrifice to be on these services because the bulk of content still exists in the proprietary silos. Because the actual protocols and main developers are also intrinsically motivated by the this separation, it’s hard to picture how they could even try to extend/extinguish here.

Like, if Threads fully federates, I’d guess that quite a lot of people block their instance just to keep their hands clean. Those that interact with Threads via Fedi probably fall into the boat that I would. I want some particular content or to follow some people, just not shoveled at me however Meta decides it should be, and not in a way that they can profit from showing me ads. If Meta pulls some bullshit, it’s likely the Fedi would more or less just block them entirely then give up and start a Threads account. And I have a hard time seeing a world where they go to Eugen or basically any of the other driving forces in the Fedi and are like “we need you to change Mastodon so we can [do some typical Facebook bullshit” and Eugen are like “yeah cool with me.”

I think its more likely that Threads users are eventually going to see fedi users dropping a long comment or some post that is about how it’s nice to have a clean ad-free feed and move clients if not over to the fedi in general. It won’t be enough to really matter for Meta other than to say “see we don’t have a monopoly!” and hey, if the fedi gets a little bigger it’s all good for the rest of us.

I didn’t know that. Hmm, sounds like it’s decently likely this is a bit overblown then. I mean, I suppose there are a lot of lazy companies out there that will skip this, but that severely limits the functionality in a way that it’s going to force the secure method.

Sort of. If you’re receiving a notification from a remote server on iOS or standard android, they go through Apple or googles servers. That said, some apps rather than sending your device the actual notification (where this vulnerability comes from) will instead send a type of invisible notification that basically tells the app to check for a new message or whatever and then will display a local notification so the actual message stays on device and inside of the hosting services servers (like a self host.)

There are a few things I’d consider:

• How many users are going to be on the MC server? MC is pretty notorious for eating RAM, and since most of my home server adventures often includes multiple VMs, I would look for something with at least 32 gb of ram.
• for plex (I’m guessing similar is going to be the case for Jellyfin) how many users do you expect to support concurrently, and how good are you at downloading in formats that the clients support direct play for? Most remote plex users are going to require transcoding because of bandwidth limits, but if you have direct play for most of your local clients or have a good upload and don’t have to transcode 3+ streams at a time, you’re probably fine with just about anything from the last 10 years in terms of CPU.
• also re: plex, do you have any idea in terms of storage requirements? Again, if you’re just getting started < 10 tb of storage in mind, you can get by with most computers.

Anyway, to give you an idea, I run both of these and quite a few other things besides on a Dell R710 I bought like 4 years ago and never really have any issue.

My suggestion would be grab basically any old computer laying around or hit up eBay for some ~$100-$200 used server (be careful about 1u’s or rack mounts in general if noise is a concern, you can get normal tower-case servers as well) and start by running your services on that. That’s probably just about what all of us have done at some point. Honestly, your needs are pretty slim unless you’re talking about hosting those services for hundreds of people, but if you’re just hosting for you and a few friends or immediate family, pretty much any any computer will do.

I wanted to keep things very budget conscious, so I have the r710 paired with a rackable 3016 jbod bay. The r710 and the rackable were both about $200, and then I had to buy an HBA card to connect them, so another $90 there. The r710 has 64 gb of ram and I think dual Xeons plus 8 2.5" slots. The rackable is 16 3.5" slots, so what this means is I basically don’t have to decommission drives until they die. I run unRAID on the server, which also means that I can easily get a decent level of protection for drive failure, and I don’t have to worry about matching up drives and all that. I put a couple of cheap SSDs in the 710 for cache drives and to run things I wanted to be a little more performant (MC server, though tbh I never really had an issue running it on spinning disks) and this setup has been more or less rock solid for about 5 years now hosting these services for about 10 people.