[D] marknadal: <@!636489182214357002> try to keep me accountable (but warning, may fail several times around)
[D] marknadal: brb
[D] jabis: <@!178314946201780224> howbout introducing a sidechannel for partial acks directed at only the initiator expecting the full save
[D] Maxotronic: Is there a straightforward comparison between Gun and Dat? 🙂
[D] jabis: regular ack mechanics would be contained and the sharding should work, but your WIP is only interesting to that 1 party - so partyline the progress
[D] mmalmi: >
cause lS:false definitely stops
gun/https://github.com/amark/gun/blob/master/gun.js#L1958
<@!178314946201780224>localStorage.clear();location.reload()doesn't reset my gun data. I wonder if it could be using indexedDB despite initializing withGun({peers: [], multicast:false, store: localStorage, indexedDB: false});
[D] jabis: getting too late for my brains too, 2.20am x)
[D] anthonyfabrizi: I was hoping we can delete string or object by putting a null
[D] marknadal: <@!648558515463651338> explain what you mean more?
<@!636489182214357002> like indexedDB is "refilling" localStorage? Isn't easy to check by console.log(localStorage) to see what props are on it?
<@!706150500621353112> ignoring the bug, you should be able to
<@!87929869865852928> DAT uses append-only logs, so you can't update/mutate bytes in place like GUN does (tho GUN also supports append-only logs too). DAT primarily NodeJS, while GUN is built 1st for browser & supported in NodeJS. But 🤷 you're asking a pretty biased source. 😉
<@!636489182214357002> like indexedDB is "refilling" localStorage? Isn't easy to check by console.log(localStorage) to see what props are on it?
<@!706150500621353112> ignoring the bug, you should be able to
.put(null) anything except top level (ie gun.get('foo').put(null)).<@!87929869865852928> DAT uses append-only logs, so you can't update/mutate bytes in place like GUN does (tho GUN also supports append-only logs too). DAT primarily NodeJS, while GUN is built 1st for browser & supported in NodeJS. But 🤷 you're asking a pretty biased source. 😉
[D] marknadal: BBL
[D] mmalmi: Can it be indexedDB if I initialize the instance with
localState = Gun({peers: [], multicast:false, store: localStorage, indexedDB: false});?
[D] mmalmi: let's try
localStorage: false...
[D] mmalmi: yeah, it's still persisting stuff
[D] rogowski: <@!624103263482150912>
I'm drafting a test for RAD query.
I'm drafting a test for RAD query.
1) memory object
- a range of date, hour by hour. i.e. from 2020-01-01T00:00:00Z to 2020-08-12T00:00:00Z. `{"2020-01-01T00:00:00Z":1, "2020-01-01T01:00:00Z":2}`
- reimplemented a small lib do search.
2) gun storage
- put the memory object in gundb node.
3) Make queries in both: memory object and gun storage. Both must have the same results.
- Query 1: {'>':'2020-01-01', '<':'2020-01-02'}
- Query 2: {'>':'2020-01-05', '<':'2020-01-07'}
- Query 3: {'=':'2020-01-05'}
- Query 4: { '*':'2020-01-05' }
- Query 5: { '^':'2020-01-05' }
[D] mmalmi: > Hey, quick question. If I made an e2ee chat with gun, would new users joining the room be able to see history? A lot of e2ee chats don't preserve history for new members and I'd want a way to transfer the history over. The naive approach is for a peer to "DM" the event history over to the new user
<@87929869865852928> on iris-lib group channels everyone shares their group encryption key to new participants, who can then see the history
<@87929869865852928> on iris-lib group channels everyone shares their group encryption key to new participants, who can then see the history
[D] Gorgonslayer: since your all about FOSS, privacy, security
[D] Gorgonslayer: end programs are centralization because the user cant edit it if it become abandonware or the developers are greedy and ant-freedom
[D] anthonyfabrizi: <@!178314946201780224>
(async() => {
let ref = await gun.get('test').get('2020-08-13').put({name: 'data1'}).then()
await gun.get('feed').get('2020-08-13').put(ref)
await gun.get('feed').get('2020-08-13') // returns {name: 'data1'}
await gun.get('test').get('2020-08-13').put(null).then()
await gun.get('test').get('2020-08-13') // returns null
await gun.get('feed').get('2020-08-13') // still returns {name: 'data1'}
})()The last line should be null, right?
[D] Dyno: Welcome <@500656809531670539>!!! GUN (https://github.com/amark/gun) is a P2P protocol for syncing data used by 8M+ people monthly across Internet Archive, HackerNoon, DTube (decentralized youtube), Notabug (p2p reddit), & more. Please try the 5min tutorial (https://gun.eco/docs/Todo-Dapp) to get started!
[D] anthonyfabrizi: <@!612728945313316904>
[D] Dyno: Welcome <@241168448934117376>!!! GUN (https://github.com/amark/gun) is a P2P protocol for syncing data used by 8M+ people monthly across Internet Archive, HackerNoon, DTube (decentralized youtube), Notabug (p2p reddit), & more. Please try the 5min tutorial (https://gun.eco/docs/Todo-Dapp) to get started!
[D] mimiza: > <@!624103263482150912>
I'm drafting a test for RAD query.
1) memory object - a range of date, hour by hour. i.e. from 2020-01-01T00:00:00Z to 2020-08-12T00:00:00Z. `{"2020-01-01T00:00:00Z":1, "2020-01-01T01:00:00Z":2}` - reimplemented a small lib do search. 2) gun storage - put the memory object in gundb node. 3) Make queries in both: memory object and gun storage. Both must have the same results. - Query 1: {'>':'2020-01-01', '<':'2020-01-02'} - Query 2: {'>':'2020-01-05', '<':'2020-01-07'} - Query 3: {'=':'2020-01-05'} - Query 4: { '*':'2020-01-05' } - Query 5: { '^':'2020-01-05' }<@!621087760496853023> yoo bro it somehow works but it is not really reliable somehow. Please read the latest conversion here amark/gun#993
[D] mimiza: <@!621087760496853023> it only works when you not refreshing your browser, weird huh ? gun._.graph still shows its data, but user.get(...).get(lex) just shows data only when you stay in the same browser instance and just done putting some data. If you refresh your browser, it doesn't work. Confusing
[D] diatche: > Walter did the
<@!178314946201780224> not yet. I'm still planning on writing some PANIC tests. It's been hard to find the time though
@peculiar/webcrypto NodeJS shims install correctly? (Wait, <@!322522915834953738> you know what is going on? What is it?) WebRTC not work in NodeJS, only browser. In browser WebRTC should continue to sync between the signaled peers regardless of server, if this is not working, could be the regressions that happened in 2020 as I've been trying to updating the code.<@!178314946201780224> not yet. I'm still planning on writing some PANIC tests. It's been hard to find the time though
[D] diatche: >
miniqidev 👏 evdama & diatche would your workaround fix that as well? Could you comment in that issue. Is this only happening for Typescript stuff? If so, maybe we could just add something in the docs for now?
<@!178314946201780224> Are you talking about the gun.user() errors? If so, I can't say whether or not this is only Typescript related as all my development in Typescript 😀 . Basically the workaround is, after importing gun:Gun.SEA = require('gun/sea');. Where should we add this to the docs?
[D] Dletta: > <@!612728945313316904>
let id = 'XYZ'; gun.user().get('posts').get(id).put({...})Above works for me
let id = 'XYZ'; gun.user().get('posts').get(id).put(null)Above didn't work for me, I don't know why
<@!706150500621353112>
Null seems to be broken at the moment... Mark is in the middle of some rewrite that should fix this <@!178314946201780224>
[D] anthonyfabrizi: <@!612728945313316904> Okay thanks
[D] Dletta: I use an older version of gun until the new and improved arrives
[D] anthonyfabrizi: How long do you think the new one comes out?
[D] anthonyfabrizi: Can you send me the older version url?
[D] Mizahnyx: I start getting "NO! Unverified data" plus a dump of the object in console
[D] Mizahnyx: Are the different versions incompatible?
When I message from gitter it means I haven't read/caught up on chat (discord automatically marks things as "read" if I view it there).
Trying to get back into the habit of coding at night... got a little done last night, wish me luck today. I'll be sure to reply to everyone later (like I usually do) and welcome everyone, but may not be responsive over the weekend.
Trying to get back into the habit of coding at night... got a little done last night, wish me luck today. I'll be sure to reply to everyone later (like I usually do) and welcome everyone, but may not be responsive over the weekend.