I wanted Micro.blog to be so strictly reverse-chronological and anti-algorithmic timeline, that I waited a long time to make this change: just flipped conversations to be oldest at top. The clicked post on the web is also lightly highlighted.
@aaronpk You could probably use the `/api/states` endpoint (https://developers.home-assistant.io/docs/en/external_api_rest.html#get-api-states) and filter the result with the `entity_id` starting with `zone.`
@aaronpk But if the Microsub server includes some post in a timeline response, it has to include the full body of that post, right? Even if the client doesn't need the body yet?
@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?
@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?
