this post was submitted on 09 Sep 2024
76 points (98.7% liked)
askchapo
22763 readers
19 users here now
Ask Hexbear is the place to ask and answer ~~thought-provoking~~ questions.
Rules:
-
Posts must ask a question.
-
If the question asked is serious, answer seriously.
-
Questions where you want to learn more about socialism are allowed, but questions in bad faith are not.
-
Try [email protected] if you're having questions about regarding moderation, site policy, the site itself, development, volunteering or the mod team.
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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. It might make sense if the communities could be bridged, but Reddit will never develop the APIs to make that possible. As long as Reddit is read-only, it makes more sense just to link to a libreddit instance.
yeah bridges are pretty neat
god bless that ever happens lol. never
This wouldn't be annoying if well implemented IMO.
If bridge servers could configure:
we could either federate with a bridge configured to our liking or run our own instance.
Example ideas:
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: