• breadguyyyyyyyyy@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 days ago

    I keep seeing this type stuff but neither peertube or friendica are genuine replacements at this point, mastodon is weaksauce compared to akkoma or a misskey fork, and loops is alpha software. also yes signal is centralized but it just works and has contact discovery so it owns matrix and xmpp when compared to whatsapp. basically none of this stuff is truly ready

    • Meldrik@lemmy.wtf
      link
      fedilink
      English
      arrow-up
      0
      ·
      10 days ago

      As software, PeerTube is great and there’s actually plenty of content to consume if you can find it. The more content creators we can get to use PeerTube, the more appealing PeerTube will also become.

      Check this link out, if looking for content: https://peertube.wtf/

      • megrania@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 days ago

        “If you can find it” … that’s the crucial point I suppose … but without a discovery algorithm, interesting creators, and a VAST content archive, it can hardly be called an “alternative” for YouTube.

        When I was looking into it I found the best use case was to use it as a self-hosted video archive to replace/extend my Vimeo. At least at that point, all instances that were remotely interesting were not taking any users, and the generic ones seemed to be very far away from what I’m doing content-wise.

        And I guess as long as that’s the case, and you have no ways to monetize content nor any significant reach due to the federated fragmentation, I don’t think it’s an interesting software/federated platform for creators …

          • megrania@discuss.tchncs.de
            link
            fedilink
            English
            arrow-up
            0
            ·
            10 days ago

            I’m running my own instance, and typically post my stuff on mastodon, so I guess I have made the first step?

            It’s a bit of a Catch-22 I suppose … low numbers of viewers makes it less attractive for creators, and fewer interesting creators make it less attractive for viewers.

            Taking into account the other aspects that make it less attractive for viewers (fragmentation and inconvenience … having to dig through “Find the right instance for you” tutorials, no matter how well curated, can be a bit of a turn-off compared to just going to a central point and find what you’re looking for), I don’t have that much hope that it’ll reach a critical mass of both viewers and creators to catapult Peertube into large-scale relevance … as sad as I am about saying that.

  • Kalcifer@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    11 days ago

    Signal isn’t federated [1][2][3.1]; it’s decentralized [1][2][3.2]. Though, for all practical purposes, I would generally argue that it’s centralized.

    References
    1. Signal-Server. signalapp. Github. Published: 2025-01-31T15:34:14.000Z. Accessed: 2025-02-01T09:24Z. https://github.com/signalapp/Signal-Server.
      • This is the source code for the server that Signal uses.
    2. “Signal (software)”. Wikipedia. Published: 2025-01-06T09:34Z. Accessed: 2025-02-1T09:30Z. https://en.wikipedia.org/wiki/Signal_(software).
      • ¶“Architecture”. ¶“Servers”.

        Signal relies on centralized servers that are maintained by Signal Messenger. In addition to routing Signal’s messages, the servers also facilitate the discovery of contacts who are also registered Signal users and the automatic exchange of users’ public keys. […]

    3. “Reflections: The ecosystem is moving”. moxie0. Signal Blog. Published: 2016-05-10. Accessed: 2025-02-01T09:40Z. https://signal.org/blog/the-ecosystem-is-moving/.
      1. ¶5. to ¶“Stuck in time”. ¶3-6

        One of the controversial things we did with Signal early on was to build it as an unfederated service. Nothing about any of the protocols we’ve developed requires centralization; it’s entirely possible to build a federated Signal Protocol-based messenger, but I no longer believe that it is possible to build a competitive federated messenger at all. […] [interoperable protocols] [have] taken us pretty far, but it’s undeniable that once you federate your protocol, it becomes very difficult to make changes. And right now, at the application level, things that stand still don’t fare very well in a world where the ecosystem is moving. […] Early on, I thought we’d federate Signal once its velocity had subsided. Now I realize that things will probably never slow down, and if anything the velocity of the entire landscape seems to be steadily increasing.

      2. ¶“Stuck in time”. “Federation and control”. ¶6.

        An open source infrastructure for a centralized network now provides almost the same level of control as federated protocols, without giving up the ability to adapt. If a centralized provider with an open source infrastructure ever makes horrible changes, those that disagree have the software they need to run their own alternative instead. It may not be as beautiful as federation, but at this point it seems that it will have to do.