1. 15

    If anyone is interested in seeing how opinions change over time, this same question was asked two years ago.

    1. 0

      Awesome!

    1. 4

      Working on building my startup (a messaging app/alternative to the panopticon social media giants). Trying to figure out how to get the messaging right, get people to sign up and try it out, while also making the product work flawlessly.

      1. 4

        If you want to really differentiate, implement what’s discussed in the paper linked in my comment on this thread for contact discovery. It’s a new level of privacy that not even the folks at Signal and similar are achieving right now

        1. 3

          That’s really interesting, thanks for pointing it out. Contact discovery is definitely something tricky and we haven’t even tried to do it yet because of the obvious privacy/security issues.

          If you’re interested in chatting more about this, I’d love to talk to you. brenden@umpyre.com

          1. 2

            The on-line phase of our fastest protocol takes only 2.92s

            I’m not knocking your protocol; keep up the good work!

            But… I’ll happily knock your presentation style. [UPDATE: If I were the author, I’d like to think I’d do some things differently:] It’s fine to differentiate the setup-phase from the online-phase, etc, down in the meat of the paper, but it seems a bit disingenuous to bury the durations of the other phases (one of which is a different order of magnitude) and not present the total-end-to-end time at all. Also, I don’t have 1gb free except on SD card, and writing to that is slower than wifi…

            1. 2

              Not my paper! I wish it was :)

              These are absolutely valid criticisms. I appreciate that the authors show a table of how they fall short of requirements for real messaging applications.

        1. 2

          Scanned the blog post - what does it even do?

          Clicked the link to the homepage - at least there was one. Only a signup form.

          Sorry, I’m out - try again next time with a website or a better text. I have no idea why I as an open source developer would need a messaging platform.

          1. 1

            Thanks for the feedback. It’s a difficult idea to wrap your head around at first, but once it clicks most people have that “aha!” moment and everything’s downhill.

            We’ve debated the idea of a glossy landing page vs. a sign up form, and we haven’t really found the right answer. My personal preference is that when you go to umpyre.com you land in the app, rather than hitting a landing page. This is better for existing users IMO.

            1. 1

              Sorry for the late reply, but I’m torn on this one. DigitalOcean has something like this which I hate.

              Every time I’m logged in there (not soo often) I need the Pricing page, so I need a new privacy window to get to the actual landing page because they hide the normal page from logged in users. I’m sure there are good reasons, but it doesn’t match how I use the site :P

          1. 0

            It says “your data is stored locally for your privacy” and yet it requires a phone number to register? Am I the only one who sees a contradiction here?

            1. 2

              The goal of the phone verification is to keep spam/bots/fake accounts off.

              We’ve thought long and hard about this, but the options are very limited. One option is to use a reference/invite system like lobste.rs, but I don’t think that’s great because it cuts out a lot of people. Another option is to use 3rd parties, another is to use captchas. Captchas have a lot of problems, and we don’t want to depend on 3rd parties.

              If you have other ideas on how to make sure accounts are good quality (i.e., real humans), while also reaching wide audiences, I’m open to suggestions.

              1. 1

                Thanks for the feedback by the way, I updated the wording to be more clear. Hope you give us a shot some day.