pull down to refresh

Thanks for your feedback. However, Github Pages only allows static content as far as I know and I need a database in the background with some logic around it. Therefore, I don't see how this would add more security, right? As long as you can be sure that your secret has been correctly encrypted on the client side, it shouldn't matter that match if the storage server is trustworthy or not.
I think you could use AES encryption to generate base64 URLs from cleartext. They will be long and ugly, but reversible with a key and not requiring the database.
reply
That's a nice idea. It would go a bit against my requirement that you should be able to communicate the code easily via phone / in person but it's a good idea that has merit.
reply
you can api to a url shortener like bitly. the short url can be communicated via a piece of paper. this will create an encrypted messenger operating with full transparency directly from github.
reply
Yes, true, did not think about the database. Then no, it cannot be verifiably trustless. Whoever has access to the database can spy on and change the links.
reply