The Mostr bridge now has a new way to tag ActivityPub content on Nostr. This has been standardized in NIP-48! 🎉 https://github.com/nostr-protocol/nips/pull/693

Previously Mostr events used the ambiguous and proprietary "mostr" tag to indicate people and posts from ActivityPub, eg:

["mostr", "https://gleasonator.com/objects/9f524868-c1a0-4ee7-ad51-aaa23d68b526"]

Now those "mostr" tags are gone, and the same ting would instead be expressed like this:

["proxy", "https://gleasonator.com/objects/9f524868-c1a0-4ee7-ad51-aaa23d68b526", "activitypub"]

Proxy tags can be used to locate the original content on the web. Not just for ActivityPub, but also for RSS, Matrix, Bluesky, and whatever else we decide to bridge.

Clients can use this to indicate messages from other protocols, and may choose to include a link to the source content. It could even be used to deduplicate content between bridges and merge threads.

Reply to this note

Please Login to reply.

Discussion

Shout out to nostr:npub1cdzl6gys3egf4jewk786y7q2a7nmdldqevuf395pw6uk8j2uukcs7rl5s4 for authoring "FEP-fffd: Proxy Objects" and inspiring this NIP.

https://codeberg.org/fediverse/fep/src/branch/main/fep/fffd/fep-fffd.md

(Also, Pleroma fixed the Link bug, so I'll upgrade the bridge to the newest version of this FEP after a little while)

Supported in gossip already:

So is this now the cleanest way to add #RDF to nostr events?

Cc nostr:npub1melv683fw6n2mvhl5h6dhqd8mqfv3wmxnz4qph83ua4dk4006ezsrt5c24

So can I interact with people on ActivityPub/Mastodon from NOSTR/Damus? Or are the posts I’m seeing in my feed from mostr.pub duplicated threads that the OP won’t know are being interacted with on this side unless they come here?

How about proxied NIP-05?