As pointed out by I think james O'beirne on the mailing list, the discussion here between Luke-Jr and greg maxwell about tradeoffs in how full nodes sync is *very* enlightening; even if you don't understand every line, it should really give you something to think about.
Lines 205-330 of: http://www.erisian.com.au/bitcoin-core-dev/log-2019-04-04.html
@waxwing And as we need our own BSQ explorer anyway that could be maybe a combined BTC / BSQ expolorer using Esplora: https://blockstream.com/2018/12/06/esplora-source-announcement/
Any dev who wants to work on that please get in touch. We have a basic BSQ explorer already but would be cool to get it more sophisticated one. https://explorer.bisq.network/testnet/
A list of some Bitcoin (/Cryptocurrency) accounts with proof-of-ownership to help get you started. https://gist.github.com/KevinKelbie/2890e997b7564ab080f8f74c54eb5a2c#file-mastodon-md
Third of four interviews on this podcast is with David Chaum. He discusses his history in crypto a bit; it's pretty interesting: https://letstalkbitcoin.com/blog/post/dd-episode-31-privacy-trust
Some thoughts on Signal (although it won't be news to most here):
I've been hearing about Mastodon for a while and I'm willing to try it out. Last night I learned that you can't keep your identity should an instance be shut down, which I am not a fan of. I was thinking maybe someone could build something on top of git, where as you gpg sign all your commits (messages/replies) and you can refer to them across repos (instances) and your gpg key *is* your identity. The biggest hurdle is probably user experience around key management. Like Bitcoin.
Bitcoin Entrepreneur, open source enthusiast, GreenAddress, Blockstream
Bitcoin Maston Instance