Five forces, Wasabi, XMP, SSH, COI, OnionShare

  • I think I haven't yet mentioned Porter's five forces analysis. Well, nothing new in the article, but now it's linked.
  • DuplicatiWasabi - I just configured Duplicati backup to use Wasabi eu-central-1 S3 buckets, and it works perfectly. Thanks!
  • I always laugh when others fail. Today I noticed that I haven't enabled XMP memory profile, even if I've got XMP memory modules installed. Duuh, fail, ... Ehh, it's so good idea to pay double price for high end XMP memory and then not even enable the feature. Ehh, well now it's enabled. Better later than never.
  • Studied RFC 4344 about ssh / cipher rekeying recommendations. Pretty much moot with modern AEAD ciphers.
  • Chat over IMAP (COI) project made me smile. Back in day when P2P was coming Napster and so, upstream was all the time the problem in most of cases. I thought it would be so easy to use SMTP to make chunked block delivery with multiple recipients. Because IP multicast does't work as well as it should, practically at all. This would alleviate the upstream problem, when 1-to-Many delivery would be possible. But as you might have guessed, email rate limits would kick in very soon. Yet in the good old days, little rate limits were in place. Idea of COI is good, but I see trouble, when email is being used for something it isn't designed for and the email deliverability is nowadays a problem all the time. - Anyway, this fits well with the concept I've mentioned earlier, anything over anything. - I wonder what email providers will say when I'll end up sending 80000 emails per day, each message 8 megabytes and with 30 (BCC) recipients / message. I guess they'll ban me. - I really wonder why people think is some kind of new idea, duh. It's just different lighter UI to same system. At one time I got email admins annoyed, by sending CD images in email, back in days, when that was a HUGE message and I probably consumed more disk space from the system with my email than all the other users and messages combined. By today's standards, it would be something similar to sending 8 terabyte email. That was fun.
  • Limited hangout - Classic strategy. To come clean with the facts, while forgetting some "minor details". Of course while not forgetting the half-truth, which is daily strategy used by everyone? It's also well working trolling strategy, to present things so that everyone thinks you're wrong, when you're right. You're just keeping the facts which prove you being right till the very end. Very efficient and very annoying to your opponents. Especially in the cases where you have technically perfect proof that you're absolutely right about everything you said.
  • Memoization - Yes, that's exactly what the pyclockpro is designed for, with easy to use Python decorator.
  • Gaofen 4 first (?) geostationary remote sensing satellite, providing high resolution visible, ultraspectral (hyperspectral?) including IR. When that's topped out with Jilin constellation with 138 other surveillance satellites, they'll get pretty good coverage of earth. Anyway, this is expected development and capabilities will just get better in future. kw: IMINT
  • Read: Cloud Programming Simplified: A Berkeley View on Serverless Computing. kw: FaaS, BaaS, Functions, Backend, Kubernetes, App Engine, Object Storage, CDN, As mentioned earlier, different solutions suit for different workloads and purposes. I'm pro public cloud and serverless, but for specific kind of tasks, that's just not the option to use.
  • game (no link, game is already gone?) - That's pretty much the ship game I wrote back in early 90's. Yet it was just two players on single computer. Nice to see the concepts. Yet my version didn't support ramming, collisions yes, but same damage to both ships. But wind, islands, and all the maneuvers to aim gunshots. Yet my version did have firing distance, based on the time you pressed the fire button before releasing it.
  • Played with OnionShare 2, it works as promised and can be used when required. Very nice and secure way of transporting data, with minimal meta leaks and high data security. Of course I would use one extra layer of protection, and encrypt data on trusted environment, before moving it to the system running OnionShare.