Amber on Nostr: Primarily, we are going to focus on multi user instances. Think of two shared ...

Primarily, we are going to focus on multi user instances. Think of two shared mailboxes at two different apartment complexes. Instead of going through a central place to dump all mail without someone addressed you can do a bit better. Each individual mailbox can send and receive to another mailbox. From one apartment complex to the other. This is handled the same way. server A will collect all of the mail that server B has sent to it. Server A will then go back, and instead of it being exclusive one piece of mail per subscriber it is just stored as one piece of mail that all subscribers can access. This also can end up in global/firehose tab. Now, there are exceptions to this. When you put a post in limited modes such as follower-only, unlisted and so on it does not behave exactly like this.

When you have a follower-only post, it is only sent to the intended recipients by the server. It is still picked up by the server, but the server is expected to allow access to only people that are allowed access. If server A had mail addressed for users not on server B, server B would not be able to fetch it (in theory). Great, now let’s talk about federation with this. If server A and B are talking to each other, this is called federation. They are communicating, they only tend to establish federation status when at least a couple subscribers exist on both ends. What is limited federation in respect to things such as remote suspend then? Say that I decide I don’t want mail from X on server A anymore, but I want to receive the rest of the mail from server A. I can just suspend X on server A, so that all of the mail from other users on server A can still get through but X cannot. 2/?