Well that's an interesting thought... The ever-growing storage ... • Aaron Parecki

Jamey Sharp https://toot.cat/@jamey • Jul 13
@aaronpk Hey, on another note: after conversation with NewsBlur's developer, I'm thinking about RFC5005 as a way for feed consumers to reduce storage costs, and I wondered if this makes sense to you. If you know you can re-fetch any feed entry from the origin server at any time because it has paginated archives, then you can aggressively discard your cached copy of anything whenever you want... right?

Well that's an interesting thought... The ever-growing storage requirement was my main concern with launching Aperture, so I limited it to only storing the last 7 days of posts. If I knew I could show a "read more" link and fetch the feeds on demand that would certainly make my life easier while still letting people browse through more content than I want to cache/store permanently.

Portland, Oregon • 86°F

Fri, Jul 13, 2018 3:21pm -07:00

1 like 1 reply
- Jamey Sharp
Have you written a response to this? Let me know the URL:
- Jamey Sharp toot.cat/@jamey
  
  @aaronpk Do you have any statistics on storage costs for GUIDs vs post titles vs publication dates vs post contents?
  I'm thinking there are multiple sensible levels of cache flushing. It seems nice to keep just enough information to browse the list of posts, while discarding the contents of a post until someone actually opens it. But if nobody scrolls back in the history for a feed for a while, it's probably okay to discard the old post metadata too.
  Microsub couldn't do that as-is, can it?
  
  Fri, Jul 13, 2018 10:31pm +00:00

Posted in /replies using monocle.p3k.io