• davel@lemmy.mlOP
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    7
    ·
    edit-2
    18 days ago

    There are six bullet points. Which ones are no longer true?

    The only one I know of is point 4, in that you can now choose not to share your phone number. But, IIUC, the app uses the dark pattern of forever nagging you to share it, hoping you’ll eventually accidentally click the wrong choice.

    • AmbiguousProps@lemmy.today
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      1
      ·
      18 days ago

      Point 2 is mostly not true, in that Molly exists and you can do reproducible builds with either implementation.

      • EngineerGaming@feddit.nl
        link
        fedilink
        arrow-up
        4
        ·
        18 days ago

        To be fair, from Signal’s attitude it seems that Molly is tolerated rather than welcomed. And that it may be shut off if it gets big enough.

    • breadguy@kbin.earth
      link
      fedilink
      arrow-up
      10
      ·
      18 days ago

      4 and 5, from what I remember you have to opt into being discoverable by number even if you give it your contacts. that said I don’t fw signal for the other reasons stated, it’s basically just the easiest secure alternative to texting.

    • sqgl@beehaw.org
      link
      fedilink
      arrow-up
      8
      ·
      18 days ago

      I use the Signal a lot and have never been nagged to share my phone number.

    • flatbield@beehaw.org
      link
      fedilink
      English
      arrow-up
      7
      ·
      18 days ago

      2 is probably wrong. Molly exists. Trademark cannot be used to prevent other implementations, just the use of the name or other dress. What may not be open is the server side code and federation is not supported.