Agreed on all fronts. Discord is one of our primary references, though the MVP will be closer to Telegram.
OpenSeed functions very similarly to SteemConnect, except in addition to allowing apps to post on your behalf, it also enables them to integrate additional features. So PeakD could use OpenSeed to do everything SteemConnect does, AND any other features offered in OpenSeed like chat, off-chain posts and comments, and more. Also, we could have the messages on chain, we just think it would be more harmful to Hive than beneficial. It would also be a more complicated implementation and the user experience would likely be worse. But we could use either the Memo operation or custom JSON ops to store messages, it’s just not a good idea. So that is a conscious design decision and so far every app developer we’ve spoken to agrees with it.
Appreciate the kind words, maybe I deserved some of that shit ;)
Doing the opposite of what Heimin does is a pretty good rule of thumb IMO 😂
Hey Andrew, out of all this chaos, I've been genuinely interested in how your life would change... I'm really excited to see you working on this project. I'm glad you're outsourcing in a place with a ton of excellent developers hang out and I'm super interested to see how this all takes shape.
Super glad you're a part of Hive... you're a huge part of this community.
Hey man! Good to see you're still hanging around too! Thanks for the kind words and I hope to see you again soon
I'am currently working on a Discord-like app which doesn't require a middleware an runs client-side just purely on HIVE blockchain.
So far good progress have been made, chatrooms are represented by root posts on the chain and chat entries are represented as replies to that post. In my test, I see no real downside client-side the fast block creation times on HIVE makes it already feel like "realtime" chat.
If we can find consensus and could create a common standard for chats on the chain - it could be become available on every frontend and be compatible.
Would you advise me to wait for OpenSeed in this case?
Definitely come by the discord server (yes ironic 😂) and join the OpenSeed conversation. If Hive users were to adopt such a standard we would be happy to integrate it into OpenSeed. That being said, we have given a lot of thought to this feature, and solicited tons of user and developer feedback on their preferred implementation and found that there is not much demand for an on-chain implementation. After all, Hive/Steem has been around for 4 years and such a solution has been possible since day one. One should consider why no such standard has been adopted after all these years. I believe @therealwolf developed such a standard for Steem Chat, but the fact that this project was not successful should be viewed as a warning sign. Most experienced Hive developers are looking for ways to remove data from the blockchain, not bloat it further. That's why we have off-chain posts and comments in OpenSeed as well. It is my belief that a decentralized, public, immutable database is not the right way to store messages and that a distributed, mutable database is far superior. It is understandable why one would be tempted to use Hive for this purpose as it is difficult to bootstrap such a distributed network, however, that is exactly what we are doing with OpenSeed. Sorry to rain on your parade, and it's entirely possible that I am wrong in my conclusions, I just wanted to inform you of my experience and the logic behind our decisions so that you can plan accordingly.
Thank you very much for detailed information here.
I'am joining you on discord - guess it's even better in working on such features in a team :)
Absolutely!
hey, I don't have a lot of tech background, but wouldn't it be possible instead of a chatting system to just have an inbox messaging system? I can't imagine (again I don't know much about this stuff 😅) that it would be too hard to implement, but it would extremely help the user experience on e.g., peakd.
That would be more of a question for the PeakD developers. OpenSeed's messaging system can be represented in the way you mention, that is more of a user interface question.