stebalien changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.4.18 and js-ipfs 0.33 are out! Get them from dist.ipfs.io and npm respectively! | Also: #libp2p #ipfs-cluster #filecoin #ipfs-dev | IPFS, the InterPlanetary FileSystem: https://github.com/ipfs/ipfs | Logs: https://view.matrix.org/room/!yhqiEdqNjyPbxtUjzm:matrix.org/ | Forums: https://discuss.ipfs.io | Code of Con
<ctOS>
Obo[m]1: I didn’t emailed you about the API timeout issues (as discussed on reddit) either, for the same reason.
<Obo[m]1>
No worries at all. I'm basically whitelisting all email addresses so this doesn't happen again
<ctOS>
Obo[m]1: you can often adjust the required spam score before messages are flagged as spam if you’re get false positives. assuming a competent email host, of course.
<Obo[m]1>
I just whitelisted everything
<Obo[m]1>
we don't get enough emails for it to matter
<Obo[m]1>
plus I'd rather not take the chance and ignore people that may want to reach out like yourself
<ctOS>
Obo[m]1: anyhow. any thoughts on a DNSLink mirroring service? (described a few messages ago)
<Obo[m]1>
admittedly this is probably an area that I could learn from you!
<Obo[m]1>
I haven't worked much with DNS link yet
<Obo[m]1>
This certainly does give me an excuse to link into it though
<ctOS>
Obo[m]1: run `dig TXT _dnslink.media.ctrl.blog.` you’ll get the TTL (cache time in seconds) and the IPFS object path. or `ipfs dns media.ctrl.blog` but that doesn’t give you the TTL.
<ctOS>
Obo[m]1: my ideal pinning service for use with websites would automatically recheck the domain when the TTL expires, and pin any new IPFS object
<Obo[m]1>
Hmm that sounds interesting
<Obo[m]1>
Let’s talk more tomorrow
<ctOS>
I’m fairly certain it would be your most popular product in no time.
<Obo[m]1>
It sounds like a pretty good use case
<Obo[m]1>
I’ll hit you up tomorrow. Unfortunately I have to head out for the night.
Papa_Alpaka has quit [Quit: Going offline, see ya! (www.adiirc.com)]
therecluse26 has joined #ipfs
jhulten has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mateusbs17 is now known as mateusbs17|afk
mischat has quit [Remote host closed the connection]
purisame has quit [Ping timeout: 258 seconds]
dsiypl4 has quit [Ping timeout: 268 seconds]
jhulten has joined #ipfs
<postables[m]>
@ctOS: is the TTL for `_dnslink.media.ctrl.blog` 999seconds/16.65minutes?
<postables[m]>
want to make sure im parsing correctly before i do anything else
<ctOS>
postables[m]: it’s set to 1000 seconds, but an intermediary DNS cache will reduce the TTL for every second they’ve cached it
<ctOS>
postables[m]: run `dig TXT _dnslink.media.ctrl.blog @1.1.1.1` wait 5 seconds, and run it again.
<ctOS>
(you may not hit the exact same Cloudflare DNS server so you may need to run it more than twice to see the caching in effect)
<postables[m]>
ah yes i see
<ctOS>
postables[m]: you can charge customers 5 cent per 1000 checks/month (counted across all mirrored domains) to discourage super-low TTLs. You really don’t want to set super low TTLs for performance reasons.
<postables[m]>
my DC uses its own caching DNS servers, I'm tossed between just running it against my dns servers, or pointing to a standard one like clouflare or google
jesse22 has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<ctOS>
postables[m]: DNS is designed to be decentralized. Run it against whatever recursive DNS provider you want. It may be an idea to enable DNSSEC validation (my domain is signed if you need a test domain) and setup DNS over TLS, however. (Offered by Quad9.net, Cloudflare-DNS.com, and DNS.Google.) That will help ensure websites/IPFS pins won’t get hijacked. systemd-resolved supports both if you need something that's super-easy to
<ctOS>
setup.
<postables[m]>
already have DDNSSec enabled 😜
<postables[m]>
was the first thing i did spinning up this dns server
<ctOS>
postables[m]: do you allow downgrades if validation fails? if so then not enabled.
<ctOS>
postables[m]: ps: all my servers are setup with quad9, cloudflare dns, and google dns. queries are randomly sent to recursive providers and forwarded to another if it fails. it's pretty much as redundant as it can be.
<ctOS>
pradhanphy[m]: when it comes to dns privacy, the best you can do is to spread your queries out on as many recursive providers as possible. that way, no single one will know all the domains you visit. kind of the same privacy you can expect with IPFS, come to think of it.
<postables[m]>
i've been considering moving to BIND but I really don't want to deal with th eheadache of managing a BIND server, did that once in college and it was a PITA
<postables[m]>
i''ve got an experimental side project for IPFS that I work on every once in awhile, trying to set up a sort of federated-authoritative IPNS server system
<ctOS>
postables[m]: anyhow, for the purpose of a DNSLink mirror service it doesn’t matter which recursive provider you use.
<ctOS>
You can resolve and cache against the root servers if that makes you happy. :P
<ctOS>
postables[m]: oh, and IPFS supports having DNSLink information on the domain without using the dedicated subdomain. <insert the Dat protocol discussion on why that is a bad idea here> You may want to support it if only to detect it and discourage its use.
<postables[m]>
😂 yea i've got a 2 part processing step to detect that, and detect valid ones
<postables[m]>
well im gonna go grab some food, when im back shouldn't take long to finish this up and i'll run a test.
jhulten has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
daMaestro has joined #ipfs
lidel` has joined #ipfs
lidel has quit [Ping timeout: 240 seconds]
lidel` is now known as lidel
clemo has quit [Ping timeout: 250 seconds]
aldenp has quit [Quit: Leaving]
therecluse26 has quit [Ping timeout: 258 seconds]
grahambell has joined #ipfs
purisame has joined #ipfs
eof has quit [Ping timeout: 246 seconds]
hexfive has quit [Quit: WeeChat 2.3]
eof has joined #ipfs
therecluse26 has joined #ipfs
q6AA4FD has quit [Ping timeout: 246 seconds]
grahambell has quit [Quit: Page closed]
spinza has quit [Quit: Coyote finally caught up with me...]
q6AA4FD has joined #ipfs
spinza has joined #ipfs
laughingBull has joined #ipfs
IRCsum has quit [Ping timeout: 264 seconds]
}ls{ has quit [Ping timeout: 258 seconds]
Algonkian has quit [Ping timeout: 244 seconds]
}ls{ has joined #ipfs
thomasan_ has joined #ipfs
necolo has joined #ipfs
thomasan_ has quit [Remote host closed the connection]
IRCsum has joined #ipfs
laughingBull has quit [Quit: WeeChat 1.4]
thomasan_ has joined #ipfs
thomasan_ has quit [Remote host closed the connection]
ONI_Ghost has joined #ipfs
daMaestro has quit [Quit: Leaving]
harpula has joined #ipfs
thomasan_ has joined #ipfs
necoloXD has joined #ipfs
lassulus_ has joined #ipfs
<necoloXD>
Hello! I have problems with ipfs.
craigo has joined #ipfs
lassulus has quit [Ping timeout: 240 seconds]
lassulus_ is now known as lassulus
<necoloXD>
I wanna to copy the data from ubuntu system to another machine, I've tried to copy the whole data in blocks and datastore folder and paste, but I still cannot get any data.
thomasan_ has quit [Remote host closed the connection]
necolo has quit [Ping timeout: 256 seconds]
zeden has quit [Quit: WeeChat 2.3]
gelmutshmidt has quit [Remote host closed the connection]
<deltab>
necoloXD: what happens when you try?
<necoloXD>
cannot get any blocks
Belkaar has quit [Read error: Connection reset by peer]
Belkaar has joined #ipfs
Belkaar has joined #ipfs
<deltab>
necoloXD: what do you mean by paste?
kapil____ has joined #ipfs
<necoloXD>
tar the datastore and blocks folder and transfer it to the target machine, untar and mv and replace in target machine's ipfs folder.
<necoloXD>
totally replace them
<ctOS>
necoloXD: you mean to say you’re litterally trying to copy ~/.ipfs from one machine to another?
<ctOS>
Make sure you exit IPFS on both systems before you do this. It can’t be running.
<ctOS>
necoloXD: you can transfer pinned data over IPFS itself too: ssh your-user@remote-machine -C "ipfs pin ls -t recursive -q" | xargs -I% ipfs pin add %
<ctOS>
necoloXD: gets the list of pinned resources on the remote systems and pins them locally
<necoloXD>
ctsOS: cool. I've tried stop IPFS and do it again, now I could get the data with 'ipfs block get'
<postables[m]>
@ctOS: got my first prototype for this dlink mirroring stuff running for `media.ctrl.blog`
<ctOS>
postables[m]: cool!
<ctOS>
postables[m]: blog.ipfs.io updates weekly, so another good test domain.
<postables[m]>
not sure how to best test this.... i guess you could like make some changes or whatever, and send me the hashes that were previously in your ttl records and i cna verify they were pinned? i guess before i started this i probably should've added a print statement saying its pinning
<postables[m]>
*edit:* ~~not sure how to best test this.... i guess you could like make some changes or whatever, and send me the hashes that were previously in your ttl records and i cna verify they were pinned? i guess before i started this i probably should've added a print statement saying its pinning~~ -> not sure how to best test this.... i guess you could like make some changes or whatever, and send me the hashes that were
<postables[m]>
previously in your ttl records and i cna verify they were pinned? i guess before i started this i probably should've added a print statement saying its pinning lol
<postables[m]>
ah yes blog.ipfs.io good choice
<ctOS>
postables[m]: media.ctrl.blog usually updates two--three times a week
<postables[m]>
cool i'll just add some print statements then lol
<ctOS>
postables[m]: the feature is useless without deduplicated storage accounting, though.
<ctOS>
Well, not useless but too pricey.
<postables[m]>
good thing i already put deduplicated storage in my backend 😉
<postables[m]>
well its in a branch not yet merged into code-base need to run some more tests first
<postables[m]>
but yea it would be pretty pricey without it
<ctOS>
Well, keep pinning stuff from the DNSLink mirrors. Do it with separate test accounts for each domain. Make sure to preserve all pins and gather some data about the pre and post deduplication storage requirements and associated costs.
<ctOS>
Great marketing material/blog post right there.
<postables[m]>
haha we are quite there yet, need to make sure prototype works, once confirmed refine to handle multiple domains simultaneously, then integrate the billing aspect
<postables[m]>
*edit:* ~~haha we are quite there yet, need to make sure prototype works, once confirmed refine to handle multiple domains simultaneously, then integrate the billing aspect~~ -> haha we aren't quite there yet, need to make sure prototype works, once confirmed refine to handle multiple domains simultaneously, then integrate the billing aspect
mikolalysenko has joined #ipfs
<ctOS>
postables[m]: and do share some implementation notes with the community, will you?
<postables[m]>
once its done 😃
<ctOS>
Great
* ctOS
is off to bed -- g'night all, and thanks for all the good discussions
<postables[m]>
night!
Mateon1 has quit [Remote host closed the connection]
Mateon1 has joined #ipfs
blallo has quit [Remote host closed the connection]
appa has quit [Ping timeout: 258 seconds]
appa has joined #ipfs
blallo has joined #ipfs
_whitelogger has joined #ipfs
}ls{ has quit [Quit: real life interrupt]
dimitarvp has joined #ipfs
zane has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Pulse2496 has joined #ipfs
hexfive has joined #ipfs
kapil____ has quit [Quit: Connection closed for inactivity]
seba- has quit [Ping timeout: 250 seconds]
ikari` has joined #ipfs
TimMc has quit [Ping timeout: 240 seconds]
TimMc has joined #ipfs
rendar has joined #ipfs
DrFelder has joined #ipfs
dimitarvp has quit [Read error: Connection reset by peer]
dimitarvp has joined #ipfs
ylp has joined #ipfs
BeerHall has joined #ipfs
clemo has joined #ipfs
Mottengrotte has joined #ipfs
toxync01- has quit [Ping timeout: 250 seconds]
toxync01 has joined #ipfs
seba- has joined #ipfs
inetic has joined #ipfs
vyzo has quit [Quit: Leaving.]
vyzo has joined #ipfs
<DrFelder>
Hey, maybe somebody can help me: I added and pinned a file, and tried to access it through a gateway, but the connection just times out. Am I doing something wrong?
harpula has quit [Ping timeout: 252 seconds]
MrSparkle has quit [Ping timeout: 250 seconds]
user_51 has joined #ipfs
MrSparkle has joined #ipfs
user_51 has quit [Ping timeout: 268 seconds]
ONI_Ghost has quit [Read error: Connection reset by peer]
ONI_Ghost has joined #ipfs
Kamilion has quit [Remote host closed the connection]
user_51 has joined #ipfs
Kamilion has joined #ipfs
user_51 has quit [Ping timeout: 258 seconds]
<shoku[m]>
Often it takes the gateway a while to find your content
user_51 has joined #ipfs
hexfive has quit [Quit: WeeChat 2.3]
bifilarcoil[m] has joined #ipfs
<DrFelder>
How long does it normally take the gateway? An hour or so? What is your experience?
chiui has joined #ipfs
clemo has quit [Ping timeout: 258 seconds]
Caterpillar has joined #ipfs
nonono has joined #ipfs
spinza has quit [Quit: Coyote finally caught up with me...]
spinza has joined #ipfs
zeden has joined #ipfs
gritzko has quit [Ping timeout: 258 seconds]
vmx has joined #ipfs
<hsanjuan>
DrFelder: it should be pretty quick, but right now there are apparently some bugs which have degraded discoverability. There are a bunch of people working on this and I think we're going to see improvements quite soon
gritzko has joined #ipfs
therecluse26 has quit [Ping timeout: 268 seconds]
peterix has quit [Ping timeout: 244 seconds]
gritzko has quit [Ping timeout: 244 seconds]
peterix has joined #ipfs
ctOS has quit [Quit: Connection closed for inactivity]
Mottengrotte has quit [Read error: Connection reset by peer]
malaclyps has quit [Read error: Connection reset by peer]
mischat has joined #ipfs
malaclyps has joined #ipfs
mischat has quit [Ping timeout: 252 seconds]
<DrFelder>
seba-: After trying a few things, I think part of my current issues are network problems. I can retrieve files, but i can't "publish" anything. I will look into it.
<seba->
DrFelder read my experiments
<seba->
we can test together if you want
<seba->
^.^
<DrFelder>
seba-: I did
vmx has quit [Ping timeout: 246 seconds]
<seba->
DrFelder, can you tell me your peer ID?
Fessus has quit [Remote host closed the connection]
polman has quit [Ping timeout: 246 seconds]
BeerHall has quit [Read error: Connection reset by peer]
Fessus has joined #ipfs
polman has joined #ipfs
BeerHall has joined #ipfs
spinza has quit [Quit: Coyote finally caught up with me...]
aldenp has joined #ipfs
vmx has joined #ipfs
Pulse2496 has quit [Ping timeout: 246 seconds]
craigo has quit [Ping timeout: 252 seconds]
therecluse26 has joined #ipfs
dsiypl4 has quit [Ping timeout: 268 seconds]
Mottengrotte_ has quit [Read error: Connection reset by peer]
<whyrusleeping>
but tldr; libp2p ping is: send 32 bytes, read the same 32 bytes back, repeat as many times as you like
<seba->
ok
<seba->
but how do i negotiate and all that
<seba->
like if i telnet on 4001
<seba->
i get /multistream/1.0.0
<seba->
what do i respond
<whyrusleeping>
Ah, yeah. Thats why I wrote that libp2p in lua
vmx has quit [Remote host closed the connection]
<seba->
etc etc.
vyzo has quit [Quit: Leaving.]
<seba->
just approx. tell me
<whyrusleeping>
read through my readme there, its a good start
<seba->
i'll read the code
<seba->
yes i did that
<seba->
but just how it looks like for example
<seba->
just to get a quick feel
<whyrusleeping>
yeah, so you would send back that multistream string
vyzo has joined #ipfs
<seba->
so i send back /multistream/1.0.0
<whyrusleeping>
then you would send /plaintext/1.0.0\n
<whyrusleeping>
you need to length prefix it, which is hard to do via telnet
<seba->
ok that's to ignore encryption
<seba->
ok
<whyrusleeping>
yeah, that ignores encryption
<whyrusleeping>
then you need to negotiate the stream multiplexer
<seba->
so how do i length prefix? is that just a binary byte or smallint?
<whyrusleeping>
yeah, its a binary varint that represents the length of the string you are sending
<seba->
ok
<seba->
ok so varint first and then just "normal text"
<seba->
gotcha
<seba->
and then?
<seba->
how does the negotiation look like for stream multiplexer
<seba->
if i want to just do ping
<seba->
[thanks for the code thou, that's what i was kinda looking for]
<whyrusleeping>
I've wanted to have a 'single stream' mode, but we don't have that in ipfs right now, so you have to now speak the stream multiplexer protocol
<seba->
i mean is IPFS just special implementation of libp2p?
<seba->
how do they differ
<aschmahmann[m]>
libp2p is a p2p/networking stack. IPFS uses that stack to do other things (like distributing files)
<seba->
ok so libp2p is routing
<seba->
and peer discovery
rendar has quit []
jhulten has joined #ipfs
<aschmahmann[m]>
It's very modular and has a lot of components. I'd check out https://github.com/libp2p/go-libp2p and look at the dependencies to get a general idea
<aschmahmann[m]>
they are even divided up into categories to make scanning the components easier
jhulten has quit [Client Quit]
jonathan[m]1 has joined #ipfs
<aschmahmann[m]>
Similarly looking at the dependencies of https://github.com/ipfs/go-ipfs gives a pretty good idea of what IPFS is about
purisame has quit [Ping timeout: 245 seconds]
purisame has joined #ipfs
DrFelder has joined #ipfs
DrFelder has quit [Client Quit]
purisame has quit [Ping timeout: 245 seconds]
jhulten has joined #ipfs
ygrek has quit [Remote host closed the connection]
<seba->
well i hope i'll manage to implement my own version of ping
<seba->
^.^
ygrek has joined #ipfs
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
zane has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jhulten has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
maxzor has joined #ipfs
<postables[m]>
seba~: libp2p is networking so that covers routing peer discovery pubsub etc...
<postables[m]>
mgoelzer linked to me a really good video in the libp2p chat the other day definitely recommend watching it
<Obo[m]1>
was it the one where he's speaking at web3 summit?
<postables[m]>
Yes
<Obo[m]1>
yeah that was a great talk
<Obo[m]1>
I'm excited to see how libp2p progresses outside of just IPFS
ctOS has left #ipfs [#ipfs]
ctOS has joined #ipfs
<postables[m]>
Same, it's a lot of fun to work with
florianH_ has quit [Quit: Connection closed for inactivity]
purisame has joined #ipfs
jhulten has joined #ipfs
tombusby has quit [Remote host closed the connection]
tombusby has joined #ipfs
aldenp has joined #ipfs
jesse22 has joined #ipfs
jhulten has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
maxzor has quit [Ping timeout: 258 seconds]
maxzor has joined #ipfs
clemo has quit [Ping timeout: 268 seconds]
jesse22_ has joined #ipfs
jesse22 has quit [Ping timeout: 272 seconds]
jesse22_ has quit [Read error: Connection reset by peer]
jesse22 has joined #ipfs
MrSparkle has quit [Ping timeout: 246 seconds]
MrSparkle has joined #ipfs
jhulten has joined #ipfs
hurikhan77 has quit [Ping timeout: 252 seconds]
clemo has joined #ipfs
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
maxzor has quit [Remote host closed the connection]
zane has joined #ipfs
maxzor has joined #ipfs
jesse22_ has joined #ipfs
jesse22 has quit [Ping timeout: 268 seconds]
stoopkid has quit [Quit: Connection closed for inactivity]
hurikhan77 has joined #ipfs
zeden has quit [Quit: WeeChat 2.3]
stoopkid has joined #ipfs
zane has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<ctOS>
postables[m]: any progress on mirroring? :)
<postables[m]>
@ctOS: yea the code ran well had to cut it short last night though as we started our production hardware cut over a bit earlier
<postables[m]>
But Ive been sketching out a way to handle multiple domains at once and will probably mock that up tonight while I'm formatting abunch of disks
<postables[m]>
One issue I had though was it took a long time to find the CID your dnslink resolved to but I think that was because I had pointed my test code against a test IPFS docker container
zdub3[m] has left #ipfs ["User left"]
<ctOS>
postables[m]: I had a look now and found 20+ nodes with the current CID, so probably on your end
spinza has quit [Quit: Coyote finally caught up with me...]
<postables[m]>
I'm unsure how to handle cases were someone may pass on a non `_dnslink` record since it doesn't appear that the `go-ipfs/namesys` package resolves that. so basically for non `_dnslink` records I'm thinking giving that to the namesys package, and resolving. If they are using `_dnslink` then I extract the IPNS entry to resolve or the IPFS hash to pin as I'm getting the TTL.
<postables[m]>
Sleep/wait for the TTL to pass, then I trigger a pin, recheck TTL sleep/wait for that and rinse and repeat
<postables[m]>
@ctOS: Yea it was working fine when I ran the test on my actual node, most likely means I need to make some changes to the test environment we spin up in docker
<ctOS>
postables[m]: what do you mean a "non _dnslink" record? There can be any number of TXT records on the bare domain or on the special sub domain.
abaiste has quit [Read error: Connection reset by peer]
mindCrime has quit [Ping timeout: 245 seconds]
abaiste has joined #ipfs
abaiste has quit [Max SendQ exceeded]
rtjure has quit [Ping timeout: 268 seconds]
<ctOS>
postables[m]: you can probably optimize by recording the previously pinned CID so you don't have to wait for IPFS to pin something that is already pinned in the account
<ctOS>
postables[m]: oh, keep in mind that some DNSLink domains may return dnslink=/ipns/have-fun-with-that :P
<ctOS>
At which point you'd have to resolve the IPNS name to get the current IPFS CID
<ctOS>
postables[m]: which is why I suggested you create an IPNS Mirror and DNSLink mirroring services at the same time. I may have forgotten to mention that reasoning, however. Not of interest to me personally, but I guess some sites use it like that.
<ctOS>
postables[m]: if the ipns is a domain instead of a hash, you can reuse what you've already built to resolve that DNSLink domain name
rtjure has joined #ipfs
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
zane has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
i1nfusion has quit [Remote host closed the connection]
ygrek has quit [Ping timeout: 246 seconds]
i1nfusion has joined #ipfs
zane has joined #ipfs
abaiste has joined #ipfs
abaiste has quit [Max SendQ exceeded]
<postables[m]>
@ctOS: I already check for that if it's an IPNS link I resolve it first 😋
<postables[m]>
But what do you mean `if IPNS is a domain instead of a hash`?? Like `dnslink=media.ctrl.blog`?
<postables[m]>
Cause if that's what you mean than I'm definitely not doing that. I basically check if it's `/ipfs` or `/ipns`. If it's ipfs I go straight to pin if it's ipns I resolve first then pin
<ctOS>
postables[m]: no, I mean that an IPNS can be a domain name. E.g. _dnslink.example.com can return dnslink=/ipns/ipfs.example.com
random_yanek has quit [Read error: No route to host]
<postables[m]>
Ohhhh okay, Hmm I'll have to double check because I use `go-ipfs-api.shell.Resolve` so I'm not sure if that already is capable of resolving a domain name IPNS link or just a hash IPNS link
random_yanek has joined #ipfs
<ctOS>
postables[m]: actually you can test with "ipfs.io" itself
doomdiee1 has joined #ipfs
jesse22_ has quit [Remote host closed the connection]
jesse22 has joined #ipfs
doomdiee1 has quit [Client Quit]
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
mischat has joined #ipfs
<postables[m]>
Oh cool I'll do that
purisame has joined #ipfs
discopatrick has joined #ipfs
jhulten has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]