@technology Is there a Usenet like app/website/whatever of the Fediverse?
So, I’ve sort of grown up in the Usenet, and this whole Federation thing sort of feels very reminiscent of it. To the point where I’m wondering why there isn’t a way to access it in this fashion? Any tips would be very helpful. I love the idea of this thing and would probably even begin running my own server if that becomes viable.

  • nyan@lemmy.cafe
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    A quick skim of the protocol documents suggests you’re right: Activity Vocabulary doesn’t even mention the “discovery” use case, and no allowance seems to have been made for it. I can’t fathom what they were thinking.

    The short-term workaround would be scraping the Web portal “Communities > Local” page of each instance periodically for a list (and cache the info centrally? Not sure.) Hopefully the raw HTML is parsable enough that you wouldn’t have to involve Selenium (which I’ve used in my day job—it’s awful) or its ilk.

    The correct fix is, of course, to add the “discovery” case and messages supporting it to the protocol, either as an extension or as core for the next version. This might take years.

    It might be worth asking browse.feddit.de how they get their information.

    • JustusWingert@mastodon.socialOP
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      @nyan so it’s not only me missing the elephant in the room. O_o
      That’s a pretty huge gap. Which has severe consequences all the way down the pipe…
      There’s a current issue with lemmy with comments not being synchronized properly. Possibly a direct consequence of the entire system replication being push with no backup pull or reconciliation in the protocol.
      I’m looking into a couple directions right now, but this is completely breaking the foundational promise of the very concept of fediverse…

      • nyan@lemmy.cafe
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        It’s possible that if you’re trying to build a Twitter substitute on top of the protocol, the issue looks like a mere Sicilian dwarf elephant, since Twitter doesn’t have great discoverability either (or need it, really), and synchronization hiccups matter less for that kind of service. It’s when you’re trying to build a Reddit/Usenet substitute that things fall down.

        But yeah, it really is a gap in the design.