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

Censored text is still viewable #92

Open
tyliec opened this issue Apr 18, 2024 · 3 comments
Open

Censored text is still viewable #92

tyliec opened this issue Apr 18, 2024 · 3 comments
Labels
existing-bug An existing bug in UIPA.org 1.X

Comments

@tyliec
Copy link
Member

tyliec commented Apr 18, 2024

Describe the bug

The portal currently has the feature of scrubbing text from a request for privacy purposes. For example:

Image

While the << ... >> scrubbing is present in the portal UI, the text is still visible on the request's RSS/XML feeds.

Image

Example Affected Request:

Expected behavior
Request text is not only scrubbed in the Web UI, but also in the RSS/XML Feeds.

@tyliec
Copy link
Member Author

tyliec commented Apr 18, 2024

This might not actually be an issue:

Hmm…I am not sure that is something that needs to be fixed. In the end, those e-mail addresses would be disclosable as part of the public records. If the system were disclosing the user’s name (when that person did not want to be identified), that would be a different story. But I don’t think the requester’s name is disclosed in the RSS feed from what I saw of the screenshot. In fact, I question why it scrubbed the e-mails at all because now you cannot tell whose correspondence has been requested, so someone searching later would not know what had been requested previously—unless they clicked on the attachment that had the responsive records.

@tyliec tyliec added existing-bug An existing bug in UIPA.org 1.X and removed bug labels Apr 25, 2024
@russtoku
Copy link
Member

russtoku commented Jul 3, 2024

If it's highly desirable to give users of UIPA.org confidence in what the system does then I think both the current behavior and the desired behavior should be clearly stated to prevent misunderstanding and unmet expectations.

Then if the current behavior isn't what's desired, further action should be taken to change the current behavior.

@sthapa
Copy link

sthapa commented Oct 9, 2024

After talking to Brian, we should redact the xml feed as well

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
existing-bug An existing bug in UIPA.org 1.X
Projects
None yet
Development

No branches or pull requests

3 participants