Fediverse following and conversation

When Open web is enabled, the journal receives a handle shaped like @name@moments.im. A reader searches for that full handle in a Fediverse app and follows it there. The journal's identity is created as the network first looks it up, so a newly enabled handle may take a moment to appear everywhere.

A custom web domain does not change this display handle. The handle identifies the Moments Fediverse actor; the custom domain remains the canonical web address for the journal itself.

A moment reaches followers only when it is public and you choose to share it beyond the journal. This same choice places it in the Moments community. Unlisted and password-protected moments are never sent.

Edits and removals can be delivered to the wider network after a shared moment changes. Because each remote service operates independently, delivery may not be instant and copies outside Moments cannot be absolutely controlled.

Conversation can be enabled on an eligible shared moment. Readers reply from their own Fediverse account, and the reply appears below the moment after it reaches Moments. Visitors without a Moments account can begin from the Conversation area by entering the home of their Fediverse account, then finish the reply in their own app.

The owner sees incoming replies in the Open web hub. Replies can be hidden or their author blocked when a boundary is needed. Blocking is a moderation tool, not a public spectacle.

Blocking an account hides its existing replies and prevents new ones. Unblocking allows future participation but does not automatically restore replies that were already hidden.

Readers who want a broader selection can follow the Moments community identity rather than one journal. It carries curated public community moments and is separate from the owner-level follower relationship described above.