Currently, both Wafrn and Bridgy Fed adds a custom field on app.bsky.feed.post (fediverseId, fullText and fullTags for Wafrn, bridgyOriginalUrl, and bridgyOriginalText for BF).
This lexicon can have the original URL of a bridged post, the full text of the post, content warnings (if a client wants to consume it so it shows that instead of “Graphic Media”), and some additional metadata (e.g. for Wafrn we can have a backlink on a ask question lexicon (net.wafrn.ask.question) if the post is an ask answer and such.
I have discussed this with snarfed on Wafrn’s Discord a while ago but it can be good to add it here too.
3 Likes
Hell yes! I’m excited for this too.
My (our) current plan at lexicon.community is to base this heavily on FEP-fffd (aka proxy links). Those are relatively minimal, just the URI of the referenced original object and, optionally, its type.
There are tradeoffs to making these records minimal and not copying any of the original objects’ content into them. The benefit is that they can be generic and work with any lexicon, not just eg app.bsky.feed.post. They also don’t need to be updated every time the original object is updated.
The drawback is that if ATProto clients want to fetch the original object, they need to support whatever non-ATProto protocol(s) it lives on.
There are probably also hybrid/halfway points between those two options!
2 Likes