<alterego>
richardlitt: several, I'm implementing a go project that works with IPFS objects, so I need to do a few things like put objects, get objects findprovs, etc
<richardlitt>
Cool. Are the `--help` commands not enough?
<alterego>
Eww, you want me to invoke ipfs with exec? :P
<daviddias>
I am looking at it, but I was hoping you would know what was the dep that caused this regression since you work a lot with these tools :)
<daviddias>
if you can take a look, that would be great :)
jhulten_ has joined #ipfs
<dignifiedquire>
daviddias: will do, by the way I have to write my own rust-multihash before I can use it in rust-multiaddr to parse ipfs addresses :(
<dignifiedquire>
the google one has those nasty license headers, uses openssl (which I might not get around for now) and only implements encode
<daviddias>
Well, try to open an issue first
<dignifiedquire>
daviddias: no chance, achin opened to prs without comments weeks ago
<dignifiedquire>
*two
<daviddias>
But the decode of multihash doesn't have to be inside multiaddr
<dignifiedquire>
it’s not maintained at all
<dignifiedquire>
it was just written and dumped :(
<daviddias>
In js it is just parsed by multiaddr
<daviddias>
I see
jhulten_ has quit [Ping timeout: 240 seconds]
<dignifiedquire>
well I need ipfs address <-> base58 hash
<dignifiedquire>
(in multiaddr)
elima has quit [Ping timeout: 246 seconds]
e-lima has quit [Ping timeout: 255 seconds]
sivachandran has joined #ipfs
Ursium has quit [Read error: Connection reset by peer]
Ursium has joined #ipfs
<sivachandran>
jbenet: As you asked I have network packets capture of communication between two IPFS peers. It is a 545Mbps communication channel between these two peers but IPFS took 14secs to download 100mb file.
<sivachandran>
jbenet: I can able to read the pcap file with Wireshark. Is there something I should look at it?
elima has joined #ipfs
e-lima has joined #ipfs
Ursium has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<dignifiedquire>
but it makes no sense, 0.3.10 release was after the pr was merged
<dignifiedquire>
no right
<dignifiedquire>
my commits were before
<dignifiedquire>
but the merge happend after :cry:
Tera2342 has joined #ipfs
zen|merge has quit [Remote host closed the connection]
<daviddias>
also "Last built 1 week ago using go version go1.5.1 linux/amd64 and 489 seconds of time" which means we have a multipart bug that was fixed on the http package of go1.5.2
<dignifiedquire>
daviddias: :(
<ipfsbot>
[js-ipfs-api] Dignifiedquire pushed 1 new commit to 0.3.10: http://git.io/v0biq
<ipfsbot>
js-ipfs-api/0.3.10 7ffa08c dignifiedquire: Add headers back, need to wait for 0.3.11
<Stskeeps>
is there something like getting notified that a IPNS updated?
keorn has quit [Ping timeout: 265 seconds]
<dignifiedquire>
daviddias: for me tests are all good now locally
<dignifiedquire>
daviddias: if you want take a stab at the njdson stuff, I’ll probably can look at it earliest tonight
zen|merge has joined #ipfs
zen|merge has quit [Changing host]
zen|merge has joined #ipfs
<dignifiedquire>
(work and stuff ;) )
<daviddias>
sweet, thank you dignifiedquire :)
<dignifiedquire>
daviddias: :'(
<dignifiedquire>
daviddias: vinyl-fs-browser is f*** us again.
reit has joined #ipfs
<daviddias>
oh.. I'm afraid to ask, but i have to, how?
<dignifiedquire>
a dependency of it is not compatible with webpack anymore because it uses require in a non static way
<daviddias>
'anymore', can't we usea previous version?
<dignifiedquire>
no idea what changed and when.. my old install ran fine, reinstalled everything and suddenly it’s broken
<daviddias>
"glob-stream": "^5.0.0" should solve it
<dignifiedquire>
deleting vinyl-fs-browser as well...
<dignifiedquire>
fixing it to glob-stream@5.2.0 solves it for now
<ipfsbot>
[js-ipfs-api] Dignifiedquire pushed 1 new commit to 0.3.10: http://git.io/v0bQN
<ipfsbot>
js-ipfs-api/0.3.10 7bf5460 dignifiedquire: Fix glob-stream version to avoid issues with upgraded micromatch library
NightRa has joined #ipfs
brixen has quit [Ping timeout: 256 seconds]
jhulten_ has joined #ipfs
<daviddias>
seems like semver police has been sleeping on their job :p
<dignifiedquire>
daviddias: yep
martinkl_ has joined #ipfs
jhulten_ has quit [Ping timeout: 240 seconds]
brixen has joined #ipfs
hoony has joined #ipfs
<xiaonormie>
semver police
<xiaonormie>
:D
compleatang has joined #ipfs
brixen has quit [Ping timeout: 272 seconds]
mildred has joined #ipfs
randomguy has joined #ipfs
pfraze has joined #ipfs
hellertime has joined #ipfs
hellertime has quit [Ping timeout: 255 seconds]
Ursium has joined #ipfs
gaboose has joined #ipfs
chriscool has quit [Quit: Leaving.]
pfraze has quit [Remote host closed the connection]
pfraze has joined #ipfs
pfraze has quit [Remote host closed the connection]
hellertime has joined #ipfs
<dignifiedquire>
daviddias: have you started on the ndjson stuff yet?
Kubuxu has joined #ipfs
martinkl_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Kubuxu>
\o I was wondering if there is some system or plan in place to incorporate IPFS as cache for HTTP. It would improve enrollment of IPFS significantly.
<Kubuxu>
at lest IMHO
<dignifiedquire>
daviddias: anyhow I just did it ;)
<ipfsbot>
[js-ipfs-api] Dignifiedquire pushed 1 new commit to 0.3.10: http://git.io/v0Nsk
<ipfsbot>
js-ipfs-api/0.3.10 ecccc92 dignifiedquire: Parse chunked responses using ndjson....
hoony has quit [Ping timeout: 260 seconds]
keorn has joined #ipfs
<ipfsbot>
[js-ipfs-api] Dignifiedquire pushed 1 new commit to 0.3.10: http://git.io/v0NGF
<ipfsbot>
js-ipfs-api/0.3.10 4881206 dignifiedquire: docs: Update CORS handling docs....
keorn has quit [Ping timeout: 255 seconds]
Tera2342 has quit [Ping timeout: 240 seconds]
Ursium has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
cemerick has joined #ipfs
j0hnsmith has joined #ipfs
Ursium has joined #ipfs
jhulten_ has joined #ipfs
arpu has quit [Quit: Ex-Chat]
jhulten_ has quit [Ping timeout: 240 seconds]
<ipfsbot>
[go-ipfs] rht force-pushed fix/logwriter-stall from b3094ab to d72ffae: http://git.io/v0bJZ
<ipfsbot>
go-ipfs/fix/logwriter-stall d72ffae rht: Reduce the number of auto gc tests...
keorn has joined #ipfs
pfraze has joined #ipfs
pfraze has quit [Ping timeout: 240 seconds]
keorn has quit [Ping timeout: 255 seconds]
jedahan has joined #ipfs
pokeball99 has quit [Ping timeout: 255 seconds]
pokeball99 has joined #ipfs
zz_r04r is now known as r04r
supertyler has joined #ipfs
jedahan has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<supertyler>
Hi - I am new here. Looking for some help.
NeoTeo has quit [Quit: Teo is off. Bye :)]
drathir has quit [Ping timeout: 272 seconds]
Encrypt_ has joined #ipfs
NeoTeo has joined #ipfs
arpu has joined #ipfs
bigbluehat has quit [Ping timeout: 250 seconds]
<fazo>
supertyler: Hi :) what do you need help with
<daviddias>
dignifiedquire: I was out, now I'm back
<daviddias>
:)
<daviddias>
ok, in that case I'll continue to focus on the bitswap stuff :)
<fazo>
daviddias: woo you're doing js-bitswap?
Guest47859 has joined #ipfs
<daviddias>
yep :) trying to make it flexible, so that we can have several bitswap strategies
<fazo>
finally :D can't wait for ipfs in the browser
<fazo>
I really like how flexible everything you have worked on is. the js implementation of things looks quite better than the go one
<daviddias>
yeah, I like a lot our design decisions when it comes to modularity, specially when it comes to describe what each thing is, having a clear interface and expecations
dignifiedquire- has joined #ipfs
<dignifiedquire->
daviddias, fazo and the rust one will be even better :P
<fazo>
dignifiedquire good luck writing multithreading software in rust lol
<dignifiedquire->
I actually look forward to it
<dignifiedquire->
I've done concurrency in c on graphiccards befor :D
<dignifiedquire->
so this will be a cake walk
<fazo>
damn. You won't have any problems at all then :D
<dignifiedquire->
and at least I get real multithreading not this JS oh god performance is bad lets not do that cause it's hard
elima has quit [Ping timeout: 255 seconds]
e-lima has quit [Ping timeout: 246 seconds]
<fazo>
true that. JS runs in browsers, but multithreading is really bad.
dignifiedquire- has quit [Remote host closed the connection]
reit has quit [Ping timeout: 240 seconds]
elima has joined #ipfs
e-lima has joined #ipfs
keorn has joined #ipfs
Encrypt_ has quit [Quit: Quitte]
<ion>
Rust used to have lightweight threads but then they got removed. :-(
supertyler has quit [Ping timeout: 252 seconds]
keorn has quit [Ping timeout: 265 seconds]
mafintosh has quit [Ping timeout: 272 seconds]
keorn has joined #ipfs
sugarpuff has quit [Ping timeout: 256 seconds]
oleavr has quit [Ping timeout: 272 seconds]
martinkl_ has joined #ipfs
voxelot has joined #ipfs
voxelot has joined #ipfs
oleavr has joined #ipfs
sugarpuff has joined #ipfs
nham has joined #ipfs
mafintosh has joined #ipfs
<ipfsbot>
[go-ipfs] rht force-pushed fix/corsconfig from 7d88d5a to f98f7b1: http://git.io/vBxYK
<ipfsbot>
go-ipfs/fix/corsconfig f98f7b1 rht: Add SetAllowedOrigins race test case...
jhulten_ has joined #ipfs
keorn has quit [Ping timeout: 256 seconds]
martinkl_ has quit [Ping timeout: 240 seconds]
keorn has joined #ipfs
ulrichard has quit [Ping timeout: 260 seconds]
martinkl_ has joined #ipfs
<dignifiedquire>
ion: how come, do you have a link with some background story around that?
<dignifiedquire>
fazo: what’s the single most important thing for it that you want to promote?
<fazo>
the point of this app is letting the users share anything with the world, create and manage communities, without depending on any third party
<fazo>
dignifiedquire: I'm not sure D:
<dignifiedquire>
those are multiple things
<dignifiedquire>
if you want a successfull thing, focus on one thing (that might be large) but one thing only
<randomguy>
Freedom-board :P
<fazo>
uhm let me think
<dignifiedquire>
from what you’ve been telling me it feels like the most important aspect for you is to provide a place for communities to grow?
<fazo>
if I had to focus on one thing, it would be the fact that it's distributed. There is no necessary third party for it to work
<randomguy>
than maybe include 'connect' in the name?
<fazo>
dignifiedquire: I don't think so, I think the point is more to provide a distributed alternative to existing services
<fazo>
with huge advantages and power to the users
<dignifiedquire>
that’s a great thing, but more of a technical feature, the question is what is what does it provide to the end user
<fazo>
that would be control and power.
<dignifiedquire>
control over what?
<fazo>
everything they publish
<dignifiedquire>
okay, so it’s about publishing?
<randomguy>
can users delete boards?
<fazo>
yep. It's about sharing content.
<randomguy>
ipfs isnt permanent?
<fazo>
randomguy: yes but nothing stops anyone else from making backups
<fazo>
exactly
<dignifiedquire>
okay so the main thing that a user can do is to publish content on a permanent basis?
<randomguy>
you also need a ''private'' area for groups
<randomguy>
this content needs to be encrypted
<fazo>
for example: sometimes it happens on services like reddit or random forums that someone deletes stuff and does things, so people take screenshots or archive pages. In this app, this is not necessary, the app is the archive
<fazo>
randomguy: it's planned, but far away for now
<dignifiedquire>
on the other hand if you ever write something and regret it you have no chance of taking it back
<dignifiedquire>
though that is kind of a general problem on the internet
<fazo>
dignifiedquire: yes, it's to publish content and have the highest possible control
<fazo>
yes, since it's a general problem, I chose to embrace that
<fazo>
you can't really solve that. You can only work around it
<fazo>
so I thought about making it a core feature
<randomguy>
well if other people would only receive what u share with ipns publish, you could delete content and it wont be streamed anymore -> deleted ;)
<fazo>
you can still take back things. You can delete everything, but you can't make the app and its users forget about it
<dignifiedquire>
okay, now that we know that we can work on a name based around the premise “Share your content in a reliable, uncensored and permanent way”
<fazo>
sure :)
<fazo>
randomguy: yes but anyone can store old records and keep the data.
<randomguy>
well in theory but you can make it hard to read the ipfs hash ;)
<randomguy>
so its not common and doesnt show up
<randomguy>
on other sites, users can also take screenshots .. so its ok :)
<fazo>
the main focus areas are: -public- community building, content sharing, being distributed and thus more powerful
<fazo>
think about when you want to open a blog, you have a community to manage, or you want to share your stuff like code, projects, any media
<fazo>
for a blog you either microblog on twitter, or you use another centralized service
<fazo>
for code you use github. For media? either your blog, tumblr, or twitter. maybe facebook
<randomguy>
so its 'hosting for everyone on your own computer'
<dignifiedquire>
or good ol bulletin boards
<fazo>
and for a community? it depends, you can manage it on facebook or github depending on where it's born
<fazo>
or you can set up a forum
<fazo>
this platform wants to be a distributed, very easily accessible alternative to all of these
keorn has quit [Ping timeout: 256 seconds]
<fazo>
yep, it's hosting for everyone on your own computer, with the highest possible control given to the end user
<fazo>
a truly open platform, the first of its kind if it works
<fazo>
there is no alternative to this that works in a browser without external applications. This one will
<randomguy>
u need ipfs as an external app doesnt you ?
<fazo>
and in seconds you can publish your papers, code, blog posts, pics, media, anything
<fazo>
randomguy: for now, but ipfs for the browser is in development
<randomguy>
but where do u save and publish your content if u are only in browsers temp folder?
<fazo>
randomguy: it's stored in the browser, then there will be servers pulling everything they can find to replicate it. Anyone can run one of these and contribute to the community
<randomguy>
ah ok
<fazo>
and you will be able to know more or less how many copies are around
<randomguy>
so there are file-size-limits ?
<fazo>
no
<fazo>
it's also a file system. So you can interact with it so easily, you just have to change a couple files.
<randomguy>
but lets say i host such 'super-node' and i dont want that one guy stores 80% of his videos on my computer? because others also need space?
<fazo>
well, according to the rules of this app, it's your problem :) your super node isn't smart enough to know that one user is taking up too much space.
<randomguy>
so either reward them for hosting or let them choose what to host
<fazo>
yeah it's gonna be the second. they will choose of course
<fazo>
I also plan a button similar to the infamous facebook "like" button
<fazo>
but instead of "liking" stuff you keep it on your computer. You seed that content, serving it to other people that want to see it. This way you truly show that you like that content, because it's not just about pressing a button, it's donating some bandwidth and some space on your machine because you want that content to reach new audiences
<randomguy>
ok now your Project sounds like: Ipfs everywhere :)
<dignifiedquire>
fazo: what about “perma”, “permablocks”, or “openblocks”
<randomguy>
permabase ;)
<fazo>
you can think of it as the ultimate user interface to ipfs.
baselab has joined #ipfs
<randomguy>
'InterBase'
<fazo>
dignifiedquire: uhm not bad, but we need better I guess
<randomguy>
pinIt
<dignifiedquire>
blocker
<dignifiedquire>
blokker
<dignifiedquire>
nah
<dignifiedquire>
ignore me
<fazo>
uhm... Fileform?
<fazo>
damn, may not be the name, but it sounds cool
<dignifiedquire>
it sounds nice, but form doesn’t seem to fit for me
<fazo>
yeah... but it's an unbelievable name, it sounds so cool, yet there's __nothing__ named fileform
<fazo>
anyway I think I figured out what I want this to be
<fazo>
a user interface to IPFS
lidel has quit [Ping timeout: 256 seconds]
<fazo>
a complete, feature complete one that is general enough to cover most use cases yet specific enough to appeal to many audiences
<dignifiedquire>
then call it uPFS
<fazo>
uhm doesn't sound nice, sorry
lidel has joined #ipfs
martinkl_ has joined #ipfs
<fazo>
you guys are a huge help. I didn't even know that I didn't know what I wanted this application to be lol
<fazo>
damn I like Fileform though.
<dignifiedquire>
;D
<fazo>
it also makes a lot of sense: on this app, everything is just a file, you can literally view it as a huge collections of files using go-ipfs