app.bivri.graph.getSuggestedFollows

Get Actors the authenticated Member could follow next, and say where the list came from. When the Member's account is hosted somewhere other than this deployment's own PDS, their own app.bsky.graph.follow records are read from their own repository and matched to Bivri Actors by DID; every other case, including a Member who is hosted here, a follow list this service could not read, and a follow list that matched nobody, answers with the popular-Creator fallback and names the reason instead of presenting the fallback as a Bluesky match. Matching is by DID and never by handle, so a renamed account is still matched and a recycled handle is never matched to the wrong Actor. The caller is never in its own suggestions, and an Actor the caller already follows on Bivri is never suggested.

Details · query
Kindquery
Authoritygraph.bivri.app
Indexed

What's different

There is nothing to compare yet: this is the only version of app.bivri.graph.getSuggestedFollows anywhere.