profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/4c656554/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

4c656554/pyCREST 5

A python implementation of the CREST demand model - for creating multiple profiles.

4c656554/LVCalc 1

A network-reduction load-flow calculator for a generic low voltage UK feeder

4c656554/wiki 1

The Ethereum Wiki -

4c656554/BlockchainMeetup 0

A repository for contract code from Cardiff Blockchain Meetup

4c656554/CIRED2017Paper 0

The code accompanying the CIRED 2017 paper "Automation of the Supplier Role in the GB Power System using Blockchain Based Smart Contracts"

4c656554/dht 0

The DHT powering the HyperSwarm stack

4c656554/dht-rpc 0

Make RPC calls over a Kademlia based DHT.

push eventoodaspace/oo.computer

Lee

commit sha 9d870f783f232bb6e3da4b0954c059079c19537d

console debug

view details

push time in a day

push eventoodaspace/oo.computer

Lee

commit sha 129f307b4e098e5a744e46568e26331950c5e159

console debug

view details

push time in a day

push eventoodaspace/oo.computer

Lee

commit sha f23bb1a6cf723a52532aa22e8db41d3534a6073d

debug console

view details

push time in a day

push eventoodaspace/oo.computer

Lee

commit sha 1e9a00276093f396c6b3838def5165ae33e79d53

set up sub bee on receive

view details

push time in a day

push eventoodaspace/oo.computer

Lee

commit sha c36d754814a04d6750c1e6820e8e3513412f6ab7

fix brace error

view details

push time in a day

push eventoodaspace/oo.computer

Lee

commit sha 5db90c2a68c2aaffdf6cad2efb558a1acecfaf80

convert buffer to string pre send

view details

push time in a day

push eventoodaspace/oo.computer

Lee

commit sha 9c197386347bf258b4c61404a124c7d03e91a091

debug console logs

view details

push time in a day

push eventoodaspace/oo.computer

Lee

commit sha e2eb2fdd2d80c260d2c6b2af346d3ded3eb5f649

toString braces

view details

push time in a day

push eventoodaspace/oo.computer

Lee

commit sha 50e35a19c28c2f9bb21c35299f7ff9fc7a23f395

convert signal buffer to string on receipt

view details

push time in a day

push eventoodaspace/oo.computer

Lee

commit sha 0f1648d11162fd83e18cb6609457ce62b995d6be

for await in signal send

view details

push time in a day

push eventoodaspace/oo.computer

Lee

commit sha 5398b86b18e96f4e3ff199a8d3155f20486de73f

console logs added for debug

view details

push time in a day

push eventoodaspace/oo.computer

Lee

commit sha d97876949b1ebaf69087a346f15a1b2f3795a799

remove some console logs

view details

push time in 2 days

push eventoodaspace/oo.computer

Lee

commit sha ac94eaa823592ed559b28e2e7936f3b9ed8d20fb

key quotation marks

view details

push time in 2 days

push eventoodaspace/oo.computer

Lee

commit sha 5e70cf90cdb7bbf60770f9ffae05d73db6f8c98a

key encoding

view details

push time in 2 days

push eventoodaspace/oo.computer

Lee

commit sha 3487245911ec66ee6505f6f1d8d72fea3f6f66c9

convert msg to string

view details

push time in 2 days

push eventoodaspace/oo.computer

Lee

commit sha c9dea920b5c6a75a87946eeb6386cd1793ad8be7

remove keyPair2 ref

view details

push time in 2 days

push eventoodaspace/oo.computer

Lee

commit sha df108c300896a487e7922db96fa7e40cc3fa10fc

fix RequestSignalChain msg

view details

push time in 2 days

push eventoodaspace/oo.computer

Lee

commit sha ade332ec4ddce1cb8a993689e87f31ed8f7dfd4d

add nodesarray to main.js

view details

push time in 2 days

push eventoodaspace/oo.computer

Lee

commit sha 5fa94a298a42cc134b0488d569231312cf35ac17

update lookup

view details

push time in 2 days

push eventoodaspace/oo.computer

Lee

commit sha 044ae4be5bd56cfa34756244ba71af59eaa28e79

correction to media dirs, main.js

view details

push time in 2 days

push eventoodaspace/oo.computer

Lee

commit sha 3c6a3a1340d7057e4565862865797c06ad6654ee

Major update direct dht, ipfs replaced

view details

push time in 2 days

issue commenthypercore-protocol/hyperbee

Values stored as keys when using sub of sub

Can you clean up the formatting? A bit hard to read.

Done

was the key

4c656554

comment created time in 4 days

issue openedhypercore-protocol/hyperbee

Values stored as keys when using sub of sub

I'm getting values stored as keys when using sub, minimal example to reproduce:

let Hypercore = require('hypercore') let Hyperbee = require('hyperbee') let myCore = new Hypercore('/myCore2', {valueEncoding: 'utf-8'}) let myBee let a myCore.ready(async () => { console.log('core ready') myBee = new Hyperbee(myCore,{keyEncoding: 'utf-8', valueEncoding: 'binary'}) await myBee.ready() console.log('bee ready') let mySubBee = myBee.sub(myCore.key.toString('hex')) let mySubSubBee = myBee.sub('fe766f9a420f08c28f4c067fd7a5a01f86aa6e198e44dd68af1470c1db611c09') await mySubSubBee.put('e3e03a4a511d49a87468f13d1aa297081812d51e6138cfc70071d237a561a2c9','testvalue') await mySubSubBee.put('ca7bd4311e9d21e4c8d04162970998d715b8b92c92ee4ff434357f312647b401','anothertestvalue') for await (let val of mySubSubBee.createReadStream()){ console.log(val) } });

Gives:

{ seq: 2, key: 'ca7bd4311e9d21e4c8d04162970998d715b8b92c92ee4ff434357f312647b401\x1A\x10anothertestvalue', value: null } { seq: 1, key: 'e3e03a4a511d49a87468f13d1aa297081812d51e6138cfc70071d237a561a2c9\x1A\ttestvalue', value: null }

I expected the value fields to be populated with testvalue and anothertestvalue

created time in 4 days

startedhypercore-protocol/hyperbee

started time in 12 days

MemberEvent

PR closed hyperswarm/dht

Reviewers
Mutable/immutable records doc changes and return value correction
+36 -19

3 comments

2 changed files

4c656554

pr closed time in 16 days

push event4c656554/dht

Lee Thomas

commit sha 2e4d2fe48db1c7f9cab986ea135d9dd118f54048

Update to github review version of readme

view details

push time in 16 days

PullRequestReviewEvent

Pull request review commenthyperswarm/dht

Mutable/immutable records doc changes and return value correction

 module.exports = class HyperDHT extends DHT {       }     })     await query.finished()-    return { signature, seq }+    return { query.closestNodes, signature, seq }

Was my bad, I was unfamiliar with getter in constructor syntax.

4c656554

comment created time in 18 days

Pull request review commenthyperswarm/dht

Mutable/immutable records doc changes and return value correction

 Then on one computer listen for connections // create a server to listen for secure connections const server = node.createServer() -server.on('connection', function (noiseSocket) {-  // noiseSocket is E2E between you and the other peer-  // pipe it somewhere like any duplex stream+start() -  console.log('Remote public key', noiseSocket.remotePublicKey)-  console.log('Local public key', noiseSocket.publicKey) // same as keyPair.publicKey+async function start () {+  server.on('connection', function (noiseSocket) {+    // noiseSocket is E2E between you and the other peer+    // pipe it somewhere like any duplex stream -  process.stdin.pipe(noiseSocket).pipe(process.stdout)-})+    console.log('Remote public key', noiseSocket.remotePublicKey.toString('hex'))+    console.log('Local public key', noiseSocket.publicKey.toString('hex')) // same as keyPair.publicKey -// make a ed25519 keypair to listen on-const keyPair = DHT.keyPair()+    //process.stdin.pipe(noiseSocket).pipe(process.stdout) // pipe somewhere -// this makes the server accept connections on this keypair-await server.listen(keyPair)+    // log received data:+    noiseSocket.on('data',(data) => {+      console.log('received data: ', data.toString())+    })+  })++  // make a ed25519 keypair to listen on+  const keyPair = DHT.keyPair()++  // this makes the server accept connections on this keypair+  await server.listen(keyPair)+} ```  Then on another connect to the computer using the public key of the key-pair it is listening on  ``` js-// publicKey here is keyPair.publicKey from above-const noiseSocket = anotherNode.connect(publicKey)+start()++async function start () {+    // publicKey here is keyPair.publicKey from above+    const noiseSocket = await anotherNode.connect(publicKey) -noiseSocket.on('open', function () {-  // noiseSocket fully open with the other peer-})+    noiseSocket.on('open', function () {+      // noiseSocket fully open with the other peer+      // send a test message:+      noiseSocket.write(Buffer.from('test'))+    }) -// pipe it somewhere like any duplex stream-process.stdin.pipe(noiseSocket).pipe(process.stdout)+    // pipe it somewhere like any duplex stream+    // process.stdin.pipe(noiseSocket).pipe(process.stdout) ++}

https://github.com/hyperswarm/dht/pull/51/commits/245bdae069b0dbfefe7f299bb1334ae486a58767

4c656554

comment created time in 18 days