In practice, it's not so bad. It basically exists so you boost twitter posts without doing the whole screenshot copy-paste rigamarole (and so people can tell it's legit and not just a fake screenshot). Occasionally I'll see somebody boost some Adam Johnson or Jeet Heer tweet on Masto and it is because of bird.makeup. In my experience it does a pretty poor job of keeping in sync though. A lot of accounts only show old tweets.

yeah bridges are pretty neat

I feel like this is different for Twitter and Reddit though. Mirroring twitter kind of makes sense. You don't see anything unless you follow an account (opt in), and you can boost a meaningful tweet and it's not particularly obnoxious. Having hundreds of RedditGPT ass communities floating around making tens of thousands of automated comments and hundreds of thousands of automated votes that we can't even comment in would be obnoxious as hell,

god bless that ever happens lol. never

This wouldn't be annoying if well implemented IMO.

If bridge servers could configure:

• source whitelist / blacklist (subreddits, users, etc.)
• post content types to mirror (links, images, text posts, comments, etc.)
• vote behavior (ignore votes from reddit, lemmy, or both)
• fetch behavior (federated servers, cache advertisement, polling frequency, comment thread max depth, etc.)

we could either federate with a bridge configured to our liking or run our own instance.

Example ideas:

• mirror only the decent Marxist subs from reddit.
• mirror some lib subs for posting bridge links to /c/the_dunk_tank instead of screenshots or the reddit link, which would be better for privacy & opsec and allow us to comment and rebuke BS or dunk without interacting with reddit.

I had a discussion with an irl friend about the various proxy frontend servers (nitter, libreddit, etc.) and how the cat-and-mouse game of blocking / rate limiting makes them unreliable and annoying to use. We discussed the idea of frontends federating their cached content with one another, where queries to the frontend would check other federated servers for the cached content before trying the official API, making it easier for proxies to avoid getting rate limited and preventing rate limiting and breaking API changes from blocking access to content already cached.

Direct ActivityPub integration is basically that, but with a bunch of added benefits:

• interaction with the content
• access the content with the same (open source) client they use for the fediverse
• access more content than their proprietary counterparts, making the fediverse more appealing to normies who just want to laugh at memes
• display links posted to both Lemmy and reddit as crossposts, so users could browse by local / subscribed, but also see the reddit comment section if they desire