I dunno if is a real problem or is just something that can appen
Most likely hitting an heroku limit? check the service faq
Clients that break these limits in requests will see their request fail with a 400 Bad Request response.
@ruslanjan: You have to manually create a text index. In MongoDB or SQL, this is done automatically for you (if you specify you want it indexed), but in Gun you create the index yourself:
gun.get('thatIndex').get(item.name).put(refToItem);
and then you use the LEX queries
@rococtz:matrix.org
@cryptoboid :wave: hiiii! :) :clap: @mundane_pftts:matrix.org ! Did that work?
@achilldotes_twitter only a server can generate emails so you'd need a backend :( :( :( tho in past we've talked about adding an email gateway to the relays that has a rate limited notification API, would you be interested in helping build this? I'll screencall and show you the code & algorithm to start. Elsewise on page load just check localStorage for account else generate
@ruslanjan 3 years ago @robertheessels built a full text search demo, but it probably would need to be rebuilt - you up for that? Its fun! :clap: @rococtz:matrix.org Bunch of phonetic word vector indices! I'll screencall and help work you thru it.
@GiuseppeLantieri :clap: @lmangani:matrix.org . Maybe try to redeploy? (If you can tell me the crash error, that'd help)
@yokowasis yo @mmalmi <-- Iris-lib Q for you!
@rococtz:matrix.org AXE screencall today work for you?
@achilldotes_twitter only a server can generate emails so you'd need a backend :( :( :( tho in past we've talked about adding an email gateway to the relays that has a rate limited notification API, would you be interested in helping build this? I'll screencall and show you the code & algorithm to start. Elsewise on page load just check localStorage for account else generate
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!@ruslanjan 3 years ago @robertheessels built a full text search demo, but it probably would need to be rebuilt - you up for that? Its fun! :clap: @rococtz:matrix.org Bunch of phonetic word vector indices! I'll screencall and help work you thru it.
@GiuseppeLantieri :clap: @lmangani:matrix.org . Maybe try to redeploy? (If you can tell me the crash error, that'd help)
@yokowasis yo @mmalmi <-- Iris-lib Q for you!
@rococtz:matrix.org AXE screencall today work for you?
@cryptoboid can you update the docs section with this info? https://github.com/amark/gun/wiki/Svelte
1 reply
@mochic :wave: !! If you want to get latest value, probably want
.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: I had a look at the docs and code for AXE, but unfortunately it's beyond my abilities. It requires full time involvement and I am afraid it's not possible for me at this point. I am afraid I will have to limit myself to helping around in the chat and answer questions and continue to play with Gun as someone who consumes Gun for the moment
@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.
@yokowasis excellent! Yes the PR is good idea just wanted to move the code into the appropriate self-contained adapter, and similarly for multicast in
gun/lib/multicast. the http.js npm start calls those adapters, so don't fear, edits there to use env configs will be part of the default check.
@amark I have just created this indexed text search as an example for @ruslanjan
If you are happy with the code, I can update the AWESOME list in the wiki
https://codesandbox.io/s/react-playground-forked-lyn1g
If you are happy with the code, I can update the AWESOME list in the wiki
https://codesandbox.io/s/react-playground-forked-lyn1g
1 reply
wow that was so fast that you built it!
is it much harder to split on word (or n-grams) and index each word?
^ I was wanting to find "cute Fox"
since
* LEX is prefix based it correctly found fast cheetah
that's only because I have no idea how to use LEX! :) Do you have an example of "includes" as opposed to "prefix"?
I will try it now
and you know how important O(1) perf is to me
I argued we could create an "includes" operation later on top
by doing just this, then indexing the values as their own
and re-running LEX (the more limited version) on that
so while a little more work on top, it only needs to be done once as a framework, and then we get for free all the same O(1) perf that the system forces.
any idea why this happened ?
BRB jumping on a call
amazing demo so fast!