Skip to content

Federation: trust/safety UX for remote content (replica indicators + block/report remote users) #167

Description

@krazyjakee

Because remote content originates on servers the user doesn't control, the client should make provenance clear and give users/admins moderation levers.

What to do

  • Clearly indicate replica/remote provenance on spaces, DMs, and messages (building on the origin badge work).
  • Allow blocking/reporting a remote user by qualified ID and hiding their content locally.
  • Consider an indicator when a peer is untrusted or unreachable.

Acceptance

  • Users can identify remote content and block a remote user; blocked remote content is hidden locally.

Server reference

  • Trust state per peer: src/routes/admin.rs, src/db/federation.rs; authority/anti-spoof hardening: commits 6930907, 7f82f6a, 49c7ed4.

Server reference — accordserver branch claude/federated-servers-xlydlj.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestfederationCross-server (peer-to-peer) federation

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions