Is this causing a problem?

I don't know which department would be able to respond to this feedback. Perhaps release management??

Your Firefox user agent has the same 20100101 time stamp: Gecko/20100101

jscher2000 said

Is this causing a problem? I don't know which department would be able to respond to this feedback. Perhaps release management??

causing a problem? not that I know of yet.... I have keeped my copy of crash reporter symbols up to date... but the time stamps are out of date..

cor-el said

Your Firefox user agent has the same 20100101 time stamp: Gecko/20100101

I see what you mean... I looked up mine in About:config... I wonder why this is the case...

In the case of the user agent this is a decision to anonymize the user agent.

• https://hacks.mozilla.org/2010/09/final-user-agent-string-for-firefox-4/

There is more to come:

• bug 1559747 - User-Agent string needn't reveal a user is running 32-bit Firefox on a 64-bit OS
• https://www.soeren-hentzschel.at/firefox/mozilla-entfernt-architektur-information-aus-user-agent-von-firefox/

I don't see the point of doing that... Firefox Devs need to know what version of Firefox a crash was used on plus for other reasons too probably...

Melchior (aka Joseph) said

Firefox Devs need to know what version of Firefox a crash was used on plus for other reasons too probably...

If your Firefox crashed this year and you submitted a crash report, you can use the "View" button for a report on the about:crashes page to see what information the crash reporter is able to gather. It's definitely not limited to what is in your user agent string.

The Telemetry environment shows all data that is included in the crash report in JSON format. This includes processor (CPU) and OS information and display (graphics card and monitor).