You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now, whenever a bridging message is sent by Bridgy on my behalf to someone on BlueSky, they start following my full, unbridged account instead of the bridged one.
I never managed to see what exactly is written in the bridging message sent to BlueSky users, because when I tried to, by requesting the bridging of my BlueSky full account to Mastodon, I got what's describe in #1544
It's as if the domain is still [cache?] mapped to my full BlueSky account somewhere! If so, it should be out of the scope of Bridgy, but I want to make sure that I'm not missing something pertaining to Bridgy.
The text was updated successfully, but these errors were encountered:
I'm closing this as "unconfirmed" for now, since the observation could be circumstantial, and the root cause could be undelivered bridging initiation messages, as described in #1548
I used to use my domain name as the handle for a normal, full BlueSky account.
Then 1) I created a bridge for my Mastodon account, then 2) mapped my domain to the bridged account via DNS record, then 3) instructed Bridgy to use my domain as the username, which seems to have succeeded.
Now, whenever a bridging message is sent by Bridgy on my behalf to someone on BlueSky, they start following my full, unbridged account instead of the bridged one.
I never managed to see what exactly is written in the bridging message sent to BlueSky users, because when I tried to, by requesting the bridging of my BlueSky full account to Mastodon, I got what's describe in #1544
It's as if the domain is still [cache?] mapped to my full BlueSky account somewhere! If so, it should be out of the scope of Bridgy, but I want to make sure that I'm not missing something pertaining to Bridgy.
The text was updated successfully, but these errors were encountered: