<alu>
i dont believe it this documentation is out of date
<alu>
ima try it anyways tho
<lgierth>
not saying it *will* work -- just that i can't up with any obvious reason why it wouldn't
<dyce_>
nodejs is a little more ram intensive than go i assume?
<lgierth>
i'm not sure if there are any native npm module dependencies, for example
<lgierth>
cross-compilation for them would have to be figured out
<lgierth>
dyce_: i don't know about nodejs's ram usage, but i'd guess there's a bit of overhead. go-ipfs and js-ipfs aren't really comparable at the moment though, there's more work todo for them to be equivalent
dignifiedquire has quit [Quit: Connection closed for inactivity]
ralphthe1inja has joined #ipfs
Quiark_ has joined #ipfs
kvda has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
opposable has quit [Remote host closed the connection]
producible has joined #ipfs
kaiza has joined #ipfs
ygrek_ has joined #ipfs
charley_ has joined #ipfs
pfraze has quit [Remote host closed the connection]
Guanin_ has left #ipfs [#ipfs]
Guanin_ has joined #ipfs
go1111111 has quit [Ping timeout: 276 seconds]
charley_ has quit [Ping timeout: 244 seconds]
Akaibu has joined #ipfs
micxjo has joined #ipfs
go1111111 has joined #ipfs
producible has left #ipfs [#ipfs]
reit has joined #ipfs
reit has quit [Read error: Connection reset by peer]
postoral has joined #ipfs
pfraze has joined #ipfs
demize has quit [Quit: Do Androids Dream of Electric Sheep?]
demize has joined #ipfs
Arakela007 has joined #ipfs
charley_ has joined #ipfs
_rht has quit [Quit: Connection closed for inactivity]
pfraze has quit [Remote host closed the connection]
charley_ has quit [Ping timeout: 244 seconds]
pfraze has joined #ipfs
IlanGodik has joined #ipfs
devbug_ has quit [Ping timeout: 240 seconds]
voxelot has quit [Ping timeout: 268 seconds]
mildred has joined #ipfs
tmg has quit [Ping timeout: 252 seconds]
s_kunk has quit [Ping timeout: 248 seconds]
ugjka has joined #ipfs
tmg has joined #ipfs
chriscool has joined #ipfs
<mildred>
Hello, what's the current state of javascript implementations. Is there something available that can get and decode a node using a gatewat HTTP API, and store a new node the same way?
zootella has joined #ipfs
zz_r04r is now known as r04r
Darksecond has joined #ipfs
pfraze has quit [Remote host closed the connection]
kvda has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
zootella has quit [Quit: zootella]
Arakela007 has quit []
Arakela007 has joined #ipfs
zorglub27 has joined #ipfs
SWingedSeraph has quit [Ping timeout: 246 seconds]
SWingedSeraph has joined #ipfs
rendar has joined #ipfs
ralphthe1inja has quit [Quit: Lost terminal]
ralphtheninja has quit [Quit: Lost terminal]
ralphtheninja has joined #ipfs
s_kunk has joined #ipfs
ipfsrocks has quit [Ping timeout: 276 seconds]
agent008_ has quit [Ping timeout: 252 seconds]
DFM20 has quit [Ping timeout: 276 seconds]
DFM20 has joined #ipfs
agent008 has joined #ipfs
dignifiedquire has joined #ipfs
zootella has joined #ipfs
ygrek_ has quit [Ping timeout: 244 seconds]
screensaver has joined #ipfs
zootella has quit [Quit: zootella]
zootella has joined #ipfs
<jbenet>
mildred i believe so-- ask diasdavid -- he should be around soon
zootella has left #ipfs [#ipfs]
<ipfsbot>
[go-ipfs] chriscool created t0300-improve-debug-message (+1 new commit): https://git.io/v2p8t
<ipfsbot>
go-ipfs/t0300-improve-debug-message 94083ae Christian Couder: t0300: improve docker_build debug message...
disgusting_wall has quit [Quit: Connection closed for inactivity]
Encrypt has joined #ipfs
go1111111 has quit [Ping timeout: 264 seconds]
<ipfsbot>
[js-ipfs-api] dignifiedquire created greenkeeper-karma-mocha-reporter-1.3.0 (+1 new commit): https://git.io/v2pER
<ipfsbot>
js-ipfs-api/greenkeeper-karma-mocha-reporter-1.3.0 c25cc01 greenkeeperio-bot: chore(package): update karma-mocha-reporter to version 1.3.0...
<ipfsbot>
[js-ipfs-api] dignifiedquire deleted greenkeeper-karma-mocha-reporter-1.3.0 at c25cc01: https://git.io/v2puO
<dignifiedquire>
good morning everyone
<chriscool>
good morning dignifiedquire!
ulrichard has joined #ipfs
go1111111 has joined #ipfs
zootella has joined #ipfs
Quiark_ has quit [Ping timeout: 252 seconds]
zootella has quit [Quit: zootella]
<mildred>
daviddias: what's the state of the javascript implementation ? Is there enough code so I could download a raw block from a gateway and parse it (data and links). And create a block and post it to a gateway ?
zootella has joined #ipfs
zootella has quit [Quit: zootella]
jaboja has joined #ipfs
Guanin_ has left #ipfs [#ipfs]
ecloud has quit [Ping timeout: 246 seconds]
ekaron has quit [Ping timeout: 240 seconds]
<ipfsbot>
[js-ipfs-api] dignifiedquire created greenkeeper-karma-mocha-reporter-2.0.0 (+1 new commit): https://git.io/v2poV
<ipfsbot>
js-ipfs-api/greenkeeper-karma-mocha-reporter-2.0.0 ae72011 greenkeeperio-bot: chore(package): update karma-mocha-reporter to version 2.0.0...
ecloud has joined #ipfs
reit has joined #ipfs
cemerick has joined #ipfs
charley_ has joined #ipfs
s_kunk has joined #ipfs
charley_ has quit [Ping timeout: 240 seconds]
Encrypt has quit [Quit: Quitte]
Encrypt has joined #ipfs
reit has quit [Quit: Leaving]
zootella has joined #ipfs
zootella has left #ipfs [#ipfs]
kaotisk has quit [Quit: Leaving]
grey- has joined #ipfs
grey- has quit [Ping timeout: 252 seconds]
s_kunk has quit [Ping timeout: 252 seconds]
cemerick has quit [Ping timeout: 240 seconds]
ugjka has quit [Quit: Leaving]
Magik6k has quit [Excess Flood]
Akaibu has quit [Quit: Connection closed for inactivity]
IlanGodik has quit [Quit: Connection closed for inactivity]
_rht has joined #ipfs
ggoZ has joined #ipfs
Guanin_ has joined #ipfs
kaotisk has joined #ipfs
ugjka has joined #ipfs
charley_ has joined #ipfs
Guanin_ has left #ipfs [#ipfs]
charley_ has quit [Ping timeout: 240 seconds]
computerfreak has joined #ipfs
zorglub27 has quit [Ping timeout: 240 seconds]
inconshreveable has quit [Remote host closed the connection]
inconshreveable has joined #ipfs
Akaibu has joined #ipfs
grey- has joined #ipfs
M-HirmeS has joined #ipfs
s_kunk has joined #ipfs
cemerick has joined #ipfs
inconshreveable has quit [Remote host closed the connection]
jaboja has joined #ipfs
ipfsrocks has joined #ipfs
<C-Keen>
Is a ipfs get and then a ipfs pin add faster than issuing a sole ipfs pin add ?
<C-Keen>
also is there a way to see what's actually happening in the background?
zorglub27 has joined #ipfs
ipfsrocks has quit [Ping timeout: 240 seconds]
<dignifiedquire>
richardlitt: daviddias what format are we doing the sprint summary today?
tlevine has quit [Ping timeout: 246 seconds]
tlevine has joined #ipfs
cemerick has quit [Ping timeout: 260 seconds]
reit has joined #ipfs
reit has quit [Client Quit]
micxjo has quit [Quit: Connection closed for inactivity]
ipfsrocks has joined #ipfs
jaboja has quit [Ping timeout: 244 seconds]
reit has joined #ipfs
reit has quit [Client Quit]
reit has joined #ipfs
<richardlitt>
dignifiedquire: normal.
<richardlitt>
dignifiedquire: Oh, no.
<richardlitt>
dignifiedquire: I'll post mine within the hour. Make it a human one.
leer10 has quit [Remote host closed the connection]
<dignifiedquire>
richardlitt: okay
<dignifiedquire>
full list in gh comment?
<dignifiedquire>
or only human
<richardlitt>
dignifiedquire: feel free to wait until I post mine.
<dignifiedquire>
will do
<richardlitt>
lgierth: you there?
pfraze has joined #ipfs
ipfsrocks has quit [Ping timeout: 244 seconds]
OutBackDingo has quit [Remote host closed the connection]
ashark has joined #ipfs
cow_2001 has quit [Quit: Offense is taken, not given. No need to disarm the world. Just make yourself bullet proof. Sticks & stones people. Block. Unfollow. Laugh.]
Tv` has joined #ipfs
Encrypt has quit [Quit: Quitte]
cow_2001 has joined #ipfs
<daviddias>
I'll do a mix
<daviddias>
by endeavour
<daviddias>
summary
<daviddias>
and then full list of tasks completed
<daviddias>
but let's see
Animazing is now known as `Animazing
`Animazing is now known as Animazing
Animazing is now known as Anlmazing
Anlmazing is now known as Animazing
<daviddias>
richardlitt: the etherpads urls are the ones from the last sprint, do we want to reuse them?
<daviddias>
if so, should we really use dates on the url then?
<voxelot>
Kubuxu: really interested in reading you CRDT on IPFS blag when you get it up :)
<richardlitt>
daviddias: is that your only summary? :)
<richardlitt>
whyrusleeping noffle lgierth jbenet please take a look at the awesome sprint updates so far and add your own. Let's see if we can start the sprint on time today. https://github.com/ipfs/pm/issues/93
<daviddias>
richardlitt: I'm still writting it. I just keep hitting save cause I'm afraid of loosing the changes :)
<richardlitt>
LOOSE THE CHANGE!
* richardlitt
watches nickles and dimes going everywhere
* richardlitt
as if from a catapult, headed towards some city
<richardlitt>
"Is this what Machiavelli meant when he said 'Never fight a war with your purse?'?", asks a mercenary next to the catapult
<richardlitt>
... (Sorry, got a little sidetracked there. Good luck, daviddias)
<haad>
richardlitt: to clarify today's format, do we write a summary and a link to tasks? not sure where to write what...
<dignifiedquire>
daviddias: just use your editor which saves to disk :P
<daviddias>
is it annoying that I write to github directly? I can write it somewhere first, for sure
<dignifiedquire>
daviddias: not annoying, just for your sanity that you don't loose anything
<daviddias>
living on the edge :P
jaboja has joined #ipfs
ipfsrocks has quit [Ping timeout: 246 seconds]
<whyrusleeping>
gooood morning
<haad>
o/
<richardlitt>
whyrusleeping: good morning buddy!
<richardlitt>
daviddias: I always write it elsewhere, first. It seems smarter, to me. The GitHub comments is not a proper versioning system.
<daviddias>
mornin' whyrusleeping :)
* noffle
lives
<richardlitt>
daviddias: I use a closed repo for all private markdown docs, and save and update all of my things there. Also means I can move to another machine without hassle.
* richardlitt
watches lightning flash above the old castle where noffle has risen
wiedi has quit [Quit: ^Z]
<dignifiedquire>
whyrusleeping: good morning to you :)
<dignifiedquire>
daviddias: I too like to live life dangerously :D
Sonarpulse has joined #ipfs
ipfsrocks has joined #ipfs
<richardlitt>
Almost ready, everyone?
<voxelot>
don't let anyone say IPFS devs aren't hardcore... we might not save our documents.. boosh
<dignifiedquire>
reaaady :)
<dignifiedquire>
voxelot: :D:D:D
<richardlitt>
did you just call me hardcore, voxelot?
<richardlitt>
:D
* richardlitt
feels chuffed. going to read it that way from now on.
richardlitt is now known as hardcorerick
<voxelot>
haha
<voxelot>
ready
<hardcorerick>
fsck yeah
<hardcorerick>
whyrusleeping noffle lgierth daviddias you ready?
<hardcorerick>
haad?
<lgierth>
here
<lgierth>
typing
<dignifiedquire>
hardcorerick: where are the eather pads for this week?
charley_ has joined #ipfs
<hardcorerick>
dignifiedquire: they're in the sprint for this week.
<dignifiedquire>
ah right -.-
<hardcorerick>
:D
<daviddias>
hardcorerick?
hardcorerick is now known as RichardLitt
<RichardLitt>
Yeah, that is gonna get confusing as hell.
<whyrusleeping>
Kubuxu: mmm, that may have to be a thing then
<richardlitt>
This week, we are changing things up a bit. Instead of copying and pasting all of our tasks, we'll just copy over our summaries that we've written, and link to the tasks.
<noffle>
richardlitt: love your headers <3
<Sonarpulse>
the exchange and routing specs in protocol/ no longer exist?
<daviddias>
**Summary:** This sprint on js-ipfs was a lot about _enablement_ and getting the next big feature on the roadmap done, that is `swarm`. I've focused on creating the foundation on js-ipfs for it to be easy to add extra features implemented, that is in: core, http-api or cli, by doing it myself for for a group of features, add comprehensive tests for each part
<daviddias>
and explain what I've done in the Captain.log + listing what needs to get done on issues, tagging them with difficulty and the 'help wanted' label, in case they are available to be done without anything blocking, this lead to several new contributions, thank you everyone :). On the swarm level, I've added it to js-ipfs, but started hitting some problems when
<daviddias>
it comes to interop with go-ipfs go-libp2p, to go after this issues, I entered the Go land, and went on an adventure to simplify js-libp2p-swarm, to reduce the amount of magic it was doing by default, and expose more operations, so it is easier to debug (by having more control), see the libp2p segment for more updates on that.
<daviddias>
richardlitt: also, how does this format looks in terms of you being able to pick things for the weekly?
<richardlitt>
daviddias: much, much easier.
<dignifiedquire>
richardlitt: only links correct?
<richardlitt>
dignifiedquire: should be, yeah
ipfsrocks has quit [Ping timeout: 276 seconds]
<richardlitt>
Hmm. I don't think we should use Pastebin, if not all clients support it.
<richardlitt>
I think having split paragraphs is OK.
<whyrusleeping>
could you at least put them all in one pastebin if thats how youre going to do it?
<daviddias>
I can
<richardlitt>
No, I don't think that helps. I think at that point we should just link to GitHub
<richardlitt>
I think just copy over the paragraphs, and maybe keep down the noise in the summaries. Talk about things you really care about, not line items
<richardlitt>
But meta aside: good work, daviddias !
<richardlitt>
Super glad you're getting into Go, and I'm also chuffed your making libp2p-spdy less hacky, and opening up js-ipfs for newcomers a bit more
<richardlitt>
That's awesome.
kaotisk has quit [Ping timeout: 246 seconds]
<daviddias>
richardlitt: thank you
<richardlitt>
Anyone else have any comments for daviddias?
charley_ has joined #ipfs
<richardlitt>
Let's keep this short and simple, it's already been 20 minutes for one person and we've got a lot of people to go.
<dignifiedquire>
all good from my side, nice work on the go side :)
<richardlitt>
These past two weeks have been productive. I helped us switch up the sprint, so that we have a Monday off and that we run on a fortnightly basis. This involved a lot of talking to people. I reviewed all of the open PRs on http-api-spec, and merged a few of them - we're getting there, although there is more work to do (mostly involving me talking to
<richardlitt>
@whyrusleeping). This coincided with a lot of go-ipfs PRs. We published last month's weekly, which took way more time than it ought to have, and I'm hoping that never happens again. I also udpated a few bugs and added a dependency, wihch gets PR creators, to name-your-contributors, the module I use for getting a list of community contributors for the IPFS
<richardlitt>
Unfortunately the BostonJS talk wasn't recorded. I can upload my keynote slides somewhere if someone wants them, but I tend to adlib based on one or two words on a slide, so I don't think it will be helpful for anyone.
<lgierth>
that bostonjs line came after EOF
<whyrusleeping>
whats left to do on the api spec? just the open PRs?
<richardlitt>
lgierth: I wrote it after EOF. :P
<lgierth>
ok :)
<richardlitt>
whyrusleeping: yep! That's it. I assigned each PR to the person whose feedback I need before I can merge it
<Sonarpulse>
does go-ipfs currently use libp2p
<richardlitt>
Unfortunately, that's 90% you. :D Maybe we should take a few hours and go through each one together? That worked well, last Wednesday
<lgierth>
i checked today and i have nothing assigned \o/
<Sonarpulse>
or is the refactoring a work in progress?
<lgierth>
Sonarpulse: yes
<lgierth>
it uses it
<Sonarpulse>
oh good
<Sonarpulse>
the links in the table of contents on the libp2p readme are broken
<whyrusleeping>
Sonarpulse: yeah... those are links to javascript stuff for some reason
<whyrusleeping>
i'm not really sure what happened there
<richardlitt>
Anyone else have comments for richardlitt?
<daviddias>
sad that your talk didn't get recorded, happy I got a preview of it :)
<daviddias>
you should deliver it again :)
<Sonarpulse>
is there any spec for p2p?
<richardlitt>
daviddias: I've submitted a version of it to csv,conf and scotlandjs, I think
<daviddias>
sweet :)
<richardlitt>
Will also submit it to OS Feels and maybe IcelandJS. Seems like I might as well.
<richardlitt>
No reason not to talk about it more than once.
<lgierth>
Sonarpulse: in the specs repo
<richardlitt>
Ok. Kubuxu isn't here, So I will cover for him
<richardlitt>
I wasn't super productive when it comes to IPFS (Uni started, Vulkan got released) but I was able to get something done. gx, gx-go and ipget are now available on AUR which is really nice. I worked on blag about CRDT on IPFS which would sum up my thoughts, ideas, problems and solutions. It will be something others could reference while implementing their
<richardlitt>
owns. I am blocked really hard on ipfs/go-ipfs#2405, I can flush the datastore but it will probably repeat. Also general question: how to name packaged fs-repo-migrations? Ping me on IRC with possible names.
<richardlitt>
============ EOF ================
<richardlitt>
I think putting those on AUR is super awesome, Kubuxu: thanks!
<richardlitt>
@whyrusleeping can you help out with ipfs/go-ipfs#2405?
<whyrusleeping>
richardlitt: sure, put an issue for me over at github.com/whyrusleeping/todo
<richardlitt>
Done.
<richardlitt>
Ok, let's move on to the next person.
<dignifiedquire>
> Success is stumbling from failure to failure with no loss of enthusiasm.
<dignifiedquire>
> -- Winston S. Churchill
<dignifiedquire>
Two weeks have gone by, and I actually got everything done I set out to do
<dignifiedquire>
in the last sprint. `karma-peer` now has the ability to dynamically launch browsers,
<dignifiedquire>
which will help @diasdavid, and hopefully more people, to write better tests for
<dignifiedquire>
libp2p in the browser.
<dignifiedquire>
The "Big Bad Tests" for `go-ipfs` are on on their way with
<dignifiedquire>
`randor`, which now is able to rerun tests predictably based on stored data, so it's
<dignifiedquire>
easy to find and fix bugs. @whyrusleeping is already working on the first bug that
<dignifiedquire>
`randor` detected.
<dignifiedquire>
A big highlight for me personally was the first show of "dignified hacks" last Monday, where I
<dignifiedquire>
live streamed myself coding on the big webui refactoring. There were some technical
<dignifiedquire>
issues but I hope to do another one this week.
<dignifiedquire>
The overall progress on the webui is that I started on the files browser (based on new files
<dignifiedquire>
api in 0.4) which already lists files and is able to create directories. In addition all
<dignifiedquire>
the geolocation data now uses the fixed ipfs-geoip.
<dignifiedquire>
And last but not least, I famliarized myself with the codebase of the website, fixing some
<dignifiedquire>
basic performance issues (image compression, dead code) and started thinking of what the
<dignifiedquire>
next iteration might look like.
<lgierth>
\o/
<dignifiedquire>
EOF
<lgierth>
excellent stuff
<dignifiedquire>
thanks :)
<richardlitt>
Woot! Well done dignifiedquire!
<dignifiedquire>
Also i proposed a talk to squatconf :)
<dignifiedquire>
but not about ipfs so it didn't make the cut above
<richardlitt>
Nice.
<richardlitt>
nginnever: you here?
<dignifiedquire>
ah also voxelot and I recorded a debugging session on webpack+karma tests for js-ipfs-<sth> you can watch it here: https://www.youtube.com/watch?v=vY82T08noXY
<voxelot>
i wish that would have shown your screen more.. not just my stupid face watching you fix things hah
<dignifiedquire>
:D
<richardlitt>
Can someone remind me who nginnever is on IRC? :P
<voxelot>
<---
<richardlitt>
what
<daviddias>
voxelot: ahahaha
<richardlitt>
but you're nathan
<voxelot>
indeed i am richard
<richardlitt>
Nathan, do you need three separate names?
<richardlitt>
:P
<dignifiedquire>
nathan = nginever = voxelot
<voxelot>
n = nathan
<richardlitt>
Gahh
<richardlitt>
ok
<voxelot>
im confusing haha
<whyrusleeping>
i really hadnt made that connection yet myself
<richardlitt>
Well, ready to go?
<whyrusleeping>
i was wondering with github.com/voxelot wasnt right
<voxelot>
The past two weeks I have been studying more than I have been producing but I am getting much more comfortable with tests, the difference between using IPFS in the browser and node env, standards and practices, and so on. I wasn't able to spend as much time as I would like working on and studying our react webui project but I did tune into dignified hacks and that was helpful for a quick view of our components and data flow in the webui.
<voxelot>
I spent some time researching a few commands in go-ipfs (cat and object get). I wrote some notes or a step-by-step analysis of what happens during those commands or what I can understand as to what's happening after seeing noffle do this with init. I spent some time writing web tests for data-importing module with dig and I started writing some export feature code to unwrap our hashes and retrieve files. Also created a distribution file for pe
<voxelot>
er-id that will require node/forge rebuild to be able to work with browserify.
<noffle>
I've been spending time reflecting on my own goals individually and how they connect to my work on IPFS. tl;dr I'm going to be focusing more on js-ipfs and on building p2p primitives to support apps on IPFS. My week reflects this:
<noffle>
I did a lot of reading on p2p subjects (bittorrent, david dias' webrtc work, gossip protocols), and produced several modules: 3 to support ipfs-pad (p2p text editor), and 2 to support p2p pubsub (potentially for haad's orbit-db). Also began spec'cing out the 'ipfs init' process for js-ipfs.
<noffle>
==eof==
s_kunk has quit [Ping timeout: 240 seconds]
<dignifiedquire>
nice stuff noffle :)
computerfreak has quit [Quit: Leaving.]
<noffle>
it's aside, but also wrote a node module readme generator
<lgierth>
I just came back from a nice and productive week in Paris. I got to spend lots of time with @cjdelisle and @ansuz at @xwiki-labs, we discussed the state and future of cjdns/fc00, layed out ideas for routing improvements, and drafted spec documents for the switch and cryptoauth layers. I'll post them to the github.com/fc00/specs repo shortly, and we'll continue working on them for the rest of March. I want to
<lgierth>
start working on Go implementations of the switch and cryptoauth in April. The switch and routing layers of fc00 might be the foundation of a smarter swarm for IPFS/libp2p, so this is all very exciting.
<lgierth>
IPFS-wise, the sprint was dominated by hunting down subtle issues. The v04x/v03x multiplexer called multireq still doesn't seem to be 100 % good. I fixed a couple bugs with tremendous help from @whyrusleeping. I've also been debugging issues with fetching big DAGs (e.g. GeoIP). The metrics dashboard at metrics.i.ipfs.io has gotten a facelift too, and will get more detailed metrics on HTTP requests and
<lgierth>
responses.
<lgierth>
=== EOF ===
<richardlitt>
why is t0060 important, noffle?
<dignifiedquire>
lgierth: is metrics public? I can't open it
<lgierth>
dignifiedquire: get cjdns
<lgierth>
it's within fc00::/8
<dignifiedquire>
lgierth: :'(
<dignifiedquire>
I don't know how to do that
<lgierth>
it has a good readme
<lgierth>
:)
danielrf has joined #ipfs
<dignifiedquire>
hmmm will see when I'm bored
<noffle>
richardlitt: it was a test I added custom ports to, but making it use port zero was much more work
<noffle>
so nice to see that did
<Sonarpulse>
The libp2p spec contains some goals, but where is the nitty-grity actual protocols?
<gra>
some questions to go/libp2p: I wanted to start working it as a base for a new project. However I saw that all the routing stuff based on Kademlia is missing.
<gra>
It is not used as a base for IPFS right now, correct?
<richardlitt>
Does anyone else want to contribute to the sync?
<richardlitt>
Guess not.
<richardlitt>
In that case, I hereby conclude this weekly Sync. Thanks everyone! Super great work this week.
arpu has quit [Remote host closed the connection]
<richardlitt>
The first of the video hangouts (run every two weeks) happens in around 30 minutes - it'll be the Apps on IPFS one.
<richardlitt>
You do not have to go to the hangouts to ask questions, but it might be useful, if you like. You can stream them live, or join them. We'll post links here.
<haad>
richardlitt: thanks!
<richardlitt>
That's all for today.
<richardlitt>
========== End of Sync =============
<richardlitt>
haad: no problem
<lgierth>
thanks richard
<richardlitt>
noffle whyrusleeping lgierth daviddias ====> I wrote up your major accomplishments in the weekly.
<Sonarpulse>
the spec their mainly seems to have the principles behind libp2p
<daviddias>
right now we are getting really nice swarm interop between go and JS
<Sonarpulse>
oh good
<voxelot>
a link will be posted here in chat for each of the scheduled hangouts
<daviddias>
then, we will tackle peer routing and record store, which already works in go and JS, but implemented in different ways (the JS uses IPLD and IPRS, also specs)
<Sonarpulse>
ah, so JS is pushing the spec compliance :)
<Sonarpulse>
the network-transport-* packages at least
<Sonarpulse>
but is just designed for haskell<->haskell
<Sonarpulse>
so the internals aren't really specified
<jbenet>
hey everyone, im here and reading, just in a large meeting with others. i can step out to join hangouts though. which would be the most useful for me to attend?
<jbenet>
(probably go-ipfs, js-ipfs, infra?)
<Sonarpulse>
which makes me worried one would have to basically reimplement all that
<richardlitt>
jbenet: probably.
<voxelot>
personally would love to have jbenet in js-ipfs but you know.. im partial
<gra>
For Haskell <-> somethingElse, protobuf should do it I think
<daviddias>
Sonarpulse: I'm not familiar with that module, what is your feeling?
<Sonarpulse>
That is the cloud haskell project
<Sonarpulse>
which, for a few years now, has been focused on abstracting stuff for writing distributed systesm
<Sonarpulse>
....sounds like libp2p
<Sonarpulse>
so it's very well designed and modular
wiedi has joined #ipfs
<Sonarpulse>
but I bet a lot details (wire protocols, etc) isntead of being carefully planned, are just kinda left to change, for example automatically derived serializations
<Sonarpulse>
which is great for a single language system
<Sonarpulse>
but no so great for implementations in multiple languages
<Sonarpulse>
that's great...nicely thoughtout multiplexing of TCP sockets...but I have no idea of exact wire format because if I am using this library at both ends I don't care
<daviddias>
libp2p is a framework/language/interfaces to agregate all our options when it comes to transports, stream multiplexing, nat traversal, peer discovery, peer routing, record store (names), etc
<daviddias>
I feel that (skimming through), this Haskell project had a goal of creating a framework to have distributed apps, by making assumptions based on what the system capabilities were going to be
<daviddias>
but I need to read more :)
<daviddias>
join libp2p chat today!
gra has quit [Ping timeout: 244 seconds]
<Sonarpulse>
this is a seperate irc channel or the hangout?
<dignifiedquire>
lgierth: ping fails
<dignifiedquire>
no idea what I need to do
<voxelot>
Sonarpulse: join the video hangout, sounds like you have a lot of input
<daviddias>
jbenet one of the key points from the js-ipfs hangout was that we need to figure out the 'Data Importing' spec, https://github.com/ipfs/specs/pull/57 , we are getting it to work, but it is really inspired on go-ipfs impl and dedicated to unixfs/files. It will work, but feel hacky on the browser
<dignifiedquire>
whyrusleeping: pin-rm was my fault -.- I accidentally generated the same random data into it so it was removing the same thing in parallel -.-
<whyrusleeping>
YESSSSSS
mildred has joined #ipfs
peer____ has joined #ipfs
<Kubuxu>
whyrusleeping: there is also lockup problem with big repos
<Kubuxu>
dignifiedquire: are you able to observe with randor/
<Kubuxu>
?
<dignifiedquire>
Kubuxu: I haven't tested repos of that size yet
<dignifiedquire>
whyrusleeping: just pushed, you should be able to run all tests in parallel easily now
<Kubuxu>
Ok, thanks for info. I can for sure say that 16GB == lockup, this is at what my repo sits.
<lgierth>
every one of our gateways has a bigger repo :)
<Kubuxu>
Hmm, interesting.
<Kubuxu>
Almost all commands I do, just don't return.
<Kubuxu>
I might nuke everything and start adding once again.
<dignifiedquire>
Kubuxu: maybe whyrusleeping can take a peak at your repo before you nuke it I can imagine it would be of some use
<Kubuxu>
np, I could expose API or even store the repo
domanic has joined #ipfs
wiedi has joined #ipfs
bsm117532 has joined #ipfs
domanic has quit [Ping timeout: 248 seconds]
ipfsrocks has joined #ipfs
inconshreveable has quit [Remote host closed the connection]
domanic has joined #ipfs
<whyrusleeping>
Kubuxu: interesting...
<whyrusleeping>
is it 16GB worth of one file?
<whyrusleeping>
and this is on 0.4.0?
<whyrusleeping>
and what exactly locks up? (lets move this to an issue)
<Kubuxu>
It is 16GB worth of a lot of file (cdn-js, my files, nothing secret).
<Kubuxu>
Everything that uses datastore.
<whyrusleeping>
best info for me to have will be the output of `ipfs diag sys`, and a stack dump of the daemon when its stuck
<Kubuxu>
How do I do stack dump?
<whyrusleeping>
easy way is curl localhost:5001/debug/pprof/goroutine\?debug=2
charley_ has quit [Remote host closed the connection]
charley_ has joined #ipfs
<Kubuxu>
first call works, second hangs
Encrypt has joined #ipfs
<Kubuxu>
whyrusleeping: so it isn't slow disk, I can give you access to API over cjdns if you want
charley_ has quit [Read error: Connection reset by peer]
charley__ has joined #ipfs
<Kubuxu>
(disk is 2x SAS in RAID 1)
<whyrusleeping>
i need to buy a new disk... my raid box is far far away and my desktop only has two 128GB ssd's in mirror
<whyrusleeping>
and i have 3GB free space
<grey->
yes, yes you do.
<Kubuxu>
I have to buy a SSD to my notebook.
<Kubuxu>
Shift HDD to CD bay and put SSD in.
<grey->
1TB mSATA SSDs are only about $300 right now, and mSATA to SATA adapters are $8 if you don't have mSATA.
<grey->
it is mindboggling how inexpensive fast storage is now.
<Kubuxu>
Samsung released 15TB SSD
<grey->
hahahaha, yeah but the costs on those are insane.
<Kubuxu>
for only ~7000 green
<grey->
the upshot: they will drop the cost of other SSDs.
grey- has quit [Quit: bbl]
<Kubuxu>
It is about -40% as for $/GB
rendar has quit [Ping timeout: 248 seconds]
<ipfsbot>
[go-ipfs] hutenosa opened pull request #2453: deploy: includes commit hash & version (master...fix/version-commit-hash) https://git.io/vaeno
grey- has joined #ipfs
domanic has joined #ipfs
<whyrusleeping>
i spent too much at ikea this week to justify buying another hard drive... i'll just have to find junk to delete
<whyrusleeping>
on a somewhat related note, ikea has the coolest lamps
<grey->
haha
<grey->
well, I am looking for paying work again, so I can relate.
<grey->
I have donated drives to projects in the past.
<grey->
this one seems like it would be worth it.
<whyrusleeping>
lol, i'm mostly kidding
<whyrusleeping>
i should really just drive across town and get my raid box and set that up again
<grey->
*shrug* I'm not. LBA48 support in OpenBSD is in part because I bought the first drive I could find that required it and mailed it to the OpenBSD project.
<whyrusleeping>
oh nice!
<grey->
it seemed like they would benefit from it; monetary donations are nice, but since that project also requests hardware, I do what I can to help when I have the means.
<whyrusleeping>
yeah, that cuts away the discussion of what to spend the money on
<grey->
I would say talk to iXSystems and see if they have anything spare lying around to mail you, they are using IPFS in FreeNAS now. (that is, after all, how I found out about the project)
<grey->
I consulted for them briefly in 2013, good people.
<whyrusleeping>
we've talked with iX systems in the past, they are super cool
<whyrusleeping>
and the guy who started freeBSD works there, right?
<grey->
he does now! ^_^
charley__ has quit [Read error: Connection reset by peer]
<grey->
jkh is awesome. I get a little fanboy around him though.
<grey->
(which was sort of awkward)
<whyrusleeping>
he's actually in this channel every so often
<whyrusleeping>
not right now, but you can find him in the logs
<grey->
makes sense, they run their own IRC network too.
<grey->
IRC, it is the language of "our people" (people being those who develop code on the internet that is)
<whyrusleeping>
haha, indeed
<grey->
I mean, there's SMTP and other nonesense too.
<grey->
I keep on hoping, perhaps not in vain, that SILC or PSYC2 or some encrypted communications protocol will become more popular someday, but it hasn't.
<grey->
I noticed someone wrote a chat app based around IPFS though? I should try that.
<grey->
the fact that someone even did that I think is a hallmark of how interesting IPFS is.
<whyrusleeping>
its a little slow at the moment, but that use-case is high priority
<whyrusleeping>
:D
<grey->
crypto can be slow; thankfully computers are much faster on the whole.
<grey->
I remember it would take about a minute to do key negotiation with SILC on a soekris (basically a 486)
<grey->
these days with AES-NI offloading and such, a lot of crypto is thankfully much much faster.
charley_ has joined #ipfs
<whyrusleeping>
yeah, extended instructions are awesome
<grey->
potentially! All of the MMX and SSE and VTd and VMX and whatnot get a bit annoying to keep track of after a while, particularly as so few deal with low level opcode stuff. I miss the simplicity of a nice 6502 or 68000 instruction set.
<grey->
<- old nerd.
<whyrusleeping>
lol
<whyrusleeping>
todays rough equivalent is arm
<grey->
I mean, I am 40 now, if I were a computer, I should have been decommissioned a long time ago.
<whyrusleeping>
buy yourself a chromebook
<grey->
yeah, ARM never interested me much (I may have been annoyed to see one of the first demos on the Archimedes, not only ripped tunes from Kefrens' Desert Dreams from the Amiga, but they didn't even get the timing correct, so the tune played off key)
ygrek_ has quit [Ping timeout: 276 seconds]
<grey->
similarly, I saw someone post a video of FS-UAE running on the Raspberry Pi 3, and it wasn't even emulating an Amiga 500 at full frame rate. ;-/
<grey->
1.2Ghz 64bit ARM you would think could mimic a 7Mhz 16bit 68000 with a few custom chips well enough, but in practice, I've even crippled 2.25Ghz core2duos trying to do the same.
Encrypt has quit [Quit: Quitte]
* grey-
may also be a bit of a virtualization and emulation nerd.
sknebel has left #ipfs [#ipfs]
<grey->
thankfully, I have found on a top of the line Macbook Pro from the past couple of years, I can emulate an Amiga well enough I can reproduce the kinds of timing errors that were only observable by switching PAL code to NTSC to observe them.
<grey->
FS-UAE is pretty neat at least.
<grey->
reproducing old software timing affectations takes a lot of effort to do well; many emulators will just gloss over the precision required to exhibit that, but it also means that such code will also break or not run correctly.
<whyrusleeping>
yeah, i remember reading about how hard it was to get a bug for bug compatible implementation of an NES emulator
<whyrusleeping>
oh yeah
<whyrusleeping>
that link
<grey->
hehe
<grey->
these days I find mednafen is exemplary for a lot of that.
<whyrusleeping>
huh, i've never seen that one before
<grey->
but it feels pretty ridiculous. I prefer hardware when I can afford it and store it.
<grey->
it's F/OSS, runs a lot of things.
<grey->
the save-state rewinding feature is *amazing*
<grey->
OpenEmu on OS X derives a lot of code from it and is much easier to use though if you've got a Mac.
<grey->
and I've even run it on Windows with success!
<grey->
though I spent a lot more time getting it built on PCBSD at one point (the FreeBSD port was a bit out of date)
<whyrusleeping>
lol, "it works on my system, i wonder if i can find a system it doesnt work on"
<grey->
anyway, I have some odd interests, but most of them involve computing.
ygrek has joined #ipfs
<grey->
hehe
<grey->
maybe! ;)
<grey->
I think I have just become accustomed to cross platform testing as a habit at this point in my life.
<grey->
(also, part of why I am deeply interested in emulators and virtualization things; it at least reduces hardware utilization slightly)
<whyrusleeping>
yeah, it lets us move towards easier cross platform code
conway has joined #ipfs
<grey->
I find docker and containerization mindsets a bit backwards though; at the end of the day, you want to run code with as few abstractions and unnecessary extraneous layers as possible.
<whyrusleeping>
yeah... docker is a bit strange on that end, but it does actually run the code as a process directly on your computer
<grey->
for testing, that can be useful, but it's pretty daft to run in production.
<grey->
In my opinion at least.
<grey->
Albeit, I have created use cases for such nonsense, but they are mostly weird and involve multiple layers of encryption.
<grey->
(running FreeBSD within bhyve within FreeBSD within VMWare was something I did years ago that was a fun proof of concept of something I had been trying to do for years, but not something I would recommend anyone doing in practice)
<grey->
it was also horridly slow.
<whyrusleeping>
lol, reminds me of the time some friends and i tried to see how many layers deep we could run virtualbox
<whyrusleeping>
er, no. it was qemu
inconshreveable has joined #ipfs
<grey->
by comparison, running mednafen within PCBSD within Vmware, though still slow, was still at least fast enough to mimic an NES accurately even with full disk encryption at each layer.
<grey->
yeah, qemu would be easier to deal with than Virtualbox.
Encrypt has joined #ipfs
* whyrusleeping
wonders why a NES needs full disk encryption
<grey->
I couldn't make use of VirtualBox or even Parallels for that experiment at the time since they would not pass the appropriate VTd and VMX instructions to the guest.
<grey->
whyrusleeping: haha, good question. At the time: mostly because I wanted to see if it would even be usable.
<grey->
it was (albeit, on a fast machine with SSD)
<whyrusleeping>
niceee
<grey->
longer term, I have some weird hardware project for a 1980s video game system that is waiting for something like an Edison or Raspberry Pi or Edison to get small enough.
ipfsrocks has joined #ipfs
<grey->
the software end of things I think is mostly where I need it to be at least.
<grey->
the hardware I want still needs to get smaller.
<grey->
If Google actually releases Project Vault someday, maybe that would work though, I could at least try it. The form factor is within my needs at least.
<grey->
I wrote Edison twice. Meh, Galileo? I guess? Whatever Intel is calling their SoC things these days or next I suppose.
<whyrusleeping>
but they need lots of extra plugins to actually do anything with
<grey->
Not quite small enough to fit within a HuCard form factor though.
<grey->
(which was the media format for the PCエンジン/TurboGrafx-16 which is the intended recipient of said bizarre hardware project)
Senji has joined #ipfs
<grey->
that platform was ahead of its time, but and still holds a soft spot in my heart.
<grey->
egads, I am not typing too well at the moment.
<grey->
I should probably sleep. :)
<grey->
anyway, IPFS may play a part in what I have in mind too, I should experiment with it more, but preliminary use has been exciting!
inconshreveable has quit [Remote host closed the connection]
conway has joined #ipfs
charley_ has quit [Ping timeout: 244 seconds]
Senji has quit [Ping timeout: 260 seconds]
charley_ has joined #ipfs
zootella has quit [Quit: zootella]
<richardlitt>
achin: ping
zootella has joined #ipfs
ashark has quit [Ping timeout: 260 seconds]
charley_ has quit [Ping timeout: 260 seconds]
tmg has joined #ipfs
drathir has quit [Ping timeout: 260 seconds]
<richardlitt>
achin: If I could ahve the committers for the weekly, than it is all set to ship! :D
<richardlitt>
Throw them in the draft if possible?
<conway>
Greetings, I've been getting errors in the console with the following: ERROR mdns: mdns lookup error: failed to bind to any multicast udp port mdns.go:131
<conway>
Is this a known issue, or something I should open a proper issue over?