website client of gitter keeps me from switching tabs, which makes me hit send so I can go look something up
Ionic React... finally it's freshened...
@OAXP there is an old bare-bones private chat example here (but it is ~1 year old so probably needs some fixing in some places) https://gist.github.com/amark/7dceae874a20878fdb9e2a8eed109bb5 and a good video example of shared-private data social network here https://www.youtube.com/watch?v=ZiELAFqNSLQ You don't need to host a JS app on your web host, GUN is decentralized! How else can we improve the tutorial/docs? GUN automatically syncs data to the other browser peers, as long as you have at least 1+ bootstrap peers listed (which the Todo-Dapp tutorial shows you how), you don't need to "do" anything, GUN does it for you!
@Dletta NICE !!! NICE !!! NICE !!! now what, to try and get freeCodeCamp moving forward?
@gunBot-disc yo yo :) you gitter+discord bridge? @mhelander I know, right! Very exciting.
@amark sync speed seems good. Server has the latest version and RN uses Sirpy’s rnsupport branch
@amark Not sure, hard to see through the chaos, they got so much inertia with their announcement, in the first 2 days they had over 200 volunteers show up and basically everyone and their mum has framework ideas. Hard to see who even is the guy to ask the right questions. Looks like it’s mainly auth they would be trying to solve with gun. But some guy also said
They're prob going to adopt the same decentralized identity as Matrix or Activity Pub tbh
Would be cool if Iris login worked
They are very much undecided. Once all the volunteer teams are built, they will assign stuff, currently it’s discussions in GitHub issues.
One of the main guys pushing discussion forward is 13 :laughing:
Don't get me wrong, it's cool that he's into tech so early. Just kind of a funny thing
That’s why it’s so hard to know. Not sure who is official and who is just saying ‘we should do this, as we need... etc” It’s not a we until you’re on the team. Or are you on the team?
Just for the price of a bare metal server instance on aws, ;)
My understanding the default behavior of Gun is to make all nodes peers (all nodes get a copy of the entire datastore), but is there a configuration that allows a node to act more as a cache. In other words, any thing that was previously requested (via on/once) is found locally. New requests will have the effect of pulling data from the peer for a slower response (and future quickness). But otherwise will not fetch data that the user has not requested.
@dougwhitehead not all peers need to store all the data, tho relay peers have a tendency to automatically store more data since they're often helping facilitate connecting different peers when WebRTC/etc. fail.
If you are deploying GUN via ephemeral containers like Docker/Heroku/etc. then it is likely that the RAD storage is not even persisting across container resets, so those relay peers are already acting as temporary caches.
And all in-memory instances of GUN will only pull chunks of data from disk/backup based on dynamic request from users/browsers, they never load all the data in advance.
Is there some sort of performance hit associated with obscene bushiness of nodes? In other words, would there be a performance difference between a tree with 1000K nodes off a single parent vs. a tree with 7 layers with 10 nodes per parent (10^7).
While I understand all nodes have a unique address, there may be something I am not accounting for (e.g. cascading callback registry) that would be adversely effected by a node being bushy
@amark No problem. Followed your convo with Michael, Gun is super suitable for a ‘small feature’ set app like meetup
@dougwhitehead In storage all data is flat, each key is found at root ( hence on can do gun.get(soulOfanyLevel)) Radix makes this fast retrieval as it turns keys into radix tree, so theoretically no performance hit. However, if you don’t know the soul of what you are getting and have to traverse the 7 layers, you are going to see slow down
I see. The soul is an index in the underlying datastore. so to traverse 7 levels is to follow 7 layers of indirection (7 DB queries), whereas a single layer with 100K branches is a single DB query.
I suppose I was thinking of it mapped to a RDB, and your answer about the radix tree is implemented differently. But in any case, the bushiness of the node should not matter.