amark on master
Update README.md (#1181) (compare)
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!
Clients that break these limits in requests will see their request fail with a 400 Bad Request response.
await SEA.pair()to create new! Then you can
SEA.secret(share their email with some admin account you run. Usernames are not secure cause there is no centralized enforcement of who owns the username, this is p2p/offline/local-first remember!
.put(instead. If you want like the "last chat message in chat history" tho where you still need to use
.set(then you could always have a special
.get('chat').get('last').put(gunRefToLastSentMsg)property you index to and read from.
@amark regarding my PR on Github. I feel like the example/http.js is still the best way to quickly, and error-proof, deploy a relay server. I mean all you need to do is
npm start. It's not about whether axe is bugged or not. But some people / company prefer, their relay is not becoming part of the AXE network.
That's my reason. Perhaps, while we're at it, it would be great to also to make the multicast port changeable via environment. It's always good to have more option.
http.jsnpm start calls those adapters, so don't fear, edits there to use env configs will be part of the default check.