Comment on A general fediverse client app, supporting multiple content types? (mastodon, lemmy, peertube, etc)

SnotFlickerman@lemmy.blahaj.zone ⁨3⁩ ⁨weeks⁩ ago

• matcha_addict@lemy.lol ⁨3⁩ ⁨weeks⁩ ago

  I would be glad if a unified web client exists. Mobile app is not necessary.

  source

  • SnotFlickerman@lemmy.blahaj.zone ⁨3⁩ ⁨weeks⁩ ago

    I’m not actually super familiar with the unified web clients, but you could be right that one is out there, or perhaps we’re just asking too soon in the general Fediverse development cycle. In a year or two, someone might have designed something like that, perhaps with a post like this as inspiration.

    source

    • JupiterRowland@sh.itjust.works ⁨2⁩ ⁨weeks⁩ ago

      But where would a unified Web client run in the first place? It would have to be installed on a Web server and, from there, access the Web servers of the various different server apps which would still be entirely different and independent installations.

      For a Web client with no actual server backend, the same would go as for a mobile app: It would have to cover pretty much all features of everything. If uniting Lemmy and Mastodon in one UI seems tricky already, try adding Hubzilla and (streams) to the mix.

      If you’re actually looking for a unified Web server and client, i.e. one Fediverse project that literally covers everything the Fediverse can do with one login on one server and one identity: This won’t happen.

      This would be way too much for one Fediverse project to tackle. You’d basically have to start with (streams), add back all functionality that has been removed since the first fork from Hubzilla (and that’s a whole lot), make all kinds of non-nomadic protocols compatible with nomadic identity via Nomad and ActivityPub, and then gradually add all kinds of features from all over the place, from PeerTube to Funkwhale, from PieFed to Owncast, from Mobilizon to BookWyrm. And you’d have to soft-fork everything and keep them in-sync with their respective upstreams.

      The outcome would be too complex for most. People would have to deal with their account/their login not being their identity because their identity is containerised in a channel. They would have to wrap their minds around nomadic identity. They would have to deal with fine-grained permissions settings. They would have a post editor that’s every bit as powerful as those on big blogging platforms when all they want to do is tweet and retweet and occasionally watch a video. And they would have tons of features on top.

      The whole thing would be an utter nightmare for its developers as well, seeing as they’d constantly have to track over 100 Fediverse projects and implement any upgrades which they’ve rolled out.

      source

      • Fisch@discuss.tchncs.de ⁨2⁩ ⁨weeks⁩ ago

        But where would a unified Web client run in the first place? It would have to be installed on a Web server and, from there, access the Web servers of the various different server apps which would still be entirely different and independent installations.

        There are already web clients for the fediverse, like Photon for Lemmy

        source

        • -> View More Comments
      • SnotFlickerman@lemmy.blahaj.zone ⁨2⁩ ⁨weeks⁩ ago

        Man, I already run like 10 different microservices that all have their own web portal and they’re all locally hosted.

        What’s one more?

        source
• linearchaos@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  Just split the difference and give me PWAs. Let The matrix tell my brain the steak is chewy and delicious.

  source

  • JupiterRowland@sh.itjust.works ⁨2⁩ ⁨weeks⁩ ago

    Hubzilla and (streams) can be installed as PWAs.

    source
• halm@leminal.space ⁨2⁩ ⁨weeks⁩ ago

  So maybe an inelegantly hacked together startpage that shows all your feeds in one for the morning coffee?

  source
• Jumuta@sh.itjust.works ⁨2⁩ ⁨weeks⁩ ago

  ngl web apps are even worse, they’re so bloated and janky, I wish everything had a native app

  source