I might be missing something, but all of these seem like solvable problems. They are mostly data transformation problems, AFAICS.
For example, it seems fairly trivial (especially relative to the payoff of doing so) to map a Bluesky feed to a key pair in Nostr to make it easy to consume that way.
Indeed, this could be a monetisation vector for relays able to offer more advanced interoperability features.
It’s not like the problems of integrating with, say, Twitter, Reddit, or Facebook. There are far more obstacles to that than merely transforming data from one shape into another: violating terms of service, lack of APIs, KYCing, etc.
Replies (1)
Yeah it's interesting to look at this in the context of legacy social media: Facebook and X literally *can't* interoperate, not necessarily on any technical level -- although as these platforms are constantly introducing and taking away new features that becomes fraught -- but because of legal and fiduciary issues.
Meanwhile, I think there are certain common "nouns and verbs" to microblogging social media that at least allow for some "floor" of interoperability -- posts, likes, comments, reacts, boosts, quotes, etc -- these things in their basic form are pretty universal.
Obviously Zaps aren't going anywhere outside of Nostr, but signalling an "intention to Zap" could be a powerful way to attract people to the network.
