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
zane has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
thomasan_ has quit [Remote host closed the connection]
refpga has quit [Ping timeout: 250 seconds]
jesse22 has quit [Remote host closed the connection]
jesse22 has joined #ipfs
mischat has joined #ipfs
jhulten has joined #ipfs
mischat has quit [Ping timeout: 252 seconds]
DrFelder has joined #ipfs
littleebee has quit [Quit: Updating details, brb]
jhulten has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
littleebee has joined #ipfs
DrFelder has quit [Client Quit]
tglman has joined #ipfs
Mateon3 has joined #ipfs
Mateon1 has quit [Ping timeout: 268 seconds]
Mateon3 is now known as Mateon1
thomasan_ has joined #ipfs
}ls{ has quit [Ping timeout: 250 seconds]
thomasan_ has quit [Remote host closed the connection]
}ls{ has joined #ipfs
user_51 has quit [Ping timeout: 244 seconds]
user_51 has joined #ipfs
lassulus_ has joined #ipfs
lassulus has quit [Ping timeout: 246 seconds]
lassulus_ is now known as lassulus
thomasan_ has joined #ipfs
thomasan_ has quit [Remote host closed the connection]
tombusby has quit [Remote host closed the connection]
tombusby has joined #ipfs
<ctOS>
postables[m]: For your testing needs I do also have a CNAME delegated DNSLink domain at [_dnslink.]media.cf.ctrl.blog. It should resolve to _dnslink.media.ctrl.blog. (I set that up for use with a Cloudflare-IPFS gateway at media.cf.ctrl.blog.) You'll notice that the TTLs are different; the resolved TTL is expected. Just realized you could use that.
<ctOS>
Isn't DNS fun?
notdjdv has joined #ipfs
djdv has quit [Disconnected by services]
notdjdv is now known as djdv
<postables[m]>
awesome thanks 😄
<postables[m]>
that'll give me some good edge cases to test for
<postables[m]>
not as fun as using 96000bit serial connection to configure some UPS -.-
djdv has quit [Disconnected by services]
<ctOS>
postables[m]: where "resolved" means the TXT record's TTL and not the CNAME's TTL
djdv has joined #ipfs
<ctOS>
or is that called "canonical"? I'm not 100% certain about the correct terminology here.
<postables[m]>
sounds good, i probably wont get around to makign these modifications tonight but sometime this weekend for sure
<postables[m]>
prrett ysure its canonical
obensource has joined #ipfs
<ctOS>
postables[m]: maybe you can find a way to use delegated DNSLink to provide some sort of add-on service for managed DNSLink
<ctOS>
"upload your website files here and we'll configure and update DNSLink for our (after one-time CNAME delegation setup)"
<postables[m]>
i mean for awhile i did have the ability to publish DNSLink records on Route53, specifically for my domain, but I suppose i could re-add and modify that code to use third-party AWS keys. AWS has pretty decent permission configuration so it should be theoretically possible to give us API keys for Route53 that literally just have permission to create CNAME and TXT records for a single domain
<postables[m]>
but personally im a little iffy of being responsible for other people's AWS keys and whatnot
<postables[m]>
although i suppose people could give us like a one-time use API key for whatever domain provider they use
<ctOS>
postables[m]: no, no. your customers create the _dnslink CNAME "customer-subdomain.dnslink.temporal.cloud." entry. Then you publish updated dnslink records to customer-subdomain.dnslink.temporal.cloud
<postables[m]>
oh okay i see what you're saying. yea i don't see why that wouldn't be possible
<postables[m]>
that would work with the pre-existing code i had actually
<ctOS>
postables[m]: `dig media.ctrl.blog A` will show you that that subdomain is just a CNAME to BunnyCDN. I setup the CNAME to point to the domain setup and maintained by my CDN.
<ctOS>
postables[m]: actually, you could just create an API for publishing an IPFS hash to DNS. Many managed DNS hosts (especially those operated by domain registrars) don't have an API, so you could provide IPFS-DNSLink-as-a-service
<ctOS>
postables[m]: I'm sure this would be useful to folks.
<postables[m]>
yea, so i guess it would make sense to just use our domain which is with Route53 that has a pretty solid API and i've used it before to publish DNSLink records. We already let people publish IPNS records with a ton of different keys they can create (RSA, or ED25519) so thats like 50% of the work done already
<postables[m]>
realistically its all done since I've already written the DNSLink publishing code haha.... guess its time to reintegrate it
lnostdal has joined #ipfs
<ctOS>
User deployment could be as easy as: ipfs add -r -q direcotry/ | tee your-pinning-api | your-dnslink-publishing-api
<postables[m]>
yea would probably take less than a day to reintroduce the dnslink code, and test. could probably have it available as an API call in 2-3 days with pr review etc...
jesse22 has quit [Remote host closed the connection]
<postables[m]>
well ill be back in a bit, time to go install 2 beasts of a server and some RAID6 storage 😁
jesse22 has joined #ipfs
Jesin has joined #ipfs
_whitelogger has joined #ipfs
mindCrime has joined #ipfs
mindCrime has quit [Remote host closed the connection]
Sigma has joined #ipfs
jesse22 has quit [Remote host closed the connection]
jesse22 has joined #ipfs
purisame has quit [Ping timeout: 250 seconds]
DrFelder has joined #ipfs
DrFelder has quit [Client Quit]
<postables[m]>
@ctOS: now that I've got the dev environment IPFS server it looks like the dnslink mirror prototype is properly working! I think next I'm going to add some processing to skip pinning if the content hash is the same, if not then I'll run a pin update with from being the already pinned content hash, and to being the new hash that was pulled
ctOS has quit [Quit: Connection closed for inactivity]
}ls{ has quit [Quit: real life interrupt]
cheet has quit [Quit: ZNC 1.8.x-nightly-20190102-481fdb5a - https://znc.in]
vyzo has quit [Quit: Leaving.]
vyzo has joined #ipfs
cheet has joined #ipfs
irdr has quit [Remote host closed the connection]
Belkaar has quit [Quit: bye]
Belkaar has joined #ipfs
Belkaar has joined #ipfs
mischat has joined #ipfs
hexfive has quit [Quit: WeeChat 2.3]
jesse22 has quit [Remote host closed the connection]
mischat has quit [Remote host closed the connection]
jesse22 has quit [Remote host closed the connection]
jesse22 has joined #ipfs
_whitelogger has joined #ipfs
<M-Sonata>
well, one thing is that every ipfs hash starts with a prefix indicating the version of the specification that was used to generate and represent the hash
<Swedneck>
i don't think that's what they're referring to
<Swedneck>
"IPFS has historical versioning that preserves the past so we as the users can find the information that may now be missing."
vyzo has quit [Quit: Leaving.]
DrFelder has joined #ipfs
DrFelder has quit [Client Quit]
hacman has joined #ipfs
craigo has joined #ipfs
<postables[m]>
I think people say that because when you alter content and add it to IPFS you get a different hash. So you can basically construct a timeline of an object's history (versioning'ish)
daMaestro has quit [Quit: Leaving]
<postables[m]>
So you can have an IPLD object that links to all the versions of some content say a whitepaper
<Swedneck>
but there's absolutely no way of figuring out old hashes from the current hash
<Swedneck>
there's no `ipfs name version ipfs.io -1`
<postables[m]>
Sure, but you can make an IPLD object to track the versioning
<Swedneck>
which how many people do?
lidel` has joined #ipfs
lidel has quit [Ping timeout: 272 seconds]
lidel` is now known as lidel
toppler` has joined #ipfs
toppler has quit [Ping timeout: 268 seconds]
obensource has quit [Quit: WeeChat 1.0.1]
spinza has quit [Quit: Coyote finally caught up with me...]
obensource has joined #ipfs
cheet has quit [Ping timeout: 258 seconds]
daMaestro has joined #ipfs
DrFelder has joined #ipfs
<postables[m]>
Probably very few but that doesn't make it any less of a feature/functionality
DrFelder has quit [Client Quit]
<Swedneck>
idk, feels like a bit of a stretch when you have to make it yourself
ctOS has joined #ipfs
craigo has quit [Remote host closed the connection]
<postables[m]>
I mean it should be pretty simple to solve
jesse22 has joined #ipfs
<postables[m]>
Although making it a smooth UX experience that will be hard
ichoquo0Aigh9ie has joined #ipfs
<Swedneck>
it would be nice if IPNS keys had their history automatically tracked
<Swedneck>
and you'd be able to look it up with `ipfs name version`
<Swedneck>
´ipfs name version ipfs.io -5` to see what it pointed to 5 versions back, `ipfs name version ipfs.io <DATE>` to see what it pointed to at some date in time
<Swedneck>
`ipfs name version ipfs.io -5` to see what it pointed to 5 versions back, `ipfs name version ipfs.io <DATE>` to see what it pointed to at some date in time
<Swedneck>
actually i guess it would be `-5 ipfs.io` and `-d <DATE> ipfs.io`
<Swedneck>
you get the gist
ichoquo0Aigh9ie is now known as jalcine
jalcine is now known as jacky
cheet has joined #ipfs
plexigras has quit [Ping timeout: 258 seconds]
pecastro has quit [Read error: Connection reset by peer]
DrFelder has joined #ipfs
DrFelder has quit [Client Quit]
daMaestro has quit [Quit: Leaving]
cheet has quit [Ping timeout: 268 seconds]
cheet has joined #ipfs
cheetypants has joined #ipfs
cheet has quit [Ping timeout: 250 seconds]
chiui has joined #ipfs
<ctOS>
Dat has versioning. Maybe have a look at what they do?