Cis allies in the UK: Send HMRC a GDPR right to erasure request to remove your gender! Template request:
Dear Data Protection Office,
As you are no doubt aware, Article 17 of the Data Protection Act 2018 (UK GDPR) grants a "right to erasure".
It is my understanding that HMRC, jointly with DWP, has records of my gender. I also understand that HMRC claims a "legitimate interest" basis for processing these records, however neither HMRC nor DWP have been able to cite any specific legislation or regulations that currently require that information.
According to ICO guidance "It is not enough to rely on vague or generic business interests." and. You must think about specifically what you are trying to achieve with the particular processing operation.". Furthermore, when relying on this basis, your processing must be weighed against the individual's interests, rights, and freedoms.
Gender is a very personal matter to me, and UK courts have repeatedly reaffirmed that it is covered under Article 8 of the Human Rights Act 1998, which protects my "right to respect for [my] private and family life".
Since the UK fully equalized pension ages in 2019, there is no clear, widely applicable need for HMRC or DWP to process gender information. ICO guidance states that information processing relying on a legitimate interest basis "must be a targeted and proportionate way of achieving your purpose".
Processing gender information for every taxpayer is neither targeted nor proportionate. If there were some obscure circumstances where this information were required, HMRC and/or DWP could accomplish their compliance goals in a targeted and proprotionate way by only requesting and processing gender data as needed.
As complying with my request will require you to identify my records, I am providing my details here:
Name: ____
Date of birth: ____
National Insurance Number: ____
Address: ___
Sincerely,
Email to: advice.dpa@hmrc.gov.uk
If they refuse, complain to your MP.
@kowalabearhugs Currently, some parts of Cuprate are licensed under AGPL-3. This means anyone using this code should keep their derivative works as open source and use the same license. The license protects the project from hostile forks and generally serves as a deterrent against privatization of public goods. Lemmy, Mastodon and many other Fediverse servers use AGPL-3 license and it is totally reasonable choice for Cuprate too.
However, when this CCS proposal was discussed some people started to push aggressively against AGPL (going as far as calling it "legal nightmare") and the developer agreed to change the license and even agreed to re-write AGPL-licensed parts of the application if needed.
As I said, this is a mistake, and makes Monero weaker. I think Cuprate may eventually become a dominant implementation because Rust provides a better security and developer experience, and a big chunk of modern cryptographic libraries is being written in Rust (especially in zero-knowledge cryptography). But now any company can safely use Cuprate as part of their infrastructure because it has business-friendly license, create a closed-source fork and hire developers who were previously working on open-source version.
The change of license is basically a signal that corporate interests are more important than interests of ordinary users. As for examples of where this attitude leads, see any cryptocurrency project where companies or "foundations" pay developers for their work and therefore shape the product. Exceptions are rare, and Monero is one of few that relies on donations and crowdfunding.
Everyone, a friendly reminder, https://kbin.social is **not** the only #Kbin server or instance.
You can check the official website: https://kbin.pub and hover on the “Instances” menu.
One such Kebin instance is https://fedia.io
Please, do not be afraid to use a non-flagship server. Help distribute the load.
Lastly, and most importantly, Kebin is a very new software and development is moving fast. A little patience is needed.
As of this post, the official website states: This is a **very early beta** version.
There is no logo or mascot yet, so I'll just use…
KEVIN!!!!1
GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.
All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.