Marc Glasser
Marc Glasser
Is [this issue](https://github.com/Expensify/App/issues/51449) still necessary if we stop redacting the chats themselves and start redacting the messages instead? 🤔
Yes, looks good. Let's update the Issue description with the new details? I can get started on this tomorrow.
Made some progress on this one today. We are returning these messages via various different paths... it could take some time to track down all of it. e.g. the search...
Almost wrapped on this one. Seems like `ReconnectApp` and pusher updates are not accessible by supportal so no need to worry about these flows.
Put this into review today.
>populate their onboarding/ConciergeDM with the invited member set of tasks Just for reference... what are these exactly? Is this built already or a new set of tasks we are showing?...
>if someone tries to access information in Supportal that has been redacted, all they see is ongoing spinners. I think we can definitely show a generic error in the case...
Looks like we have logic [here](https://github.com/Expensify/Auth/blob/4a0789d4ed4b794be13f838d9c56852c0e639b60/auth/command/OpenReport.cpp#L209C1-L212C1) to return "nothing" but not to throw any specific error message. Here's one proposal... Supportal can't access something we can return a specific jsonCode...
Oh yeah also I think it's `411 Insufficient privileges` for OldDot... let's see...
Oh wait no, that is a pretty generic one... I'll come up with something 😄