you're using a public/demo one which is not guaranteed to be reliable, run your own GUN server and the issues will disappear
issue still continues
that's got nothing to do with it
not sure where you're getting this from, but you need to run your own GUN server and then use that for your project if you want it to be reliable and up to your own devices ;)
nah, ngrok is just a packet forwarding tool, i know it perfectly, not good for your case
But it use to be working i do not understand the problem what changed
its a lot easier if you start a GUN server somewhere (dynos, glitch, anything) and connect there w/o trickery
Your errors will dissipate very quickly
free
its a lot better if you find out from there precisely than out of a chat ;)
Okay but i still doubt it is becouse of i dont have GUN server it use to be working just fine.
you're using someone else's peer, it might go offline, be broken, disappear, etc
up to you man, do as you prefer :) just sharing advice
and YES pure luck 15 days is a row sounds fine, if there's an issue with that specific server, it might even be 360 days of luck. Use your own resources if you want to guarantee uptime/etc in your app
s
right now
but if you see websocket connections fail, look no further
i belive it has something with the code
I used the same codes before
hi. If I created a user in one computer and try to login that in another computer I got this error? what is dare is not a function.
Hello wonderful person! :) Thanks for using GUN, please ask for help on http://chat.gun.eco if anything takes you longer than 5min to figure out!
radisk.js:28 ERROR: Radisk needs `opt.store` interface with `{get: fn, put: fn (, list: fn)}`!
tmp_js_export.js:362 Error calling method once on: Gun_: {$: Gun, root: {…}, id: 5, back: {…}, on: ƒ, …}[[Prototype]]: Object error: TypeError: dare is not a function
...
...
I found it. it is a /lib/store.js function triggered
Gun.on('create', function(root){
...
@jabis :+1:
@dweorh_twitter interesting . Can I ask a dumb question: What use cases exist for "everyone" certificates?
@deathg0d https://gun.eco/docs/RAD#lex ! :)
@dot357:matrix.org glad you got your issue fixed! :)
@ulvido You're missing
:clap: @dweorh_twitter @lmangani:matrix.org @yokowasis !
@Fredaroo_twitter so more generics? Yes, please be detailed, the better I can improve things then.
@daviddahl Wow. Wowowowwow. Can you help me get http://securerender.org/ off the ground? I've already gotten Mark Mayo (ex-CPO Mozilla) Brendan Eich, and some Edge roughly interested.
@dweorh_twitter interesting . Can I ask a dumb question: What use cases exist for "everyone" certificates?
@deathg0d https://gun.eco/docs/RAD#lex ! :)
@dot357:matrix.org glad you got your issue fixed! :)
@ulvido You're missing
gun/lib/radisk.js in your list it looks like.:clap: @dweorh_twitter @lmangani:matrix.org @yokowasis !
@Fredaroo_twitter so more generics? Yes, please be detailed, the better I can improve things then.
@daviddahl Wow. Wowowowwow. Can you help me get http://securerender.org/ off the ground? I've already gotten Mark Mayo (ex-CPO Mozilla) Brendan Eich, and some Edge roughly interested.
4 replies
@amark Hey, for me there are a few use cases, to store some not critical data like:
- Anonymous tracking.
- Leave feedback, do a survey
- Leave contact details to call-back or so
Nothing fancy. Only one user can be authenticated at the time, so if we would like to do all that in one session, it would require 3 new users, with user().auth and user().leave. Not a big deal, but there is information in SEA.certify() about 'everyone' but should be 'everyone authorized'. That may save other developers hours of debugging ;)
“Gun.js: Painless React State Management”. Comments? https://siriusbusiness.fi/gun-for-react-state-management
feel free to suggest edits https://github.com/mmalmi/mmalmi.github.io/blob/master/_posts/2021-9-27-gun-for-react-state-management.md
link to some redux boilerplate example would be welcome
Indeed, as part of the flow you should create and maintain a separate index of users that's made for searching and interacting without using (or leaking) anything about the real user objects. Possibly opt-in ;)