Also, if you want to reverse engineer it, why not just straight-forward engineering without reversing it?
https://gun.eco/docs/Porting-GUN
https://gun.eco/docs/Porting-GUN
@rococtz:matrix.org thank you so much, I think this might be my prime choice as long as it's open source. Looks very robust. My only complaint is how it automatically creates an account on first page visit. However, I bet that is more of a DAPP thing and is pretty well respected in the DAPP community. I will be considering that in my implementation.
that's nothing to do with gun
it's just an app decision in iris messenger
@3210jr :wave: ! :clap: @rococtz:matrix.org
@libensveto_twitter ahh duh I should have realized that lol sorry. Interesting. I'm not super familiar with blockchain/payment world, so is what gun is doing here is realtime updates - but don't they depend upon reading ethereum status, so therefore just as slow?
@achilldotes_twitter :wave: ! :clap: :clap: @rococtz:matrix.org !
@libensveto_twitter ahh duh I should have realized that lol sorry. Interesting. I'm not super familiar with blockchain/payment world, so is what gun is doing here is realtime updates - but don't they depend upon reading ethereum status, so therefore just as slow?
@achilldotes_twitter :wave: ! :clap: :clap: @rococtz:matrix.org !
@3210jr: anytime, good luck with the app 👍️ I think we always have to assume bad intentions from the users when building apps
@ruslanjan: what do you mean by that?
Iris should automatically create an account if you navigate to a url other than the root (https://iris.to). I chose that so I don’t need to make views for non-logged-in users, keeping things simple
Yet you’re not blocked by the login screen when following a direct link to someone’s profile
Hey again, the docs indicate that the
I'm coming across it in a few examples and snippets, and have some uncertainty around it. Thanks!
user.grant() method is deprecated, what is recommended instead of that? is it to create a certificate like: var certificate = await SEA.certify(alice.pub, ["^AliceOnly.*"], bob) and then use the cert in writing to the users node?I'm coming across it in a few examples and snippets, and have some uncertainty around it. Thanks!
1 reply
Maybe stupid question but couldn't find in docs... Is there anyway to protect data from unauthorized modification or maybe immutable unchangeable data?
1 reply
Hi,
I played with user nodes as read only data and was surprised to see users child nodes listed by get users node by pub key?
gun.get('~<PUBKEY>').once(console.log)
[...]
BUM: {#: '~MHmPSW9L6hPIz6LSOT_awz53vgOV3KzJU_q6EjtwbYc.hAorZTIMtoVvGiIOSlFVG0Ts_PlwDsoRm6gJikT_ZL4/BUM'}
BUM2: {#: '~MHmPSW9L6hPIz6LSOT_awz53vgOV3KzJU_q6EjtwbYc.hAorZTIMtoVvGiIOSlFVG0Ts_PlwDsoRm6gJikT_ZL4/BUM2'}
BUM3: {#: '~MHmPSW9L6hPIz6LSOT_awz53vgOV3KzJU_q6EjtwbYc.hAorZTIMtoVvGiIOSlFVG0Ts_PlwDsoRm6gJikT_ZL4/BUM3'}
BUM4: {#: '~MHmPSW9L6hPIz6LSOT_awz53vgOV3KzJU_q6EjtwbYc.hAorZTIMtoVvGiIOSlFVG0Ts_PlwDsoRm6gJikT_ZL4/BUM4'}
[...]So it's possible to read the hole user nodes / graph if the public key is known?
So have a user/trusted node encrypt data in a signed fashion so as long as you trust that user you can rely on the data?
Some days back there was an example with path like node names / IDs... Thats nice to get child nodes. But is there a technical reason why I shouldn't use path style (
/parent/child/node) to create new nodes? I can keep that strings simple without special characters apart from/...
Ok, read graph / tree like a path seams to work, but create nodes that way seems to be not the same...
@ruslanjan SEA includes the await ability, GUN does not by default.
@mmalmi :clap:
@3210jr :clap: @jakethejab .
@erokken:matrix.org :clap: @jakethejab
@pwFoo
@libensveto_twitter :clap:
@mmalmi :clap:
@3210jr :clap: @jakethejab .
@erokken:matrix.org :clap: @jakethejab
@pwFoo
.open(cb after requiring it, docs/API#open/ has no special meaning, at any point the soul or UUID could be random, not a path, so be careful.@libensveto_twitter :clap:
@pwFoo: What do you mean by hide? Hide them when you request them or just hide them so nobody can access them at all?
@rococtz:matrix.org I think it's needed by design... But wasn't clear to me.
@pwFoo: yes, in gun ALL data is visible by everybody, even if they don't know the pub key
@pwFoo: right, I should have mentioned that! everything is visible, but if you encrypt it on the client side using SEA.encrypt, everybody will still be able to see it but it won't mean anything to them
Would be cool If we could just use existing network
btw how AXE is going?
@amark: Imagine this situation, please: I deploy my peer to heroku and it will have AXE turned on by default. My peer will automatically be added to a cluster. After a while, my peer gets taken down for whatever reason. Is there any way to ensure the data was replicated redundantly on other peers? Is there any way to force that?
@erokken:matrix.org :clap: @rococtz:matrix.org !
@rococtz:matrix.org because we have millions of unreliable browsers to start with, that will already be emulating that behavior, yes, relay peers will have the same logic.
Peers will choose a shard key, and the health of that shard key (online replication factor) will have to be monitored.
@rococtz:matrix.org because we have millions of unreliable browsers to start with, that will already be emulating that behavior, yes, relay peers will have the same logic.
Peers will choose a shard key, and the health of that shard key (online replication factor) will have to be monitored.
@amark: How can we make them choose the right shard key? Can you tell a node relay "Hey, other than being a relay, can you also make sure you always watch this subgraph?" ? The other worry is how do you watch user spaces since they are all root nodes?
@amark: Are there any examples on how to use these shard keys? I am a bit behind on that and on AXE in general
I would like to, but where would I start? At the moment I know nothing about it
🤩🤩🤩Thank you!!! You're already so helpful just replying to people too!!
Sorry I would've replied right away but I started working on docs and missed your message.
@amark: no worries :) It would be great if you could share all the reading materials on AXE and then we can see where that takes us! I am in New Zealand
@rococtz:matrix.org well :P the explainers are in podcasts from years ago I'd have to hunt down, the code is just stuff like https://github.com/amark/gun/blob/master/lib/axe.js#L35-L58 ... what this basically says is "each time somebody asks for data, take turns sending it to 3 other peers at a time. If they happen to reply all with the same data, then stop sending it to the network. If the data is different, or nobody is subscribed, keep falling back to others in turn"
lines 69 ~ 95 is for when somebody saves data to the network, it tries to only relay it to people who are subscribed to common soul, and debounce (but that might be causing the delays :( so need to PANIC test this... https://github.com/amark/gun/blob/master/test/panic/load.js , https://github.com/gundb/panic-server )