Corporations don’t just sit out on new technologies, and no matter how hard you try you can’t force them to. Defederating from Meta’s new project preemptively is naive, and will not do much of anything.

Protocols are going to be adopted by corporations, whether we like it or not. SMTP, LDAP, HTTP, IP and 802.11 are all examples of that. If it ends up that meta is able to destroy the fediverse simply by joining it, that is a design flaw on OUR end. Something would then clearly need to be different in order to prevent future abuse of the protocol.

FOSS is propped up by corporations. By for profit corporations. If you want to stop those corporations from killing projects, you put safety guards up to make sure that doesn’t happen. You don’t just shut them out and put your head in the sand.

  • dosidosankofa@kbin.social
    3·
    1 year ago

    … so I could host an instance with a magazine that is essentially a digest of federated instances, and I can add/remove based on whatever aligns with my principles?

    I don’t think I have that right, sorry but if you could explain it a little differently, I’m still trying to understand how the fediverse is.

    • ryan@the.coolest.zone
      3·
      1 year ago

      So, as an example. I am on the.coolest.zone which is where my account is registered. I have a magazine on it called fediverse@kbin.social, which is where I am viewing this thread. In fact, you will be able to view it here: https://the.coolest.zone/m/fediverse@kbin.social

      I have only three actual magazines on my own instance - random (this is necessary for all kbin instances to collect uncategorized posts), BestOfBlind, and Android (which was my attempt to create a magazine that collects threads based on hashtag, but it’s not working right). Everything else is a magazine which is actually a federated version of either a kbin magazine from another kbin community or a Lemmy community from a Lemmy instance.

      The couple of things that seem to be missing or broken right now:

      • As stated, trying to get a magazine going based on hashtag does not seem to be working.
      • There’s no way to collect up multiple communities into one, so I have separate magazines for android (kbin.social) and android (lemmy.world). That’s a little annoying!
      • As far as I can tell, you can’t delete a magazine yet. If I federate a magazine / community and decide I actually don’t want it on my instance anymore (or I created m/android to test the hashtag and found it doesn’t work right), tough luck it seems - I’m stuck with it.
      • Hosting costs - Of my 80GB VPS, I appear to have used about 60GB so far just in federating other content to me. This is going to become a problem within this week! I don’t know what to do about that or whether there’s a way to prune old content or what! (I don’t want to re-host everyone’s memes, as dank as they are!)

      kbin and Lemmy are both very new applications, so these will likely shake themselves out over time, but it’s a bit of a rough experience right now. 😅