Ever since the profile redo, the age was shown in the network profile, but not in the per-site profiles. So if someone wanted to see the age, they had to go to the network profile. However.. It's vanished! The field is still there in the profile editing, however. It doesn't appear as if this was implemented: Isn't it time to remove the age from network profile?

So... Where is it?

  • Hmmm a change to se.com was just pushed out earlier today. Maybe we finally removed it. – animuson Apr 11 '17 at 20:34

That was an oversight - we removed Age from Profiles ages ago, but still had the code in. When looking at removing the code completely, I saw that SE.com still uses it, and we removed it there as well now.

  • So the only way to see age is to go to Area 51 now? – Mithrandir Apr 11 '17 at 21:05
  • Age really should not matter, so it's a good thing. @Mithrandir. – Shadow The Dragon Wizard Apr 11 '17 at 21:06
  • @ShadowWizard - yah, but if you're removing it, might as well remove it everywhere. – Mithrandir Apr 11 '17 at 21:07
  • @Mithrandir Area 51 is.. different. But feel free to start a new feature request asking to remove it there. :) – Shadow The Dragon Wizard Apr 11 '17 at 21:10
  • Removed it from Area 51 as well, good catch. It is still in the SE Data Dump because people use those for larger scale data analysis. – Michael Stum Apr 12 '17 at 0:17
  • 1
    Is this now also removed from the database itself, as result of GDPR? It broke SEDE... – Shadow The Dragon Wizard Jun 4 '18 at 8:24
  • @ShadowWizard define "broke SEDE"? what exactly are you seeing? but: yes, gone – Marc Gravell Jun 4 '18 at 11:24
  • @MarcGravell all existing queries that contains the age column now throw error, and there are thousands of those, many linked around in many places. Why not just clear the data and leave it blank? – Shadow The Dragon Wizard Jun 4 '18 at 11:27
  • @ShadowWizard There are also many queries that filter and group by this. I opted to not silently break these. Since SEDE is also the source of the data dump, we also don't want a forever null column propagating there. There's also having to explain "well...it's there but..." every so often. Given that users are able to fix the queries on their own, I'm okay with this decision. – Nick Craver Jun 4 '18 at 12:03
  • @NickCraver thanks, can you please also post it as answer here? – Shadow The Dragon Wizard Jun 4 '18 at 12:30
  • Also curious about "chain of pings" here... has Michael pinged Marc to come and take a look, then Marc called Nick? :) – Shadow The Dragon Wizard Jun 4 '18 at 12:32
  • I just happened to see it in our chat. I look through about 34 info feeds for items each Monday morning. – Nick Craver Jun 4 '18 at 15:29

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .