Feature Request: Opt-Out from Cyber Circle Creator #6
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: revengeday/cyber-circle-creator#6
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Since Cyber Circle Creator is a fork of AMNatty/Mastodon-Circles, I have reviewed the issues there, which I will briefly mention here:
From: karlorg (Aug 30, 2024)
URL: https://github.com/AMNatty/Mastodon-Circles/issues/14
From: Seirdy (Jan 27, 2024)
URL: https://github.com/AMNatty/Mastodon-Circles/issues/8
From: fluoriteByte (Jan 1, 2024)
URL: https://github.com/AMNatty/Mastodon-Circles/issues/6
It is clear from these comments that users want the ability to opt out of the tool. I have already considered this, and I will create a feature request here to explore such a solution. I will use this issue to keep you updated on the progress.
Sidenote:
Karlorg raises a significant point about the structure and functionality of Fediverse instances. The inherently open nature of APIs allows applications like Mastodon to take full advantage of their decentralized nature. This openness can inadvertently lead to issues concerning data accessibility, as the APIs potentially expose user data broadly unless specific measures are taken. However, it's important to note that the availability of this data is indeed intentional, as outlined by the ActivityPub protocol. This protocol is designed to facilitate a decentralized and interconnected social network ecosystem.
For those who have concerns about data exposure, one approach might be to consider switching to a centralized social network that does not use open APIs. Alternatively, running a local-only instance could provide an additional layer of privacy. These options might better align with users' privacy expectations, while still allowing engagement within social networks, albeit with different levels of openness and control.
It is also important to highlight that Cyber Circle Creator operates without storing any data on external servers. Everything generated by the tool happens entirely within the user's browser, ensuring complete user control over their information. There is no intention—financial or otherwise—to analyze this data.
Current measures
The first step I have taken is to add a user-agent to the
create-circle.jsfile. This allows Fediverse administrators to completely block the Cyber Circle Creator using the user-agent. This measure serves as an initial response to address user concerns about data control. For detailed information on how administrators can implement this blocking mechanism, I have created a guide in the wiki titled "Opt-Out: Guide for Fediverse Administrators," which you can find here.In addition to this, I am planning further enhancements. One potential approach is to implement an opt-out feature that would give users more control and allow them to actively choose against "data collection" by the Cyber Circle Creator.
I am looking for collaborators who are interested in partnering with me to develop this feature.
However, implementing such functionalities is technically challenging, as
create-circle.jsis very large and has numerous dependencies that can slow down the integration of new features.