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.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 Con
Guest63655 has quit []
random_yanek has quit [Ping timeout: 245 seconds]
hph^ has joined #ipfs
<AuHau>
lordcirth I see,
<AuHau>
do you know if the syntax for ttl is the same as for lifetime?
markg85 has joined #ipfs
<markg85>
ping raulk
<lordcirth>
AuHau, ipfs name publish --help
<lordcirth>
and yeah, pretty much
<AuHau>
Ok, the documentation is not really specific about it
<postables[m]>
Apparently it's been fixed 🤔
random_yanek has joined #ipfs
<lordcirth>
AuHau, btw, while I can resolve your ipns link, I can't seem to load the content
pecastro has quit [Ping timeout: 250 seconds]
<markg85>
Hi
<markg85>
I'm guessing some of you devs run ArchLinux? :)
<markg85>
Could anyone give me some pointers on how to compile go-ipfs on arch?
<AuHau>
lordcirth Yeah, it was testing thing, so it might be not available... No worries, but thanks for letting me know
<lordcirth>
markg85, compile for dev, or you just want to run it?
<postables>
:thinking: i think i shared the screenshot of when i was testing it on my laptop but this the public gateway that should be usable by any i2p proxy (at least i think)
cheetypants has quit [Quit: ZNC 1.8.x-nightly-20190128-91af796c - https://znc.in]
cheet has joined #ipfs
plexigras has joined #ipfs
<seba->
postables, that's great ^.^
<seba->
postables, do you know how IPNS works, the caching of it?
<postables>
thanks :D im not super familiar with how the caching works, but i think the first value considered is the ttl?
<arthur>
i'm also confused about caching ipns in general
<arthur>
after pining it and shutting down the laptop
<arthur>
(i pinned it on a different computer)
<arthur>
i want to ensure the ipns name will still resolve
<arthur>
and pining it by ipns does not seem to accomplish this
<seba->
could you set up higher caching times?
<postables>
arthur: i believe if you leave the node online it will do automatic republishing of the records. if you pin `/ipns/...` i believe you'll be pinning the hash that its pointing too
<seba->
like maybe a setting
<seba->
hm
<seba->
that your IPNS doesn't change that much
<postables>
`ipns.RepublishPeriod` in `$IPFS_PATH/config` allows you to change the republish period, default i think is every 4hrs
<postables>
i believe cache time depends on the lifetime and/or ttl values, so by default its every 24 hours but ive tried with a 48 hour lifetime and it seems to work
<seba->
but do other nodes respect that?
<postables>
respect the cache? i think if you have a lifetime for say 24 hours, and 12 hours after you publish that record, you use the same key to publish another record with a lifetime of 1 hour, then i think the default behavior would be to ignore that one, since the first publish has a longer lifetime
<arthur>
the system doing the publishing is online only occationally, and I'd like to use a pining server to keep my site "up"
<postables>
i believe though you can use the ttl value to get better control, so you could have a ttl value of 1 hour, which would mean after 1 hour any new publish is considered "new". although the default is 24 hours.
<arthur>
from reading that link, and the rest of the sectiosn on ipns it sounds like it's not an appropriate tool for this
<postables>
arthur: you could always export the key to your pinning node, but you would at some point need to refresh the record, otherwise it will expire
<arthur>
unless a system other than the originator can re-publish the ipns messages every 23 hours
<seba->
ok
<postables>
well who ever controls the key can publish the record
<postables>
so by default your using the self key (aka, the key of your node) but you can use any key you generate
<arthur>
right, and the key must be present to generate the new notifications, or it would be vulnerable to replay/backdating attacks
<arthur>
dns may be a better tool for this than ipns, if i'm understanding this, since it is persisted elsewhere. I'm new so i'm likely misunderstanding
<postables>
well with dns you can use TXT records and embed `dnslink="/ipfs/..."` and use that. I do that for the api docs for my program, and its been extremely useful
<arthur>
yea, i think that's a better fit for what i'm doing
<arthur>
thanks
<postables>
so lets say you have a dnslink record at ipfs.example.org, you can go to an ipfs gateway https://ipfs.io/ipns/ipfs.example.org and itll show up :D
<postables>
np, dnslink does sound like your solution
gde33 has quit [Ping timeout: 246 seconds]
gde33 has joined #ipfs
gde33 has quit [Remote host closed the connection]
postables has quit [Remote host closed the connection]
gde33 has joined #ipfs
lostSquirrel 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
href has joined #ipfs
spinza has quit [Quit: Coyote finally caught up with me...]
spinza has joined #ipfs
gniux has joined #ipfs
clemo has joined #ipfs
woss_io has joined #ipfs
senden9[m] has joined #ipfs
pecastro has joined #ipfs
gniux has quit [Ping timeout: 244 seconds]
gniux has joined #ipfs
kapil____ has joined #ipfs
xcm is now known as Guest6169
Guest6169 has quit [Killed (hitchcock.freenode.net (Nickname regained by services))]
xcm has joined #ipfs
agsv has joined #ipfs
<agsv>
my API listening addr seems to be /ip4/127.0.0.1/tcp/5001, but on netstat I see 127.0.0.1:5001 0.0.0.0:* LISTEN
<agsv>
oh man I noobed out that means listening on loopback
andi- has quit [Ping timeout: 250 seconds]
malaclyps has quit [Read error: Connection reset by peer]
andi- has joined #ipfs
malaclyps has joined #ipfs
andi- has quit [Excess Flood]
lostSquirrel has quit [Ping timeout: 244 seconds]
andi- has joined #ipfs
Mateon3 has joined #ipfs
Mateon1 has quit [Ping timeout: 250 seconds]
Mateon3 is now known as Mateon1
markg85 has joined #ipfs
piti has quit [Ping timeout: 244 seconds]
gmoro has joined #ipfs
modnarz has quit [Ping timeout: 245 seconds]
modnarz has joined #ipfs
xcm has quit [Read error: Connection reset by peer]
ValdikSS has quit [Excess Flood]
xcm has joined #ipfs
ValdikSS has joined #ipfs
piti has joined #ipfs
l2d has quit [Remote host closed the connection]
l2d has joined #ipfs
dimitarvp has joined #ipfs
biplavo has joined #ipfs
_whitelogger has joined #ipfs
Wioxjk has quit [Ping timeout: 240 seconds]
jesse22 has quit [Ping timeout: 264 seconds]
Wioxjk has joined #ipfs
<ToxicFrog>
It means listening on everything.
<ToxicFrog>
Oh, wait, missed the rest of the line.
lordcirth has joined #ipfs
<ToxicFrog>
It means listening on loopback port 5001 for connections from anywhere.
lordcirth__ has quit [Ping timeout: 272 seconds]
<agsv>
yea just tested with a remote machine
jesse22 has joined #ipfs
dasj19 has joined #ipfs
kapil____ has quit [Quit: Connection closed for inactivity]
mowcat has joined #ipfs
markg85 has quit [Quit: Konversation terminated!]
biplavo has quit [Quit: Page closed]
Wioxjk has quit [Ping timeout: 245 seconds]
crimastergogo has joined #ipfs
Wioxjk has joined #ipfs
crimastergogo has quit [Remote host closed the connection]
crimastergogo has joined #ipfs
gniux has quit [Ping timeout: 246 seconds]
Xenguy has quit [Ping timeout: 246 seconds]
Xenguy has joined #ipfs
lidel` has joined #ipfs
lidel has quit [Ping timeout: 268 seconds]
lidel` is now known as lidel
reit has joined #ipfs
spinza has quit [Quit: Coyote finally caught up with me...]
math_ has quit [Ping timeout: 246 seconds]
math_ has joined #ipfs
dsiypl4 has joined #ipfs
spinza has joined #ipfs
kesenai has quit [Quit: Leaving]
dsiypl4 has quit [Ping timeout: 246 seconds]
xcm has quit [Remote host closed the connection]
JCaesar[i] has quit [Remote host closed the connection]
xcm has joined #ipfs
gmoro has quit [Ping timeout: 268 seconds]
cyfex has quit [Ping timeout: 240 seconds]
cyfex has joined #ipfs
arthur has quit [Ping timeout: 250 seconds]
The_8472 has quit [Ping timeout: 252 seconds]
crimastergogo has quit [Quit: crimastergogo]
The_8472 has joined #ipfs
arthur has joined #ipfs
zane has joined #ipfs
dsiypl4 has joined #ipfs
The_8472 has quit [Ping timeout: 240 seconds]
The_8472 has joined #ipfs
wking has quit [Ping timeout: 272 seconds]
Sunflowery has joined #ipfs
SunflowerSociety has quit [Read error: Connection reset by peer]
sim590 has joined #ipfs
clemo has quit [Ping timeout: 244 seconds]
kesenai has joined #ipfs
<rialtate[m]>
If I "share" a file via ipfs is there anyway to estimate the number of viewers/consumers of that file or is that a complete tradeoff for being decentralized?
vyzo has quit [Quit: Leaving.]
vyzo has joined #ipfs
<Swedneck>
you can see roughly how many people are sharing the file
<rialtate[m]>
<Swedneck "you can see roughly how many peo"> How?
<Kolonka[m]>
ipfs dhtprovs [hash]
<Kolonka[m]>
(iirc)
<Swedneck>
some ipfs command i can never remember
<Swedneck>
ah, `ipfs dht findprovs <hash>`
renich has quit [Ping timeout: 268 seconds]
bahumbedbug has left #ipfs [#ipfs]
<rialtate[m]>
So, is that the number of nodes that have it pinned or?
<Swedneck>
number of nodes that say they have it
<Swedneck>
not necessarily pinned
<seba->
but people can access it via gateways
woss_io has joined #ipfs
mischat has joined #ipfs
Lochnair has quit [Ping timeout: 250 seconds]
obensource has quit [Ping timeout: 272 seconds]
<postables[m]>
seba-: in the case of accessing it via gateways it will still show up as its cached in the node
<seba->
yes
<seba->
but you don't see the N of users
obensource has joined #ipfs
<postables[m]>
ah true
kesenai has quit [Quit: Leaving]
Ai9zO5AP has quit [Ping timeout: 272 seconds]
<seba->
postables[m], do you know if there's an IPFS http header that can be used with IPNS?
<seba->
oh
<seba->
i'm silly
<postables[m]>
uhmm outside of a gateway i dont think http headers are even cosnidered
<seba->
probably X-Ipfs-Path: /ipfs/... works also