Johan Kiviniemi
Johan Kiviniemi
Awesome
I’m not sure if I have understood this correctly, but I’m under the impression that `must-revalidate` only applies if the content has already expired. http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.4
It seems to me that `must-revalidate` means that given an object that expired according to `max-age`, a cache must return an error instead of a stale copy if it fails...
DNS lets you say explicitly for how long a record can be cached. Perhaps we should do that with IPNS names? `ipfs name publish --ttl=3h` which would be taken advantage...
It was mentioned on IRC that `resolve` does not provide TTL information to be used for `max-age`. `resolveOnce` could be changed to return a TTL value. `resolve` could start at...
Would this be a reasonable starting point? ``` diff diff --git a/namesys/interface.go b/namesys/interface.go index 09c296c..b0b740d 100644 --- a/namesys/interface.go +++ b/namesys/interface.go @@ -47,6 +47,14 @@ const ( // trust resolution to...
``` […] i'm overall -1 on returning the TTL on every Resolve call. i think that should be a separate function call. most uses of Resolve do not care. and...
> We decided to not add support for modrinth since it goes against the principles that our open-source community has (me not included). Unless they remove ads from their website...
Here’s a command that replicates the same directory structure: ``` % rsync -Pav --delete -f '+ /rfc-index.txt' -f '+ /rfc[0-9]*' -f '- *' ftp.rfc-editor.org::rfcs/ rfcs/ && ipfs add -r rfcs...
Mumble is real-time only AFAIK.