<noflag>
my webui isn't showing node info or peers
rendar has quit [Quit: Leaving]
<apophis>
noflag: are you trying to view statistics for a remote server?
<noflag>
no, local
<whyrusleeping>
NeoTeo: is that for running on an iPhone?
<apophis>
ok. how long have you been running IPFS?
<noflag>
a few minutes
<noflag>
the console loads, but isn't showing info
<whyrusleeping>
noflag: what version of ipfs?
<NeoTeo>
whyrusleeping Yes or OS X
<whyrusleeping>
NeoTeo: ooOoo, fun!
<noflag>
ipfs version 0.3.10-dev
<NeoTeo>
:)
<noflag>
ipfs works and cli shows a lot of peers
<jadedfs>
Sorry to butt in, but I have the same issue. Same version of IPFS, GNU/Linux.
<jadedfs>
The cli statistics work, but web UI doesn't.
Matoro has quit [Ping timeout: 240 seconds]
<NeoTeo>
Obviously the node is not running on the phone until we get an actual IPFS implementation in Swift (although I know that some of the Cocoa guys here in Cph have got PeerFlix (?) running on the new AppleTV)
<NeoTeo>
Since that's Node stuff perhaps it would be possible to run the js node on the Apple TV/iOS devices as well.
<NeoTeo>
I see now that peerflix is mafintosh's :) It all comes full circle.
__konrad_ has joined #ipfs
<pjz>
whyrusleeping: how parallel is go-ipfsd? if I run multiple ipfs commands using the CLI (which presumably talk to the single running ipfsd) will they block on each other?
<whyrusleeping>
pjz: nope
<richardlitt>
@mappum @kyledrake @lgierth @whyrusleeping Please add your TODOs for this sprint into https://github.com/ipfs/pm/issues/51! Thanks.
<richardlitt>
@jbenet too, if you're awake. Also, up for chatting now if you like.
<lgierth>
on it thank you :]
<whyrusleeping>
richardlitt: you da best
<richardlitt>
thanks lgierth
<richardlitt>
thanks whyrusleeping
<whyrusleeping>
working on it in a scratchpad, will post when i'm done
Matoro has joined #ipfs
neoteo_ has joined #ipfs
rombou has joined #ipfs
neoteo_ has quit [Remote host closed the connection]
__konrad_ has quit [Ping timeout: 246 seconds]
tilgovi has quit [Ping timeout: 264 seconds]
OutBackDingo has quit [Quit: Leaving]
cow_2001 has joined #ipfs
<cow_2001>
e-cat: hi
chriscool has quit [Ping timeout: 240 seconds]
OutBackDingo has joined #ipfs
TheWhisper has quit [Quit: Leaving]
Remjey has joined #ipfs
TheWhisper has joined #ipfs
water_resistant has quit [Quit: Leaving]
<Remjey>
Hello, is there somewhere a list of ports to open in my firewall to have ipfs work perfectly? I already opened the tcp:4001 port but I wonder if I should open the udp:5353 port
apophis has quit [Quit: This computer has gone to sleep]
Matoro has quit [Ping timeout: 240 seconds]
ygrek_ has joined #ipfs
<achin>
hi there. in the current version of ipfs, it only uses TCP to communicate between nodes, so tcp/4001 is all you need
ygrek has quit [Ping timeout: 240 seconds]
<Remjey>
achin: ok thanks
OutBackDingo has quit [Quit: Leaving]
<achin>
(i'm not sure what udp 5353 is for)
rombou has quit [Ping timeout: 252 seconds]
<kpcyrd>
mdns?
jamie_k_ has quit [Quit: jamie_k_]
rombou has joined #ipfs
Matoro has joined #ipfs
tilgovi has joined #ipfs
voxelot has quit [Ping timeout: 276 seconds]
davidar has joined #ipfs
<davidar>
haadcode_: awesome, building now :)
<davidar>
ping?
joshbuddy has quit [Quit: joshbuddy]
HoboPrimate has quit [Quit: HoboPrimate]
OutBackDingo has joined #ipfs
rombou has quit [Ping timeout: 240 seconds]
pfraze has joined #ipfs
tilgovi has quit [Remote host closed the connection]
NeoTeo has quit [Quit: ZZZzzz…]
<Remjey>
kpcyrd: in fact, i wonder how it is possible for ipfs to listen of the same port as avahi at the same time :|
<kpcyrd>
Remjey: reuseport, probably
rombou has joined #ipfs
joshbuddy has joined #ipfs
devbug has quit [Ping timeout: 265 seconds]
joshbuddy has quit [Quit: joshbuddy]
flyingdonut has joined #ipfs
<flyingdonut>
Is it possible to export and transfer your node's ipns key for use elsewhere or when changing machines?
<achin>
all you need is your ~/.ipfs/config file
od1n has joined #ipfs
<flyingdonut>
Ah, ok. I see the PrivKey in the config file. Can the PeerID change and still have the key work, or is the key tied to that id?
<achin>
the peerID is a hash of the public key of the privatekey listed in the config file
<achin>
so they are tied
od1n has quit [Ping timeout: 246 seconds]
f[x] has joined #ipfs
<flyingdonut>
so the private key can't be used by multiple nodes to (for example) update an ipns path, right?
od1n has joined #ipfs
<lgierth>
flyingdonut: there's going to be support for multiple keys soon
<lgierth>
so that multiple nodes can share responsibility for a namespace
<flyingdonut>
ok, thanks!
ygrek_ has quit [Ping timeout: 240 seconds]
od1n has quit [Ping timeout: 240 seconds]
Qwertie has quit [Ping timeout: 250 seconds]
<pjz>
is on-disk blocksize the same as the size returned by block stat?
Qwertie has joined #ipfs
od1n has joined #ipfs
od1n has quit [Client Quit]
Teruyuki has quit [Remote host closed the connection]
od1n has joined #ipfs
goatbush has joined #ipfs
flyingdonut has left #ipfs ["WeeChat 0.4.2"]
apophis has joined #ipfs
od1n has quit [Ping timeout: 240 seconds]
Matoro has quit [Read error: Connection reset by peer]
Matoro has joined #ipfs
xelra has quit [Ping timeout: 250 seconds]
xelra has joined #ipfs
apophis has quit [Ping timeout: 276 seconds]
rombou has quit [Ping timeout: 250 seconds]
apophis has joined #ipfs
<ipfsbot>
[go-ipfs] whyrusleeping force-pushed refactor/transport from 6885955 to 22c41ea: http://git.io/v8I9y
<ipfsbot>
go-ipfs/refactor/transport 22c41ea Jeromy: only fail interface setup if all addresses fail...
<whyrusleeping>
hopefully none of my enemies lurk this channel, but my fatal weakness is chocolate covered pomegranate seeds
<whyrusleeping>
i've yet to restrain myself from eating an entire bag in one sitting
<achin>
i've never had those. but all of a sudden i want them
<ion>
Sounds tasty.
<whyrusleeping>
i'm pretty sure theres some sort of drug in them
guest234234 has quit [Ping timeout: 265 seconds]
<ion>
It’s called chocolate.
<whyrusleeping>
but chocolate bars dont have the same 'sit here and eat them until they are gone' effect on me
<achin>
maybe it's the bite-sized-ness. do you have similar problems with pistachios ?
<whyrusleeping>
salted roasted almonds to a lesser extent...
<whyrusleeping>
hrm...
<whyrusleeping>
you might be on to something
<ion>
How about salted roasted chocolate covered almonds?
<achin>
ion: we want whyrusleeping to remain productive. if you cause him to go into a salted roasted choholate covered almond coma, you'll never be forgivven
<whyrusleeping>
ion: wait.. thats a thing?
<whyrusleeping>
it is a thing...
<ion>
I didn’t actually know.
<whyrusleeping>
jbenet: they all passed (except for a few random failures that i ran a couple more times to be sure)
devbug has joined #ipfs
od1n has joined #ipfs
<jbenet>
ok
<ipfsbot>
[go-ipfs] jbenet pushed 1 new commit to master: http://git.io/v8Kmp
<ipfsbot>
go-ipfs/master ece43a5 Juan Benet: Merge pull request #1937 from ipfs/refactor/transport...
<ipfsbot>
[go-ipfs] jbenet closed pull request #1937: refactor net code to use transports, in rough accordance with libp2p (master...refactor/transport) http://git.io/vlPfP
<multivac>
OperationalError: database is locked (file "/usr/local/lib/python2.7/dist-packages/sopel/db.py", line 64, in execute)
<ipfsbot>
go-ipfs/master 76dedd8 Juan Benet: Merge pull request #1495 from rht/gc...
voxelot has quit [Ping timeout: 276 seconds]
mildred has joined #ipfs
border0464 has quit [Ping timeout: 240 seconds]
border0464 has joined #ipfs
__konrad_ has joined #ipfs
rombou has joined #ipfs
niekie has quit [Ping timeout: 240 seconds]
<haadcode_>
davidar: pong
anshukla has joined #ipfs
<davidar>
haadcode_ (IRC): sorry, IRC bridge dropped out for a while
ygrek_ has quit [Ping timeout: 240 seconds]
dd0 has quit [Ping timeout: 240 seconds]
<haadcode_>
davidar: was afk. did you try it out?
<davidar>
No, not yet, was installing stuff from npm last I looked
rombou has quit [Ping timeout: 240 seconds]
<davidar>
I'll try it out later tonight
<haadcode_>
k
slothbag has joined #ipfs
s_kunk has quit [Ping timeout: 252 seconds]
anshukla has quit [Remote host closed the connection]
amstocker has quit [Ping timeout: 246 seconds]
dignifiedquire has joined #ipfs
apophis has quit [Quit: This computer has gone to sleep]
<ipfsbot>
[go-ipfs] whyrusleeping pushed 1 new commit to fix/add-mem: http://git.io/v86R9
<ipfsbot>
go-ipfs/fix/add-mem 9d18f13 Jeromy: rework editor creation and finalization...
grahamperrin has quit [Remote host closed the connection]
rendar has joined #ipfs
niekie has joined #ipfs
<ipfsbot>
[go-ipfs] jbenet pushed 1 new commit to master: http://git.io/v86up
<ipfsbot>
go-ipfs/master ca443b3 Juan Benet: Merge pull request #1956 from ipfs/hotfix/err-log-query...
<ipfsbot>
[go-ipfs] jbenet deleted hotfix/err-log-query at 70b64ac: http://git.io/v86zJ
NightRa has quit [Quit: Connection closed for inactivity]
e-lima has quit [Ping timeout: 240 seconds]
jamie_k has quit [Quit: jamie_k]
e-lima has joined #ipfs
rombou has joined #ipfs
silotis has quit [Ping timeout: 240 seconds]
jamie_k has joined #ipfs
rombou has quit [Ping timeout: 240 seconds]
dd0 has joined #ipfs
silotis has joined #ipfs
s_kunk has joined #ipfs
Encrypt has joined #ipfs
parenchymatitis has quit [Ping timeout: 240 seconds]
voxelot has joined #ipfs
voxelot has joined #ipfs
<ipfsbot>
[webui] masylum closed pull request #82: Bypass CORS in development by proxying `Origin` headers correctly (master...feature/bypass-cors-in-developement) http://git.io/vnu3W
thurificate has joined #ipfs
jhulten has quit [Ping timeout: 246 seconds]
jamie_k has quit [Quit: jamie_k]
master8787 has joined #ipfs
NeoTeo has joined #ipfs
joshbuddy has joined #ipfs
rombou has joined #ipfs
e-lima has quit [Ping timeout: 250 seconds]
thurificate has quit [Remote host closed the connection]
zabirauf has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<victorbjelkholm>
davidar, semver is up to the author, not a fault of semver... Complain at node ;)
<victorbjelkholm>
davidar, you'll need to reinstall node_modules after upgrading node version. Also, you should be on npm^3
<victorbjelkholm>
if you're not, do npm install -g npm@latest
<haadcode_>
davidar: back. yeah, you want to use node 4.2 or later. with 0.x version it won't work. see the Vagrantfile in the repo for example how to install node 4.x on ubuntu.
<davidar>
haadcode_: oh, should i have my daemon running?
<haadcode_>
davidar: that's for 'ipfs swarm connect'. sometimes it takes a while to find the peers that have the required hashes (ie. channel messages)
<haadcode_>
davidar: you don't need to have the daemon running, the program starts one.
<davidar>
ok, not getting errors anymore
<davidar>
but sending messages doesn't seem to be working
ion has quit [Ping timeout: 252 seconds]
jamie_k has quit [Client Quit]
<haadcode_>
davidar: can see you now
<haadcode_>
your messages
<davidar>
(or receiving from what i can see, it's just blank)
hoony has joined #ipfs
<davidar>
cool, it works :)
<haadcode_>
cool :)
ion has joined #ipfs
dignifiedquire_ has joined #ipfs
dignifiedquire_ has quit [Client Quit]
voldial has quit [Quit: WeeChat 1.2-dev]
<davidar>
VictorBjelkholm (IRC): get in here ;)
<victorbjelkholm>
davidar, haha, busy with real work!
<victorbjelkholm>
weekday + working hours
<victorbjelkholm>
bah
<davidar>
oh yeah, timezones :p
<victorbjelkholm>
yeah... Where are you located btw davidar?
<davidar>
australia
<victorbjelkholm>
oh.. Have fun with those spiders
<davidar>
they're nothing compared to the dropbears...
NeoTeo has quit [Quit: Teo is off. Bye :)]
jamie_k has joined #ipfs
hellertime has joined #ipfs
jamie_k has quit [Client Quit]
<victorbjelkholm>
"Drop bears are commonly said to be unusually large, vicious, carnivorous marsupials related to koalas"
<victorbjelkholm>
wtf
<victorbjelkholm>
carnivorous koalas? davidar just gave me yet another reason to never visit australia
<davidar>
yep, and they're particularly fond of tourists
<victorbjelkholm>
"Drop bears are less likely to attack people with Australian accents, according to experts at the University of Tasmania"
<locusf>
:D
<davidar>
hehe, i love the "attacking prey" picture
NeoTeo has joined #ipfs
<locusf>
damn vampire koalas
<cryptix>
i wonder if busyboxes sshd is named after them and what i should think about that ^^
<davidar>
cryptix: who do you think writes busybox? ;)
<cryptix>
aussies? :P
<davidar>
i was thinking dropbears :p
<cryptix>
aah ^^
<locusf>
hah april-1
<davidar>
locusf: only 6 months late :p
<davidar>
or whatever 11-4 is
<davidar>
7
<__konrad_>
isn't it april 1 in australia right now?
<davidar>
__konrad_: only if you're in a state that observes daylight savings ;)
<davidar>
otherwise it's just the proverbial "last tuesday"
<victorbjelkholm>
I thought Australia was a permanent april 1. Like mother natures april 1
<__konrad_>
xD
jamie_k has joined #ipfs
<davidar>
ouch, VictorBjelkholm, ouch :p
<davidar>
although probably true :p
<davidar>
VictorBjelkholm (IRC): where is Catalunya ? :/
<davidar>
.w Catalunya
<multivac>
[WIKIPEDIA] Catalonia | "Catalonia (Catalan: Catalunya, Occitan: Catalonha, Spanish: Cataluña) is an autonomous community of Spain and designated a "historical nationality" by its Statute of Autonomy. Catalonia consists of four provinces: Barcelona, Girona, Lleida, and Tarragona. The capital and largest city is Barcelona, the..." | https://en.wikipedia.org/wiki/Catalonia
<davidar>
oh, catalonia
devbug has quit [Remote host closed the connection]
pfraze has joined #ipfs
hoony has quit [Quit: Page closed]
cemerick has joined #ipfs
<davidar>
haadcode_: hrm, seems to get stuck on "fetching object" every so often
jamie_k has quit [Quit: jamie_k]
voxelot has quit [Ping timeout: 260 seconds]
jhulten has joined #ipfs
besenwesen has quit [Ping timeout: 240 seconds]
jamie_k has joined #ipfs
ThomasWaldmann has quit [Ping timeout: 255 seconds]
<davidar>
haadcode_: anyway, looks really good otherwise, keep it up :)
<davidar>
night all
ThomasWaldmann has joined #ipfs
ThomasWaldmann has quit [Changing host]
ThomasWaldmann has joined #ipfs
besenwesen has joined #ipfs
besenwesen has quit [Changing host]
besenwesen has joined #ipfs
<NeoTeo>
night :)
<haadcode_>
davidar: roger
jamie_k has quit [Client Quit]
jhulten has quit [Ping timeout: 240 seconds]
jamie_k has joined #ipfs
qgnox has quit [Ping timeout: 265 seconds]
rombou has joined #ipfs
<victorbjelkholm>
davidar, catalunya is currently in spain but soon to the east of spain :D
border0464 has quit [Ping timeout: 240 seconds]
border0464 has joined #ipfs
jamie_k has quit [Quit: jamie_k]
apophis has joined #ipfs
Encrypt has joined #ipfs
jamie_k has joined #ipfs
rombou has quit [Ping timeout: 240 seconds]
qgnox has joined #ipfs
rombou has joined #ipfs
jamie_k has quit [Quit: jamie_k]
jamie_k has joined #ipfs
tsenior has joined #ipfs
jamie_k has quit [Quit: jamie_k]
jamie_k has joined #ipfs
rombou has quit [Ping timeout: 255 seconds]
tsenior has quit [Ping timeout: 240 seconds]
jamie_k has quit [Client Quit]
dignifiedquire has quit [Quit: dignifiedquire]
jamie_k has joined #ipfs
rombou has joined #ipfs
Encrypt_ has joined #ipfs
SWingedSeraph_ has joined #ipfs
<pjz>
:liked Barcelona when he visited.
JohnClare has joined #ipfs
Encrypt has quit [Ping timeout: 240 seconds]
Encrypt_ is now known as Encrypt
jamie_k_ has joined #ipfs
jamie_k has quit [Ping timeout: 246 seconds]
jamie_k_ is now known as jamie_k
SWingedSeraph has quit [*.net *.split]
stoopkid has quit [Quit: leaving]
pfraze has quit [Remote host closed the connection]
tsenior has joined #ipfs
rombou has quit [Ping timeout: 250 seconds]
yoshuawuyts has quit [Ping timeout: 264 seconds]
sickill_ has quit [Ping timeout: 264 seconds]
rombou has joined #ipfs
yoshuawuyts has joined #ipfs
sickill has joined #ipfs
roguism has joined #ipfs
apophis has quit [Quit: This computer has gone to sleep]
<roguism>
Hey, I just read the whitepaper, and I must say I'm really impressed.
danslo has quit [Remote host closed the connection]
danslo has joined #ipfs
<roguism>
A couple questions; can a node advertise multiple routes? i.e. a multi-device user? How do other nodes handle multiple routes?
<achin>
i'm not sure what you mean by a "route"
<roguism>
address
<achin>
at the moment, there is only 1 node per address(peerID), and 1 peerID per node
<achin>
(did that answer your question?)
<roguism>
Yeah; is that an inherent limitation of the protocol, or simply due to the early stage of the implemenation?
<roguism>
Is there plans to go beyond 1 node=1 peerID
<achin>
as far as i know, it's just an implementation thing
<achin>
i think there are some github issues about this
<roguism>
alright, cool
<roguism>
Also, can a node serve procedural content?
<achin>
like dynamic content?
<roguism>
Like "/ipns/<alice>/" provides a service where she provides the sum of any two numbers given to her
<achin>
no. an IPNS is just a mapping from a peerID to a content hash
<achin>
a content hash is static content, always
<roguism>
Hmm, okay
<cryptix>
roguism: you can use ipfs to dial $peerID and make your own services on top: /ipfs/QmTkzDwWqPbnAh5YiV5VwcTLnGdwSNsNTn2aDxdXBFca7D/example#/ipfs/QmQwAP9vFjbCtKvD8RkJdCvPHqLQjZfW7Mqbbqx18zd8j7/api/service/readme.md
<achin>
(a dynamic user-interface can be provided though, by a javascript app, or something similar. but this means all logic is client side)
<cryptix>
but it requires golang skills currently
<roguism>
cryptix: I'm a bit rusty on my golang, but that looks like what I was getting at
jamie_k has quit [Quit: jamie_k]
Encrypt has quit [Quit: Quitte]
JohnClare has quit [Remote host closed the connection]
JohnClare has joined #ipfs
pfraze has joined #ipfs
tsenior has quit [Read error: Connection reset by peer]
tsenior has joined #ipfs
JohnClare has quit [Ping timeout: 244 seconds]
Encrypt has joined #ipfs
dignifiedquire has joined #ipfs
NightRa has quit [Quit: Connection closed for inactivity]
voxelot has joined #ipfs
voxelot has joined #ipfs
OutBackDingo has quit [Ping timeout: 252 seconds]
jamie_k has joined #ipfs
rombou has quit [Ping timeout: 240 seconds]
roguism has left #ipfs [#ipfs]
OutBackDingo has joined #ipfs
jhulten has joined #ipfs
voxelot has quit [Ping timeout: 276 seconds]
fazo has joined #ipfs
fazo has quit [Changing host]
fazo has joined #ipfs
jhulten has quit [Ping timeout: 240 seconds]
fazo has quit [Client Quit]
davidar has quit [Ping timeout: 240 seconds]
tsenior has quit [Ping timeout: 260 seconds]
M-david has joined #ipfs
bsm1175321 has quit [Remote host closed the connection]
tinybike has joined #ipfs
tsenior has joined #ipfs
haadcode_ is now known as haadcode
tinybike has quit [Ping timeout: 276 seconds]
e-lima has quit [Ping timeout: 250 seconds]
ThomasWaldmann has quit [Ping timeout: 255 seconds]
ThomasWaldmann has joined #ipfs
forth_qc has quit [Quit: Lämnar]
tsenior has quit [Remote host closed the connection]
e-lima has joined #ipfs
tsenior has joined #ipfs
NightRa has joined #ipfs
wtbrk has joined #ipfs
amade has joined #ipfs
water_resistant has joined #ipfs
tsenior has quit [Read error: Connection reset by peer]
<dignifiedquire>
jbenet: richardlitt daviddias have you thought about setting up something like a discourse instance for a more focuesed communications platform with users? similar to https://forum.safenetwork.io/ and https://users.rust-lang.org/
ianopolous has quit [Ping timeout: 246 seconds]
Matoro has quit [Ping timeout: 240 seconds]
rombou has joined #ipfs
Matoro has joined #ipfs
s_kunk has quit [Ping timeout: 240 seconds]
hoony has joined #ipfs
ianopolous has joined #ipfs
voxelot has quit [Ping timeout: 250 seconds]
dignifiedquire has quit [Quit: dignifiedquire]
rombou has quit [Ping timeout: 276 seconds]
dignifiedquire has joined #ipfs
qgnox has quit [Ping timeout: 260 seconds]
kent_ has quit [Quit: kent_]
hoony has quit [Quit: hoony]
Matoro has quit [Ping timeout: 244 seconds]
Matoro has joined #ipfs
ygrek_ has joined #ipfs
chriscool has quit [Ping timeout: 246 seconds]
ianopolous has quit [Ping timeout: 272 seconds]
koo7 has quit [Ping timeout: 265 seconds]
chriscool has joined #ipfs
tinybike has joined #ipfs
<richardlitt>
dignifiedquire: I hadn't yet. Would be good at some point.
<richardlitt>
I'm not sure anyone's had issues finding us atm?
qgnox has joined #ipfs
chriscool has quit [Ping timeout: 250 seconds]
<ansuz>
<3 unknown unknowns
captain_morgan has joined #ipfs
<achin>
i'm sure there are people who would perfer a discourse forum over IRC
infinity0 has quit [Remote host closed the connection]
Matoro has quit [Ping timeout: 255 seconds]
infinity0 has joined #ipfs
HoboPrimate has joined #ipfs
<victorbjelkholm>
dignifiedquire +1 would be nice to have a discussion forum somewhere...
<victorbjelkholm>
richardlitt, would be good since now discussions are spread all over the place, sometimes without any sense
<richardlitt>
hmm.
<victorbjelkholm>
like we have ipfs/ipfs, ipfs/faq and ipfs/support which have kind of the same type of questions
<richardlitt>
And the google group, and IRC
<victorbjelkholm>
I didn't even know about the google group
<victorbjelkholm>
hah
<richardlitt>
Yeah.
<ansuz>
decentralized tech projects are hilarious for this kind of thing
<richardlitt>
Well, it's hard, because ipfs/ipfs has a specific function from Juan's perspective
<richardlitt>
and I'm not sure FAQ and support are the same.
chriscool has joined #ipfs
<victorbjelkholm>
richardlitt, I understand the difference between them. But I don't think people just finding out about IPFS does
<ogzy>
it wokerd when i try with different content
<ogzy>
achin: richardlitti am trying to understand what happens when i run publish
<pjz>
richardlitt: 'ipfs name publish' makes the specified reference show up if someone looks up /ipns/<your peerID>
<achin>
indeed, it seems to be working now
<achin>
it could be that the gateway nodes were just taking a while to resolve your ipfs name
<achin>
ipns name*
<ogzy>
pjz: how does this information spread between nodes?
<achin>
via the DHT
<pjz>
ogzy: what achin said
<pjz>
though IPNS names can also be published via DNS
Matoro has joined #ipfs
kent_ has joined #ipfs
infinity0 has quit [Ping timeout: 250 seconds]
jamie_k has joined #ipfs
<victorbjelkholm>
lgierth you mentioned you'll create issue about the pincoop things you guys mentioned yesterday, did you get to that?
<victorbjelkholm>
cannot find it
<dignifiedquire>
richardlitt: victorbjelkholm the issue is exactly this, too many places and especially people new to the people don’t have a single place to ask questions/check announcements/view already answered things
<pjz>
need like an ip{f,n}s stackoverflow
<dignifiedquire>
github is great for bugs, and irc is nice for chats but a forum is much better for proper community building
<victorbjelkholm>
maybe we should write a distributed forum on ipfs that collects all the question from different github repos :)
<victorbjelkholm>
one git repository = one forum section, everything is stored in ipfs
<richardlitt>
victorbjelkholm: I think that would work well.
<richardlitt>
dignifiedquire: I'm not sure that a forum would make there be less places, unless we shut down FAQ
<dignifiedquire>
which would be a great project, but I don’t think we should fall into the trap of trying to do everything at once and just use a working solution like discourse for now until we have something ready that is on par in terms of feature
cemerick has quit [Ping timeout: 240 seconds]
<victorbjelkholm>
pjz, stackoverflow would just be for q&a. What I think dignifiedquire (and me, in case he agrees) is after is a place where you can have discussions
<richardlitt>
support could be shut down; maybe we could just tag FAQ questions as 'support' questions instead
jamie_k has quit [Client Quit]
<victorbjelkholm>
jbenet, what terminal are you using normally?
<richardlitt>
Forums really aren't all that different than GitHub issues; the difference is that people aren't used to using GitHub issues as discussions
<victorbjelkholm>
richardlitt, well, a github issue gets completed at one point or another. forum threads tends to be locked because of breaking the rule, or live on forever
<richardlitt>
victorbjelkholm: No, that's just a convention for bugs. There's no reasons to complete a question issue
<dignifiedquire>
richardlitt: yes and no, it’s much easier in a forum to organize things, e.g. things like sticky topics at the top, subforums, tags etc
<richardlitt>
dignifiedquire: sticky topics is a good point, as are subforums and being able to add your own tags
<dignifiedquire>
also don’t underestimate the importance of using things people are already used to
<dignifiedquire>
it lowers the entry barrier, especially for non-tech people who are trying to get to know your project
<richardlitt>
dignifiedquire: agreed
<dignifiedquire>
we are used to using github day in and out, but a lot of people are not
<richardlitt>
I'm not actually advocating against one, I'm just leery of adding another venue to fix the "we have too many venues" problem
<ogzy>
pjz: and istead of using gateway.ipfs.ip/ipns, can it be also used a peer ip?
<richardlitt>
The best way to proceed here is to unironically open a GitHub issue about it on ipfs/community
<dignifiedquire>
if we do it, we should shutdown as much of the other venues and migrate them over
<richardlitt>
dignifiedquire victorbjelkholm would you like to do that?
<dignifiedquire>
:D
<richardlitt>
Well, we could shut down the google groups, FAQ, and Support.
<dignifiedquire>
sure I can create an issue, will paste the the irc chat in there
<richardlitt>
Cool.
pfraze has quit [Remote host closed the connection]
<victorbjelkholm>
makes sense. The more I think about it, the more I like the idea of having a forum frontend on top of github issues spread about repos. But that's probably a different discussion :D
pfraze has joined #ipfs
<richardlitt>
victorbjelkholm: well, we need to be careful not to extrapolate too far from GitHub
<richardlitt>
That's one of the issues with Trello ,Waffle, etc combined
pfraze has quit [Remote host closed the connection]
<victorbjelkholm>
richardlitt, no, sure, this is just my mind wondering about, not suggesting we actually build this for organizing the ipfs community
<victorbjelkholm>
we're on the same page :)
<achin>
one problem with the current github repos, is that the visiblity is pretty terrible
<dignifiedquire>
richardlitt Yeah that’s a start, but I didn’t even know it existed (docs is pretty misleading as a title)
<richardlitt>
achin: I can fix that. :)
<dignifiedquire>
(project in the navigation as well)
<pjz>
ogzy: when you enter httsp://gateway.ipfs.io/ipns/... into the browser, your browser hits that URL, which makes a request to its local ipfs daemon to fetch /ipns/... and return it to you over HTTP
<richardlitt>
achin dignifiedquire Added a note to make a PR to IPFS/IPFS with that list.
<dignifiedquire>
but that’s another discussion around the website which I don’t want to open right now
<pjz>
ogzy: if you have a local ipfs daemon running, you can get the same result by going to http://localhost:5001/ipns/...
<richardlitt>
I tried really hard to come at this as a new user, but I still have difficulties finding the gaps sometimes. thanks so much!
<richardlitt>
dignifiedquire: we're going to redo the website "at some point."
<dignifiedquire>
I bet you will, and if all goes well I can help with that :)
<pjz>
ogzy: note that 'fetch /ipns/...' checks a bunch of places: the dht, dns, etc.
<dignifiedquire>
but not today
<achin>
at the risk of complaining too much without offering suggestions, i will also mention that the current github repos can be confusion. it might not be clear if i should open a disucssion in the community repo, support repo, awesome-ipfs repo, archives repo, notes repo, or the apps repo :P
<richardlitt>
achin: It really depends on the discussion
<richardlitt>
Please feel free to ask me at any time, I should be able to help.
<dignifiedquire>
achin: that’s why I think a forum is so important, if it’s clear from the discussion that it will be an actionable item it can easily be migrated to a github issue on the right repo, but that way you don’t have to know which is the correct repo when starting the discussion
<richardlitt>
I can tell you what those are for, if you like.
<dignifiedquire>
richardlitt: but you explaining it to every person joinging the community doesn’t scale particulary well, does it ;)
<achin>
for sure. but if i want to start a discussion about an awesome app that i'm writing that will do something related to archives, where might i open a discussion thread?
<achin>
awesome-ipfs, archives, apps, or community might all be good fits
<richardlitt>
dignifiedquire: which is why I love questions like this. Becuase I can use them to figure out where I can explain this better so I don't have to, again
<victorbjelkholm>
awesome-ipfs for sure not, it's just a list. But yeah, I agree with your point. It's difficult
<richardlitt>
Doing something again and again, personally, is my best motivator to fix something
<richardlitt>
achin: Archives.
<richardlitt>
awesome-ipfs is for finished projects. community is for meta stuff
<dignifiedquire>
richardlitt: that’s true
<richardlitt>
achin: apps would also work. Good point. But Either of those is OK! We will redirect if needed
<richardlitt>
what this is telling me is that project-directory.md needs to be a) more public b) include more than just the repo description
<achin>
i don't think you can actually move issues
<richardlitt>
I should write up small paragraphs about what each repo is actually for
Encrypt has quit [Quit: Eating time!]
<richardlitt>
achin: we close and reopen often.
<richardlitt>
issues are cheap.
<dignifiedquire>
richardlitt: but on the other hand you are creating quite a lot of noise for people trying to follow the current stream of events if you close and reopen issues a lot
<richardlitt>
dignifiedquire: yes. I'm not happy with it, either.
<richardlitt>
the key is to never present a unified answer to any question, especially on IRC
<richardlitt>
Wait, no, I shouldn't have said that.
<richardlitt>
:D
<richardlitt>
at this point, a ipfs/meta repo for discussion might just cover everything.
<richardlitt>
But a forum would be better, maybe.
<dignifiedquire>
:D
<achin>
i'm not really sure what the solution is. i'm not really sure what the *problem* is
<achin>
but i am pretty sure we can do better, even if it's just an incremental improvement
roguism has quit [Ping timeout: 240 seconds]
<richardlitt>
achin: Well, incrementally, here's a way we can help: a) PR awesome-ipfs saying it is only for finished projects. b) PR ipfs/apps and ipfs/archives explaining in the README what they are for. Right now, those are vague. c) PR ipfs/community adding a note that this is only for meta non-code discussions d) PR ipfs/community explaining our Issue process. I
<richardlitt>
actually this last one on my todo list, sorta, this week
<richardlitt>
Do those sound good to you? If so, I'll do them all now.
<dignifiedquire>
for me the *problem* is that IPFS is in the beginning of generating a great community around it but it is a) very hard for people to find and enter at the “right” point b) even for people who are strongly involved in the project to keep an overview of all the exciting things happening
<achin>
yep, i think those would all be good ideas. and you're right: the fact that these are all repos means that the community can help improve and set direction
<richardlitt>
In the future, I think that cuts down on your one edge case. Yes, it's a lot of copy editing, but that's what I think I like doing, and it's something that would potentially make it easier. I think one of the issues is an idea of what 'issues' are, which doesn't gel with how the core IPFS team uses them, and an idea of repository monoculture, which is a
<richardlitt>
thing we don't subscribe to as a team
TheWhispery is now known as TheWhisper
<richardlitt>
dignifiedquire: I'm working on that. I think a blog would help a lot, and just better entry points. Maybe a 'So, you're new to IPFS?' document woudl be good
<richardlitt>
I would be 110% happy to help with writing that
<richardlitt>
another problem is that we are in fact fairly scattered, disorganized, and remote. That's the nature of the beast
roguism has joined #ipfs
<dignifiedquire>
exactly, that’s why we should try to use tools to help us organize things as good as we can
<richardlitt>
Just to be clear: I hear your confusion and completely understand you.
<dignifiedquire>
re doc, yes for sure
<richardlitt>
I think a forum might help
<dignifiedquire>
also it’s very easy to set up a discourse instance or there is even a hosted version, so we could always try it out and see how it goes
<richardlitt>
BUt I'm not sure another venue for talking is really the solution
<richardlitt>
We already don't fully engage with what we have
<richardlitt>
Look at the sync yesterday, for example. Everyone wandered away after an hour, although three people hadn't gone
<richardlitt>
They ended up updating a lonely IRC room. It was sad.
<ipfsbot>
[go-ipfs] whyrusleeping force-pushed fix/add-mem from df57ec3 to 5ccad84: http://git.io/v81Ov
<ipfsbot>
go-ipfs/fix/add-mem 5ccad84 Jeromy: rework editor creation and finalization...
<achin>
here's another incremental improvement: move the FAQ from ipfs/ipfs to ipfs/faq, and instead of including the answers inline, link to the issues
<richardlitt>
achin: !!! I should have caught that.
<achin>
(this would re-enforce the idea that users should get in the habbit of browing the issues of ipfs/faq for useful data)
<dignifiedquire>
true, but imagine the sync would happen in a forum directly (now that is a stretch maybe but stay with me) instead of the dual github/irc it wouldn’t matter how many people (except for those posting updates) take part, but everyone especially in different time zones has a very easy way of keeping up to date with the latest developments and who is doing what
<richardlitt>
Added to my list of things to do.
<richardlitt>
dignifiedquire: the issue isn't the tech, there, I think. It's the attention.
<richardlitt>
dignifiedquire: The only way I can think of for fixing that is kind of enforcing google hangouts so that people see each other, and/or incentivizing it better.
<dignifiedquire>
maybe, gotta go bring my son to bed now sorry
<richardlitt>
Humans are not good at synchronous talking to a screen. Humans, get with it.
<richardlitt>
dignifiedquire: no worries!
<richardlitt>
Gonna go to a new coffee shop // climbing gym. Will be on in a bit
<richardlitt>
thanks so much, achin dignifiedquire and victorbjelkholm
<achin>
thanks richardlitt
<richardlitt>
I want to start giving people bitcoin for talking about awesome stuff on here :/
<achin>
how about filecoin credits :P
<richardlitt>
haha
<richardlitt>
yep
<victorbjelkholm>
richardlitt, thank you for caring about those things :) Very valuable
<ogzy>
pjz: so the ipns is also distributed and each node has the information about a hash?
<achin>
not exactly. your node needs to remain online for other nodes to resolve your ipns name
<ogzy>
achin: for how long?
<achin>
forever. if your node is offline for more than 24 hours, the network forgets about your ipns name (anyone trying to resolve it will get an error)
<ogzy>
achin: what does other nodes get about my publish information?
joshbuddy has joined #ipfs
<pjz>
ogzy: just the name and the name of the block the name points to
<pjz>
ps: I'm working on a commercial pinning service, FWIW
<ogzy>
pjz: and what information does the block has?
<achin>
this is similar to content -- if you want to guarentee that the content remains available, you have to pin it and remain online. but the difference is: with content you can sometimes go offline if other nodes are pinning it. in ipns, only your node can publish your peerID
<pjz>
ogzy: the block has whatever you put in it via ipfs
<ogzy>
pjz: we are putting a peerid or hash there?
<ogzy>
pjz: oh ok my peerid is there
<pjz>
ogzy: a block is a hash, sorry, bad nomenclature on my part
<ogzy>
pjz: so a node is looking at the hash and learning my peerid?
<ogzy>
pjz: and then from dht my ip, is it what happens?
<pjz>
ogzy: ...no, a node looks at your peerid and finds the hash you published
<ogzy>
pjz: and that hash is the content
<achin>
i can't tell -- are you still talking about ipns? or ipfs content now?
<pjz>
ogzy: ipns is how you associate a static name (your PeerId) with different content (different hashes)
joshbuddy has quit [Quit: joshbuddy]
<pjz>
ogzy: so today if I do 'ipns publish QmAAAA..' then if you look up my PeerId (which doesn't change) you'll get QmAAAA...
<achin>
you'll get the String "QmAAAA"
<achin>
you'll not get the data (if there is any) assocaited with the hash QmAAAA
<pjz>
not from the ipns resolution, no
jamie_k_ has joined #ipfs
<achin>
right. it's worth being careful here, and not conflating two different operations
<pjz>
but the data is sometimes fetched transparently if you, for example, FUSE mount ipns space, and then do 'ls /ipns/<mypeerid>/'
<pjz>
that's got to not only resolve mypeerid into a hash, but also ipfs-fetch the hash and show it to me
<pjz>
right
<pjz>
though PeerIDs are not the only way to publish into IPNS
<achin>
at the moment, what else can you use?
<pjz>
put a hash in a text record in a DNS entry and /ipns/some.domain.com/ will resolve to the hash
<achin>
oh, true. i had considered that different from "ipns"
<achin>
but maybe that's just me
<pjz>
ipns is, in general, the mapping of names to IPFS hashes
<ogzy>
achin: pjz ok a bit confused, when i run ipfs name resolve mypeerid, it goes to a block and finds the hash, and by using this hash i can get the content?
<ogzy>
pjz: so this happens on the machine where publishes runs, for another node, the block is distributed? they have the same block also or they need my node to get the hash information?
<achin>
except be careful of the term "block" in this context
<ogzy>
achin: indeed dont know exactly what block is
<pjz>
ogzy: sorry, I didn't understand your question
<pjz>
victorbjelkholm: Very simple: pay the service to pin your data, at a specified $$/TB*h rate.
<ogzy>
pjz: you said i need to keep the node online, trying to understand the reason
<achin>
when data is stored in the ipfs DHT, it needs to be refreshed periodicly
<victorbjelkholm>
pjz, ah, very similar except pincoop would be free and a collaborative service and yours would involve money
<pjz>
ogzy: ah, right, if you use 'ipns publish' then that publishes _via the DHT_ so you have to stay online to keep your peerid published into the DHT
<pjz>
victorbjelkholm: sure. My target is some base reliable infrastructure so people can use IPFS for, say, backups, and not be worried that their data will disappear someday.
<victorbjelkholm>
same goal/target then as well, heh :)
<ogzy>
pjz: that sounds a bit wierd, the data doesn't need a node to be alive, i can add a content and can access it without running my node again right?
Matoro has quit [Ping timeout: 240 seconds]
<pjz>
ogzy: if someone else has pinned it
<ogzy>
pjz: ok
<achin>
this makes me realize that i don't actually know what other data is stored in the DHT
<pjz>
ogzy: data migrates between nodes, so if node A puts some data online and then node B requests it, now they both have copies... _and both will serve them out_.
<ogzy>
pjz: i had read the draft paper and trying to understand the worload of ipfs and ipns, is there anyother technical documents that i can follow?
<ogzy>
pjz: so this is pinning?
<roguism>
ogzy: ipfs is content-addressed (i.e. wikipedia article+version) whereas ipns is name-addressed (i.e. wikipedia article by name)
<pjz>
ogzy: no
<pjz>
ogzy: pinning comes in later, when node B, who was just looking at the data, doesn't need it anymore so garbage collects it. ('ipfs repo gc')
<pjz>
ogzy: node A, on the other hand, is the publisher of the data so wants it to stay around so has it 'pinned' - that is, it's flagged to _not_ be deleted by repo gc.
<pjz>
ogzy: it's possible for multiple people to pin the same block of data, thus giving it multiple permanent sources, as well as all the transient sources that result from people viewing it
jamie_k has joined #ipfs
<lgierth>
whyrusleeping: hrm again.
<lgierth>
should run it on a second host again
fiatjaf has joined #ipfs
pinbot has joined #ipfs
<fiatjaf>
`ipfs get` is stuck at 62.0 MB
<fiatjaf>
in my other machine it is stuck at 0 B
<fiatjaf>
ipfs get /ipfs/QmTQ4rYmHqDib2BpvxsT2rWZUFvbrXvCF5gPJnPJyFZp3w
jamie_k has quit [Ping timeout: 260 seconds]
TheWhisper has quit [Quit: Leaving]
<achin>
fiatjaf: that's a pretty big thing. 1.3GB total
TheWhisper has joined #ipfs
<fiatjaf>
achin: how do you know?
<achin>
ipfs object stat QmTQ4rYmHqDib2BpvxsT2rWZUFvbrXvCF5gPJnPJyFZp3w
<fiatjaf>
oh, thank you
<dignifiedquire>
richardlitt: do you know if there is a server I could use to setup a test install of discourse and who could give me access to it?
<fiatjaf>
achin but why I can't ipfs get it?
<richardlitt>
dignifiedquire: I do not know. Ask whyrusleeping about an IPFS server. I'd be interested in what you find.
<achin>
could be that the data just isn't available -- the node that was pinning it went offline
<achin>
or is having network connection issues
<dignifiedquire>
whyrusleeping: ping for infrastructure (server) questions/access
<ogzy>
pjz: to understand the details of DHT, should i check cademlia & coral?
<dignifiedquire>
richardlitt: also re earlier discussion, feel free to ask me if you need feedback on anything I’m still learning but very happy to give feedback and suggestions on anything “user” facing
<richardlitt>
dignifiedquire: Thanks! Same for me. I need to touch code more, I'm very code light right now due to lack of use
<fiatjaf>
also, I have tried from my home computer and from a VPS, my home computer stops the download at 62 MB, the VPS at 0 B.
<fiatjaf>
is this a bug?
<achin>
fiatjaf: do you see a directory listing?
<richardlitt>
dignifiedquire: normally I'm a front end dev / designer, too.
<dignifiedquire>
richardlitt: I always run to code when I’m struggeling with ui things, it’s like a save haven for me, where as doing design/ui/ux things is always much more putting yourself out there in the open
<fiatjaf>
achin: also, I can `ipfs ls` it
<achin>
fiatjaf: so while the hash for the top-level directory might be abailable, one of the chunks of data might be missing
<richardlitt>
dignifiedquire: I run to docs. Docs are safe. I understand docs. :P
<achin>
"ipfs get" will try to download everything, by recursively following each link
<fiatjaf>
achin: try clicking the links. it's a bunch of pdfs, they all seem to be there.
Matoro has joined #ipfs
<fiatjaf>
achin: if one is not, even then ipfs should download the available chunks for me, right?
<achin>
fiatjaf: i can't, it's not loading for me in my web browser
jamie_k has joined #ipfs
<fiatjaf>
that's strange.
<dignifiedquire>
richardlitt: it’s always good to have something one is comfortable with to relax :)
<fiatjaf>
why is loading here?
<victorbjelkholm>
lgierth, you saw my ping before?
<achin>
i just refreshed, and it's loading now
<lgierth>
victorbjelkholm: oh hey i only got to why's :P i refrained from it yesterday because i didn't wanna keep calling it openipfs, but also didn't wanna call it pincoop yet without your confirmation :P
<whyrusleeping>
dignifiedquire: whatsup?
<dignifiedquire>
whyrusleeping: trying to keep you busy ;)
<dignifiedquire>
whyrusleeping: we were talking about adding a forum earlier and I was wondering if we could setup a discourse instance for testing on the existing infrastructure from ipfs
<victorbjelkholm>
lgierth, no, was thinking about you mentioned that you would create issues about the things you were talking about yesterday
<dignifiedquire>
whyrusleeping: it’s all self contained in a docker container so it should not interfere with the rest of the system
<victorbjelkholm>
something about new architecture and things that I already thought about and wanted to share somewhere on the interwebz
<lgierth>
yeah doing that now! just didn't know what to call it yesterday :)
<whyrusleeping>
mmm, jbenet didnt like discourse last time it was suggested
<dignifiedquire>
do you remember why?
<lgierth>
dignifiedquire: woah gotta set up email for discourse? :(
<lgierth>
oh hey "No existing mail server?"
<lgierth>
kk
joshbuddy has joined #ipfs
<dignifiedquire>
lgierth: well you do want a way to send emails, but yes you don’t have to setup your own email server if you don’t want to
<lgierth>
yeah got it
<dignifiedquire>
whyrusleeping: main thing I’m interested to know is if he is against the use of a forum in general or if there is just something particular about discourse he doesn’t like
<pjz>
it's supposed to be a forum-like interface to github issues
<pjz>
anyone up to set it up to poke at?
<dignifiedquire>
I can try, I have a working ruby installation anyway
<dignifiedquire>
pjz: not looking good, native extension are failing to compile :(
<pjz>
dignifiedquire: ruby envs are such a pain :) ah well
<dignifiedquire>
pjz: don’t get me started ;)
jamie_k has quit [Quit: jamie_k]
qgnox has quit [Quit: WeeChat 1.3]
<dignifiedquire>
pjz: I’m afraid this is pretty pointless, just a simple clone of discourse, but just a lot less good and powered by github issues
G-Ray has joined #ipfs
<pjz>
dignifiedquire: fair enough; it was just something I stumbled across; the idea of an alternate interface to existing resources seemed better than adding yet another resource
<dignifiedquire>
pjz: sure, keep the ideas coming :)
Encrypt has joined #ipfs
mikee has joined #ipfs
<pjz>
dignifiedquire: go write a forum based on github issues!
grahamperrin has joined #ipfs
anticore has quit [Ping timeout: 276 seconds]
<ion>
. o O (A commercial pinning service could also keep your IPNS record alive.)
<pjz>
ion: yeah, I have plans for something along those lines, but I want to get the pinning service going first :)
roguism has quit [Ping timeout: 240 seconds]
<ipfsbot>
[go-ipfs] whyrusleeping force-pushed fix/add-mem from 5ccad84 to 4bbe1c0: http://git.io/v81Ov
<ipfsbot>
go-ipfs/fix/add-mem 4bbe1c0 Jeromy: rework editor creation and finalization...
<dignifiedquire>
pjz: if you invent a time machine and send it over sure :)
OutBackDingo has joined #ipfs
<ion>
G-Ray: What will be called libp2p will be separated from go-ipfs soon, most of your coffee should probably go into it. And you could collaborate with someone working on a Tor transport to prevent the daemon from leaking information between certain networks.
ygrek_ has quit [Ping timeout: 240 seconds]
ogzy has quit [Quit: Konversation terminated!]
<G-Ray>
ion: So I should wait before libp2p is out ?
arpu has quit [Ping timeout: 240 seconds]
cemerick has joined #ipfs
joshbuddy has joined #ipfs
<ion>
G-Ray: Not necessarily, but any work you do now will need some (likely small and mechanical) changes to fit the separated libp2p.
grahamperrin has left #ipfs ["Leaving"]
od1n has joined #ipfs
<ion>
G-Ray: It will also be good to consider whether you want to target go-ipfs master of dev0.4.0. whyrusleeping might have a good idea about that.
OutBackDingo has quit [Quit: Leaving]
OutBackDingo has joined #ipfs
Whispy has joined #ipfs
apophis has joined #ipfs
od1n has quit [Ping timeout: 252 seconds]
TheWhisper has quit [Ping timeout: 244 seconds]
Whispy is now known as TheWhisper
heterognath has joined #ipfs
anhydridize has joined #ipfs
corupay has joined #ipfs
reticulated has joined #ipfs
corupay has quit [Remote host closed the connection]
atrapado has quit [Quit: Leaving]
anhydridize has left #ipfs [#ipfs]
cemerick has quit [Ping timeout: 260 seconds]
disusered has joined #ipfs
anhydridize has joined #ipfs
jamie_k_ has quit [Quit: jamie_k_]
jamie_k has joined #ipfs
edsilv has joined #ipfs
edsilv has quit [Client Quit]
anhydridize has left #ipfs [#ipfs]
chriscool has quit [Ping timeout: 250 seconds]
e-lima has quit [Ping timeout: 250 seconds]
heterognath has left #ipfs [#ipfs]
chriscool has joined #ipfs
G-Ray has quit [Quit: Konversation terminated!]
apophis has quit [Ping timeout: 255 seconds]
ygrek_ has joined #ipfs
anticore has joined #ipfs
chriscool1 has joined #ipfs
chriscool has quit [Read error: Connection reset by peer]
apophis has joined #ipfs
<whyrusleeping>
0.4.0 will be soooon
voxelot has joined #ipfs
<NeoTeo>
\o/
<NeoTeo>
Will we need to migrate on this one?
<dignifiedquire>
whyrusleeping: stop teasing us :P
<ion>
whyruteasing
OutBackDingo has quit [Quit: Leaving]
<whyrusleeping>
yeah, that will be a migration
<whyrusleeping>
i'm rebasing it right now
<whyrusleeping>
then i need to integrate ipfs-update (which is code complete) into go-ipfs
<whyrusleeping>
release 0.3.10 with that change
<whyrusleeping>
and then 0.4.0 will be ready to merge
<lgierth>
:):)
disusered has quit [Ping timeout: 276 seconds]
<whyrusleeping>
trust me, i want this just as badly (lets be real, WAY MORE BADLY) as you guys to
<whyrusleeping>
do*
<dignifiedquire>
whyrusleeping: I bet you want it, working on a relase this size is building up
<dignifiedquire>
btw any time frame on 0.3.10 (need that patch you did for station)
Matoro has quit [Ping timeout: 240 seconds]
<whyrusleeping>
dignifiedquire: the plan is 0.3.10 ships by monday with or without ipfs-update
<whyrusleeping>
my job is to make sure ipfs update gets in that release
<dignifiedquire>
cool, then stop talking to me and get on it :)
<whyrusleeping>
lol
apophis has quit [Ping timeout: 250 seconds]
OutBackDingo has joined #ipfs
OutBackDingo has quit [Client Quit]
apophis has joined #ipfs
OutBackDingo has joined #ipfs
_disusered has joined #ipfs
anticore has quit [Ping timeout: 240 seconds]
OutBackDingo has quit [Quit: Leaving]
jamie_k has quit [Quit: jamie_k]
NeoTeo has quit [Quit: Teo is off. Bye :)]
<whyrusleeping>
i wish git rebase had a '--retry-this-one' option
<whyrusleeping>
to let me retry the merges i did on just one step
_disusered has quit [Ping timeout: 276 seconds]
<whyrusleeping>
i also wish abort had a way to not clear my git rerere cache...
NeoTeo has joined #ipfs
<ion>
Abort clears the rerere cache? Aww.
<whyrusleeping>
yeah
<whyrusleeping>
it sucks
<whyrusleeping>
was very upset when i decided to abort 50 commits into a rebase, and retry it
OutBackDingo has joined #ipfs
<whyrusleeping>
and i had to manually go through all that shit over again
<ion>
Ouch
jamie_k_ has joined #ipfs
pfraze has joined #ipfs
astrocyte has quit [Read error: Connection reset by peer]
noflag has quit [Quit: Leaving]
astrocyte has joined #ipfs
astrocyte has quit [Remote host closed the connection]
__konrad_ has quit [Ping timeout: 240 seconds]
OutBackDingo has quit [Quit: Leaving]
ianopolous has joined #ipfs
jadedfs has quit [Quit: Lost terminal]
OutBackDingo has joined #ipfs
chriscool1 has quit [Quit: Leaving.]
Encrypt has quit [Quit: Sleeping time!]
chriscool has joined #ipfs
<bergie>
hmm, seeing bunch of "bitswap: context deadline exceeded workers.go:92"