Pre-tip bill: $81.12
Rough tip: $16
Pre-checksum total: $97.12
9 + 7 = 16 (?)
Final: $97.16 (last digit of sum = 6)
Adjust up to $16.04 or down to $15.94? The mental math could trip people up.
I'm confused about the exact problem you're having.
If Compass' composer.lock
is referencing 0.1.1, try running composer update p3k/quartz-db
to get it to update that version, or change your composer.json
to reference >=1.1.4
.
It sounds like that's the root of the problem, as that fix was in version 1.1.3.
QuartzDB explicitly stores everything in UTC, in order to have control over the date-based sharding and retrieval. If you're reading the files directly you'll need to account for this. The API it provides will take timezones into account, so for example you can use the query method and pass in a local timestamp that includes a timezone offset and you'll get back the right results. I strongly recommend not reading the storage files directly and instead using the API that QuartzDB provides.
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?
@aaronpk id property has to be either content-negotiable or always json. url property can be html. you may use <link> tags in html to point to json resources, also.