Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • pleroma pleroma
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 669
    • Issues 669
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PleromaPleroma
  • pleromapleroma
  • Issues
  • #3121

Non-HTTP/S "url" entries cause entire post to be rejected (blocks FEP-fffd)

The current draft of FEP-fffd proposes adding additional url entries to signal that a post is bridged from another protocol, like Nostr or AT. This requires using non-HTTP/S URIs, such as nostr: or at:, to identify objects on these alternate protocols.

There's no need for Pleroma to actually support this FEP, but currently Pleroma will reject any posts with a non-HTTP/S URI in url. This makes implementing FEP-fffd in other applications impractical because it will cause posts to be ignored by Pleroma.

Ideally, Pleroma would simply ignore url entries it does not understand, without rejecting a post entirely.

Assignee
Assign to
Time tracking