I’m happy to announce that the a.gup.pe Mastodon groups now federate into Lemmy. Previously they were just empty communities, but now they’re being filled with content. Fantastic news.

You can see the federation working properly at !bookstodon@a.gup.pe

If this has been the case for ages and I’m just the last person to notice, I’m sorry.

  • Die4Ever@programming.dev
    link
    fedilink
    arrow-up
    5
    ·
    10 months ago

    You’re framing it as if this is a bad thing that Lemmy can only see some of the agupe content, but wait until you see how much content non federated platforms can see from each other! I really don’t see how some content is worse than none, if you really want all of it then make an account over there like every other social network in the past requires you to browse on their site/app. It’ll probably improve over time but it really sounds like you’re upset that it already sometimes works instead of not at all.

    • maegul (he/they)@lemmy.ml
      link
      fedilink
      English
      arrow-up
      5
      ·
      9 months ago

      Well sure, glass half full or half empty. To be clear, my problem isn’t with either lemmy or a.gup.pe … they’re open source projects doing great things IMO, and I hope I’ve not made any of their devs upset.

      My problem is with what seems to me — as a mostly technically naive user that tries to pay attention to what others who know better are saying — a tendancy on the part of the fediverse to not live up to its hype or promise, which, AFAICT, is attributable to the nature and design of the protocol and how federation works on the fediverse.

      And sure, we can celebrate something half working … there is, as you say, definitely something cool in seeing federation happen.

      But there’s a reality here that is too easy for open source projects to ignore … user experience matters.

      Unless you’ve got a great big sign on the app/platform that warns any user that this thing will not work at any random time (which OSS users implicitly understand but not everyone does) anytime the UX breaks in unexpected, uncontrollable and incomprehensible ways, a user has an upsetting experience. Sure, it’s a bit of a first world problem, but the promise of social media is to connect socially with people, which involves an expressive and emotional behaviour. Moreover, people are drawn to the fediverse for emotional reasons: join the “good place”, do the “right thing”, help build a better internet etc.

      The moment something unexpectedly breaks on someone as they’re earnestly trying to reach out and make this place work for them, something rather frustrating and a little heart breaking happens.

      In this case, there’s something iffy about the protocol itself that things like this can “half work”.

      You ask whether it’s better that it doesn’t work at all … and I’d say yea, probably. For the simple reason that to some user “half working” won’t be discernible from “fully working”, creating an expectation of functionality that will inevitably be disappointed. What happens when someone posts to the group and it doesn’t get federated and they get no replies or interaction? They’re gonna think there was something wrong with their post. If it happens a few more times, there’s gonna be some psychological effect, however much we don’t like to think about how emotionally bound we are to social media. What if they praise that a.gup.pe is on lemmy and tell everyone they should use it to only realise down the line that they’ve told people to try something that doesn’t work well and feel embarrassed and frustrated that they’ve dedicated time, energy and their personal endorsement on something that’s clearly got problems in the foundations? That’s not a bitter experience that turns people off of caring about the fediverse? Why wasn’t there someone warning everyone that the system wasn’t working? Why allow something to only half work without telling anyone about it?

      If this doesn’t make sense to you … I can assure you it happens … people have gotten very upset over things just breaking down here. And part of the difficulty isn’t that the system is inconvenient and hard to use … it’s that when it breaks it breaks in mysterious ways for the user, in ways that are undocumented, unknown and sometimes misconstrued and misrepresented by others.

      I don’t mean to demean the developers and their projects. But I do think broken things looking like working things is awful user experience, and that ActivityPub in the way that it seems to be a vague and very flexible protocol contributes to exactly these sorts of problems and should be criticised for it.