If I look at my contributions in the evening, contributions I had just made are given the date the next day.
Douglas, the FamilySearch website uses Greenwich Mean Time to compile reports, so depending on the time zone where you live, the calendar page may turn over to the "next" day before your local time.
I just left this idea. Use a scale to rate answers, like the popular 5 star method. Right now we only have the option to answer yes or no. This is inadequate. If we ask a 2 part question and the response only answers 1, then I can only say no. With 5 stars I could use 2, 3. or 4 for a partial response. I'm sure the question answerer would appreciate some credit rather none.
I would give you a 3 star rating. You didn't answer why. Having single time worldwide is sometime a good idea, but not always. I frequently want to see my contributions for a given day. I could if the report showed the time of a contribution. However, that would be a hassle and user unfriendly. The real solution is to make it a settings option to use GMT or ULT, user local time.
FamilySearch/Family Tree should be using UTC (see Wikipedia UTC).
I think this is an important idea.
@Douglas McPhaden Agreed that this is a good idea that should be posted in the ideas section on Communities.
I know they're technically different things (one's a time zone, the other's a time standard), but there is no difference between a time given in GMT and one given in UTC, so there is no practical difference between what FS currently does and what Douglas McPhaden suggested they do. It's like saying "instead of A, you should be doing A". What am I missing?
A Google engine search for 'why use utc instead of gmt' yields a vast number of hits. Some take the position that you do. They basically say GMT is fine with me. Scientists prefer UTC because it is more accurate.
Some software developers use UTC because their users are a world-wide group, and their domain requires more accuracy than GMT. Airlines and governmental aviation agencies use it to coordinate safety protocols. Stock exchanges use it determine time of trade.
The most important reason is to recognize and use is because it is a standard. Now the cost to convert is low. That may change in the future. It does not seem to risk much. And it would have 0 impact for you if adopted.
Also when using GMT it then applies to any person, living in any part of the world, because GMT is not local, it is universal.
Fascinating information. If I am understanding things correctly, UTC is the actual time, for lack of a better phrase, which can be expressed is a few dozen different ways, either as itself universally or for a limited portion of the earth as the time in a particular time zone.
This article: https://kylekatarnls.medium.com/always-use-utc-dates-and-times-8a8200ca3164 gives a convincing argument as to why programming should always internally use UTC but then goes on to explain how one can then have the displayed date and time be anything you wish.
So FamilySearch may very well be using UTC but converting it to the notation GMT when displayed as something more people are familiar with.
Going back to the report question, there may be some complications, both technical and legal, in using user local time to record events. First off, using user local time means that every time I make a reportable change, the program has to determine where I am in case I'm flying cross country and my local time zone is changing. Secondly, for every change the program has to determine if I have given permission to have my location known. FamilySearch does work to comply with the privacy laws of every country. I don't know what any of those are in regards to location services, but when searching for a local Family History Library, a box pops up asking for permission to use my current location and for permission to remember this for 24 hours.
Yes, this is all just speculation but I think, to give more speculation, that the only official answer from FamilySearch if you ever get one would be that 1) It's not worth the processing power that would be needed, 2) privacy considerations make this prohibitive, or 3) there are far too many more important things that need to be improved in the program right now.
I believe someone would have responded if FamilySearch uses UTC internally.
No need to update in real time. Save the latest. Put Users UTC in their profile, and ask the user whether to change, or not, before any change. This implementation obviates the possible answers you project. Processing consumption would be low. Most patrons would never need to change it, others would not want to change it often enough to require any measurable processing time. Privacy protection would only have to occur when a user has confirmed they want the change. The implementation cost here would be minuscule. It could be added to another task without appreciable time/cost impact on either.
I doubt there would very little user demand for UTC. But it would show a willingness to make small changes requested by a user.
Only the day is recorded not the time. The day for Family search begins and ends at midnight Greenwich Mean time. Surely the exact time is not critical for this record.
Historically, it is exceedingly rare for any actual FamilySearch designers or software engineers to make any comments on this board. Only with the recent update have support personnel been much involved here. So there is no reason to expect that anyone at FamilySearch that is familiar with the inner workings of the program itself will ever see your question. We have been reassured repeatedly that all ideas for improvement are funneled to them, but the only feedback from them tends to be that the suggestion either shows up a year or so later or it doesn't.
I want to see my contributions for a day. Can't do it now. Showing GMT hour makes it possible but very irksome. Local time makes it easy. Adding contributions by day, accounting for UTC difference would be great.