mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-09 03:32:54 -05:00
[Feedback] Privacy mode #513
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#513
Reference in New Issue
Block a user
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?
Originally created by @MatissJanis on GitHub (Jul 18, 2023).
Author: @joel-jeremy
Original PR: https://github.com/actualbudget/actual/pull/1272
This feature must be enabled as an experimental feature.
--
Please post your feedback and or bug reports as comments to this issue.
@MatissJanis commented on GitHub (Jul 22, 2023):
bug
privacy mode is not masking balances in the "reports" page
@shall0pass commented on GitHub (Aug 6, 2023):
Privacy mode isn't masking values in the schedules page. I'm not sure if this is intentional or not.
@Crazypkr1099 commented on GitHub (Aug 8, 2023):
Privacy mode needs to completely mask out number, ATM it's extremely easy to see how much people have since the blurring effect is very light. Increasing the blurring effect and potentially changing the numbers to be gibberish would severely make this feature better.
@shall0pass commented on GitHub (Aug 9, 2023):
I don't understand the comment about being able to read the values. If I were casually walking by and glanced at a screen, there is absolutely no way I could read this. I asked someone today to try to read it not knowing what was behind it. He got real close, squinted, removed his glasses, and probably tried crossing his eyes. He couldn't read it. Can you provide an example where it is easy? Maybe there's a rendering difference between our browsers?
@joel-jeremy commented on GitHub (Aug 10, 2023):
Thats a good point. Maybe the blur is being rendered differently by the browser? Would a setting which adjusts the global blur intensity help with this?
@joel-jeremy commented on GitHub (Aug 10, 2023):
I haven't worked on the schedules page yet. I'll address this in a future PR. Thanks!
@joel-jeremy commented on GitHub (Aug 10, 2023):
Ideas/items for succeeding PRs for privacy mode:
@Amolith commented on GitHub (Sep 4, 2023):
I just saw this feature make it into the release and it's really cool! :)
I do believe a different method of redaction is worth considering though; blur has been shown to be pretty trivially reversible and so has pixelation, albeit to a lesser degree. A much more secure method would covering those fields with a pattern not derived from the underlying text. Another would be replacing them with a solid colour, like making the foreground and background colours of those fields the same or replacing the text with some box-drawing characters like ██████
@Crazypkr1099 commented on GitHub (Sep 4, 2023):
Completely agree with amolith, blurring is decent for now but for more
privacy I would potentially like to see either a higher blur effect, or
some type of other protectant style.
Great work! Thanks for your continued contributions!
On Mon., Sep. 4, 2023, 9:33 a.m. Amolith, @.***> wrote:
@deftly1970 commented on GitHub (Sep 4, 2023):
While I agree that it isn't easy to read, I was able to pop into my budget yesterday and glance at a blurred amount that I intentionally had not seen recently and was able to read it to the point where I was only off by one digit. The amount was $1,929.39 and with little effort I guessed it to be $1,929.29. Perhaps different browsers provide different results. I am using Brave.
The other thing that I don't like is that it is trivial to see how many digits are being blurred. With a quick glance anyone can tell whether the masked amount is in the 3, 4, 5 or 6 digit range.
Love the idea though, just feel it could be taken a step further. Thanks!
@Amolith commented on GitHub (Sep 4, 2023):
This is an excellent resource explaining why redacting information using patterns based on the underlying text (blur, pixelation, etc.) is unsafe.
https://bishopfox.com/blog/unredacter-tool-never-pixelation
@MatissJanis commented on GitHub (Sep 4, 2023):
Feel free to submit a PR for this.
If you don't know how to code: feel free to open a feature request and lets see if the community likes the idea and if someone else is willing to pick it up.
@jnimmo commented on GitHub (Dec 22, 2023):
Appreciate all work by Actual's contributors, personally this isn't a feature I see myself using so the extra button just makes the display a bit busier, might've been okay to stay as an experimental feature?