Is there a queue or batching-period for the bot interacting on the BlueSky side?

[ELLIOTTCABLE]

I've sent a dozen or so BlueSky-follow-requests to the Mastodon-side bot today; and the folks I've talked to haven't recieved a DM from the bot on BlueSky yet.

Because the bot is responding quickly and correctly on Mastodon, and interactions with already-bridged people are working fine, I'm assuming there's some sort of intentional queue before the DMs are sent?

(Relatedly, a status-page might be worth adding on a subdomain - just a quick way to see if something's wrong specific to your server, federation, or something's up with the bot itself! =)

[snarfed]

Hey, sorry for the trouble here too! There is a queue, but it usually adds only seconds of delay, occasionally minutes at most.

What's probably happening is that Bluesky accounts default to only accepting DMs from people they follow, not everyone, so if they haven't changed that setting, they won't get our DMs. 😕

Obviously not ideal. I should at least add this to the docs, I'll do that.

[ELLIOTTCABLE]

Hm. It'd be better for the Masto bot to actually test that; is that possible?

If they have DMs disabled (oof, if that's the default, then … in most cases), the bot should tell the user "hey, there's nothing I can do within the constraints of consent; you're going to have to go reach out to them personally and ask them to follow @ap.brid.gy. Sorry!"

Related question: do they have to follow @ap.brid.gy, or does following a bridged account "count" as consent? (Edit: Looks like it doesn't.) I really think it should, in the latter case - that's a pretty explicit "I want this person to be able to interact with me" expression of intent; but again, obviously, I'm biased, so idk.

(Presumably, if I were implementing it, following @ap.brid.gy would toggle whether my bridged-posts were posted as 'public', or if not, then as 'followers-only'.)

Addendum: Apologies if any of this comes across as aggressive - you built a super-cool thing, and are clearly doing the best you can, given the technical and community-expectation constraints you're working within. Please don't mistake my frustration with the fractured state of our collective post-Twitter community ecosystem as frustration with you. It just … sucks to live in the worst-timeline future where I need to spend two days of my life trying to work my way through figuring out how to follow a couple dozen old acquaintences that I miss.)=

[snarfed]

Thank you for the kind words! Checking whether the recipient's DMs are open or not is a great idea, that's #1326 , feel free to follow there. PRs are welcome!