You are viewing a single comment's thread from:
RE: dMessages - Chat App Day #1
I'm probably going to try and get the token going earlier rather than later and then use that to lure in devs. It's cheaper than paying steem 🤣
I'm probably going to try and get the token going earlier rather than later and then use that to lure in devs. It's cheaper than paying steem 🤣
Feel free to have a look at the files on SR and see if you can find client side functions from there where you need em..
Is the back end NodeJS or?
Backend? LOL backends are overrated.
It's all frontend atm... hence the obfuscation!
You have all the clients individually calling or parsing the blockchain every 3 seconds to check for new messages?!
Yes, I am fully aware that I'm evil...
duuuuuude... Write a back end that only has to query the blockchain once then sends the different clients connected to the chat their messages... Saves overwhelming infrastructure by spamming the STEEM full nodes with needless requests. lol
I'm going to make that default, but for
true decentralisation's sake, I'll probably leave a limited version of the client which streams from the chain. I'm still going to have browsers verify signatures at least (or something like that - also so I can enable a pre-send (see it before it hits the chain) feature)Smart as fuck mate. I guess the way you have it set up it is truly a dApp, this impresses me. Would totally do it the way you've listed above. Having the true dApp chat is neat. Would still get a central server though to aggregate the chat messages though, and let users decide which the would like to use. (keep it defaulted to your backend server though, for Node latency health) :)
Also means I can serve history and restore the mystical
shitting dick nipplesinto the chat. I can wait for that... 😜😆Might even be able to do it in a dEcentralised fashion, by storing block numbers, so I can serve them to the dEcentralised client - and it can see for itself