hrm, i'm not sure. sounds like this would have most of the problems we've documented in https://indieweb.org/sidefile-antipattern . i imagine you'll end up with different content in this special theme, and that will diverge from the user-visible theme even more over time. not to mention you then have twice the maintenance work since there are two themes instead of one.
@aaronpk do you need to do anything special to push that many pixels?
Hmm odd! I see it as “activity: rsvp” in the webmention.io mentions endpoint. I’m not sure how to link to that, though.
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.