Fixing Micro.blog Integrations using Tapestry?
I just saw Tapestry’s “crosstalk” feature, which attempts to hide duplicate-like posts.
This could be a workaround for micro.blog’s incomplete implementation of Mastodon/Bluesky integration (where it often misses pieces of the post or context).
If I follow an account in both places, maybe I can have:
- complete Bluesky and Mastodon posts visible in Tapestry (with crosstalk hiding the micro.blog attempt to show the post, in favor of the native one)
- ability to reply from the micro.blog account
What I’m not sure about yet is how well crosstalk detection is working, or if it will properly “prefer” the source post, or sometimes hide the “wrong” one.