Once someone says they are able to grab a copy of it, I'll change it and we'll see if you get the updated content like you should.

@dave copy grabbed through the Cloudflare link

@stu Ok, let me dump a new version with 150,000 rows instead of 100,000.

@stu Ok, try it now and see if you get the bigger file.

@dave same file (exactly) through the CF link 🤔

@stu Ok, they may be caching.

@stu I just went directly through IPFS and got the bigger file. Must be caching. Let me dig.

@dave @stu I also got the 150,000 row version directly through the ipns:// uri

@steven @stu Thanks for confirming that. I'm reading about their caching. Seems like it invalidates the cache faster if you link a DNS record to it through their dashboard. Going to try that.

@dave @steven from what I've read they seem to default their caching to refresh after 6 hours... which may be good enough, depending on how often you're finally going to update the content.

I guess if people want it quicker than that they can invest the time in getting IPFS/IPNS set up properly.

@dave Just got the 150K version from both a gateway and ipfs (directly).

How often do you plan to publish (continuously?)?

@cameron Initially every 24 hours. But, the goal is to publish a sqlite version of feed table over IPFS, which would update more frequently.

"Continuously" is probably a bad term since it has other devops meanings. I guess a better description would be "frequently and automated".

@cameron Making some changes. Switching to folder instead of just the file...

@dave Wrapping in a folder seems easier on the clients (so they can see the filename).

Understood on the word "continuous". I'm still trying to figure out how to put feed urls in ipns while "continuously" updating.

@dave @cameron I got a 64MB file thru the ipns://url

@alvaro @cameron Thanks. Now we get to see how much bandwidth this uses when I dump the whole thing.