← All reports

The reverse-bridging of Nostr and ActivityPub protocols is causing events to be duplicated and re-bridged, which may result in an infinite loop.

Social IssuesProtocol InteroperabilityOct 1, 2026score 0.272 posts · 0 replies across 2 instances
The thread discusses a technical issue with the reverse-bridging of Nostr and ActivityPub protocols, where events are being duplicated and re-bridged, potentially causing an infinite loop. This raises concerns about system efficiency and data integrity.

Claims

The reverse-bridging of Nostr and ActivityPub protocols is causing events to be duplicated and re-bridged, which may result in an infinite loop.
Parent: Decentralized Social NetworksEntity: Nostr and ActivityPub protocol bridgingImpact: negativeDate: Oct 1, 2026Target: The technical feasibility and efficiency of the reverse-bridging process between Nostr and ActivityPub protocols

Source posts

@[email protected]
poster.place reverse-bridged Nostr and now every Nostr event is being duplicated into ActivityPub and then re-bridged into Nostr without proxy tags. I wonder if this could create an infinite loop.
0 boosts · 0 favs · 0 replies · Oct 1, 2026
@[email protected]
poster.place reverse-bridged Nostr and now every Nostr event is being duplicated into ActivityPub and then re-bridged into Nostr without proxy tags. I wonder if this could create an infinite loop.
0 boosts · 0 favs · 0 replies · Oct 1, 2026