• jarfil@beehaw.org
    link
    fedilink
    arrow-up
    0
    ·
    9 months ago

    Closed source helps with the second part, the connecting with a majority of people using the same closed source platform (then different people use different platforms, which is where we are now… but the DMA might solve that).

    On-device bridges could be nice if they included that in the OpenSource part.

    • shrugal@lemm.ee
      link
      fedilink
      arrow-up
      0
      ·
      9 months ago

      the connecting with a majority of people using the same closed source platform

      The platform is open, including the part that connects to other closed source platforms. It’s just Matrix and open source bridges after all. And making the client app closed souce doesn’t help with any of that.

      I’m sorry if I’m a bit pedantic about this, but it seems like you’re describing an upside to closed source software that’s just not there.

      • jarfil@beehaw.org
        link
        fedilink
        arrow-up
        0
        ·
        9 months ago

        Too pedantic 😉

        I was trying to explain that people on closed source platforms, right now, get:

        • Good network effect
        • Simple configuration
        • Enough security theatre to keep them happy
        • Different extra features

        That’s the experience I understand Beeper is trying to compete with… and make money in the process.

        Closing the client, could help them differentiate above the competition by better integrating into their own infrastructure, still keeping a simple configuration, and charging for it, while people who buy into the security theatre, woldn’t notice a difference in that respect. Expanding to selling some user metadata, or sniffing the bridges, would be an extra.