quiet, Uncategorized

For the Bluesky bridge, discoverable opt in instead of opt out is definitely something I could have (should have) figured out before the announcement. Sorry. Lesson learned.

Another thing I should have had ready beforehand was user-facing docs. The introduction post has some information, but not enough. People reasonably have lots of questions! I’ve tried to answer some, here and elsewhere, but that obviously doesn’t scale.

Docs would have avoided a lot of misapprehensions – for example, will it immediately bridge everyone and everything? (No, only when someone follows you, and only going forward.) What about blocks and reports? (They’ll work, and be bridged, as much as possible.) And deletes, and edits? (They’ll work too.) Etc.

The bridge is still a month or more away, so I haven’t written complete user docs yet, but they obviously would have helped. The current docs for bridging web sites and blogs are pretty substantial, but they don’t cover Bluesky. I’ll work on that.

Standard

156 thoughts on “

  1. @snarfed.org Thank you for all your work on this! The non-technical issues are, as is obvious by now, significant, but I love all the attention to figuring out how best to handle them.

  2. @snarfed.org
    > discoverable opt in instead of opt out is definitely something I could have (should have) figured out

    Don’t “should” yourself. I didn’t anticipate such vitriol against an AP<>ATP bridge, and I doubt we would have seen it if you’d be creating the bridge before Eternal Nov.

    The core culture of the fediverse is to join the social web together, however possible. Since EN, a loud and entitled minority seems to be pushing a culture of exclusion and balkanisation.

    (1/2)

  3. @snarfed.org I’m super grateful for you work. Do we have any update as to when the bridge might be up? Are we talking weeks or are we still a month or more away?

Likes

Reposts

Leave a Reply

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