Interesting way to catch tip modifications by waiters. However, I am always surprised that in this age of digital everything, where even currency has gone digital, we are still forced to depend on scam-prone manual tip checking.
is there some good reason why recursive cp takes -R
whereas recursive scp takes -r
?
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?