By Phone OTP I mean the following Registration/Authentication flow : To Register, user must enter phone number, user is then sent a 6 digit code via sms to the given phone number, user then must enter the code to register. To Login, it's the same flow.
By "Refuse" I mean - User has full ability to go through the flow but chooses not to for whatever reason (eg. doesn't want to share their phone number)
Based on our config you'd only have to verify your face once to mint the token... not to login every time. Any alternatives you'd recommend to guarantee someone doesn't create multiple accounts?
Valid considerations & so far I definitely agree Confluence struggles with discoverability. We've started using Confluence & hope to make sure we properly utilize "labels" to help mitigate the discoverability shortcomings. Another shortcoming we found for Confluence was the lack of Q&A options (we wanted support for something similar to an internal stack-overflow). So far we've mitigated that issue by leveraging a Q&A Confluence template from this video: https://youtu.be/IkRmyUCnRDo?t=144
Leveraging markdown to enable service agnostic documentation sounds really interesting...
Thank you & apologies for the ambiguity. Yes, by "internal communication" I'm referring to sharing information with the wider group; as you alluded, our main goal is to capture historical context & share knowledge. We'd like to ensure everyone understands HOW & WHY we're pursuing any particular strategy, employing a specific processes, going with a specific architecture, etc. Metaphorically, we're trying to make sure everyone on the ship is rowing towards the same direction & for the same reason.
For daily communication, we're all live on a discord video server during working hours so communication there is instant. We're supplementing discord with slack to enable asynchronous communication.
For roadmap & technical management we're already using Jira. Maybe Confluence would be good option?