Uncategorized

Hi Bridgy Fed fans! It’s time for another status update, headlined by two big new features.

First, you can now use custom domain handles on accounts bridged into Bluesky! Web sites and fediverse accounts can both do this; click through for instructions. Here’s an example. We’ve been excited about this for a while, we hope it makes bridged accounts feel a bit more like first class citizens.

Second, if you deactivate bridging to Bluesky, you can now undo it and bring back your bridged account! Just un-block and re-follow the bot, or for a web site, file an issue or ping me. This is supported if you first deactivated after 2024-10-22; we’re still working on the rest.

I’m also excited that Tamschi has generously volunteered to help triage issues and coordinate development. He’s been a valuable presence on the project for a while now. Please give him a warm welcome!

Oh, and I got distracted for a bit and built a labeler that emits custom self-labels, then promptly realized that custom self-labels probably aren’t allowed, even though Bridgy Fed has been using them since launch. Ah well!

Lots more since last time too:

As usual, feel free to ping me with feedback, questions, and bug reports. You can follow the now label on GitHub to see what I’m currently focusing on. See you on the bridge!

Standard

323 thoughts on “

  1. This sounds great!

    Does it still make sense to have the bridge only opt-in? This limits its usability quite a lot. Have you had any new thoughts on this?

  2. Definitely understood! No new thoughts, sorry. It’s the kind of thing that’s bigger than just me. Maybe @iftas.org or the Social Web Foundation or a similar org could help if/when the time comes.

  3. Ryan was attacked for days over this. It was fairly merciless. It was a miracle really that he came back and continued working on this.

  4. That may not be high on your to-do list, but do you think there is a way to go around the issue of bridging not working for websites using the ActivityPub plugin? I’d like to keep on using it for the Fediverse but use Bridgy for Bluesky.

  5. @snarfed.org Awesome! Creating your own domain handle seems like a really good idea. However, how does one do with the second step, after obtaining your DID? It looks like it demands that you have direct access to the menu of your bridged bluesky account in the bluesky environment. Are there any other way?

  6. Sorry for swamping you with message but I just can’t make the custom domain work. First I can’t find my bridged account user page (the tutorial seems to only work for websites, not fedi accounts, I thought they had a user page too, don’t they?)
    I used the DM method instead. I got my DID, (1/2)

  7. created the TXT record for _atproto (like I did for my Bluesky account) sent another DM to Bridgy Fed account and it replies with “/domain/ does not appear to be an IPv4 or IPv6 address.”
    Why is that? Is it because I used a subdomain? I thought they worked too. (2/2)

  8. Great stuff!

    I’m struggling to set up the custom domain. I pass HTTP verification ( https://bsky-debug.app/handle?handle=brekke.it ), but I think I’m simply too dumb to figure out which user name I am supposed to DM to the bot. I half assumed it could be anything, but I’m not getting a response.

    I’ve tried DMing
    stein <a href="https://brekke.it" rel="nofollow noopener noreferrer"><span>https://</span><span>brekke.it</span><span></span></a>
    stein.brekke.it <a href="https://brekke.it" rel="nofollow noopener noreferrer"><span>https://</span><span>brekke.it</span><span></span></a>
    stein brekke.it

    But the bot just doesn’t seem very willing to talk to me. Maybe it needs more time.

    @snarfed.org

  9. Great stuff!

    I’m struggling to set up the custom domain. I pass HTTP verification ( https://bsky-debug.app/handle?handle=brekke.it ), but I think I’m simply too dumb to figure out which user name I am supposed to DM to the bot. I half assumed it could be anything, but I’m not getting a response.

    I’ve tried DMing
    stein <a href="https://brekke.it" rel="nofollow noopener noreferrer"><span>https://</span><span>brekke.it</span><span></span></a>
    stein.brekke.it <a href="https://brekke.it" rel="nofollow noopener noreferrer"><span>https://</span><span>brekke.it</span><span></span></a>
    stein brekke.it

    But the bot just doesn’t seem very willing to talk to me. Maybe it needs more time.

    @snarfed.org

  10. Also completely forgot that I couldn’t have underscores in the domain names so I got a fix added in for the couple of bots that have those.

  11. sorry! looks like this is DNS caching, BF is still seeing an early version of your TXT record that didn’t have the did= prefix. try it again after the TTL on that record expires!

Leave a Reply

Your email address will not be published. Required fields are marked *