Bounce is an open social web migration tool. It lets you migrate your account from one decentralized social network to another, and still keep all of your followers, along with some of the people you follow.

Bounce currently supports migrating from Bluesky to Mastodon or Pixelfed. We hope to add support for the reverse direction, Threads, micro.blog, and more in the future.

Right now, only your profile, followers, and some follows. The existing posts on the accounts you migrate from and to will stay the same; only new posts going forward will get bridged back to the old account.

We hope to add support for migrating posts, likes, blocks, and other data eventually!

When Bounce migrates you, it uses Bridgy Fed to bridge your new account back to your old network so that your followers there can still see you and your posts.

For your follows, ie the people you follow, Bounce uses Bridgy Fed to detect which of them are already in your new network and following you over the bridge, and which are in your old network but are themselves bridged into the new one. It then reconnects all of those follows so that you still see and follow them after you migrate.

Under the covers, Bounce uses each network's built in support for account migration, eg ActivityPub's Move activity for the fediverse, and AT Protocol's account migration for Bluesky. Bounce migrates your old account into Bridgy Fed, so that it becomes a bridged version of your new account that's fully owned and managed by Bridgy Fed.

If you're migrating from Bluesky, the images and videos on your Bluesky account will stay visible if your account is on a PDS (server) that Bluesky themselves run. We currently don't migrate blobs (ie images and videos) from federated third party PDSes, so if you migrate an account from one of those, its images and videos will disappear after a few days.

Sorry, no. After you migrate, your old account becomes fully owned and managed by Bridgy Fed. More details here.

We're Anuj Ahooja and Ryan Barrett. We make up A New Social, the non-profit that builds and runs Bounce. We love the open social web, and we hope that Bounce can help liberate people from their platforms and enable the last network effect.

Bounce is entirely free to use, but it's not cheap to build, so we welcome donations on Patreon!

If you can't afford to donate, but you still want to contribute, feel free to file an issue, send a pull request, or tell your friends to try it.

Nothing! Bounce isn't a business, and never will be, so we don't have the same motivations to abuse your data that other services might. More concretely, we don't sell or otherwise expose any of your data to third parties, even in aggregate.

Bounce's terms of service are simple. You agree not to deliberately attack, breach, or otherwise harm the service. If you manage to access private keys or other sensitive data, you agree to report the vulnerability and not use or disclose that data.

Otherwise, you may use the service for any purpose you see fit. However, we may terminate or block your access for any reason, or no reason at all. (We've never done this, and we expect we never will. Just playing it safe.)

Do you an administer an instance or other service that Bounce interacts with? If you have any concerns or questions, feel free to file an issue or email us.

Great! Please file it in GitHub. Thank you!

Oof. Thank you for reporting it! Please file an advisory on GitHub. We may provide monetary awards for reports of significant vulnerabilities, eg reading or modifying users' private keys, if you follow these rules:

• Vulnerabilities must be in the application itself, not unrelated services like email (eg SPF/DKIM/DMARC).
• Public user data is intentionally public. That's not a vulnerability.
• No automated fuzzing, DoSes, or other high volume traffic. We block this traffic, and it will disqualify you from any possible award.

Otherwise, the code is open source, feel free to try to break in, let us know if you succeed!