Source: lists.debian.org/debian-devel/…
:::spoiler msg extract:
I want to share a public project I created in response to the ongoing discussions around OS-level age verification, age signaling, and related mechanisms in free software distributions:github.com/AntiSurv/oss-anti-s…
The project exists to document, track, oppose, and prepare the removal of OS-level surveillance, classification, and policy-enforcement mechanisms in free software distributions.
This is not limited to one patch or one component. A visible implementation path is now emerging across multiple layers of the Linux stack, including provisioning flows, account metadata services, user records, and application-facing interfaces.
[...]
The project’s position is explicit:
- no OS-level age verification
- no age si
... Show more...Source: lists.debian.org/debian-devel/…
:::spoiler msg extract:
I want to share a public project I created in response to the ongoing discussions around OS-level age verification, age signaling, and related mechanisms in free software distributions:github.com/AntiSurv/oss-anti-s…
The project exists to document, track, oppose, and prepare the removal of OS-level surveillance, classification, and policy-enforcement mechanisms in free software distributions.
This is not limited to one patch or one component. A visible implementation path is now emerging across multiple layers of the Linux stack, including provisioning flows, account metadata services, user records, and application-facing interfaces.
[...]
The project’s position is explicit:
- no OS-level age verification
- no age signaling or age-bracket APIs
- no client-side scanning or device-side inspection primitives
- no passive downstream inheritance of such mechanisms
- no geo-fencing users out of free software as a substitute for refusal
[...]
The repository is intended as a public dossier and working reference point. It includes:
- a front page and project statement
- a manifesto
- a tracker of issues, PRs, and MRs
- a policy and law background file
- a technical architecture map
- a component-by-component target list
- a downstream stripping and reversal strategy
The immediate goal is to keep the implementation path visible, linkable, and auditable so that these changes can be challenged upstream and, if they are merged anyway, stripped downstream rather than quietly inherited.
If useful, I would welcome corrections, additional evidence, and links to relevant upstream or downstream work that should be tracked.
Free software was written for users, not for surveillance.
> - Martinx - ジェームズ
:::
Document. Revert. Rebuild. Contribute to AntiSurv/oss-anti-surveillance development by creating an account on GitHub.
GitHub
ki9
in reply to redrum • • •All the PRs were opened by the same shill, dylanmtaylor. In the archinstall PR he says:
I hope this cuck gets hit by a bus.
araneae
in reply to ki9 • • •midribbon_action
in reply to redrum • • •ScoffingLizard
in reply to midribbon_action • • •TrippinMallard
in reply to redrum • • •GitHub - upper-up/meta-lobbying-and-other-findings
GitHub