imdat celeste :v_tg: :v_nb: :v_genderfluid: [witchzard]<p>Finally found some time to woek on <a href="https://tau-ceti.space/tags/Trinity" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Trinity</span></a> again, my E2EE messenger. Found a few flaws in the API-spec, ecpescially wrt editing messages and deleting them for all chat members.</p><p>Also removed some obsolete stuff, because this messenger will never require nor support mobile number or email address for account creation.</p><p>I am considering adding the ability to save your mobile number's hash on the server so that other users could find you, but this is still "under consideration" and it would always be with your explicit wish ("Opt In") . This way, the client could read your address book on your smartphone and send the hashes of phone numbers to the server to see if any of them are on this server.</p><p>But because of the (hopefully) federated nature of my messenger solution, any such user could be on any other server and thus this comparing of hashes would be worthless as it could only work on your "homeserver".</p><p>Yes, you <em>will</em> get a handle for your account (like here on fedi) and that handle will be your TrinityID, so that others can find you. The <a href="https://tau-ceti.space/tags/TrinityID" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>TrinityID</span></a> will be something <br>Iike <code>ics#tau-ceti.space</code> - but no decision has been made yet, so the syntax is still open for debate.</p><p>Anyway, I am now slowly preparing the client and then, once the client is done, I can start testing the API ans take it from there...</p>