|
moderated
Re: Configurable date and time format options
On Thu, Jun 21, 2018 at 09:27 pm, Shal Farley wrote:
Don't know why we cannot state it as a scientific notation in declining order of importance. 2018-06-22 17:18 Even though, my favourite to eliminate ambiguity is 2018-Jun-22 Arno
|
|
|
|
moderated
Re: Configurable date and time format options
On Thu, Jun 21, 2018 at 06:21 pm, <bruce.bowman@tds.net> wrote:
Retracting my previous post. One must hover the mouse over the date or time for a longer than typical PC time to get a reaction. Arno
|
|
|
|
moderated
Re: Configurable date and time format options
On Thu, Jun 21, 2018 at 06:21 pm, <bruce.bowman@tds.net> wrote:
It's already there. Just hover your mouse cursor over the displayed date/time Bruce as I had mentioned somewhere else, hovering the mouse over the date in the daily digest does absolutely nothing. Arno
|
|
|
|
moderated
Re: Configurable date and time format options
ISO 8601 for that would be 2003-03-09. If you're going to put theI agree with Shal. I also think it's important to make the ISO standard one of the options. One of the big benefits to ISO 8601 is that an alpha sort on date will also fall in chronological order without any manipulation. Dano
|
|
|
|
moderated
Re: Event: Data center power loss #outage - Wednesday, 20 June 2018
#cal-invite
#outage
Mark,
Thanks for the update and if you don't mind, I have a few comments (having been a data center manager in a past life). 1) Yes, by all means fix your notification system that pages you if it can't connect. 2) You should be concerned using a single data center in Femont, CA (if that's where it is) which is directly on top of the the Calavera's Fault - considered the most likely to generate a significant quake in the Bay Area 3) I'm surprised that a commercial data center, as I presume it is, does not have automatic backup power that instantly swaps to battery when the PG&E grid has a hiccup and then the batteries run the system till diesel generators start up and kick in. Perhaps a different data center company should be looked at. 4) Having said all of that, this is a "messaging" system. It's not a hospital or bank card processing system, or airline reservation system. So, having an outage for a few hours once in a while is not the end of the world. It is an inconvenience at best. Now, an outage of several days or weeks as Yahoo had a month or so ago is a big deal (and why I moved from Yahoo to Groups.io) and must be avoided. This should be of special concern with a datacenter on a major earthquake fault. Contracting with a data center company which has multiple sites across the country and offers 24 hour recovery at an alternate data center site is something you should look into. In these plans the data center company is on the hook to perform the transfer and recovery when a failure occurs (including IP addresses and all the other details) - not you. Moving that responsibility to the Data Center outfit may be way easier than building your own multi-center architecture. Anyway, just thought I'd chime in. Cheers -- Dan
|
|
|
|
moderated
Re: Configurable date and time format options
Mark
toggle quoted messageShow quoted text
good work In the database option date columns are still mm/dd/yyyy and times are 9.00pm not a great issue but would be good to be consistent. Chris
On 22/06/2018 00:39, Mark Fletcher wrote:
Please let me know if you see any incorrectly formatted dates/times, and please let me know if you have any questions.
|
|
|
|
moderated
Re: Configurable date and time format options
Gerald Boutin <groupsio@...>
On Fri, Jun 22, 2018 at 03:45 am, Gerald Boutin wrote:
On Thu, Jun 21, 2018 at 09:27 pm, Shal Farley wrote:I also meant to also say that I actually see 09/03/03 - not 09-03-03, for previous years and Jun 14 for previous dates this year. -- Gerald
|
|
|
|
moderated
Re: Configurable date and time format options
Gerald Boutin <groupsio@...>
On Thu, Jun 21, 2018 at 09:27 pm, Shal Farley wrote:
I'm seeing 09-03-03 - that's just wrong. It at least needs to be four digit years so one has a 50-50 chance of guessing which field is which.I totally agree that 09-03-03 is definitely wrong. Weird punctuation is not going to correct the issue. The format needs to be non-ambiguous. I am all for ISO 8601, but would live with Jun 22, 2018. -- Gerald
|
|
|
|
moderated
Re: Configurable date and time format options
Mark,
And dates you can display ... or DD-MM-YYYY.Reaching back in classmate group's Messages (and Topics) lists, and the messages themselves, I'm seeing 09-03-03 - that's just wrong. It at least needs to be four digit years so one has a 50-50 chance of guessing which field is which. ISO 8601 for that would be 2003-03-09. If you're going to put the day first please ditch the hyphens. Use dots or slashes or something else to indicate that is a non-standard format. Shal
|
|
|
|
moderated
Re: Messages, Oldest First?
Click on “Date.”
toggle quoted messageShow quoted text
Not a subject for beta. Sent from my iPhone
On Jun 21, 2018, at 6:40 PM, Sharon Villines via Groups.Io <sharon=sharonvillines.com@groups.io> wrote: --
J Messages are the sole opinion of the author, especially the fishy ones. I wish I could shut up, but I can't, and I won't. - Desmond Tutu
|
|
|
|
moderated
Messages, Oldest First?
Sharon Villines
My lists are appearing with the oldest messages first. I have a vague memory of a setting for this but can’t find it. Showing messages from 2000 first and have to scroll through almost 18 years of messages is not good.
toggle quoted messageShow quoted text
Sharon
On Jun 21, 2018, at 9:21 PM, bruce.bowman@tds.net wrote:
|
|
|
|
moderated
Re: Configurable date and time format options
Sharon Villines
What about saving the time the message was sent in all the messages? It's already there. Just hover your mouse cursor over the displayed date/time at upper right.It isn’t on any of my lists. Sharon
|
|
|
|
moderated
Re: Configurable date and time format options
On Thu, Jun 21, 2018 at 06:16 pm, Sharon Villines wrote:
What about saving the time the message was sent in all the messages?It's already there. Just hover your mouse cursor over the displayed date/time at upper right. Bruce
|
|
|
|
moderated
Re: Configurable date and time format options
Sharon Villines
What about saving the time the message was sent in all the messages? I’ve already had an instance of having to prove the times of of messages. That’s how I discovered that they were not saved past the day of the message. Sharon From: Mark Fletcher <markf@corp.groups.io> Reply: main@beta.groups.io <main@beta.groups.io> Date: June 21, 2018 at 7:39:11 PM To: beta@groups.io <beta@groups.io> Subject: [beta] Configurable date and time format options
|
|
|
|
moderated
Configurable date and time format options
Hi All, In your account, on the Preferences page, the Relative/Absolute time preference has been removed. In its place are two new preferences, for how dates and times are displayed. You can display times either in standard format, or in military (24 hour) time. And dates you can display either MM/DD/YYYY or DD-MM-YYYY. Dates formatted this way only shows up for dates that are older than this year. Otherwise, we continue to use 'Month Day' or, for something that happened on the current day, just the hour and minute (the complete date/time is available by hovering over the date). The calendar does respect the new date preferences. At some point I will also add these preferences to the default sub settings for groups, but this was already a big change, and I wanted to wait and let the dust settle before I do that. These changes touched every part of the website. I think I got all instances of dates and times, but there's a chance I missed some. Please let me know if you see any incorrectly formatted dates/times, and please let me know if you have any questions. Thanks, Mark
|
|
|
|
moderated
Re: Event: Data center power loss #outage - Wednesday, 20 June 2018
#cal-invite
#outage
I found the web site not working this morning, too, and checked the useful status page to see what had happened. As a recent immigrant from Y! Groups! I continue to be pleasantly surprised by Groups.io. It's not that it never goes wrong, although it's far more reliable than Y!, but that the level of information available is far better. This seems the right moment to say Thank you to Mark Fletcher for his dedication and competence.
- Mark, Cambridgeshire, UK
|
|
|
|
moderated
Re: Event: Data center power loss #outage - Wednesday, 20 June 2018
#cal-invite
#outage
On 21 Jun 2018 at 9:52, main@beta.groups.io Calendar wrote:
"Data center power loss #outage" EventThanks Mark. Yes we noticed this here in the UK - I realised a message I posted on a group hadn't gone through then since I needed to check bouncing status on one of our members found the website was off line. But it was up again soon after breakfast so most of our members weren't even aware. As you say, it is so rare that you probably don't need to address it. But I imagined you would be having a rather disturbed night's sleep over there in the States... 73 Dave G3YMC http://davesergeant.com
|
|
|
|
moderated
Re: Event: Data center power loss #outage - Wednesday, 20 June 2018
#cal-invite
#outage
Thanks for the update Mark. Have you considered a resiliency product to replicate into the cloud so it auto fails over your systems .
|
|
|
|
moderated
Re: Event: Data center power loss #outage - Wednesday, 20 June 2018
#cal-invite
#outage
Mark,
Thanks for the invite to this outage. Darn, I missed it! ;p Seriously: as long as no data was lost, I agree with the low priority. Thanks for the info! -- J
Messages are the sole opinion of the author, especially the fishy ones. I wish I could shut up, but I can't, and I won't. - Desmond Tutu
|
|
|
|
moderated
Event: Data center power loss #outage - Wednesday, 20 June 2018
#cal-invite
#outage
main@beta.groups.io Calendar <main@...>
Data center power loss #outage When: Description: Summary On June 20 at approximately 9:30pm, Linode's Fremont datacenter lost Internet connectivity, effectively taking the site off-line. Connectivity was restored after midnight, and the site was brought back on-line around 12:39am on June 21. Linode says that a power outage was responsible, but that's all the information they've given. More than half of the machines in the Groups.io cluster were rebooted during this process. All machines came back up without issues. Action Items I was not paged when the site went down; I happened to notice it at about 10pm. The system I use to check whether the entire site is reachable failed to notify me in this instance. I need to fix that. Groups.io is hosted in only one datacenter. To avoid this type of downtime in the future, a multi-datacenter setup will be needed. I have a technical path to get there, but it greatly complicates the system. Given that this is only the second time in four years that the datacenter has gone down, moving to a multi-datacenter setup is low priority right now. Thanks, Mark
|
|
|
