@narnikgamarnikus congrats :D :D :D
Yeah, you'd have to build your own list of online/offline users - there is an old old old prototype of this here: https://gun.eco/docs/shim.js#-code-ondisconnect-code-
@QVDev we should have you on the proper podcast to talk about your video streaming work in general.
Yeah @Dletta .
Yeah, you'd have to build your own list of online/offline users - there is an old old old prototype of this here: https://gun.eco/docs/shim.js#-code-ondisconnect-code-
@QVDev we should have you on the proper podcast to talk about your video streaming work in general.
Yeah @Dletta .
@rm-rf-etc like the new topics would like to know more about them so I can be more of a spectator asking questions during the podcast
@amark maybe a podcast specific for all upcoming work and what the state is would be nice. So everone prepares a demo and explain and gives an update and what is next on the roadmap. Probably less technical but nice to watch the showcases and posibilities of gun
@QVDev Gun sends everything as JSON, so you would have to send it as an array and do your conversion in app code.
@QVDev Or you would need to switch out the GUN transport layer for something like MessagePack. However I think that can only send binary as a Uint8Array. Not familiar with the Clamped array.
@QVDev remember we discussed this at the outdoor food garden in berlin? It'll be easier + more performant to have opt-in transport adapters with Buffers/whatever support that you add to your app (so all peers running it get the boost), than trying to get every peer in the entire protocol to all handle Buffers correctly (might not be possible on small IoT devices).
@rm-rf-etc me too! Tho, @QVDev I want to keep a sharp divide between "showing demos" as -> screencast, and "talking about existing & upcoming projects" -> as podcast. Podcasts are easy for newcomers and existing community (if they have hearing, not all in this community are) to catch up on the road/commute or in background. While demos / video is more inaccessible, and should either be shorter (for presentational & educational purposes) or more hack/pair-programming/collaborative oriented (you're not gonna miss out if you don't watch it).
@rm-rf-etc me too! Tho, @QVDev I want to keep a sharp divide between "showing demos" as -> screencast, and "talking about existing & upcoming projects" -> as podcast. Podcasts are easy for newcomers and existing community (if they have hearing, not all in this community are) to catch up on the road/commute or in background. While demos / video is more inaccessible, and should either be shorter (for presentational & educational purposes) or more hack/pair-programming/collaborative oriented (you're not gonna miss out if you don't watch it).
When we receive encrypted data, is there a surefire way to detect that the data is encrypted? For example, a user may decide they want to be anonymous, so we simply encrypt their username. However, I don't want to show other users the encrypted junk when rendering anonymous people in a list, I'd rather hide them in the frontend, or display something that looks nice but communicates that this person has gone anonymous. E.g.
username: ************* instead of username: %2aDgho!@nb
that means we possibly 4 people?
I replied to a question on stackoverflow
https://stackoverflow.com/questions/56044288/private-wite-and-public-read-in-gundb/57971655#57971655
And I ask you for help:
How to make a third user to add a comment to a post, only the author of the post and the author of this comment could edit / delete it?
Or, at least, how to make a comment which is in the third user graph, was associated with the post, located in the first user's graph?
@narnikgamarnikus you're a hero :) thanks for contributing to the StackOverflow, it does not get as much love as gitter/github/etc. CAN OTHERS HELP???? https://stackoverflow.com/questions/tagged/gun
I'm gone at a conference Friday :(
Today/tomorrow/Thurs work.
@rm-rf-etc raw SEA values are prefixed with
I'm gone at a conference Friday :(
Today/tomorrow/Thurs work.
@rm-rf-etc raw SEA values are prefixed with
SEA :) API returns auto-verified data, but doesn't decrypt (actually amark/gun#783 messes up API reply of encrypted data), that will need to be done manually or with some future convenience method I'm hoping I can get others to support/maintain.
@rm-rf-etc regarding availability for conference call. i'm on UTC+3 so might be problematic. but in general my availability is here: calendly.com/hadarr
I prefer weekend days but I can make certain times on Friday work.
You need a shared calendar
I did build an (ugly) calendar app tho
Hey guys.
user.pair() raises a deprecation warning. What whould I be using instead? I'm doing this and it's working great: // runs in browser A
const s2 = async bobEpub => {
const alice = user.pair();
if (typeof user.is !== "object") {
throw new TypeError("user.is not an object");
}
if (typeof bobEpub !== "string") {
throw new TypeError("bobEpub is not an string");
}
const sec = await SEA.secret(bobEpub, alice);
const enc = await SEA.encrypt("secret message", sec);
console.log(enc);
};
// runs in browser B
const s3 = async (encodedMsg, aliceEpub) => {
const bob = user.pair();
const sec = await SEA.secret(aliceEpub, bob);
const msg = await SEA.decrypt(encodedMsg, sec);
console.log(msg); // "secret message"
};
I know it looks ugly, but
user._.sea
this is intentional, because your keypair may not always be available in the JS app, because the goal of SEA is that it might be running all cryptographic operations in a browser extension, secure enclave, or hardware wallet.
(crypto newbie here)
@rm-rf-etc that didn't do anything :/