[Globz]

Yes I agree, encrypting the stack trace enable them to share sensitive server side error codes to the client which in return can be easily reported back without having to explain anything or try to decode cryptic custom error messages.

This is fantastic!

[jtchang]

I actually thought it was a bit jarring. Mostly because I don't know what personal information it might be collecting and having me send them.

[shawnz]

Well, it's information collected at the server side. So if they really wanted they could just store the data and give you a code, but that would require more storage on their end.

[ReverseCold]

(sorry for the sarcasm but...)

Oh no! YouTube needs to store a few kb of text! How will they have enough space?

[pkulak]

Well, it obviously only happens when something goes wrong. Seems valuable to keep the complexity and external dependencies of your error handing to a minimum.

[DelightOne]

Maybe its + a placebo since already stored in storage system + ability to see an outage maybe dropped in the filters cause it was assumed its not user-facing and so assumed lesser severity + assurance incase storage failed due to server-storage network unreachable

[agumonkey]

Also probably a unique hash too