while i don't want to throw shade on the developers' intentions, nor have any real proof of what data is being kept, a fetch request bears by minimum the source ip (which can be geolocated) and the fact that the homeserver exists and runs continuwuity.

i'd suggest a matrix channel as alternative, so hosters can opt-in by joining. plus, by leveraging the matrix protocol, such announcements become federated push notifications, meaning they could come from any homeserver (limiting ip logging) and don't imply the continued existence of such deployment, or the software which is being run

even converting such mechanism to an opt-out "auto-join announcements channel" would be more privacy respecting

BREAKING - Release 0.1 of DON'T is now available - DON'T does absolutely nothing when you start it, except to present an enormous Consent List of everything it can do if you let it. Outraged digital freedom advocates are criticizing what they call excessive download times, sluggish support, and that the app takes up memory space without doing anything.