Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Consider new Bridgy Backfill service to import past responses #917
Bridgy Backfeed sends current and future silo responses to your posts as webmentions, for your posts to handle as they come in. It would be great to have the complementary service of Bridgy Backfill (feel free to bikeshed the name) to send past silo responses to your posts as webmentions, as a way of backfilling / importing old responses to your posts, including your old posts.
The key use-case here is: help with migration away from social media.
If you can backfill/import the comments/responses on your old social media posts into your own site, then you have fewer reasons to keep around those old social media posts, and thus fewer reasons to keep around that social media account.
Such migration of responses to old social media posts would also enable deletion of those old social media posts, as a step towards de-activating and deleting a specific social media account.
Since it’s likely you may only want to run this "once" and it may take a while as it will likely require crawling your silo posts history which may be throttled, this makes sense as a separate service that you authenticate, activate, and then allow it to progress back through your old posts (and old responses to your posts), perhaps with some progress indicator, and perhaps with some sort of notification when it has completed.
This new service would be in addition to the existing Bridgy services: Bridgy Backfeed, Bridgy Publish, Bridgy for Blogs, and Bridgy Fed.
(Originally published at: https://tantek.com/2020/042/b2/consider-bridgy-backfill-service)
one key way to make it a bit easier to implement would be to start with a downloaded export/archive from the silo. i looked at recent ones from twitter, FB, and IG, and none of them include other people's comments/reactions directly, but they do provide a complete archive of your own posts, which would make fetching comments and reactions from the APIs much easier.
i have no plans to work on this myself anytime soon, but i'd happily consult with and support anyone else who wants to! could be part of bridgy or entirely separate.
sorry i didnt mean to cause any trouble! haha
i was thinking i could write a local script that just goes thru and sends in all my old tweets to webmention.io and let it figure out what content is in each. i honestly dont know if this belongs in bridgy or not. ofc if you want to support it i will hapily help dogfood as i have 3 years worth of public content to backfill
no problem! it's definitely bridgy, or at least something else, since webmention.io only handles "real" webmentions with usable source pages that include microformats2. it doesn't really know anything about silos like twitter or other social networks. that's bridgy's job.