IRC channel logs


back to list of logs

<dsmith-work>Happy Friday, Guilers!!
<cmaloney>Happy Friday
<ijp>merry fridaymass
<amz3>some gnunet hacking ftw
<OrangeShark>happy friday
<amz3>I need a nap first
<amz3>hello OrangeShark
<OrangeShark>hey amz3 how are you doing?
<amz3>fine and you?
<amz3>I got into gnunet :D
<amz3>I mean, I understand enough gnunet to work on the bindings
<OrangeShark>I think I can use a nap as well :P
<OrangeShark>amz3: also nice about gnunet, I never really had a chance to look into that project.
<amz3>they made a massive update of the documentation,
<amz3>this is not the official new documentation but a pre-release ^
<ArneBab_>daviid: if you do find something you like, please tell me :-)
<ArneBab_>amz3: is gnunet working well nowadays?
<ArneBab_>it’s been years since I last looked into it
<daviid>ArneBab_: sure
<amz3>ArneBab_: I only tested locally, but it seems like there is some activity in the network
<apteryx>Hello. Is it wasteful to have a dockerfile used for CI (building software on each commit) that starts with: apt ugrade -y ? It seems like this would waste bandwith resources... or is there some fancy caching that will prevent that from happening?
<amz3>apteryx: wrong channel?
<amz3>apteryx: I don't think you can avoid the apt upgrade -y
<amz3>apteryx: you would need a fresh image everytime CI kicks in
<amz3>apteryx: you can have "local" apt cache via aptly
<amz3>apteryx: this will speed things up