RetroShare, Riot, Hashing, Article 13, Security, DRA, Briar

• RetroShare 0.6.5 added GXS distant synchronization, which allows P2P network to server content which isn't directly available from your F2F network peers. Also the Tor hidden node and clear-net versions got merged. As I've mentioned earlier, I like RetroShare. JSON API and IPv6 support, pro! As well as they clearly mention why IPv6 is so much better than IPv4, nothing new about that of course.
• Tested latest Riot.im with friends. Works, but too early version to be really useful, also E2EE encryption is still in the work to be done. Primary pro of Riot.im is the possibility to run your own Matrix protocol server(s) as required (often synapse), installed one on VM just to check it out. And tested Android, Linux, Web and Windows clients. Wikipedia: Riot.im , Matrix protocol. Also tested it's IRC bridge feature, even if I don't actually need it. Also the types of bridging reminded me, why federated networks are often just a huge mess. And they expect users to understand all that, nope. Just today got frustrated with Mastodon, Frendica, GNU Social, Diaspora, because federation between services is often just so broken. Normal users won't bother dealing with broken systems.
• SpaceX new full flow engines - Full-flow staged combustion rocket engine - . Nice work, but not a new idea. But isn't execution what matters?
• Classic solution using AES instructions for fast perfect hashing. Just as I've though so many times, what's the difference of encryption and hashing, and the difference is really small. At least as long as you're not doing any specific attacks. Except is this case it's not designed to be "secure". But from technical standpoint that can be done in so many ways.
• Article 13 and Article 11 in EU - Interesting topic. It's really hard to balance something like that, but as expected both parties are pushing as hard as they can. But in reality what will follow later is unknown, as it often is in this kind of case. It remains to be seen how this is going to affect "user content hosting" and what are the statements which allow you to gain "operator" and not "media" status, so you're not responsible for the content anymore. Also what kind of quoting of content is considered to be fair use, at least earlier it was considered clearly more than it would be with article 11. But I've cut out some of the stuff I would have liked to post to this blog, because it contained so much quoted test from copyrighted source, that it could be easily considered as copyright infringement. Currently there has been also large differences inside EU area, how things are managed in different countries. It remains to be seen if this will change in the near future. This just reminded me about the OFF System - How some things can be technically circumvented.
• Attended a perimeter protection course, nothing new. Good reminder of the normally and widely utilized strategies. There was also show of plenty of different kind of electronic detection systems, based on camera, infrared, rf (direct radar) + mesh detection, ultrasound (audio), and so on. all which can be combined.
• Reminded my-self about Double Ratchet Algorithm.
• Tried Briar Project again, but it's still way ugly, that they think that there's no other secure way of doing key exchange than using real-time screen / video connection (being physically present or using video chat). Also for usefulness and easy connection, unidirectional connection buildup should be possible. Of course then it's up to the user to verify the identity of the remote user. So it's risky, but again, it's a trade-off between security and usability.
• Something different? - 9M730 Burevestnik and Supersonic Low Altitude Missile (SLAM)

2020-05-03