Work across federations and pointer to wellfed
kaiyou opened this issue · comments
Hey. This is pretty amazing and I look forward to helping to implement it on some federated applications.
I had started a similar initiative initially designed for Matrix and aiming at providing metadata for any federation, not just the fediverse. Also, it seemed important to me that a node can expose relationships to other nodes across federations and some non technical metadata like opinions, etc.
My initial work is available at https://github.com/kaiyou/wellfed and I'd really like to help merge some of the concepts if you deem them interesting.
If we agree on a standard way to run across federations (like Matrix, Xmpp, or even emails), I would really like to give it a try for Matrix. Afterwards I'll probably drop the wellfed project altogether since we only need so many standards.
Can you please list the concepts you are talking about? What did you do in wellfed you'd like to see implemented here?
Wellfed has the following concepts I would like to port:
- owners, people or organizations running the instance
- related servers, either friends or ran by the same owner, on the same or on other federations
- supported languages on the instance
- countries the instance is hosted or managed from and where applicable laws might impact the instance
- description, rules and tags, to freely describe the instance
- supported registration and deletion modes (does the user have to ask, can he or she migrate an account, etc.)
- a self measurement of the instance reliability based on some criteria, like ability to ensure availability or privacy
- contacts for various actions, like support, admin, legal, etc.
- entry points that point to main items on the instance if any (like main Matrix chatrooms or main fediverse accounts)
Finally, all of this comes from the need to list instances and provide useful tools to help users chose. So I think an admin should have the ability to declare the instance non public, so that he can still expose metadata for people searching the instance specifically but not appear in lists.
I think I can see some of these points but I'm not immediately sure about all of them. Since discussing all of these points in this issue might get out of hand quickly and since it's just extending the schema with the appropriate keys, would you be willing to just send an individual pull request for each proposed feature? :)
Very nice, I will try and provide some pull requests, any concept I should add first (my personal time is very limited lately, so it might take a while per PR 😄 )