You're not making Bob Alice's friend. You're putting the Gun constructor in there
I think 'bob' should be a string
so ive trying to understand how gun works but im a bit confused on some stuff. if i create a key value pair in my user graph that only i can update, how is this guaranteed? peers can reject the update if its not me that tried to update the value, but given the value can i prove that i was the only one that updated it?
hmmmmm i think im, starting to get it. i keep thinking of it in terms of an immutable blockchain where you can view the whole history of a value, but if im understanding this right this is mutable in that you can only read the current value, not any past values
but the principles of authorization and ownership verification are the same
Found the problem,
const GUN = require('gun');
const gun = GUN(/*{localStorage: false, radisk: false}*/);
const alice = gun.get('alice').put({name: 'alice'});
const bob = gun.get('bob').put({name: 'bob'});
const users = gun.get('users');
users.map().on(user => console.log(user));
users.set(alice)
users.set(bob);
alice.get('friends').map().on((friend, k) => console.log("Alice Friend", friend, k));
alice.get('friends').set(bob);
alice.get('friends').set(alice);So apparently I can't disable storage, so is there a way to run gun only in memory ?
@fsvieira: Your example about friends it's only good to see how gun saves data, but it's not good for actually storing friends. You saved them using
gun.get('users') which means they are in the public space which everyone edit/delete.
1 reply
If you want to store data that nobody can edit/delete, you have to save it in your own user sub-graph
gun.user().get('friends') (as opposed to gun.get('users')
@rococtz:matrix.org Hi, Thanks for the tip I didn't know that. But right now I am just experimenting with gun, and security or other users are not a concern right now. I am running this on node, and I would like to put this on unit tests of my project so having gun running only in memory it would be nice to have. So is there a way to run this only in memory, I was checking file adapter but it seems not to work with this example, it seems only to work with radisk.
@fsvieira: I don't know how you can you do memory only, you probably have to build your own adapter. Maybe @amark can help you with some advice
@resession: works for me
I want to use gun as a local graphdb solution (as there doesn't seem to be many out there) and gun looks great. All I really want it to do is stay in sync with a graphQL server. Presumably I will need to write an adapter, but I have 2 questions if any one if kind enough to answer. Is gun going to be overkill for just using as a local state management system, with all of the decentralization features, or will there be lots of overhead? And if not what is the easiest way to go about writing an adapter for a graphQL backend?
Hey. Can we somehow check if subscription (.on) exists and if true do not subscribe on receiving this data again?
Hi, I'm new to gun, just tried on local and now can store my first graph node
I'm wondering, will my stored data synchronized to other peers even though I'm not setting the peers at the start like the one mentioned in documentation here ?
But, if you dont provide peers, and you have axe enabled I am pretty sure it will sync
I have something like gun.get('nodes').map().once(console.log) and I can't find a way to stop that map()
(that was suppose to be a + but it got turned into a bullet)
I can't see or hear either of you
Shoot
might be a NAT issue
^^^^ new link,
@Dletta looks like meethign space relay is down
