profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/hackergrrl/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.
Kira Oakley hackergrrl Oakland, CA http://kira.solar plants, friends, punk-2-punk tech

cabal-club/cabal-mobile 147

p2p chat in your phone [dev help wanted :)]

adventure-js/arcticjs.club 68

The http://arcticjs.club website

digidem/hyperdb-osm 24

Peer-to-peer OpenStreetMap database over hyperdb.

digidem/kappa-osm 24

Peer-to-peer OpenStreetMap database using append-only logs

digidem/indexed-tarball 22

Tar archive with constant-time reads & appends. Supports spanning over multiple archives.

digidem/geojson-dissolve 15

Dissolve contiguous GeoJSON (Multi)LineStrings and (Multi)Polygons into single units.

digidem/hyperlog-sneakernet-replicator 15

peer to peer replication for hyperlog using files you can send around on a USB stick

ci-lg/p2p-community-infrastructure 12

a.k.a the "honeymoon repo" (thanks @mycognosist :) )

digidem/hyperdb-sneakernet 9

Peer to peer replication for a hyperdb using files you can send around on a USB stick.

pull request commentcabal-club/cabal-client

Upgrade cabal-core for faster installs (sodium-native)

@ralphtheninja No, I issued a membership invite for ralphtheninja. I'm not sure why you aren't receiving it.

ralphtheninja

comment created time in 2 days

pull request commentcabal-club/cabal-client

Upgrade cabal-core for faster installs (sodium-native)

Turns out cabal-client wasn't in the npm org. :)

Try now!

ralphtheninja

comment created time in 3 days

pull request commentcabal-club/cabal-client

Upgrade cabal-core for faster installs (sodium-native)

@ralphtheninja sent!

ralphtheninja

comment created time in 3 days

pull request commentcabal-club/cabal-client

Upgrade cabal-core for faster installs (sodium-native)

@ralphtheninja Is this you? https://www.npmjs.com/~ralphtheninja

Let me know and I'll add you to npm & let you publish.

ralphtheninja

comment created time in 4 days

push eventcabal-club/cabal-client

Lars-Magnus Skog

commit sha ebb5a0f8f2d90c5d4fe90ab8e0909a03839d9612

Upgrade cabal-core

view details

Kira Oakley

commit sha 51bb68aa291d2b2f2b7ef18893dc8357a20973a5

Merge pull request #79 from cabal-club/fix-sodium-native-prebuilts Upgrade cabal-core for faster installs (sodium-native)

view details

push time in 4 days

PR merged cabal-club/cabal-client

Reviewers
Upgrade cabal-core for faster installs (sodium-native)

Quickens install times from several minutes to seconds on machines lacking prebuilt binaries.

+1 -1

6 comments

1 changed file

ralphtheninja

pr closed time in 4 days

pull request commentcabal-club/cabal-core

Add CHANGELOG.md

@ralphtheninja I don't squash by default, but let me know next time & I'll give you time to squash it before we merge.

ralphtheninja

comment created time in 7 days

issue commentkappa-db/workshop

`full_game.js` : if (typeof initiator !== 'boolean') throw new Error('Must specify initiator boolean in replication stream')

@raphael10-collab This is a good point to do some web searches :)

raphael10-collab

comment created time in 7 days

push eventcabal-club/cabal-core

Kira Oakley

commit sha 57e76c6ac724ad261ba8285a8bcfdaa76ed6a15a

Fixes author field in package.json.

view details

push time in 8 days

push eventcabal-club/cabal-core

Lars-Magnus Skog

commit sha 45a282858e08ca829811dafb10bcefc2387df45f

Add hallmark to devDependencies

view details

Lars-Magnus Skog

commit sha 4e4fb633c8092ff02dcb53f3fa5bedbc24eb9006

hallmark --fix

view details

Lars-Magnus Skog

commit sha b4b234d5edb9e7a7d82ace0780791ec0f88abfcc

Make api sections in readme a little prettier

view details

Lars-Magnus Skog

commit sha d3f157a1cc63328d4267c284492edf5eeb7e275d

Add changelog entry for v1.0.0

view details

Lars-Magnus Skog

commit sha 45d2415f6cc9820f1193cd023afddb0339fd4a0a

Add changelog entry for v2.0.0

view details

Lars-Magnus Skog

commit sha 190188ce6e4b68222d864420a55ac3c6770a3277

Add changelog entry for v2.0.1

view details

Lars-Magnus Skog

commit sha f23260fd64db2224cca55c5f67cd14cd8e9ab97e

Add changelog entry for v2.1.0

view details

Lars-Magnus Skog

commit sha 80b9055d31e932fffc80337ab9baa09d790874ee

Add changelog entry for v2.1.1

view details

Lars-Magnus Skog

commit sha 2eb35f2dc2b73653c491a85ee44846c282a1e158

Add changelog entry for v2.2.0

view details

Lars-Magnus Skog

commit sha bb78a898c265d67d09e05e971aba725609e115d7

Add changelog entry for v2.3.0

view details

Lars-Magnus Skog

commit sha 2726dc41a077af938b2807e4ba0fae06c80126af

Add some notes on cabal-node on the early versions

view details

Lars-Magnus Skog

commit sha 66565bcf332d9acb54ad620590c2b10cbe80c835

Add changelog entry for v3.0.2

view details

Lars-Magnus Skog

commit sha 1926a49902a0d108d6d03ac74466d0f743d930fa

Add changelog entry for v3.0.3

view details

Lars-Magnus Skog

commit sha 19d84ff3104b43519b9dcf990d9f58ef3a5cc274

Add changelog entry for v3.0.4

view details

Lars-Magnus Skog

commit sha 0c69b71d2a4b285247f282a3aeb8c61c662bba32

Add changelog entry for v4.0.0

view details

Lars-Magnus Skog

commit sha d30c6f7b84d6b225ee84331e4261f368a7a2c6fe

Add changelog entry for v4.0.1

view details

Lars-Magnus Skog

commit sha a2ac9bbac4c21fa96badc17b4f70f08fae96a663

Add changelog entry for v5.0.0

view details

Lars-Magnus Skog

commit sha bb72c074d17ee7bf6f351ace42265eb1d78cb07e

Add changelog entry for v5.0.1

view details

Lars-Magnus Skog

commit sha 00e7670e33a902a8947f7034848fe88501afd523

Add changelog entry for v5.1.0

view details

Lars-Magnus Skog

commit sha 95893e7a26fdc6553721598ed3c6a4617a81a26d

Add changelog entry for v5.1.1

view details

push time in 8 days

PR merged cabal-club/cabal-core

Add CHANGELOG.md

Ok, here we go.

So maybe a bit overworked, but cabal-core is sort of like the flag ship module so might be worth the time to document all the versions. I've added a lot of small commits so it's easier to review each version separately and we can squash the PR later to make it a bit cleaner.

The workflow I use when making new release is basically:

npm run changelog:patch
# fill in details or tweak CHANGELOG.md
git add CHANGELOG.md && git commit -m 'Update changelog for x.y.z'
npm version patch
git push && git push --tags
npm publish

The first command will create a new section in the changelog (here showing patch as example). This will also populate the changelog with git commits, but if you want to add items manually you can also refer to pull requests e.g. (#44) and you can also refer to users on github by (@substack, @cblgh) and then hallmark --fix will automatically convert them to links.

+722 -52

6 comments

3 changed files

ralphtheninja

pr closed time in 8 days

pull request commentcabal-club/cabal-core

Add CHANGELOG.md

Thank you for investigating where the breaking change was coming from @ralphtheninja.

Looks good to me also. Merging!

ralphtheninja

comment created time in 8 days

pull request commentcabal-club/cabal-core

Add CHANGELOG.md

Excellent, thank you @ralphtheninja.

Does this mean there was no breaking protocol change created by the bump to 14.0.0?

Also, would you mind adding the instructions for how to update the changelog to the README? Perhaps near the bottom in a section for developers?

ralphtheninja

comment created time in 8 days

issue commentkappa-db/workshop

`full_game.js` : if (typeof initiator !== 'boolean') throw new Error('Must specify initiator boolean in replication stream')

It might not be something you're doing. To see if your machines can find each other over hyperswarm, try doing this on each machine:

npm i -g airpaste

Then on one run echo 'hello' | airpaste and on the other just run airpaste and see if the 'hello' text gets through. If it hangs indefinitely it's likely an issue with your network blocking multicast traffic.

raphael10-collab

comment created time in 10 days

IssuesEvent
CommitCommentEvent

issue commentkappa-db/workshop

upgrade problems & solutions to hypercore8

Done! All code is now using hyperswarm instead of discovery-swarm also.

hackergrrl

comment created time in 11 days

push eventkappa-db/workshop

Kira Oakley

commit sha 3e9516671ab1750fc881eba18e584bccd578f912

Updates the full_game example to use hyperswarm.

view details

Kira Oakley

commit sha 1262f123d109cbaf9a9ef4164421af1f93d75836

Updates all dependencies to latest.

view details

Kira Oakley

commit sha bf6a0b3bd0196e1b20264e95c42b25f784e30910

Recommends hyperswarm-web over discovery-swarm.

view details

Kira Oakley

commit sha 83cd8c85ac4289c9044fd39a886d22b78d089395

Rebuilds html.

view details

push time in 11 days

issue closedkappa-db/workshop

`full_game.js` : if (typeof initiator !== 'boolean') throw new Error('Must specify initiator boolean in replication stream')

I opened two windows and executed in both of them full_game.js:

(base) raphy@pc:~/hypercore/kappa-db/workshop$ node full_game.js 
/home/raphy/hypercore/kappa-db/workshop/node_modules/hypercore-protocol/index.js:314
    if (typeof initiator !== 'boolean') throw new Error('Must specify initiator boolean in replication stream')
                                        ^

Error: Must specify initiator boolean in replication stream
    at new ProtocolStream (/home/raphy/hypercore/kappa-db/workshop/node_modules/hypercore-protocol/index.js:314:47)
    at new Multiplexer (/home/raphy/hypercore/kappa-db/workshop/node_modules/multifeed/mux.js:42:32)
    at Multiplexer (/home/raphy/hypercore/kappa-db/workshop/node_modules/multifeed/mux.js:24:46)
    at Multifeed.replicate (/home/raphy/hypercore/kappa-db/workshop/node_modules/multifeed/index.js:258:13)
    at Kappa.replicate (/home/raphy/hypercore/kappa-db/workshop/node_modules/kappa-core/index.js:125:21)
    at Swarm.<anonymous> (/home/raphy/hypercore/kappa-db/workshop/full_game.js:40:18)
    at Swarm.emit (events.js:315:20)
    at onhandshake (/home/raphy/hypercore/kappa-db/workshop/node_modules/discovery-swarm/index.js:444:10)
    at Socket.readable (/home/raphy/hypercore/kappa-db/workshop/node_modules/length-prefixed-message/index.js:46:5)
    at Socket.emit (events.js:315:20)
(base) raphy@pc:~/hypercore/kappa-db/workshop$ 

closed time in 11 days

raphael10-collab

issue commentkappa-db/workshop

`full_game.js` : if (typeof initiator !== 'boolean') throw new Error('Must specify initiator boolean in replication stream')

Closing, assuming this is a duplicate of #29 and is now also resolved. Let me know @raphael10-collab if this is still relevant.

raphael10-collab

comment created time in 11 days

issue commentkappa-db/workshop

`full_game.js` : node_modules/hypercore-protocol/index.js:314 error

This error looks like there is a mismatch between the versions of some of the dependencies. Try

  1. git fetching from the latest master
  2. wiping your node_modules/ directory
  3. run npm install again
raphael10-collab

comment created time in 12 days

pull request commentcabal-club/cabal-client

Upgrade cabal-core for faster installs (sodium-native)

That'd be great @ralphtheninja!

ralphtheninja

comment created time in 13 days

pull request commentcabal-club/cabal-client

Upgrade cabal-core for faster installs (sodium-native)

I think cabal-core 13->14 is a breaking protocol change, possibly due to a major hypercore semver?

This makes me think about:

  1. How nice it'd be if we used changelogs, so it was easier to see what this major semver does.
  2. What we want our procedure to be around releases of breaking protocol changes. Releasing cabal-client with a new major semver is no big deal on its own, but anyone who wants to depend on it directly may not be aware that the latest version is protocol incompatible with what is currently running on clients today.

cc for thoughts: @cblgh @nikolaiwarner @okdistribute @substack

ralphtheninja

comment created time in 13 days

push eventcabal-club/cabal-core

Kira Oakley

commit sha 023d4996cd411a3e733ebe667ce3d64bc643c042

Adds missing dep, kappa-view. Removes unused deps.

view details

Kira Oakley

commit sha 0f2d8b2af175d5db853ea873704d9cacc33ad008

14.1.1

view details

push time in 13 days

created tagcabal-club/cabal-core

tagv14.1.1

Core database and replication for cabal.

created time in 13 days

push eventkappa-db/kappa-core

Kira Oakley

commit sha d189280e719da49e6a6e83f85dca3fa7cd0745e4

7.0.0

view details

push time in 14 days

push eventcabal-club/cabal-core

Lars-Magnus Skog

commit sha 2321907b42c296db5309c4c0b8e78717ea21c6e5

Upgrade sodium-universal

view details

Kira Oakley

commit sha eaf0378b357a93e4931d9cda5d23ebb0a7360f1a

Merge pull request #106 from cabal-club/fix-sodium-native-prebuilts Upgrade sodium-universal for faster install

view details

push time in 14 days

PR merged cabal-club/cabal-core

Upgrade sodium-universal for faster install

There was a tiny discrepancy where some parts were using sodium-native@3.2.1 and others using sodium-native@2.4.9, which for some reason had to compile on linux.

Reduces install time from about 1 minute 40 seconds to sub 10 seconds.

+1 -1

1 comment

1 changed file

ralphtheninja

pr closed time in 14 days

pull request commentcabal-club/cabal-core

Upgrade sodium-universal for faster install

Yay nice! Thanks @ralphtheninja.

ralphtheninja

comment created time in 14 days