[tantek]That's a good idea. I’m also collecting lists of various things to make (like new Wikipedia pages, with citations of course) and May choose some even number (maybe 30 though, 100 is a lot 😂 )
[tantek]Meetable++ for supporting Webmention updates! The 10th anniversary HWC event had ?xml garbage at the start of GWG's comment (review), so I re-sent the webmention and the ?xml stuff disappeared!
sandraWhat happens of someone else (on AP but on another instance) would reply to the comment by @arroba6.snarfed.org@atproto.brid.gy? Would that reply show up on AT? Which would mean:
sandra• There are gonna be lots of @Alice.foo.bar@[various AT->AP bridges] accounts and lots of @Alice.quux.qux.[various AP-AT bridges] accounts. Duplicates of every person who's crossed over. Maybe even recursively, someone who's bridged and then rebridged and then rebridged.
sandraAlso dots in username doesn't work everywhere. Or I would have my email/xmpp sandra.snan@idiomdrottning.org also be my Fedi username with an @ in front.
[snarfed]as for multiple bridges, you're absolutely right, they will create duplicates. the protocols themselves are open, so I don't know that there's a way to enforce eg only one official/allowed/canonical bridge, nor would we really want to, but yes, there will probably be ways to help de-dupe, eg https://codeberg.org/fediverse/fep/src/branch/main/fep/fffd/fep-fffd.md for AP
[snarfed]re "What happens of someone else (on AP but on another instance) would reply to the comment by @arroba6.snarfed.org@atproto.brid.gy?" yes, that reply would show up on ATProto on the other side
[snarfed]I'm not actively working on canonicalizing/de-duping right now, still lots of work just to get basic bridging working. the main thing I'm doing is positioning Bridgy Fed as a single service, not software that people would host themselves
sandra[snarfed]: A friend of mine also asked if you could bridge an existing AT and an existing AP (I didn't really understand why he wanted to do that)
[snarfed]I probably would discourage people from hosting alternative instances of Bridgy Fed itself. it has functionality that depends on its specific subdomains, and having different versions running in different places could confuse end users who need support, etc
[snarfed]also, basic cross posting from one account to another is relatively easy. however, full bidirectional bridging of all interactions - replies, likes, reposts, profile updates, blocks, etc - is much harder