@3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d @32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245 @3d842afecd5e293f28b6627933704a3fb8ce153aa91d790ab11f6a752d44a42d @59cacbd83ad5c54ad91dacf51a49c06e0bef730ac0e7c235a6f6fa29b9230f02 @82341f882b6eabcd2ba7f1ef90aad961cf074af15b9ef44a09f9d2a8fbfbe6a2 @e2ccf7cf20403f3f2a4a55b328f0de3be38558a7d5f33632fdaaefc726c1c8eb @fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52 It should be the responsibility of the poster to ensure their message gets to all their followers. Not the responsibility of the viewer to find all the posts from people they follow.

ActivityPub doesn't have this problem because it uses an inbox model. This makes sense because posters should be motivated to ensure their content reaches their followers.

In Nostr when a user makes a post, we should enumerate their followers and find the best relay for each by NIP-05 or NIP-65. Then deliver the event to those relays. This is essentially what ActivityPub does.