I write roughly as often on memo as I do on twitter. The engagement has gotten better as of late, but only for a few topics. Hopefully this picks up momentum soon enough...
Reading the cashport web SDK, the implementation is more complex than CashID, because it by necessity supports payments. The payments themselves seem fine, but I dislike the 3rd party centralization
Remember that it is competing with free (usernames + passwords), and that it faces the same challenges as CashID + monetization issues: namely, its value depends on the network effect of handcash.
It could potentially be widely adopted, but the for-profit nature of their "business plans" could hamper adoption significantly, and there is little technical information regarding security.
cashport enables: "giving you access to their personal information and funds". This is a powerful concept and one that is missing bitcoin, and is established in traditional finance.
This validates the idea that a good protocol should be value agnostic in terms of politics: what data to share, when to share and how to use isn't something a protocol should dictate, but users.
The other "big" usecase seems to be the simplifications for everyday life that emerges when all your cards, keys and codes merge together to form a conventient single-system auth.
From it, I've learned that demand for easy to use identification, in particular when tied to national identities, is something companies sees as valuable today.
I've now visited a first meetup to talk about CashID. The presentation lasted for 26 minutes (out of 30 planned), and a very engaged discussion emerged afterwards that lasted for ~40 minutes.
I will be attending a local meetup in Gothenburg, Sweden this wednesday to talk about CashID. In the unlikely case there's a swedishtalking person here who wants to come, let me know.
We might be witnessing the fall of Tether right now. Lots of coins moving out of exchanges and premium on BTC on bitfinex is high. If they get banking resolved it could restabilize, though.
I'm looking into backups atm. I wonder how to make "strong" pins to use for backup encryption, or if there's a better mechanism I could use to prevent use of backups when they fall into wrong hands.
Lots of quality of life fixes done today. It no longer shows metadata choices if there is no choices to be made (none was request, or those that was requested was all previously known)