* [Federation between instances](#federation-between-instances)
* [User relationships](#user-relationships)
* [Posts visibility (just a collection of thoughts; further discussion required)](#posts-visibility--just-a-collection-of-thoughts--further-discussion-required-)
* [Posts visibility (just a collection of thoughts; further discussion required)](#posts-visibility-just-a-collection-of-thoughts-further-discussion-required-)
* [Timelines](#timelines)
+ [Community](#community)
+ [Friends](#friends)
@ -13,6 +13,7 @@
+ [Untagged](#untagged)
* [Posts auto-removal](#posts-auto-removal)
* [Handling username and userpic changes](#handling-username-and-userpic-changes)
* [Blocks federation](#blocks-federation)
* [Additional features](#additional-features)
- [Technical and privacy considerations](#technical-and-privacy-considerations)
If some relationships were severed in the process,
local users will get a notification about all the severed relationships that involved them,
delivered in the same channel follow requests are delivered.
The "Community" category brings us to timelines (see below).
### User relationships
@ -207,6 +217,29 @@ So probably an user will be able to sign off with a specific person's name or to
_Question: should an user be able to pick an entirely new display name on every post, or does it make sense to limit it to postfixes only (e.g. an "user name" can post a specific post as "user name (fae/faer)" or "user name. -Person Name")? Changing the entire username will probably beneficial to some, but on the other hand it might make their posts less accessible to others, who might have a difficulty recognizing an user. And if that's the point, then maybe these users should register themselves separate accounts for every display name instead (and anyway there is an option of changing one's display name; this question only refers to the ability to modify a display name in the post compose UI)? Thanks to 🐉 for the idea_
### Blocks federation
"Community instances" will notify each other when another instance was moved into "Disconnected" category from any other ("disconnect" event), or into "Connected" or "Community" category from "Quarantine" or "Disconnected" ("connect" event).
When two instances became "Community" with each other, they will exchange current lists of "Connected"+"Community" and "Disconnected" instances.
If a local instance learned that some remote quarantined instance is "Disconnected" by some "Community" instance,
_and_ that remote instance is not added to any user-specific "Connected" list on local instance,
_and_ no users from that remote instance are in any relationship with users from local instance,
then it is automatically moved to "Disconnected" on local instance.
If such a remote instance is "Connected" but everything else holds, then it is automatically moved to "Quarantine".
Otherwise it is added to review queue in admin UI.
Similarly, if a local instance learned that some remote quarantined instance is "Connected" (or "Community") by some "Community" instance,
_and_ that remote instance is not added to any user-specific "Disconnected" list on local instance,
then it is automatically moved to "Connected" on local instance.
Otherwise it is added to review queue in admin UI.
TL;DR: If local instance doesn't know much about some remote instance, it will use federated blocklists and allowlists.
If it knows enough about some remote instance, it will not federate/defederate automatically but instead add it to admin review queue.
Additionally, every instance should probably make lists of "Connected"+"Community" and "Disconnected" public.
### Additional features
Similar to username and userpic, a client will receive a relationship status along with a post, and will be able to display it.
