How are you thinking this would work?
Would nostr events be signed by AT identities?
Or would the bridge generate new keys for each identity it encounters and publish events on their behalf?
Is anybody interested in building a nostr <-> at_protocol bridge? It should be pretty easy to do as conceptually the two protocols are very similar.
The bluesky at_protocol server is in go: https://github.com/bluesky-social/indigo
They haven’t turned on federation and proper key ownership yet but people in the know keep promising that it will be ready in two weeks.
I’d throw in to a bounty for this, anybody else?
Discussion
Profiles seem to have the data you’d need for nostr https://atproto.com/lexicons/app-bsky-actor#profile
Posts have an ID associated with them, but there’s no mechanism for delegated signing that I can see 🤔
Haven't looked at bluesky or AT, does it require nat traversal etc?
If not, users could run their own bridge service on any device and not worry about delegated signing if the architecture is similar to nostr.
From a nostr perspective all you're doing is listening for events and publishing events like any other client. You could probably just just do it in JS and then the user would only need to leave a browser tab open in the background to run their own bridge.