Final worklow, with memo.cash as example:
user visits memo.cash. scans CashID code, logs in. memo.cash create child keys, user use CashID to sign them, memo.cash can now post for user
If I understood this right, then my only complaint on memo.cash (that I am not in control of my own keys) is finally solved - and with a userfriendly design!
Nice. How about adding #video support? I guess with some external hosting like #ipfs?
A translation of satoshis into USD might be useful too. Do I send donations via the #memo tip jar?
Video support is planned. IPFS is currently the top choice for hosting. USD translations would be good. Thanks for the input. Yes, tipping is a great way to donate :)
Next, an encrypted private messaging system that works on memo.cash built on top of the Bitcoin (Cash) blockchain? Or is this a technical impossibility? Might be just too much effort?
When asked how to solve the US deficit, Warren Buffet said: "You just pass a law that says that any time there's a deficit of more than 3 percent of GDP, all sitting members of Congress are ineligible for re-election"
Evidence so far suggests that it does, but I personally feel the costs paid is too small and that eventually (if memo takes off) they will come here too.
I agree fees are too small to stop trolls. That's where reputation comes in :)
One more for a truly mobile device friendly interface:
- Open links in the existing browser window.
Icon on external links, like Wikipedia. Desktop users know how to Ctrl+Click.
So Unite.Cash utilizes IPFS to host, view, and play content posted there using the BCH op_return. Memo can look at the code to see if it would be interested for media storage/use.
Memo will likely be adding IPFS support. Not sure when though.