It sounds like the problem with that is the repo for the Memo protocol is private. So any external efforts to substantially build upon or modify the protocol are not practical.
This gives the platform more flexibility. Also pay note to the encryption outline in this document. ECIES allows asymm-encryption given only a user's public key. CashAccounts potential
Each message (OP_RETURN) would be best stored as an intent + operation. For instance, memo://${1byte-OP}${IPFSHash}. Where ${1byte-OP} = Set, Update, Revoke, etc.
No one's going to give you money for something literally anyone in our dev community could slap together in half an hour, or literal minutes if built on top of the memo protocol
I want a good platform, not something that is "slapped together". I don't really understand your anger when you are free to decide to help or not. Also, memo is not an open protocol.
If I want to add something to the memo protocol (let say private message) and you disagree/dont want to implement it then it'll fail and cause frustration for everyone
It works too with the retweet functionality that is missing here, if only 10% can rt it's weird It's a good thing because the n1 should be the one that decides because who else should
Email works the same way, over the years different email providers have added new features that have been selectively supported by others. No one controls email.
To the memo protocol ? You are the only one developing it so you are the only one modifying the protocol. I don't think there is an alternative serious site that is a "memo clone"
The memo protocol is just OP_RETURN with prefixes. Just because they don't have large amounts of traffic doesn't mean they weren't able to add new prefixes.
CSS grids. One row is 7 cols. #1 is left justified, #2 is blank (resizes with the window), #3-7 are right justified. Can't get a constant gap with #3-7; it changes with resize.
A good example is chaining comments to achieve higher character count. This would be an important feature that would break compatibility if you don't add it at the same time.
But you would still need to implement it on memo.cash to work properly, wouldn't you? I'm pretty sure that it could cause issues if different sites won't roll out features in tandem
If an app adds actions that aren't supported on Memo then just that activity wouldn't show up on this site. For instance MemberApp added maps and Wewo added blogging.