(lukeburns) @e-e-e looking at hyperchat -- pretty cool! are you imagining a situation where a participant's peers might not have the ability to read each other's feeds? seeing that `heard` appends discoveryKeys rather keys.
(e-e-e) @lukeburns yeah - I was thinking that if a peer was not connected to another in the chat history they should not be able to reconstruct that history.
(e-e-e) its really basic at the moment, the toughest part is how to share keys between peers that join - as it would be nice if someone listens to you, you could automatically also listen back. but at the moment it means you all need to share keys in some other way.
(lukeburns) @e-e-e one step in that direction might be to auto-connect to keys that connected peers have heard. e.g. if alice and bob are listening to each other, bob and charlie are listening to each other, and bob announces that he heard charlie and alice via their public keys, alice and charlie can listen to one another.
(e-e-e) interesting - perhaps as a config option it would be nice - as one way it keeps the conversation more closed, the other openning out. If you have one public key you can get them all.
(lukeburns) this doesn't feel too strange to me -- usually when i join a chat room i can see everyone who's in it. it's a little bit awkward if alice is receiving partial information about bob's communications with charlie (when messages are heard).
(lukeburns) but i could imagine there being scenarios where you might want to use more caution
(e-e-e) I am really open to contributions - I started playing with it as a way of getting more familiar with how hypercore works - but also see lots of ways it could be extended out. Eg. Defining a clear protocol rather than json for storing the data, option for displaying history etc.
(lukeburns) cool! i've been playing around with it a bit and ran into that question ^
(e-e-e) totally agree with you - not odd for chat room scenario.
(e-e-e) :)
(e-e-e) I need to also expose port options, as its blocked for me at work which is annoying
G-Ray joined the channel
biotim has quit
biotim joined the channel
pfrazee has quit
chjh joined the channel
G-Ray has quit
G-Ray joined the channel
(G-Ray) @e-e-e : I wrote a basic hyperchat script 1 year ago :P. You can exchange peers when a new peers is introcued https://github.com/G-Ray/hyperchat
(e-e-e) @G-Ray that’s hilarious - thanks for the tip and sharing.
(e-e-e) i will have a look at how you handle it.
(G-Ray) Yeah but hypercore'api changed quite a bit since then I think
(e-e-e) yeah looks like hypecore-protocol has changed a fair bit - but could probably use custom userdata. Did not even think it was a possibility, so thank you.
I would still like to create a dcentralized storage space like freenet. I can't decide if I should choose dat or libtorrent (because every files should be encrypted and should be splitted into chunks of same size I guess)
Any hints ?
blahah
everyone - chjh_ does cool science stuff and is looking to learn JS - what are people's favourite resources?
G-Ray
blahah: nodeschool.io ?
blahah
in particular, to avoid going down the 2017 JS frameworks road to hell, just straight up clean JS
G-Ray: +1
mafintosh
G-Ray: bittorrent isnt great content that updates
pfrazee joined the channel
G-Ray
mafintosh: Yes but if a content is encrypted, it can't really be updated efficiently right ?
A user would need the dat hash + a private key to decrypt the content
yoshuawuyts
blahah: JS for cats
mafintosh
You still need a mechanism to push out new updates