@gessicapps_twitter put(null)
@gessicapps_twitter ^
for example
There are a lot of onion skins for me to pull back yet with GUN.
I'm using gun to update a react page with a lot of user-editable elements that are synced across devices, and I'm noticing that it can sometimes take a while (30 - 90 seconds) to get to the latest version (it seems like it runs through a lot of the history). I would think that gun would locally cache calls to .get()?
Also would using .set() instead alleviate some of these issues? There are a lot of entries in there that are nulled or marked as deleted and it has to download the non-nulled versions first before deleting them making for a poor UX
@aaronsantiago might benefit from using the option change: true when using once().
Hmm maybe not if the change is null
I am trying to wrap my head around Lex, but the documentation does not describe what some of the characters used in the examples actually do, specifically #, +, and ..
Here are some Lex examples pulled from the SEA certify docs, could someone please describe what the #, +, and . characters do in this context?
{"*": "notifications", "+": "*"} // Path must start with "notifications", then Path or Key must contain Certificant's Pub (it's just (path||key).indexOf(pub)!=-1)
{"#": {"*": "inbox"}} // Path must start with "inbox". "get('inbox').get('Alice').get('secret').put('abc', null, cert)" and "get('inbox').get('Bob').get('sensitive').put('something', null, cert)" ARE ALL OK.
{"#": {"*": "project"}, ".": {"*": "Bob"}, {"+": "*"}} // Path must start with "project" and Key must start with "Bob", then Path or Key must contain Certificant's Pub.
"inbox/Bob" // Path must equal "inbox/Bob", it is a LEX exact match {"=":"inbox/Bob"}
["inbox", {"*":"projects", "+": "*"}, {"*":"employees"}] // an Array of rules. If any matches, continue.
@aaronsantiago: If you deleted something, it will still show as
null. The solution to get rid of this is to use map(); if the value is null just manually returned undefined so the callback is not triggered anymore. About the local storage, the 5MB limit is annoying, but IndexedDB is much much slower
3 replies
@alxndr: there are plenty of ways https://gun.eco/docs/Awesome-GUN#plugins-helpers
1 reply
This one is the first that I clicked and it doesn't give 404. It even has a youtube video on the README page and the creator is active in chat @Dletta
1 reply
@AlexZan: gun-graphin and gun-scape also should work fine (i mostly maintain them) what viasualizer projects are you referring to?
1 reply
[D]Aethiop: I've been trying to upload a file to gun by chunking the data and downloading the file is just reading those chunked data to a blob and creating object URL for it but it seems that it's not getting the full file something is wrong when reading the file because the size is not the same as the upload and also the file is corrupt. Can anyone help me out on this?
[D]Aethiop: ```let files = {};
let reader = {};
let loading = true;
var slice_size = 1024 1024 1;
let reader = {};
let loading = true;
var slice_size = 1024 1024 1;
const is_file = () => {
if (files && files[0] && files[0].size > 0) {
return true;
}
return false;
};
let prev = user.get("file");
function upload() {
if (files[0]) file = files[0];
if (is_file()) {
prev = prev.get(file.name).get("next");
reader = new FileReader();
upload_file(0);
}
}
function upload_file(start) {
var next_slice = start + slice_size + 1;
var blob = file.slice(start, next_slice);
reader.onloadend = function (e) {
if (next_slice <= file.size) {
prev.put({ data: e.target.result });
prev = prev.get("next");
upload_file(next_slice);
} else {
loading = false;
}
};
reader.readAsText(blob);
}```
[D]Aethiop: This is how I'm Uploading the download is kinda the same just reading from the linked list
[D]Aethiop: ```
async function getChunks(k) {
var next = user.get("file").get(k);
var chunks = "";
while ((await next.get("next").get("data")) != null) {
next = next.get("next");
chunks += await next.get("data");
}
return chunks;
}
user.get("file")
.map()
.once(async (d, k, n) => {
var fileChunk = await getChunks(k);
var data = new Blob([fileChunk], { type: "text/plain" });
async function getChunks(k) {
var next = user.get("file").get(k);
var chunks = "";
while ((await next.get("next").get("data")) != null) {
next = next.get("next");
chunks += await next.get("data");
}
return chunks;
}
user.get("file")
.map()
.once(async (d, k, n) => {
var fileChunk = await getChunks(k);
var data = new Blob([fileChunk], { type: "text/plain" });
var url = window.URL.createObjectURL(data);
console.log(data.size);
if (fileChunk) {
files = [
...files,
{
url: url,
name: k,
size: data.size,
},
];
}
});```
[D]Aethiop: Console log shows the same thing when uploading and downloading its just the file gets corrupt i don't understand
where files would be the wanted keys I suspect, getChunks returns a promisified gun.get.then (ie a real value) and all boils down to a single
then - well my example doesn't have return value described as it's from a generic job iterator, but you get the point
getting this error
gun.js:1672 WebSocket connection to
it work from node
was anyone able to get it working for chrome extensions? it seems like a logical use case
@ravecoin:matrix.org :fire: :) . :clap: @abow !
@cursedideology:matrix.org we don't control the site.
@connor-davis :clap: @lmangani:matrix.org yeah, trystero definitely nailing the head better than GUN - should use
@yokowasis :clap: @lmangani:matrix.org :clap: @connor-davis
@connor-davis did you make the logo yourself!? :)
@yokowasis oh no! :( don't spend hours on something when you know we can more quickly identify it as a bug or figure out what the issue was. I've not heard of a bug about callback not getting fired yet, but I know the LEX queries are some of the most complicated (they do have tests tho: gun/tests/rad/rad.js ) and had to squeeze it out in time for launch. (Thanks for the vid, your test data is all
:clap: :clap: :clap: @jabis I think you just did more tests during that debugging than I have in mocha, oye - someone here willing to toss them into that file?
... tho fetching the whole node first defeats the point, @yokowasis is correct.
@Fredaroo_twitter <3 <3 :) :) . I'm gonna refactor the docs - any tips for me while I'm at it? Will check your SO... (remind me if I don't reply)
Docs all pull from the GitHub wiki, anyone can edit in-browser instantly: https://github.com/amark/gun/wiki
@abow :sweat_smile:
@gessicapps_twitter :clap: @yokowasis
@daviddahl which talk on AXE (?). WOW nice talk (slides) yourself! What is with the 2032 date? ... YOU IMPLEMENTED THE BROWSER CRYPTOGRAPHY APIS!!??? Holy cow, you're a legend. Ah, good ol'days when "crypto" meant "crypto"... cryptography, not scamtokens. What happened to ZK? Wow, so many questions now - what were your thoughts on our 1min Cartoon Cryptography explainers? What do you think of Party? How do you like the SEA api that wraps your work?
@aaronsantiago is the 90s delay between separate devices where 1 of them is Windows? This is often fixed by adding
@alxndr :clap: @rococtz:matrix.org :clap: @lmangani:matrix.org ! There is also @mmalmi 's "explorer" in Iris, @yokowasis has a database viewer too.
@jakethejab interesting, those symbols aren't actually part of LEX officially, interesting, and I haven't used Certify yet ... can someone help? What do these other oens mean?
@aaronsantiago :clap: @rococtz:matrix.org
@bmatusiak which part of that talk? Tho in there defense... 2009 GUN didn't exist.
discord@Aethiop @aethiop way cool! :clap: @jabis ! Interesting, yo'ure saying the console.log of the upload === the download? Then we know its not corrupt at that point. Maybe we can also add this to our call coming up.
@ignas-g do you have
@cursedideology:matrix.org we don't control the site.
@connor-davis :clap: @lmangani:matrix.org yeah, trystero definitely nailing the head better than GUN - should use
makeAction as a transport layer! Such a great demo.@yokowasis :clap: @lmangani:matrix.org :clap: @connor-davis
@connor-davis did you make the logo yourself!? :)
@yokowasis oh no! :( don't spend hours on something when you know we can more quickly identify it as a bug or figure out what the issue was. I've not heard of a bug about callback not getting fired yet, but I know the LEX queries are some of the most complicated (they do have tests tho: gun/tests/rad/rad.js ) and had to squeeze it out in time for launch. (Thanks for the vid, your test data is all
a:"b" hard for me to differentiate, sorry):clap: :clap: :clap: @jabis I think you just did more tests during that debugging than I have in mocha, oye - someone here willing to toss them into that file?
... tho fetching the whole node first defeats the point, @yokowasis is correct.
@Fredaroo_twitter <3 <3 :) :) . I'm gonna refactor the docs - any tips for me while I'm at it? Will check your SO... (remind me if I don't reply)
Docs all pull from the GitHub wiki, anyone can edit in-browser instantly: https://github.com/amark/gun/wiki
@abow :sweat_smile:
@gessicapps_twitter :clap: @yokowasis
@daviddahl which talk on AXE (?). WOW nice talk (slides) yourself! What is with the 2032 date? ... YOU IMPLEMENTED THE BROWSER CRYPTOGRAPHY APIS!!??? Holy cow, you're a legend. Ah, good ol'days when "crypto" meant "crypto"... cryptography, not scamtokens. What happened to ZK? Wow, so many questions now - what were your thoughts on our 1min Cartoon Cryptography explainers? What do you think of Party? How do you like the SEA api that wraps your work?
@aaronsantiago is the 90s delay between separate devices where 1 of them is Windows? This is often fixed by adding
gun/nts.js which does clock sync (tho note: I don't think it works in latest). If not, the local benchmarks do about 5K ops/sec, however I noticed weird delays going on in AXE with the Fireship launch, so I'm hoping maybe you've figured out how to replicate it?@alxndr :clap: @rococtz:matrix.org :clap: @lmangani:matrix.org ! There is also @mmalmi 's "explorer" in Iris, @yokowasis has a database viewer too.
@jakethejab interesting, those symbols aren't actually part of LEX officially, interesting, and I haven't used Certify yet ... can someone help? What do these other oens mean?
@aaronsantiago :clap: @rococtz:matrix.org
@bmatusiak which part of that talk? Tho in there defense... 2009 GUN didn't exist.
discord@Aethiop @aethiop way cool! :clap: @jabis ! Interesting, yo'ure saying the console.log of the upload === the download? Then we know its not corrupt at that point. Maybe we can also add this to our call coming up.
@ignas-g do you have
/gun on it? My extensions don't peer actually, maybe Chrome not like outbound connections?
6 replies
@amark my video is not about the result {"a" : "b"}. It's about the amount of it get fired. The expected result is there should 7 x {"a" : "b"} fired.
The bug is : the same command run multiple times, yet it has different result.
e.g.
1st run result : 7 x {"a" : "b"} fired.
2nd run result : 4 x {"a" : "b"} fired.
8th run result : 1 x {"a" : "b"} fired.
It's using gundb on local browser with no peer. So we can rule out the latency / slow peers.
You can see my initialization below the video. It's 1 page index.html page.
Now that I think about it. I never tried local storage
@amark, > ... tho fetching the whole node first defeats the point
like I said, make a metadata .get('chat').get('meta') first - didn't need to be the root object, just somewhere in the path it seemed
like I said, make a metadata .get('chat').get('meta') first - didn't need to be the root object, just somewhere in the path it seemed
but it's definitely a reincarnation of the "first get produces undefined", so possibly a regression