-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Significant problems with bluesky to mastodon bridging #1518
Comments
Sorry for the trouble! The bridge got backed up badly last night: #1520 . We've almost dug ourselves out and caught up, but it's still a bit delayed right now. And you're right! The DM prompt to ask people to bridge their accounts is absolutely clunky. Bridging itself is clunky. I'd love to see the bridge integrated natively into client apps to make the UX easier! |
That account probably doesn't pass our checks here: https://fed.brid.gy/docs#troubleshooting We do need to improve this DM message, though! That's #758 |
Yep, I see him now. But that seems like a pretty big problem/limitation if you can only follow people with profile images :( |
Yup, spam filtering is always a tradeoff. Glad you can see him now! |
First, let me say that I am brand new to bluesky, and I have not used mastodon. But I've been trying to follow people on mastodon without success.
So my friend, who is on mastodon, and I, have been trying to debug. Yesterday, I was able to follow the bot on bluesky, it followed me back, and I was able to request follows. My friend received one, and thinks he followed the bot back. He thinks he was able to follow me from mastodon on bluesky.
However, I didn't receive any notification on bluesky that he was bridged. I can't find him if I search. And now, the @ap.brid.gy bot is just ignoring me for about 10 minutes.
More general impressions
The whole DM thing is really clunky. My friend was really confused about how to "accept" the bridge request, and what it meant. As he said:
This is a lot just to enable someone to watch them, when the information is already publicly available!
The text was updated successfully, but these errors were encountered: