amark on master
fix(npm): change glob preventin… (compare)
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.
*LEX is prefix based it correctly found fast cheetah