@mordremoth i think “federated protocol” might be overengineering this; you could do it with a simple fetch protocol that scrapes public relationships 𝑛 layers deep
this is in fact the idea behind FOAF <https://web.archive.org/web/20220518003509/http://xmlns.com/foaf/spec/20140114.html>; downsides include :—
• relationships must be public (otherwise it’s not possible to know about people “twice‐removed”)
• people need to actually bother to take the time to publish links and relevant metadata
• you need a hosted version for people who don’t manage their own websites as well as tools for making the above ergonomic for people who do
@mordremoth oh, and
• links/recommendations must also be public (for the same reason as relationships)
you could maybe get around this by automatedly just updating your own restricted‐access profile with a cached version of all of the recs of all the people you know (and they know, 𝑛 layers deep) so that people who have access to your profile don’t know WHO recommended something, just that they did (and the degrees of separation), but this massively complicates the technological implementation (every website needs to have a scraper built‐in) and there’s no protection against someone just leaking your information anyway