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
clemo has joined #ipfs
pecastro has quit [Ping timeout: 250 seconds]
Soo_Slow has quit [Remote host closed the connection]
<Phillmac[m]>
Anyone have any clue what's cauing the http 500? and how does one dubug such an error??
<Phillmac[m]>
Anyone have any clue what's cauing the http 500? and how does one debug such an error??
user_51 has quit [Ping timeout: 246 seconds]
mandric has quit [Client Quit]
ddahl has joined #ipfs
mandric has joined #ipfs
<Phillmac[m]>
Tried enabling debug log level for various modules in the logging system, but theres no useful output when a http 500 occurs
yusef has joined #ipfs
ddahl has quit [Ping timeout: 250 seconds]
Phong__ has joined #ipfs
nop has joined #ipfs
ddahl has joined #ipfs
reit has joined #ipfs
Fessus has joined #ipfs
ddahl has quit [Ping timeout: 264 seconds]
thomasan_ has joined #ipfs
nop has quit [Ping timeout: 264 seconds]
<ctOS>
Swedneck: IPFS has the better tech† but Dat actually has a working‡ consumer product with the Beaker Browser. †Though Dat Archive’s native history system could be useful in some situations on IPFS as well. ‡On IPv6; they still don’t do UPnP so almost all IPv4 peers are unreachable.
<Swedneck>
well the projects don't have to merge
<Swedneck>
for example IPFS could help store DAT data, even though they can't do all the things DAT does
<Swedneck>
IPFS nodes could*
Fessus has quit [Remote host closed the connection]
<ctOS>
Phillmac[m]: there are a few calls that return HTTP 500 by design. it might be fine. <insert dog drinking coffee in burning building meme> example: https://github.com/ipfs/go-ipfs/issues/5933
Fessus has joined #ipfs
zakzakzak[m] has joined #ipfs
<ctOS>
Swedneck: one of Dat/Beaker’s goals is to make it easy to publish a distributed website. they’re mostly doing a good job at that whereas IPFS doesn’t really deliver anything too useful for web publishing yet.
<ctOS>
They’re of course cheating a bit by having a centralized tracker server which makes updating mutable content easier.
<Phillmac[m]>
@ct05 So i have to catch the error myself??? I agree with your meme
<Phillmac[m]>
how can i determine if the error is real or not :C
<ctOS>
Phillmac[m]: do’no. I’d assume you’ve got some more details with that response than just the HTTP status code. Find the error code and grep through the code to figure out where it’s printed.
<ctOS>
Swedneck: they also cheat by having their own web browser, of course. <insert the whole discussion about origin separation and ipfs-companion/#667> Control the browser and you control the [distributed|future of the] web.
<Swedneck>
<freenode_ctO "@swedneck: one of Dat/Beaker’s g"> but ipfs nodes could still be able to pin the content, and even keep the pin up to date at some point
ddahl has joined #ipfs
<Phillmac[m]>
I mean its comming from the files_add call. do you mean go find the source for that in go-ipfs? ` ipfs files ls /` doesn't show my `.dir_map' file as existing, so theres definitly a problem of some sort
<Phillmac[m]>
I mean its comming from the files_add call. do you mean go find the source for that in go-ipfs? ` ipfs files ls /` doesn't show my `.dir_map` file as existing, so theres definitly a problem of some sort
Fessus has quit [Remote host closed the connection]
Fessus has joined #ipfs
ddahl has quit [Ping timeout: 250 seconds]
<ctOS>
Swedneck: how is that useful to either networks if the clients are talking different protocols?
<Swedneck>
well they'd have to change sufficiently for some basic bridging to be made possible
Fessus has quit [Remote host closed the connection]
Fessus has joined #ipfs
lassulus has quit [Ping timeout: 250 seconds]
<ctOS>
I don’t think the two projects really want that, though.
dimitarvp has quit [Quit: Bye]
<ctOS>
On an unrelated note: someone mentioned a seed-box like app for IPFS for Android but I lost the project link. Does anyone remember this? It was an app that would announce a CID until DHT reported a minimum of X other seeders. At that point it would stop announcing bu regularly check in to see if the minimum seeder number is maintained.
<ctOS>
Or maybe it was a raspberry pi project? Think it was for Android. Looking for the repo link
yusef has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ddahl has joined #ipfs
spinza has quit [Quit: Coyote finally caught up with me...]
<Phillmac[m]>
god I'm an idiot. I forgot to append a filename to the path i was trying to write to
thomasan_ has quit [Remote host closed the connection]
spinza has joined #ipfs
Phong__ has quit [Ping timeout: 256 seconds]
<Kolonka[m]>
>Control the browser and you control the [distributed|future of the] web.
<Kolonka[m]>
nice to see someone get it
<Kolonka[m]>
(fwiw I've added ctrl blog to a list of recs on my infantile site)
<Kolonka[m]>
also, let me know if you find out what it is ctOS
<ctOS>
Kolonka[m]: if I can find your site, you mean?
<Kolonka[m]>
if you find the program
<Kolonka[m]>
the rpi one or whatever, shoulda been clearer
cygeatwi1 has joined #ipfs
<ctOS>
Kolonka[m]: oh, sorry – I did find it. It’s in my notebook over cool ideas I don’t have time to work on. I misremembered and thought it was something someone had already developed. I just imagined an app that would seed your CIDs until others began hosting it, and would resume distributing it if the number of seeders dropped below a certain threshold.
<Kolonka[m]>
ah
<ctOS>
This exists for BitTorrent.
<Kolonka[m]>
I've had quite a similar idea written down
<ctOS>
It’s a think that should exist. You don’t want your CIDs to disappear but you also don’t want your mobile bill to run too high so you need it to auto-pause when there are others seeding it. So your phone would help with the initial seeding when you publish new content and help ensure old content didn’t disappear without costing you a fortune.
<ctOS>
Kolonka[m]: where is your infantile site?
thomasan_ has joined #ipfs
<ctOS>
Phone app makes sense because it’s probably on another network that your laptop/desktop/pi/homeserver. So network diversity/redundancy/etc. etc.
<Kolonka[m]>
if it's something you ever get the time to work on, maybe I could hit you up on Twitter some time? (about to leave now)
<Kolonka[m]>
it's half-functional, reliant on URL cloaking that doesn't work for me most of the time, and near-zero content that I'm not always able to seed
<Kolonka[m]>
maybe I'll share it when there's more worth seeing
<ctOS>
Kolonka[m]: @aeyoun on the old tweetbox
<lanzafame1>
Heh I was prototyping a similar thing the other day
thomasan_ has quit [Ping timeout: 250 seconds]
<lanzafame1>
Using cluster as the 'watcher' as it already has pin replication logic, it just needs to look at the DHT as a whole instead of just a local ipfs node
<ctOS>
lanzafame1: great. are you sharing that somewhere?
<ctOS>
lanzafame1: I almost asked for a GitHub list, but I guess I should be askin’ for its globally deduplicated and unique content address instead.
<Kolonka[m]>
just messaged you, afk
thomasan_ has joined #ipfs
clemo has quit [Ping timeout: 268 seconds]
<lanzafame1>
ctOS: not currently as it was mostly me learning how to get the DHT started. I'm hoping to have some free time this weekend to work on it some more
thomasan_ has quit [Remote host closed the connection]
yusef has joined #ipfs
yusef has quit [Client Quit]
lostfile has joined #ipfs
mandric has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
mandric has joined #ipfs
mandric has quit [Ping timeout: 250 seconds]
zeden has quit [Quit: WeeChat 2.3]
nop has joined #ipfs
mandric has joined #ipfs
snk0752 has quit [Ping timeout: 246 seconds]
mandric has quit [Client Quit]
mandric has joined #ipfs
Mateon3 has joined #ipfs
Mateon1 has quit [Ping timeout: 245 seconds]
Mateon3 is now known as Mateon1
lostfile has quit []
Thominus has joined #ipfs
lostfile has joined #ipfs
lostfile_ has joined #ipfs
lostfile_ has quit [Client Quit]
lostfile has quit [Client Quit]
lostfile_ has joined #ipfs
lostfile has joined #ipfs
lostfile_ has quit [Client Quit]
lostfile__ has joined #ipfs
lostfile__ has quit [Client Quit]
lostfile has quit [Client Quit]
mowcat has quit [Remote host closed the connection]
renich has joined #ipfs
lostfile has joined #ipfs
user_51 has joined #ipfs
lostfile has quit [Quit: Leaving]
}ls{ has quit [Ping timeout: 258 seconds]
Belkaar has quit [Read error: Connection reset by peer]
lostfile has joined #ipfs
renich has quit [Ping timeout: 268 seconds]
renich has joined #ipfs
}ls{ has joined #ipfs
Belkaar has joined #ipfs
Belkaar has joined #ipfs
renich has quit [Ping timeout: 258 seconds]
lostfile_ has joined #ipfs
lostfile_ has quit [Client Quit]
lostfile has quit [Quit: Leaving]
lostfile has joined #ipfs
lostfile has quit [Remote host closed the connection]
doesntgolf has quit [Remote host closed the connection]
lostfile has joined #ipfs
lostfile has quit [Quit: Leaving]
renich has joined #ipfs
thomasan_ has joined #ipfs
hurikhan77 has quit [Ping timeout: 258 seconds]
shizy has joined #ipfs
cygeatwi1 has quit [Quit: WeeChat 2.1]
mandric has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
BeerHall has joined #ipfs
mandric has joined #ipfs
screensaver has quit [Ping timeout: 245 seconds]
joocain2 has quit [Remote host closed the connection]
<lordcirth>
So, I tried to pin the English Wikipedia - which I expected to take days. I did not expect it to use all of my RAM and freeze my server.
<lordcirth>
At least, I think that's what's happening. I can't tell because htop won't launch
<logoilab[m]>
Uh wow thanks postables that's my project!
lordcirth has quit [Read error: Connection reset by peer]
lordcirth has joined #ipfs
lordcirth has quit [Remote host closed the connection]
lordcirth has joined #ipfs
<seba-->
who's in russia
<seba-->
logoilab[m] you?
aramiscd has quit [Quit: WeeChat 1.9.1]
<logoilab[m]>
Nope US. But that's my project I wasn't expecting to join this channel right now and find it as the most recent post
lordcirth has quit [Remote host closed the connection]
<seba-->
oh ok
lordcirth has joined #ipfs
<seba-->
logoilab[m] do you need any help
<seba-->
i'm in europe
<logoilab[m]>
You can join the group if you want. We started out on the datahoarders subreddit. At the end of this we'll have over 50TB of data collected by more than 50 people all over the world that we'll be hosting on IPFS
Caterpillar2 has quit [Quit: You were not made to live as brutes, but to follow virtue and knowledge.]
<seba-->
how does that help russians hm
<logoilab[m]>
And that's after compression. We're expecting 20x that amount uncompressed. I'm going to be stream processing it all. It doesn't really. Just a foray into big data and Internet routing infrastructure in an attempt to see what Russia does to it when they take themselves offline soon
<postables[m]>
heh saw it on my github newsfeed and its awesome
<postables[m]>
but im curious to hear how this helps the russians? is part of this going to involve spinning up bootstrap peers in russia?
<postables[m]>
i've been trying to find a cheap VPS in russia i can use but cant find any reputable providers
<logoilab[m]>
It's more about how the world responds to Russia going dark than it is what happens inside russia. The secondary goal is to identify infrastructure changes. The servers on the inside are already there. NTP servers. We traceroute in one a second and store the logs
<logoilab[m]>
Once*
Caterpillar has joined #ipfs
<lanzafame1>
Russia is turning off their internet on April 1st?
<logoilab[m]>
Some time before. For a "test" to see if they can airgap themselves in the event of an attack. At least that's the cover story
<logoilab[m]>
We don't know when that's why we're starting now
<lanzafame1>
Oh shame I thought Russia was going to play the best April Fool's prank ever
<logoilab[m]>
Yea it'd be so funny that European Internet will be having cramps for weeks
<seba-->
why
<seba-->
i doubt much gets routed through russia anyway
<logoilab[m]>
You'd be surprised. A lot gets routed out of russia. There will be a giant relief of less data and then a giant rush of it as Russia comes back online. Especially cause everyone will be eager to reach the outside world again.
<logoilab[m]>
But the purpose isn't to measure the strain it's to identify how the routes change. Appearently they'll be restructuring to introduce monitoring "chokepoints" within russia. They say for security but it's most likely for censorship and other nefarious things.
<lanzafame1>
well there goes sci-hub.tw 😞
<logoilab[m]>
gen.lib.rus.ec may go too
<seba-->
yeah sci-hub and libgen is the things i'll miss
<seba-->
libgen has db dumps
<seba-->
sci-hub doesn't
stoopkid has quit [Quit: Connection closed for inactivity]
<logoilab[m]>
Are the dumps on ipfs?
<seba-->
i doubt, there are torrents
<logoilab[m]>
Ah not to worried then. Maybe I'll add them to the network.
djdv has quit [Read error: Connection reset by peer]
djdv has joined #ipfs
crimastergogo has joined #ipfs
fireglow has joined #ipfs
PhongVu_ has joined #ipfs
q-u-a-n has quit [Ping timeout: 246 seconds]
crimastergogo has quit [Quit: crimastergogo]
dimitarvp has joined #ipfs
lostSquirrel has joined #ipfs
recursive has joined #ipfs
crimastergogo has joined #ipfs
gh0str3c0n has joined #ipfs
tttes13 has joined #ipfs
tttes13 has quit [Client Quit]
ttttes13 has joined #ipfs
<ttttes13>
Hey, which datastore the blockstore use in the ipfs cmd line plz ?
gh0str3c0n has quit [Remote host closed the connection]
gh0str3c0n has joined #ipfs
crimastergogo has quit [Quit: crimastergogo]
<voker57>
in the ipfs cmd line?
<voker57>
default is leveldb iirc
<voker57>
no, sorry, it's _datastore_
<voker57>
for blockstore it's custom format called flatfs
phongvu1 has joined #ipfs
phongvu1 has quit [Client Quit]
PhongVu_ has quit [Quit: Page closed]
PhongVu has joined #ipfs
screensaver has joined #ipfs
PhongVu has left #ipfs [#ipfs]
<ttttes13>
thanks
kapil____ has joined #ipfs
<postables[m]>
is there anyway a plugin a can be used to replace the default keystore IPFS uses? based off my interaction with the plugin system thus far, it doesn't seem like there's anyway to hook into the key management stuff ipfs does
<ttttes13>
@voker57 what i don't understand is how block provide the blocks to ipfs
<ttttes13>
so they are findable with find provider
q-u-a-n1 has joined #ipfs
<voker57>
block provide the blocks?
<voker57>
you mean how to add stuff to IPFS?
<voker57>
`ipfs add` should do the job
PhongVu has joined #ipfs
crimastergogo has joined #ipfs
<ttttes13>
what i'm trying to achieve is understand the --discover option of pubsub
<ttttes13>
ipfs pubsub sub --discover <some-topic>
<PhongVu>
hi
PhongVu has left #ipfs [#ipfs]
spinza has quit [Quit: Coyote finally caught up with me...]
PhongVu has joined #ipfs
PhongVu has left #ipfs [#ipfs]
gh0str3c0n has quit [Ping timeout: 268 seconds]
gh0str3c0n has joined #ipfs
gh0str3c0n has quit [Remote host closed the connection]
gh0str3c0n has joined #ipfs
gh0str3c0n has quit [Remote host closed the connection]
gh0str3c0n has joined #ipfs
vmx has joined #ipfs
spinza has joined #ipfs
trqx has left #ipfs ["WeeChat 2.3"]
gh0str3c0n has quit [Ping timeout: 246 seconds]
polman has quit [Ping timeout: 246 seconds]
ttttes13 has quit [Ping timeout: 256 seconds]
Soo_Slow has joined #ipfs
polman has joined #ipfs
alyoshaaa has quit [Quit: Connection closed for inactivity]
woss_io has quit [Read error: Connection reset by peer]
BeerHall has joined #ipfs
zeden has joined #ipfs
ylp has quit [Quit: Leaving.]
malaclyps has quit [Read error: Connection reset by peer]
malaclyps has joined #ipfs
drp has joined #ipfs
ddahl has joined #ipfs
lassulus_ has joined #ipfs
drp has quit [Quit: Konversation terminated!]
lassulus has quit [Ping timeout: 268 seconds]
lassulus_ is now known as lassulus
drp has joined #ipfs
drp has quit [Client Quit]
drp has joined #ipfs
crimastergogo has quit [Quit: crimastergogo]
ttttes13 has joined #ipfs
ddahl has quit [Ping timeout: 268 seconds]
lassulus has quit [Ping timeout: 250 seconds]
lassulus has joined #ipfs
Fessus has quit [Remote host closed the connection]
ylp has joined #ipfs
Fessus has joined #ipfs
Soo_Slow has quit [Remote host closed the connection]
ddahl has joined #ipfs
cygeatwin has quit [Ping timeout: 240 seconds]
ttttes13 has quit [Quit: Page closed]
Fessus has quit [Remote host closed the connection]
Fessus has joined #ipfs
Polemos_ has joined #ipfs
ddahl has quit [Ping timeout: 246 seconds]
Ai9zO5AP has joined #ipfs
ygrek has joined #ipfs
Polemos_ has quit [Quit: Leaving]
BeerHall has quit [Quit: BeerHall]
ddahl has joined #ipfs
crimastergogo has joined #ipfs
screensaver has quit [Remote host closed the connection]
screensaver has joined #ipfs
crimastergogo has quit [Quit: crimastergogo]
yusef has joined #ipfs
crimastergogo has joined #ipfs
kapil____ has quit [Quit: Connection closed for inactivity]
TimMc has joined #ipfs
quasi_snow has joined #ipfs
ylp has quit [Quit: Leaving.]
Onesiphorus has joined #ipfs
Pulse2496 has quit [Ping timeout: 258 seconds]
mandric has joined #ipfs
umma has joined #ipfs
ygrek has quit [Remote host closed the connection]
jasongwq has joined #ipfs
xcm has quit [Ping timeout: 258 seconds]
xcm has joined #ipfs
piti has quit [Read error: Connection reset by peer]
jasongwq has quit [Ping timeout: 256 seconds]
piti has joined #ipfs
zane has joined #ipfs
zane has quit [Client Quit]
Elon_Satoshi has quit [Read error: Connection reset by peer]
D_ has quit [Ping timeout: 268 seconds]
D_ has joined #ipfs
fazo has quit [Quit: fazo]
Elon_Satoshi has joined #ipfs
rabbitz has joined #ipfs
rabbitz has left #ipfs [#ipfs]
mateusbs17|brb is now known as mateusbs17
mowcat has joined #ipfs
saki has joined #ipfs
saki has quit [Excess Flood]
saki has joined #ipfs
saki has quit [Excess Flood]
matt-h has quit [Remote host closed the connection]
renich_ has quit [Remote host closed the connection]
renich_ has joined #ipfs
yusef has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
yusef has joined #ipfs
yusef has quit [Client Quit]
quasi_snow has quit [Quit: Leaving]
mowcat has quit [Remote host closed the connection]
saki has joined #ipfs
mowcat has joined #ipfs
spinza has quit [Ping timeout: 250 seconds]
saki has quit [Ping timeout: 258 seconds]
umma has quit [Ping timeout: 256 seconds]
zeden has quit [Quit: WeeChat 2.3]
zane has joined #ipfs
zeden has joined #ipfs
<AuHau>
Guys do you know if it is possible to split the IPFS's block store into several storages? I will be trying to host bigger amount of data and have several storages available (HDD, NAS, and for left overs & stale data I would like to use S3)
<logoilab[m]>
Uh RAID?
thomasan_ has joined #ipfs
<AuHau>
Hmmm RAID is HW solution, if I am not mistaken. That is not available for me as I have VPS...
<rialtate[m]>
AuHau: LVM or ZFS
<AuHau>
rialtate[m]: Thanks, I will look into those.
<ToxicFrog>
You can't use s3 as a backing store for ZFS, as far as I know
<ToxicFrog>
(or LVM, or anything else that requires a block device)
easyKL has joined #ipfs
<ToxicFrog>
I wonder if anyone's written a sort of "reverse FUSE" that exposes a block device and stores the data in dozens of files on existing filesystems
<logoilab[m]>
Sounds a bit like IPFS
biplavo has joined #ipfs
mowcat has quit [Remote host closed the connection]
mowcat has joined #ipfs
stoopkid has joined #ipfs
spinza has joined #ipfs
xcm has quit [Remote host closed the connection]
xcm has joined #ipfs
hacdias[m] has joined #ipfs
plexigras has joined #ipfs
ddahl has quit [Ping timeout: 245 seconds]
craigo has joined #ipfs
biplavo has quit [Ping timeout: 256 seconds]
ddahl has joined #ipfs
crimastergogo has quit [Ping timeout: 245 seconds]
crimastergogo has joined #ipfs
crimastergogo has quit [Quit: crimastergogo]
Belkaar has quit [Ping timeout: 246 seconds]
Belkaar has joined #ipfs
Belkaar has joined #ipfs
zxq is now known as srkk
lostSquirrel has quit [Ping timeout: 258 seconds]
nighty- has quit [Quit: Disappears in a puff of smoke]
easyKL has quit [Ping timeout: 258 seconds]
polman has quit [Ping timeout: 246 seconds]
vmx has quit [Remote host closed the connection]
polman has joined #ipfs
easyKL has joined #ipfs
mandric has quit [Read error: Connection reset by peer]
mandric has joined #ipfs
mandric has quit [Ping timeout: 245 seconds]
mandric has joined #ipfs
mandric has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
spinza has quit [Quit: Coyote finally caught up with me...]
spartas[m] has joined #ipfs
spinza has joined #ipfs
mandric has joined #ipfs
pecastro has joined #ipfs
lostSquirrel has joined #ipfs
woss_io has joined #ipfs
lassulus has quit [Ping timeout: 250 seconds]
zeden has quit [Quit: WeeChat 2.3]
lassulus has joined #ipfs
spartas[m] is now known as twwright[m]
ddahl has quit [Ping timeout: 268 seconds]
Testerbit has joined #ipfs
MikeFair has joined #ipfs
<MikeFair>
Howdy all! o/
lindeb has joined #ipfs
woss_io has quit [Read error: Connection reset by peer]
twwright[m] is now known as twwright
<MikeFair>
Anyone know if supporting alternative signing keys for an IPNS record is a thing or being worked on as a thing atm?
<seba-->
MikeFair, what do you mean
<seba-->
i.e. that you have multiple IPNS addresses?
<seba-->
on a single client?
<MikeFair>
No, that I have the same IPNS address, but a signing key other than the original private key
<seba-->
oh
<seba-->
no idea
<seba-->
not sure if that's possible hm
<seba-->
as you would have to have the same public key then
<MikeFair>
It's possible, but it requires the IPNS record itself to have a "signing key" data element
<seba-->
i mean, the IPNS address is basically base58 or whatever encoded sha256 of the public key
<seba-->
if i understand correctly
<seba-->
hm
<MikeFair>
You'd initially claim a record using the default private key; but then you could change the update key for the record as part of an update
<seba-->
oh ok, if you say so. i haven't really studied that much that part. :)
<MikeFair>
Right; so that "fixed address" never changes; currently it knows that you have permission to change what it links to becuase you know the private key that goes with that public key
<MikeFair>
that's great up until the private key gets lost or compromised
<MikeFair>
it also doesn't allow for "multiple signers" (or M of N type decisions) for who controls the IPNS updates
<MikeFair>
what I'd like to do is have a few bots be able to compute when an IPNS update should happen based on a consensus algorithm (M computers in a network of N machines come to the same update decision)
<seba-->
i'm not sure if i know enough about crypto
<seba-->
but i think the way it's done now, you can't do this
<seba-->
because the address is linked to the public key
<MikeFair>
correct; historically an update to an IPNS record is validated based solely on the update being signed by the private key to that IPNS address' public key
<seba-->
you would have to totally change how it works :)
<MikeFair>
the IPRS spec has plans to address many of the limitations; but I haven't really heard much about it since the spec was initially drafted
<seba-->
and how addresses are generated
<MikeFair>
no no, addresses would be generated the same way
<seba-->
how?
<MikeFair>
You'd just be adding to update validation code
<seba-->
can you have 10 private keys with 1 public key?
<seba-->
anyway, you could just use DNS records, that link to the IPNS
<MikeFair>
You'd have 1 public key that points to a record, with 10 other public keys as part of the data
<seba-->
and if you lose your IPNS private key just remake it
<seba-->
and point the new IPNS in your DNS
<seba-->
:)
<MikeFair>
I'd just skip IPNS at that point and use DNS to do what IPNS does ;-)
<MikeFair>
(put the IPFS CID directly in DNS)
<seba-->
or that
<seba-->
IPNS is not that good anyway, it requires the node to be online
<seba-->
kinda sucks
<seba-->
single point of failure
<MikeFair>
Not sure what you mean.... IPNS records are CIDs that behave like all other CIDs....
<seba-->
well
<MikeFair>
OH! You're thinking of the node's default IPNS record
cheet has quit [Ping timeout: 250 seconds]
<MikeFair>
I'm talking about IPNS records with custom keys
<seba-->
when you do IPNS it has to query to which CID it points to the peer
mandric has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<seba-->
and if the peer is offline
<seba-->
even if the CID is widely shared
<seba-->
it fails
<seba-->
(ok there's caching for 24 h, but ...)
<MikeFair>
Well that's the same with all CIDs though
<seba-->
naah
<seba-->
if the CID is shared around
<seba-->
it's available
<MikeFair>
a peer with the CID data has be be online
<seba-->
yes
<seba-->
but thing is that a CID can have 10 nodes
<seba-->
and if the original sharing node is offline nobody cares
<MikeFair>
Sure, and an IPNS record can point to that CID that is on 10 nodes
<MikeFair>
IIRC, because IPNS records are so small they actually live in the hash tables of the network peers themselves
<seba-->
yes
<seba-->
but for 24 h
<MikeFair>
So you need a node that doesn't purge them from its cache (pins them)
<seba-->
sure, but point is right now, it doesn't work as nicely
<MikeFair>
usually (and most simply) that's the original publishing node
<seba-->
i.e. what my point is
<MikeFair>
But IPNS is doing something different than a normal CID
<seba-->
that nodes could just retain to where it points, until is not updated
<seba-->
so that you don't have a single point of failure :)
<MikeFair>
You can tell other nodes to do that
NikolayKolev[m] has joined #ipfs
<seba-->
how?
<seba-->
it's not the default
<seba-->
:>
<MikeFair>
you pin the IPNS address
<seba-->
sure :D
<seba-->
but ipfs content is automatically like that
<seba-->
GC time is longer
Testerbit has quit [Quit: Leaving]
<MikeFair>
Hmm, I'd be suprised if you had machines that were regularly querying an IPNS record that it would auto-purge out
<seba-->
i don't know, but if i use the IPFS address directly vs. IPNS
<seba-->
it works much better
<seba-->
quicker
<seba-->
IPNS always take seconds
<MikeFair>
Porbably because it's coming from your local cache
<seba-->
IPFS is instant
<MikeFair>
and your local node has cached the CIDs you're querying
<seba-->
naah i try gateways
<seba-->
so that it's fresh
<seba-->
:>
<MikeFair>
Oh, well there is definitely an IPNS resolution "issue" atm
<seba-->
yes
<MikeFair>
in terms of speed
<MikeFair>
but what IPNS can do, that CIDs can't, is change their results for making the same CID query ;)
<seba-->
anyway that link i gave became a bit viral ;> but almost nobody accessed it using IPFS, but just http gateway but still :))
<MikeFair>
I haven't tested the "how long does an IPNS record stick around if I keep querying it on the gateways but my node is offline" time
clemo has quit [Ping timeout: 246 seconds]
<MikeFair>
I assumed it was just like all CIDs; other machines purge them because they don't pin them; and my machine needs to keep publishing it to keep it fresh
<MikeFair>
The content id that it points to is a similar but separate issue
dasj19 has joined #ipfs
<seba-->
^.^
<MikeFair>
if the IPNS record falls out of the hash map and my mahcine is offline; then the IPNS record can't resolve because the requester can't find it --- if the record resolves but my mahcine hosting the targetted CID is offline, then the content won't load
<seba-->
wow :> 20 nodes have that link
<seba-->
impressive
<MikeFair>
cool!
<MikeFair>
Is that 20 nodes have the resolved CID data; or the IPNS record?
<MikeFair>
or both
boogol has joined #ipfs
thomasan_ has quit [Remote host closed the connection]
seba- has joined #ipfs
<MikeFair>
seba-: wb o/
vyzo has quit [Quit: Leaving.]
seba- has quit [Changing host]
seba- has joined #ipfs
<seba->
:>
vyzo has joined #ipfs
<seba->
it's a transformed list from excel
<seba->
to make it visually nicer
<postables[m]>
`pin the ipns address` you're stil pinning the ipfs hash
seba-- has quit [Ping timeout: 246 seconds]
<postables[m]>
you're not actually pinning the ipns reord, you're first resolving the record to find the referenced CID and then pin that
<seba->
of some quotas for doctors
<seba->
some media picked it up
<seba->
and it became a bit viral
<seba->
:>
<seba->
half the ipfs half the http link
<seba->
i just quickly switched to ipfs because i've seen where this is going lol
clemo has joined #ipfs
Steverman has quit [Quit: WeeChat 2.3]
<aschmahmann[m]>
seba- you may already be aware of this, but IPNS waits for multiple positive responses tying IPNS Key to the relevant CID. This is because, unlike IPFS it's easy to validate the content IPNS wants to make sure it gives you the latest version and not just any version. Also, IPNS record expiration is also designed to help with this "find the latest version" problem (in addition to dealing with DHT churn just like IPFS
<aschmahmann[m]>
does)
thomasan_ has joined #ipfs
<aschmahmann[m]>
seba- you may already be aware of this, but IPNS waits for multiple positive responses tying IPNS Key to the relevant CID. This is because, unlike IPFS it's not easy to validate the content IPNS wants to make sure it gives you the latest version and not just any version. Also, IPNS record expiration is also designed to help with this "find the latest version" problem (in addition to dealing with DHT churn just like IPFS
<aschmahmann[m]>
does)
lnostdal has quit [Quit: ...time for reboot; brb/bbl'ish...]
okdistribute has joined #ipfs
okdistribute has left #ipfs [#ipfs]
lnostdal has joined #ipfs
<seba->
;>
<seba->
ok
<aschmahmann[m]>
ya, so it's always going to be slower because it's trying to help you 😃. However, as you're noticing it could definitely use some work.
<aschmahmann[m]>
*slower than IPFS resolution
<seba->
yes
Adbray_ has quit [Read error: Connection reset by peer]
cyfex_ has joined #ipfs
cyfex has quit [Ping timeout: 245 seconds]
ddahl has joined #ipfs
dasj19 has quit [Quit: dasj19]
ddahl has quit [Ping timeout: 250 seconds]
Adbray has joined #ipfs
plexigras has quit [Ping timeout: 259 seconds]
thomasan_ has quit [Remote host closed the connection]
ion has quit [Ping timeout: 250 seconds]
dgrisham has joined #ipfs
ion has joined #ipfs
dgrisham has left #ipfs ["WeeChat 2.3"]
ddahl has joined #ipfs
MikeFair has quit [Ping timeout: 240 seconds]
ddahl has quit [Ping timeout: 268 seconds]
The_8472 has quit [Ping timeout: 252 seconds]
renich has joined #ipfs
renich_ has quit [Ping timeout: 244 seconds]
spinza has quit [Quit: Coyote finally caught up with me...]