In the global profile's activity tab, all "badge" and "accept" events are timestamped with (and sorted by) the user's date of registration on the associated site:
This was very confusing.
In the global profile's activity tab, all "badge" and "accept" events are timestamped with (and sorted by) the user's date of registration on the associated site:
This was very confusing.
Nice investigative work, you're absolutely right.
After a recent attempting at optimizing the network activity query, we were selecting the wrong CreationDate
column out of the database as the activity's creation date.
This is fixed now.