Resolved enough.

Most browsers can only give us a timezone offset, like "UTC-7", not a locale name like "America/Los_Angeles". We already attempt to read this value (D15962, T3025#176547) but when I wrote that stuff it was only available in Chrome and not necessarily reliable. We do try to guess the default zone selection based on the information we get from the browser, but currently ask the user to confirm it in all cases.

I was thinking that the first time they log in, we just take the browser timezone and set the user config to that.

(Just closing this since we haven't seen an update in ~4 months and it isn't actionable.)

That didn't seem to be the case. It might have been because we only enforced Google authentication around one year ago, before that users could use a password for authentication. I can check later today, but perhaps the users that ended up with duplicate accounts never setup Google Auth.

If the only way to register is Google, it should be impossible to create more than one account per Google account.

Why is registration disabled?

It's just very
important to
thoroughly explore
the applications

This has been live for about two months without any substantive issues arising.

Ut seems to be T10145

Or if it isn't, please file a bug report.

This change didn't touch Dashboards. I think you want T10612 or maybe T10145?

I think this change broke dashboard editing slightly. Now when adding a panel to a dashboard column, the same panel gets added twice, once for each column. Removing either of the dupes removes both.

thx

You can today, just extend PhabricatorGuideModule and drop it in src/extensions. It should just show up.

Maybe it might be a good idea to allow people to create own Guides? Could be helpful for recuring setup stuff for newusers for example, like we got it at our instance.

Though I guess a "fake" dashboard is not as performant as actual dashboards. But equivalent to current hardcoded homepage?

Yeah, I think scope-wise this could get out of hand quickly and consume a month on both design and engineering. I think I can propose something here that will not take your time and maybe 1-2 days of mine.

I think we're on fairly firm technical footing on some specific changes, which I can probably lay the groundwork for and hand off to you to populate:

I have 7 panels for new Phacility Admin, trying to think of one last action panel..... .... .... memes?!? Good idea or great idea?

It's not 100% reliable but we can use that to make a pretty good guess.

We know if someone has set up arcanist, correct? They ran arc install-certificate?

In the general (Phabricator, rather than Phacility) case we could also suppress that warning while "NUX Mode" is active, for whatever "NUX Mode" means. Presumably, it's not important to fix until you get through whatever NUX flow we end up with. This would indirectly reduce the annoyance for Phacility instances, although sync is still better.