• 0 Posts
  • 5 Comments
Joined 1 year ago
cake
Cake day: June 10th, 2023

help-circle



  • Yes, but then I’d need a whole new account to keep a list of subscriptions, and completely switch to a different website / feed.

    The interesting thing would be if the same frontend could make the requests to the the API from multiple instances directly (cross-site) to fetch subscriptions for each instance and aggregate the content in the same feed, even across instances that do not federate.

    Ideally you’d get the content from those instances without server-to-server communication, and you wouldn’t need instances to proxy/cache the content from each other’s. Each instance would just serve the content they host when they do not federate. So they wouldn’t be held responsible for 3rd party content while still giving you the freedom to chose to connect with those other instances if you really want.

    Of course it would still require some level of coordination for all instances to use the same standards, and be able to authenticate the user consistently (maybe using a cryptographic key). But I expect it would alleviate the inter-instance drama by removing friction.


  • Personally I’d rather there were methods for people to access content across instances without the instances having to federate. So that the repercussions of defederation can be minimized. Then it would not be a big deal at all even if an instance didn’t federate with anyone else.

    I feel that it’s actually a big ask to expect the owners of an instance to host/proxy whatever content all other third party instances provide. If I was hosting my own instance I would actually rather prefer to not federate with anyone, because I would not want to be liable / responsible for hosting content that I don’t even have control over. Specially if the fediverse ever becomes as big and mainstream as massive social networks like reddit.