1,618 karma · joined May 3, 2011
zacwest@^^domain^^
[1]: https://www.calacademy.org/press/releases/claude-the-albino-... [2]: https://www.dropbox.com/scl/fo/i447nodpnda2agq00ekw1/AIhVA36...
1. Set up a region around the user's current location. If they exit it, note the location and set up another one around that location. This will give you around 100m accuracy, which is the minimum diameter of the monitored region.
2. Set up regions in various cardinal directions that nearly-or-just-barely overlap. If they enter one of those regions, note the location and set up another set around the current location. This can give you something closer to 50m accuracy.
For (2), this is how I did it in the Home Assistant iOS app, largely for zones that people wish to monitor which are smaller than 100m. You can find some of the annoying math here[1] (and there's tests all over for it), the logic for setting up regions here[2], and computing them here[3].
[1]: https://github.com/home-assistant/iOS/blob/master/Sources/Sh... [2]: https://github.com/home-assistant/iOS/tree/master/Sources/Ap... [3]: https://github.com/home-assistant/iOS/blob/2dfbe3c0e52a30417...
restic ... --option=rclone.program="ssh -i <identity> user@host" --repo=rclone:
which has it use the rclone backend over ssh.I've been doing this on rsync.net since at least February; works great!
> 3.1.3: The prohibition on encouraging users to use a purchasing method other than in-app purchase does not apply on the United States storefront.
> 3.1.3(a): The External Link Account entitlement is not required for apps on the United States storefront to include buttons, external links, or other calls to action.
The bit about the (formerly required in the US) entitlement is:
> Reader app developers may apply for the External Link Account Entitlement to provide an informational link in their app to a web site the developer owns or maintains responsibility for in order to create or manage an account.
They required you use a trackingless, generic URL that was unvarying per user, so you probably didn't run into it super often. Offhand, the Kobo app did use it.
> Facebook Messages are evolving to allow people to share rich content beyond text: photos, videos, audio and even stickers. We want to ensure the best possible send and receive experience where all these rich forms of content are reliably and consistently available on every platform. XMPP doesn't support all these (and future) content types, and it's difficult to ensure an XMPP client is rendering them appropriately. As such we've decided to sunset the XMPP Chat API.
https://micro.blog has a good implementation of this for both the Fediverse and Bluesky. A random example of mine that has an array of 'em if you want an example: https://zacwe.st/2025/02/12/amazon-is-removing-the-ability.h...
> alt-left and alt-right will now move by one argument (which may contain quoted spaces), not just one word like ctrl-left and ctrl-right do.
{
"description": "caps_lock to left_control or escape",
"manipulators": [
{
"from": {
"key_code": "caps_lock",
"modifiers": {
"optional": ["any"]
}
},
"to": [
{
"key_code": "left_control"
}
],
"to_if_alone": [
{
"key_code": "escape"
}
],
"type": "basic"
}
]
}I wish they'd focus more on growing their technology (e.g. a macOS app). They just did a big rewrite on all the platforms, seemingly toward this goal; I hope they keep going down that path.
If the government forces them to adopt more modern subscription practices, I think _more_ people would use their platform, not less.