gun.get('+'+opt.pid)
and gun.get('+'+ack.ok.rtc.id)
are the same node
useCallback
gets called multiple times by React, which inside you then .on(
which creates new subscription listeners each time - therefore accumulating more & more listeners over time.root.ask(function(ack){})
builds a TCP/HTTP-like req/res ontop of GUN's otherwise UDP-like messaging system. It doesn't do anything itself, it just returns an ID that it associates with your callback, message IDs on wire are like var msg = {'#': root.ask(cb), ...}
which you root.on('out', msg)
(be careful: you might need to in
it versus out
, it depends!) then another machine just has to ACK that msg ID, so you var reply = {'#': 'asdf', '@': msg['#'], ...}
that gets sent out or in. You could keep chaining these, where the reply itself may want a reply so you do instead: var reply = {'#': root.ask(cb), '@': msg['#'], ...}
and so on...Gun.state.is(data_node, keyName)
1 of the few internal utilities I kept :P
gun.user().get('timegraph').time(foo)
)?
uggh, spammers. I don't like banning/blocking powers but gonna use it, hopefully at least for good.
I'm actually going to use gun to prototype a decentralized chat app idea I had where, among other things, users decide who to block, and can also subscribe to user/community-supplied global/server-wide blocklists
https://gun.eco
or whatever to the tag list of your view or create a new view with the tag
i will add to your concept that you make chat and forums one thing, share the same backend but have different display options
I would like to do this for sure, and have given thought to how to synthesize these two experiences... but what is the difference between a forum and chat room today? To me, it's simply the pace. That, and each message doesn't come with arguably redundant details