Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Internet Censorship Findings: Expose as an RSS feed #894

Open
hellais opened this issue Dec 7, 2023 · 1 comment
Open

Internet Censorship Findings: Expose as an RSS feed #894

hellais opened this issue Dec 7, 2023 · 1 comment
Labels
censorship-findings enhancement New feature or request priority/low user feedback requests that have been added to the backlog as a direct result of user feedback or testing

Comments

@hellais
Copy link
Member

hellais commented Dec 7, 2023

Community members mentioned that it would be helpful if the Explorer Censorship Findings page included an RSS feed to inform their censorship response efforts.

@hellais hellais changed the title CIRP: Expose as an RSS feed Internet Censorship Findings: Expose as an RSS feed Dec 7, 2023
@agrabeli agrabeli added the user feedback requests that have been added to the backlog as a direct result of user feedback or testing label Dec 7, 2023
@m4mb01t4l14n0
Copy link

Thank you for adding this. From my standpoint, a nice-to-have in the future. The reasoning is that, beyond the "search for censorship incidents" API available, the "Findings" are a nice, readable result with lots of backup visuals. It's something I can send to people when I tell them "we need to be vigilant of censorship in country X based on this nice, readable finding, instead of my hard to read numbers-only report.". RSS is just such an easy mechanism for us to handle and, for many CMSes, pretty easy to enable. Thanks for all you folks do!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
censorship-findings enhancement New feature or request priority/low user feedback requests that have been added to the backlog as a direct result of user feedback or testing
Projects
None yet
Development

No branches or pull requests

4 participants