Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Dec 10 12:58

    amark on dev

    tweak doc (compare)

  • Dec 10 11:25
    RadGade updated the wiki
  • Dec 10 11:23
    RadGade updated the wiki
  • Dec 10 11:19
    RadGade updated the wiki
  • Dec 10 09:26
    sirpy closed #844
  • Dec 10 09:26
    sirpy commented #844
  • Dec 10 09:23
    sirpy commented #844
  • Dec 10 08:55
    mmalmi commented #692
  • Dec 08 15:35
    sirpy commented #844
  • Dec 08 15:34
    sirpy commented #844
  • Dec 08 15:34
    sirpy commented #844
  • Dec 08 15:15
    sirpy commented #844
  • Dec 08 14:49
    sirpy commented #844
  • Dec 08 11:10
    sirpy commented #844
  • Dec 08 04:51
    amark commented #819
  • Dec 07 00:24

    amark on dev

    if wifi off don't crash due to … axe doc music dht :) (compare)

  • Dec 07 00:19
    amark commented #849
  • Dec 06 20:47
    amark updated the wiki
  • Dec 06 09:45
    sirpy commented #844
  • Dec 06 04:28
    arsylum updated the wiki
Jachen Duschletta
@Dletta
The purpose of the meeting would to come up with a working ‘pseudo’ example so it can be implemented
narnikgamarnik
@narnikgamarnikus
Is there a way to get a list of users online?
Or I need to do user().get('online').put(true) at the entrance
and user().get('online').put(false) on exit?
Mark Nadal
@amark
@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 .
QVDev
@QVDev
Quick question: can we sent Uint8ClampedArray via gun?
@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
Rob
@rm-rf-etc
Ya, I like this idea
Julian Stahl
@ThinkingJoules
@rm-rf-etc I don't think I can make it in on the conference call. Have lots of things going on right now, both work and personal, so I wouldn't be able to contribute anyway.
@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
@QVDev
@ThinkingJoules thanks, guess I'll go for the base64 string and convert it back
Mark Nadal
@amark
@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).
QVDev
@QVDev
@amark yeah I remember the adapter will look into it. Dividance of the screencast and podcast make sense indeed as they are complete different topics.
Rob
@rm-rf-etc
@amark @QVDev well if we can get people joining in every week or every other week, could be a recorded standup meeting. Basically show whatever work has been done, even if it's just broken code, and talk about what's next.
Mark Nadal
@amark
:thumbsup: I like that idea
Rob
@rm-rf-etc
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
rogowski
@rogowski
Maybe today guys? 4pm or later after 7pm (CA time) is good for me too @Dletta
QVDev
@QVDev
I am OK for this Friday midday->evening CEST time
rogowski
@rogowski
good too @QVDev
QVDev
@QVDev
:+1:
that means we possibly 4 people?
narnikgamarnik
@narnikgamarnikus

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?

Rob
@rm-rf-etc
I guess I could implement my own format for encrypted values, so that all encrypted values begin with the same sequence of characters, and then I just slice those off before decryption.
Mark Nadal
@amark
@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 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.
Rob
@rm-rf-etc
@amark perfect!
sirpy
@sirpy
@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
Mark Nadal
@amark
@sirpy seems like mid mornings (CA time) for me would match with you. @Lightnet (?)
Rob
@rm-rf-etc

@sirpy it seems like the others all want Friday and don't want to do weekend days. @amark, @Dletta, @QVDev, @rogowski, correct?

@mhelander would you be able to join our meeting for .grant and .trust functionality?

I prefer weekend days but I can make certain times on Friday work.
sirpy
@sirpy
fridays I can only do mornings here. which is middle of the night in the US
Mark Nadal
@amark
Thursdays 10am or 11am CA time?
Rob
@rm-rf-etc
I won't be available but someone else can record
Jachen Duschletta
@Dletta
I work a 7 to 4 schedule PST but Fridays work, Weekend is family time, I could make something work... Worst case, if it’s recorded I might not need to be there, but I can scroll up and gove baseline
Mark Nadal
@amark

EVERYONE SUBMIT TIMES THAT DO WORK DON'T WORK

Rob
@rm-rf-etc
to where?
You need a shared calendar
Mark Nadal
@amark
figured just faster easier here
I did build an (ugly) calendar app tho
Daniel Lugo
@danlugo92
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"
    };
Daniel Lugo
@danlugo92
sorry about offtopic
Mark Nadal
@amark
@danlugo92 not off topic! :) this is exactly what chat room is for :)
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.
Daniel Lugo
@danlugo92
Thanks a lot. It should go without saying that user._.sea is super sensitive info right?
(crypto newbie here)
Mark Nadal
@amark
@danlugo92 yes!
@rm-rf-etc that didn't do anything :/
Rob
@rm-rf-etc
@amark what happens?