first of all, apologies for the repost, a user commented on my original post that I should use "Show HN" so first and last time (or next time in 6 months, accor

first of all, apologies for the repost, a user commented on my original post that I should use "Show HN" so first and last time (or next time in 6 months, according to the guidelines). preface : After my cellphone started having camera focus issues & fell in the river(with me), I got very annoyed with the QR code required by signal (I ended up resizing the QR code it in gimp, printing it out on paper, and scanning it with my half-dead phone to be able to re-link my computer to signal). I am still waiting for my Librem5 (yes I drank the cool aid). going in the deep: I like to develop my own solutions in general instead of using existing technology (a.k.a i'm re-inventing the wheel) My solution is not as good as signal and I know it. The two things that annoy me about signal is that [1]it requires a phone number and [2]it relies heavily on the domain whispersystems.org. The good part about my app/server (I think) is that: 1 - you can host it at home and it does not even require a domain name. (you can deploy with bare ip) 2 - it is user friendly enough (GUI, pictures upload) 3 - encryption in transit is automatic (let's encrypt or self-sign) 4 - you can destroy conversations in one click 5 - you can choose many different modes of deployment (single room, multi room, per-room certificates, wildcard certificates etc(more to come)) 6 - receiving notifications on PING only (more like slack with the @ or irc with the name... something signal lacks) The bad parts about my app/server (I think) is that: 1 - notifications via rss are not ideal, but it is the best way I found to make that app/server as standalone as possible (no 3rd party api calls required after installation). 2 - I am a jack of all trades, master of none, so I am pretty sure you can point at everything I wrote in any language and find flaws (I don't consider myself a developper) 3 - everything in there is file based, so... speed, scale and inodes :) 4 - api is not complete nor nice at the moment (work in progress) 5 - real end to end encryption is not yet implemented (I will go with good ol' gpg here(not sure how yet, let's add more tuck tape) 6 - deployment process needs improvements. (I am the only one that deployed it so far but i'm sure it does) Any feedback is welcome, you can also try to hack it and I will gladly provide assistance if you want to deploy your own instance. I will probably need help to achieve this, but I would love to see this becoming a great product made by the people, for the people with little nodes all over the place. Just like a phone number, you will know to reach your friend(s) at friends.domainx.com. with more savvy people hosting it for less savvy friends, so the data remains in the hands of people that know each others in real life instead of big corp$. P.S : you can use the demo for quick file sharing and destroy the room after. thank you for your time and (hopefully) interest!