Leaving aside the rejection of the photo, what do you think of the date of the last edition?
in computer science, itâs common to store dates in âunix timeâ which is the number of millisecond since midnight January 1 1970. if no value is found then that zero value is used instead. I was hoping the team would do something different in this case but they havenât.
This photo was submitted 2020-10-11. Computers store dates as year-month-date so itâs sortable. (Same as writing our numbers as: thousands, then hundreds, then tens, then ones. List things biggest to smallest. Makes them sortable.)
So, your 10-11 resolves to October eleventh.
1970 is just part of the wayspot title. Are you saying the building looks a lot older than that?
Half of my edits are displayed with âlast modifiedâ date 14/09/2022, which is probably another milestone similar to unix time, or a bug.
Whatâs even more strange, recent accepted photo edits show that last modified date, i.e. portal was definitely modified after the date displayed as âlast modifiedâ.
Yeah, takes me back to the days of using SAS for analytics (omg I miss it). All dates were really just a number referencing time elapsed since 1/1/1970 with a format over the top so a human could read them
Definitely looks like a default for âthis hasnt been modified yetâ. Even if it has⊠because, well, why would the last modified date be accurate anyway?
Looks like a quick update of the page to remove last modified date till it can be fixed might be handy 
â1970â is not a part of the title. The wayspot title is âCasa Lopez Fontâ. The point in question here is of the odd dating of the last edit; which is â1 ene. 1970â (a.k.a â1 Enero 1970â). That is an odd date to see, but @tehstone is correct on the unix time/milliseconds point. My best guess is somehow the timestamp mustâve been stored incorrectly on the backend server, so it either was saved as a 0 value in the database, or something else is wrong and it is defaulting to the 0 when serving the timestamp from the database as a way to account for the issue.
The last modified date is the date Niantic last modified it, not the date that the community last modified it. The text is incorrect.
(This field used to change after community modifications back in the OPR era but not any more)
Based on research I did last year, here is what affects that value:
Generates an âUpdateâ Timestamp
- Live â Retired
- Retired â Live
- Description change via forum appeal
- Title change via forum appeal
- Location edit via help chat
- Niantic changing a photo (e.g. photo removals)
- COTW imports
- App Provisional â Rejected/Duplicate
Does not generate an âUpdateâ Timestamp
- Wayspots accepted by community (including app submissions)
- Photo accepted by community
- Description edit accepted by community
- Title edit accepted by community
- Location edit accepted by community
- Niantic accepting an appeal
If none of the things that âgenerateâ a last updated timestamp have occurred, it will say 1970.
Does not explain why 14/09/2022 is displayed on half of my edits, perhaps it was the switch between lightship and ingress db, or my browser displays this date instead of unix zero date 
That must be the last time Niantic made a change.
I also have many Wayspots with the Sept 14th, 2022 last modified date on them, mostly on title/description/location edits still in queue/in voting. Interestingly, photo submissions donât have an updated last modified date if the photo has been accepted, such as this one:
I have found that if any edit was appealed and the appeal was accepted, it has a date around the time of Niantic making the change. I had title and description edits rejected by the community at the beginning of Janurary 2024 (I submitted them in Sept 2023). I appealed the rejections, Niantic approved my appeals, and the last modified date for both is Jan 19, 2024.
So, it seems as though there was some update done on Sept 14th, 2022 for the titles, descriptions, and locations. Photos are listed as submissions, not edits, so it looks like Niantic doesnât consider adding a photo to a Wayspot as an edit, thus they donât consider them as modifying the Wayspot.
Yes, itâs confusing, but this is also new, and there most likely wil be fixes over time.
It essentially means an Unix epoch time value of zero as stated in the first reply. This means January 1, 1970 at midnight UTC.
This most likely means thereâs no data for the value and the value of 0 is used in place when itâs a null value. I wouldnât worry about it as it looks to be not accepted.
I wonder if thatâs when Niantic Wayfarer started doing appeals?