alt Hacker NewsHi, this is Max from Notion.
First: This is documented and we also warn users when they publish a page. But, that’s not good enough!
Second: We don’t like this and are looking at ways to fix this either by removing the PII from the public endpoints or by replacing it with an email proxy similar to GitHub’s equivalent functionality for public commits.
P.S: Some folks here have speculated that this should be a 1 minute fix. Unfortunately that is not the case. :(
Replies
What are you doing to address the process/structural issues that allowed such a privacy issue to get to production?
What are you doing to address the support issues that allowed such a privacy issue to remain after being reported?
What are you doing to address the issues with the company's prioritisation framework that allowed such a privacy issue to remain for 4 years?
Which authorities are you reporting the privacy issue to in line with local requirements?
> P.S: Some folks here have speculated that this should be a 1 minute fix. Unfortunately that is not the case. :(
4 years.
Can you share the warning? I made a public page and would say it was not clear to me this was a consequence of doing that. The warning as I remember it (a month ago) makes it sound like the information on this page is going to be public -- not - oh yeah the email addresses of everyone who edited this page will also be leaked.
I will speculate that Notion has had more than one minute to fix it.
While you're here, why is Notion so slow on Firefox? I mean extremely slow.
Considering it was reported in 2022, and it is obviously an error, I don't think it is unfair for people here to have expected it to be fixed by now since it was first reported.
This flaw was reported four years ago. Forgive me if I don’t believe a word of what you’re saying.
> P.S: Some folks here have speculated that this should be a 1 minute fix. Unfortunately that is not the case. :(
Nonsense! It is a 1 minute fix. You just don't want to take a $ hit from inconveniencing users by breaking another part of your app.
Pull your thumb out and do the right thing. Implement the 1 minute fix, and then spend the rest of the week or month fixing the other parts of your app that might break as a result of fixing this.
> P.S: Some folks here have speculated that this should be a 1 minute fix. Unfortunately that is not the case. :(
Ignoring the “the bug was raised four years ago” part and assuming you just mean it isn't as easy as that and might break other things: what other things could resolving this potentially break? If the issue is that the PII needs to be present for private/authenticated views, would not making it unavailable everywhere including there, and fixing that later, be the better option over leaving the PII present for public views for a second longer?