Federating LinkStacks into a network

[strypey]

Have you considered ways of linking two or more instances of LinkStack into a federated network? If this also a thing, my apologies, a link to documentation or code for this please : )

What I'm imagining is a situation where the operators of two independent LinkStack instances trust the integrity of one another's data. So they allow both databases can be searched from each website.

Mobilizon is an example of this, way of sharing in larger network. It's self-hostable, free code software for meetup based groups to issue invites, receive RSVPs etc. So as with public contact info, the integrity of the data is essential to its utility.

Even better, because Mobilizon uses an open standard (ActivityPub) for the federation between intances of itself, it can also interoperate to some degree with accounts on instances of Mastodon, and other software that also implements some support for AP.

EDIT: This might also be a good use for the Murmurations protocol.

[JulianPrieber]

Federating LinkStack Instances

There have been considerations, but after reflection, I see no significant benefit in implementing a federated network for LinkStack. While I am a big supporter of the federation movement and projects like Mastodon, I believe that adopting such an approach for LinkStack may not serve the majority of its users effectively.

Why Not Federate?

1. Current Design Philosophy:

   • LinkStack's isolated instance model aligns well with the needs of independent sites and prioritizes privacy.
   • Federated features are either out of scope for the project or not practical for LinkStack's primary use cases.

2. Limited Use Cases for Data Exchange:

   • There isn't a clear need for separate instances to exchange data.
   • The primary use of LinkStack is to serve as a personal or organizational link repository, which does not typically require cross-instance communication.

3. Privacy and Simplicity:

   • A federated system introduces complexity and potential privacy concerns.
   • Isolated instances ensure data remains under the control of individual operators.

What Could Be Improved?

While I don’t see federation as a priority, I do see room for improving the ability to migrate between instances:

• A robust export/import system would allow users to move their data seamlessly if they wish to switch to a different instance.
• This would maintain the independence of instances while offering users more flexibility.

Open to Feedback

That said, I’d like to hear more about the potential benefits of federating LinkStack:

• Are there specific features or use cases that would make this approach worthwhile?
• Are there technical approaches (e.g., ActivityPub, Murmurations protocol) that could address the concerns outlined above?

If there’s a compelling argument for federation, I’m open to revisiting this idea and considering the broader picture.

Let me know your thoughts and any detailed ideas or technical approaches you have in mind!

[MattDevTec]

I agree with the above,

I personally do not see a purpose to add this into LinkStack.