3 ms·
At that time email was validated, there was no doubt people wanted it, gmail was just better email. Contrast that to something like Wave which requires people
by PaulHoule 1y ago
At that time email was validated, there was no doubt people wanted it, gmail was just better email. Contrast that to something like Wave which requires people to try something really new.
- gsf_emergency_2 1y agoIf I read you correctly: Every public-private interaction needs to be obviously infoflow symmetric.. previous example of putrescence was https://news.ycombinator.com/item?id=44231879 https://news.ycombinator.com/item?id=44231879 Where the author was not responsive to interesting comments that do not obviously provide direct utility to his social-protocol proposal (Def of DU here: https://archive.fo/I0nO4#selection-1307.122-1307.226 https://archive.fo/I0nO4#selection-1307.122-1307.226 ) https://wardenprotocol.org/blog/build-your-first-ai-agent-with-warden-protocol-a-technical-overview https://wardenprotocol.org/blog/build-your-first-ai-agent-wi... What could Wave have done better? explain why they need invites? Even better, expose their reasoning, eg they don't need to ease server pressure but they need quality signups? Anything fun I'm missing? Like skin-in-the-game moves from the private side, for macroscopic values of skin? For Wave, I'd imagine they needed to publish data on which fun parts keep the new users returning ---there were MANY! (So, we're both clearly not wishing to see their bugs from swiftly tilting these parts :)