stebalien changed the topic of #ipfs to: Heads Up: To talk, you need to register your nick! Announcements: go-ipfs 0.4.19 and js-ipfs 0.34 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
<ylp>
maybe your node is not allowed to connect to the internet ?
<ylp>
firewall etc...
<alexanarcho>
Yes, that may be the case
<alexanarcho>
Well - any idea how to change it? I m on a Mac
<ylp>
no idea
<ylp>
maybe move the binary out of quarantine ?
<alexanarcho>
Haha :D okay I see I have some more digging to do
<alexanarcho>
Anyway, thanks for the help. I ll lurk around - if anybody has experience with this feel free to tag me
<alexanarcho>
Oh, just one more question: Can I use IPFS in the browser or do I have to use it in the command line? I saw a video, where the girl typed in the address in the browser bar
<ylp>
I'm using linux...
litvintech has joined #ipfs
<ylp>
you can use ipfs compagnon
<ylp>
it will remplace public gateway with your local gateway
<ylp>
it can be also useful to see stats on your node
merethan has joined #ipfs
dethos has joined #ipfs
manray has quit [Ping timeout: 250 seconds]
gmoro has joined #ipfs
spinza has joined #ipfs
The_8472 has quit [Ping timeout: 252 seconds]
The_8472 has joined #ipfs
manray has joined #ipfs
Administrator_00 has joined #ipfs
szcc007 has quit [Ping timeout: 272 seconds]
joocain2_ has joined #ipfs
aarshkshah1992 has quit [Remote host closed the connection]
joocain2 has quit [Ping timeout: 256 seconds]
aarshkshah1992 has joined #ipfs
litvintech has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Fessus has quit [Remote host closed the connection]
Fessus_ has joined #ipfs
pecastro has joined #ipfs
The_8472 has quit [Ping timeout: 240 seconds]
Fessus_ has quit [Remote host closed the connection]
The_8472 has joined #ipfs
Fessus_ has joined #ipfs
Ai9zO5AP has quit [Ping timeout: 250 seconds]
rendar has joined #ipfs
alexanarcho_ has joined #ipfs
alexanarcho has quit [Ping timeout: 246 seconds]
BeerHall has quit [Ping timeout: 255 seconds]
BeerHall has joined #ipfs
BeerHall has quit [Client Quit]
joocain2 has joined #ipfs
Caterpillar has quit [Quit: You were not made to live as brutes, but to follow virtue and knowledge.]
joocain2_ has quit [Remote host closed the connection]
}ls{ has joined #ipfs
Ai9zO5AP has joined #ipfs
Caterpillar has joined #ipfs
spinza has quit [Quit: Coyote finally caught up with me...]
alexanarcho__ has joined #ipfs
alexanarcho_ has quit [Read error: Connection reset by peer]
kapil____ has quit [Quit: Connection closed for inactivity]
Caterpillar has quit [Quit: You were not made to live as brutes, but to follow virtue and knowledge.]
Caterpillar has joined #ipfs
Caterpillar has quit [Client Quit]
alexanarcho__ has quit [Quit: Leaving]
alexanarcho has joined #ipfs
Caterpillar has joined #ipfs
spinza has joined #ipfs
The_8472 has quit [Ping timeout: 252 seconds]
merethan has quit [Remote host closed the connection]
<alexanarcho>
Cool, seems like I uploaded my first image - anybody care to check Qmf4tmjrD84VCWnGwrK4BecPDTdy2ZamQUqSbZL18cHxdx
aarshkshah1992 has quit [Remote host closed the connection]
The_8472 has joined #ipfs
<ylp>
alexanarcho: it works
<alexanarcho>
yeehaa
ZaZ has joined #ipfs
malaclyps has quit [Read error: Connection reset by peer]
malaclyps has joined #ipfs
ec has quit [Ping timeout: 258 seconds]
joocain2_ has joined #ipfs
alexanarcho has quit [Ping timeout: 255 seconds]
ec has joined #ipfs
joocain2 has quit [Ping timeout: 256 seconds]
pecastro has quit [Ping timeout: 250 seconds]
Tiez has quit [Quit: WeeChat 2.4]
cyfex has quit [Quit: WeeChat 2.2]
vmx has joined #ipfs
Administrator_00 has quit [Ping timeout: 268 seconds]
Tiez has joined #ipfs
pecastro has joined #ipfs
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
<lordcirth_>
Weird, IPFS has been running for ages but for some reason it has 4 peers right now?
<lordcirth_>
Hmm, it was using a ton of RAM for doing nothing, restarted it, now it's got 186 peers and climbing. I think there's a memory leak.
appa_ has quit [Ping timeout: 250 seconds]
gmoro has quit [Remote host closed the connection]
gmoro has joined #ipfs
appa_ has joined #ipfs
The_8472 has quit [Ping timeout: 240 seconds]
Pulse2496 has joined #ipfs
Jonathank[m]1 is now known as kiwi_uk[m]
The_8472 has joined #ipfs
joocain2 has joined #ipfs
joocain2_ has quit [Ping timeout: 256 seconds]
alexanarcho has joined #ipfs
zeden has joined #ipfs
zeden has quit [Quit: WeeChat 2.4]
yoongster[m] has joined #ipfs
gde33 has quit [Ping timeout: 246 seconds]
ZaZ has quit [Read error: Connection reset by peer]
mdrights has joined #ipfs
joocain2_ has joined #ipfs
redfish has quit [Remote host closed the connection]
<Bl4ckC0r3>
ofcourse my next closest peer to me is in USA and I am far away in Europe
<Bl4ckC0r3>
china next peer, after china is mars i mean planet mars
joocain2 has joined #ipfs
alexanarcho_ has joined #ipfs
alexanarcho has quit [Ping timeout: 250 seconds]
<TimMc>
Yeah, so there's that, but like I said you also have to consider that only one other node in the network may currently be online and have that file, and *their* connection may be slow.
joocain2_ has quit [Ping timeout: 256 seconds]
zane has joined #ipfs
manray has quit [Ping timeout: 250 seconds]
<Bl4ckC0r3>
ok
philipp[m] has joined #ipfs
manray has joined #ipfs
renich_ has joined #ipfs
renich has quit [Ping timeout: 255 seconds]
arthuredelstein has quit [Ping timeout: 268 seconds]
astrofog has quit [Remote host closed the connection]
arthuredelstein has joined #ipfs
detran has joined #ipfs
joocain2_ has joined #ipfs
joocain2 has quit [Remote host closed the connection]
quijote has joined #ipfs
spinza has quit [Quit: Coyote finally caught up with me...]
kmal has joined #ipfs
kmal has quit [Client Quit]
ylp has joined #ipfs
kmal has joined #ipfs
kmal has quit [Client Quit]
htc^ has joined #ipfs
PotatoPro has joined #ipfs
kmal has joined #ipfs
yatsukino[m] has joined #ipfs
kmal has quit [Quit: leaving]
b7219264 has quit [Quit: Leaving]
b7219264 has joined #ipfs
__jrjsmrtn__ has joined #ipfs
kmal has joined #ipfs
<philipp[m]>
As per default configuration I'm only serving files that I have actively fetched beforehand, right? I just started reading about ipfs and still figuring out how everything works.
spinza has joined #ipfs
cocooncrash[m] has joined #ipfs
xelra_ is now known as xelra
<ylp>
philipp[m]: yes
Wioxjk has joined #ipfs
kmal has quit [Quit: Leaving]
kmal has joined #ipfs
kmal has quit [Client Quit]
kmal has joined #ipfs
The_8472 has quit [Ping timeout: 240 seconds]
<detran>
Is there a way for multiple servers to udpate the same ipns pointer?
<kmal>
detran: Assuming I'm thinking about it correctly, you're correct: you wouldn't be able to revoke and keep the same namespace.
joocain2_ has quit [Ping timeout: 256 seconds]
<detran>
Which means you can't authorize some other server to make updates to your namespace and then later rescind that access.
<detran>
Just thinking out loud.
<kmal>
Ah, I see. Yeah, doesn't seem like that would work -- cool idea though!
<detran>
Thanks! I was hoping to use as way to do account migration from one service to another and keep the same username/id (ipns address).
<kmal>
Account migration? Hmm... Out of curiosity, do you know of any services that use ipns addresses as usernames that currently exist?
<kmal>
Sounds like there are some cool applications for that -- I just can't think of any at the moment.
<detran>
Nope. Just an idea I was playing with - when you register with the service they would write your account data to ipfs and then update your ipns to point to it. And if you wanted to migrate to another provider of that service you would just register your name (ipns address) with the new service and revoke the old service's private key
<detran>
You could break the private key into 3 pieces and store one publicly under your ipns, one privately under your ipns, and give one share to the service. Since you can reconstruct the private key with 2 out of the three pieces, the service would be able to post using your public piece and it's own piece, but you could revoke using your private piece and the public piece.
<detran>
But, ipfs being immutable, the service could still use your old pieces to recreate the private key
<detran>
Or, if it was malicious, just reconstruct the private key and store it.
Stenstad[m] has left #ipfs ["User left"]
ylp has quit [Quit: Leaving.]
<kmal>
Probably.. (ominous music) That sounds like a really cool idea. As for multiple servers updating the same pointer -- it seems like it would be easier to keep control over your address, and have the service generate the ipfs data but you run the command to update your ipns address. That wouldn't be as user friendly though, and I haven't put much thought into it.
<kmal>
Anyway, best of luck with your ideas -- sound like they have great potential!
<detran>
thanks!
rendar has quit []
plexigras has joined #ipfs
KwukDuck has joined #ipfs
<TimMc>
Or you can add more indirection: One IPNS points to another, and you "revoke" the second by pointing the first one elsewhere. :-P
Midnght_J has joined #ipfs
Midnght_J has left #ipfs [#ipfs]
Midnght_J has joined #ipfs
Midnght_J has quit [Remote host closed the connection]
sz0 has quit [Quit: Connection closed for inactivity]
<detran>
ooh, that's simple yet brilliant!
<detran>
The service could just create it's own namespace and you just point yours at it
alexanarcho_ has quit [Quit: This computer has gone to sleep]
alexanarcho_ has joined #ipfs
Taoki has joined #ipfs
<TimMc>
Revocation would take time and not be guaranteed, I suppose.
alexanarcho_ has quit [Client Quit]
<TimMc>
Or... hmm, when an IPNS record expires and isn't replaced, it's effectively dead, is that right? So that would set a bound on revocation.
Tiez has quit [Quit: WeeChat 2.4]
<kmal>
Sounds right... I believe that's why clients like Siderus Orion have to keep republishing IPNS records.
PotatoPro has quit [Quit: PotatoPro]
ylp has joined #ipfs
<kmal>
"Every IPNS key has a lifetime in the network" (Orion help text) Well, since it has a lifetime, I think it would be a sound conclusion to say it's dead after it expires :) (correct me if I'm wrong)
<TUSF>
Huh… Would it be useful to have a kind of public account system over IPNS? Replace passwords with a pub/priv key system, where control of your IPNS record proves your identity?
<TUSF>
A server may give you a public key that you point a link to in your ipns record
<kmal>
TUSF: From what I understand, you'd have basically a list of links in your ipns record? Is that correct?
<TUSF>
The idea is, you'd have a key like /ipns/Qm, where you can link something like /ipns/Qm/github.com, where this github.com link would have your public key, while Github has a private key they compare it against.
Adbray has quit [Remote host closed the connection]
joocain2 has quit [Ping timeout: 256 seconds]
<TUSF>
And then you can have a /profile link that has arbitrary identity info and such.
<TUSF>
Basically a singular account linked to everything… ya know, if there was any kind of agreement on using it lol
joocain2 has joined #ipfs
<kmal>
:) So you'd have your /ipns/Qm-my-key that you'd set to /Qm-insert-site-here/my-id , then the site could verify that you have control over /ipns/Qm-my-key by checking and making sure it all matched up?
<TUSF>
Right
<kmal>
I think that's definitely a great idea! I'm trying to think if there are any immediate problems -- but nothing is coming to mind besides needing to protect the key pair.
<kmal>
Wait... We'd need to figure out to make sure someone couldn't just impersonate someone else by changing their /ipns/Qm-my-key link.
xentec has quit [Quit: memento mori]
<kmal>
i.e. I change my ipns link to point to your account and try to log in
xentec has joined #ipfs
<kmal>
Although that could be solved by only allowing one ipns link, or something else that would probably be easy to implement.
<TUSF>
Yeah, the idea is that the site you're linked to would internally know which ipns link a key should belong to
<kmal>
Yeah. That would work. Any ideas off the top of your head why an implementation like this would be preferable to the current username/password system? I have a vague notion of decentralization and more control -- but nothing concrete at the moment.
<TUSF>
The only concrete idea is that it can be used for interoping between recognized sites… but that may be seen as a negative be privacy-minded folk 😅
<kmal>
While the convenience it could provide would be great -- I'm not sure if I want all my accounts to be tied to /ipns/Qmnotarealhash : )
<kmal>
So I guess you could say I'm one of those privacy-minded folk.
xentec has quit [Ping timeout: 250 seconds]
kmal has quit [Quit: Leaving]
xentec has joined #ipfs
<detran>
kmal, I'm with you - it's probably unreasonable, but I go to some lengths to not let my accounts with different services to be linked
<Mikaela>
Is there an issue about that or how is IPNS key transferred? Having it tied to a single device is one of the reasons why I haven't looked into it
<detran>
Mikaela: I asked around here about that, and apparently you export/import ipns keys
<detran>
though I haven't found the actual documentation for it
<Mikaela>
I see
<detran>
here's what my logs say:
<detran>
<Magik6k> detran: you can push multiple IPNS names from a single node using `ipfs key` and `ipfs name publish --key=<somekey>` apis
<detran>
sorry for the formatting
<detran>
I was asking a slightly different question, whether you can publish to multiple different namespaces from a single ipfs node, but I think it applies in this context as well
xelra has quit [Remote host closed the connection]
<Mikaela>
I had thought that there were longer keyfiles than something that can be pasted as command line argument?
i1nfusion has quit [Remote host closed the connection]
i1nfusion has joined #ipfs
<Mikaela>
Thanks :)
quijote has quit [Ping timeout: 250 seconds]
<Mikaela>
I have also been wondering, is there any side effect of setting reprodiver strategy to pinned instead of all? Does it hurt the goal of having visitors to popular content cache it so there is less resource usage for the server? Will other users accessing the content on LAN know I have the content? I read on GitHub that other nodes can still download the content from me, even if I don't advertise having it or do
<Mikaela>
connected peers always know what I have?
quijote has joined #ipfs
<Magik6k>
LAN discovery has nothing to do with reproviding, so it won't be affected. Currently reproviding is very broken / slow, so it doesn't really work well even with `pinned` strategy (I'd recommend using `roots` for now)
<Magik6k>
(Technically provider records can contain local addresses, but given how broken the provider system is, it shouldn't really matter)
<ylp>
to know which node has a hash you have to perform a lookup in the DHT
<Magik6k>
Local discovery works by querying other nodes through MDNS
<ylp>
ok
<Mikaela>
Thanks, I think pinned is working for me with lowering HighWater/LowWater as I generally have ~20 connections (my HighWater), but now that I have a lot of tabs open including something from ipfs I seem to have 222 connections which would kill IPv6 in my Huawei router if it hadn't died earlier
joocain2_ has joined #ipfs
<Magik6k>
That's because IPFS (mainy DHT) opens a lot of connections at once (connections newer than `ConnMgr.GracePeriod` ignore connection manager)
thistle has joined #ipfs
joocain2 has quit [Ping timeout: 256 seconds]
<Magik6k>
There are fixes in the works for this though
<TUSF>
It's kinda silly and pointless, but still interesting to me.
<Magik6k>
IPNS wouldn't be useful for that, but if you could teach mail clients to talk over libp2p, you could send mails to something like `person@QmPeerID`
<TUSF>
That's the idea
<TUSF>
I kinda conflate Peer IDs with IPNS a lot, hah
szcc007 has joined #ipfs
ekardnam has quit [Remote host closed the connection]
ekardnam has joined #ipfs
jphastings has quit [Quit: Connection closed for inactivity]
plexigras has quit [Ping timeout: 250 seconds]
joocain2 has joined #ipfs
yatsukino[m] has left #ipfs ["User left"]
xelra has joined #ipfs
joocain2_ has quit [Ping timeout: 256 seconds]
detran has quit [Ping timeout: 246 seconds]
appa_ has quit [Read error: No route to host]
appa_ has joined #ipfs
jurajselepsimple is now known as jurajselep|simpl
Adbray has joined #ipfs
kmal has joined #ipfs
gmoro has quit [Ping timeout: 246 seconds]
The_8472 has quit [Ping timeout: 252 seconds]
spinza has quit [Read error: Connection reset by peer]
www2 has joined #ipfs
The_8472 has joined #ipfs
pecastro has quit [Ping timeout: 272 seconds]
spinza has joined #ipfs
joocain2_ has joined #ipfs
treora_ has left #ipfs [#ipfs]
treora has joined #ipfs
kmal has quit [Read error: Connection reset by peer]
ygrek has quit [Ping timeout: 255 seconds]
joocain2 has quit [Ping timeout: 256 seconds]
renich_ has quit [Quit: renich_]
renich_ has joined #ipfs
The_8472 has quit [Ping timeout: 240 seconds]
q-u-a-n2 has quit [Remote host closed the connection]
The_8472 has joined #ipfs
jon1012 has quit [Ping timeout: 245 seconds]
jon1012 has joined #ipfs
jon1012 has quit [Ping timeout: 246 seconds]
alexgr has joined #ipfs
jon1012 has joined #ipfs
kmal has joined #ipfs
The_8472 has quit [Ping timeout: 252 seconds]
cyfex has quit [Ping timeout: 246 seconds]
The_8472 has joined #ipfs
Guest84895 has joined #ipfs
Guest84895 has left #ipfs [#ipfs]
joocain2 has joined #ipfs
joocain2_ has quit [Remote host closed the connection]