I cant give you guys a link to try it yet though since the build is broken with some weird BigInt error, i submitted a bug report to create-react-app about it
heres a comparison between gun and yjs latency and performance wise for the position syncing (theres a small fps counter top left, gun fps is at least 40fps lower)
im using a context like this to access
gun and user
3 replies
then im updating the player location in an interval like this
and im reading position updates using
.on
@syonfox: If you put data in Gun, it will be readable by everyone, no matter where you put it. If you put data in public space, everyone can modify it and you can't do anything about it. If you put under your own user space, only you can edit it by default. There is a feature (SEA.certify) that allows you to grant people write access to your user space data. There are 2 ways of certifying:
1) specific people (only Bob and Alice can write under this part of the graph)
2) wild card rules (for example everybody can write under this subgraph but only under a key that contains their own public key, or maybe everybody can write under
1) specific people (only Bob and Alice can write under this part of the graph)
2) wild card rules (for example everybody can write under this subgraph but only under a key that contains their own public key, or maybe everybody can write under
messages/inbox/)
This means there is no actual use case for the public space in a production-ready app. It's good for testing, it's good for prototyping, for debugging, for many things, but definitely not for storing app data that you care about
I am trying to create an user but get undefine as ack. const handleSignUp = (e) => {
e.preventDefault();
user.create(id, password, (ack) => {
console.log(ack.sea);
// if (ack.sea) {
// user.get("profile").put({
// pub: ack.sea.pub,
// name: userName,
// pic: profilePic,
// });
// }
});
};
e.preventDefault();
user.create(id, password, (ack) => {
console.log(ack.sea);
// if (ack.sea) {
// user.get("profile").put({
// pub: ack.sea.pub,
// name: userName,
// pic: profilePic,
// });
// }
});
};
@rococtz:matrix.org Thanks that does clear it up. I naively assumed certify did something simaler to sign. https://gun.eco/docs/SEA.certify
https://gun.eco/docs/Content-Addressing There is also frozen data whitch compleates the picture
https://gun.eco/docs/Content-Addressing There is also frozen data whitch compleates the picture
@bresnow
@DrAlta <3 <3 <3 Thank you, I really appreciate hearing that. Open Source is hard work, everyone uses it, but few express gratitude, even fewer fund, even fewer help. Our ratio is like 1 person contributor to like 10million users. :scream_cat:
@syonfox correct, nobody can change that post, even if they follow it from the public space. However, anyone could override the public space's link to your post to something else. You may want the frozen space (content-addressed), which is public but cannot be edited (by anyone, even the author).
@lain:iwakura.xyz hey! @mike.stone_gitlab also building games. We were just chatting about latency a minute ago on twitter. In my space game, I see about ~100ms latency. Looks like yours is higher? (Tho hmm, mine may be because of WebRTC) Definitely should be able to get it down lower. I like these FPS benchmarks, I need more of them to keep testing GUN against. Let's do a screencall?
:clap: @rococtz:matrix.org @rococtz
@Mac16661 does it happen if there are no peers?
@finwo there is nothing more common than the browser :P and Skypack is able to automate ESM & @aethiop was able to figure out even React-Native without weird changes to GUN. If there is a will ;) there is a way ;) shoot me some times.
.map() may be async, pulling from remote peers. I'm guessing remix requires the data to be return data synchronously, and that's causing the mismatch.@DrAlta <3 <3 <3 Thank you, I really appreciate hearing that. Open Source is hard work, everyone uses it, but few express gratitude, even fewer fund, even fewer help. Our ratio is like 1 person contributor to like 10million users. :scream_cat:
@syonfox correct, nobody can change that post, even if they follow it from the public space. However, anyone could override the public space's link to your post to something else. You may want the frozen space (content-addressed), which is public but cannot be edited (by anyone, even the author).
@lain:iwakura.xyz hey! @mike.stone_gitlab also building games. We were just chatting about latency a minute ago on twitter. In my space game, I see about ~100ms latency. Looks like yours is higher? (Tho hmm, mine may be because of WebRTC) Definitely should be able to get it down lower. I like these FPS benchmarks, I need more of them to keep testing GUN against. Let's do a screencall?
useEffect I think does weird magic, try location.watch = location.watch || location.on(... to prevent its magic maybe? :clap: @connor-davis correct, here, I believe, I've seen a lot of React apps trash GUN performance because of some weird useEffect magic.:clap: @rococtz:matrix.org @rococtz
@Mac16661 does it happen if there are no peers?
@finwo there is nothing more common than the browser :P and Skypack is able to automate ESM & @aethiop was able to figure out even React-Native without weird changes to GUN. If there is a will ;) there is a way ;) shoot me some times.
@syonfox oh good you already found frozen/content!
anyone know of a good decentralized identity solution? like a way to have the same login across different apps for example. the user auth in gun works for a single app, but you cant just give your username and password around to different apps right?
Tho again, the big problem is HTML/DOM have the biggest security exploits, so I'm probably gonna ship my own "gaming" version of it, which I doubt the others will sponsor.
I'm trying to get my custom version out ASAP but bleuh, have to create webworker <-> sandboxed UI bindings and that suuuuucks, here was the demo from the toher week: https://twitter.com/marknadal/status/1459369619488010243
1 reply
you see many here in the community are keeping help/support alive :P and I should be working on docs, but I kinda want to have the docs run this, so the docs can be interactive itself. This is separate from our opportunity to test & fix & battleharden AXE agaisnt the 50M monthly users, which... is most vital, cause things keep growing so fast.
I'm trying to do weekly office hours to do screencalls to get bugs fixed and people organized to help speed up these things
so hollar if you want to be involved with the others on the actual building of this.
@amark lmk what you end up doing with AXE, I would love to help some more with that! I been dissecting Trystero with the hope of creating a DHT just for Gun that works both in node and the browser AND creates a chord-like network of peers, though that could flip the entire concept of axe haha
@Manuel-777: have you checked out bugout? https://github.com/chr15m/bugout i always wondered which is more decentralized, trystero or bugout. trystero uses trackers which if its a public tracker then it can get overloaded with traffic, bugout uses webtorrent.
though, i don't know if one is better than the other, in fact thats what i wanna find out. check out bugout and tell us/me your initial thoughts about how it would compare to trystero. i looked at both but i still have no idea how one compares ot the other, other than bugout uses webtorrent(so by extension that means dht) and trystero uses webrtc with public trackers.
@rogowski already has PANIC tests for stuff like this.
checked the repo, looks like bugout relies on trackers too(not dht). @amark: wish i could but this week i'll be spending extra time at the office(training for my new position). my knowledge is very general and basic, but i hope @Manuel-777 joins you. i have been reading his posts here and its interesting.
Also @amark In terms of the way that peers work, does gun like switch between peers everytime it wants to send out data or do all peers get the same data? Because my concern always has been about how much storage will be available and what happens when a peer gets full
And All the jazzz