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
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?
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...
@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:
@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.
I have been thinking about the idea of automatically creating an account on first visit. I think it is something integral to DAPPs, but at the same time, I think slightly more credentials might be necessary for certain projects. I am thinking in particularly about email authentication. Would it be possible to use SEA to grab user emails and enforce account verification by email? I've taken a first glance at SEA but my biggest concern seems that it would be difficult to add this.
One other concern I have is that it's mentioned in the gundb docs that "It is unsafe to use usernames as links". Why? If a user can already see another username, why can't we have the username appear as example.com/username? Is this sort of option pre-built into SEA? If I can have email authentication, then I would feel more comfortable with allowing accounts to have the advantage of having example.com/username.
Just trying to get a good idea of how things work.
Thank you for taking the time to read this!
