In T4214#120383, @qgil wrote:

What I didn't explain is that this Phabricator header was one of the most contentious topics among some of our most experienced volunteers and some of my managers too. They were happy to fork the header and assume the cost of maintaining the local code. I calmed the discussion by promising that one day this will be fixed. So yes, communities care about their logos.

PS: if my story encouraged you to lower the priority from Normal to Wishlist, maybe I should have done something different on my Friday afternoon. :)
PS2: The "spooky eye" is not an hypothetical expression, I'm just quoting. In any case, as of today it doesn't compete with the popularity of the "Phabricator" wordmark.

In T4214#120376, @qgil wrote:

We call it "Wikimedia Phabricator" and our community talks about "Phabricator". Therefore [Wikimedia logo] + "Phabricator" makes sense, while "[What is this spooky eye?] + "Wikimedia" will create more confusion than the vanilla Phabricator header. I think the perceptions in other communities using Phabricator will be similar. All of them know their own logos, and all of them will recognize "Phabricator".

I think that Phabricator should be "white label" software that anyone can take and quickly configure so it looks like it comes 100% from their own organization. That way, new users won't have any idea they are using Phabricator, and will instead think their own organization has some sweet tools, or in the SaaS competitor case, that SaaS competitor A really builds some great software!

See T8516 for the "detect misconfiguration better" task.

In T8453#120118, @tao_qiping wrote:

Sorry I raised T8436, as this ticket is focus on search custom field. so I re-open it again as I still can re-repro it on list field, below is my custom field. can u please verify a list field to see if it is fixed, if so I may need to update my code to latest.

"tke:system": { 
     "name": "System", 
      "required": true, 
      "type": "select", 
      "search": true, 
      "copy": true, 
      "options": [ "", "SharePoint", "Agent Appointment", "Agent Registration", "AR Overdue", "Business Travel Approval", "CAPA (Corrective Instruction)", "Cash Advance Approval"]
      }

One new piece of tech: made it easier for Editors to raise DuplicateKeyException as a normal ValidationException, so callers don't have to handle this case specially.

Just double checking the images that comprise a mock are also "space'd" properly by this change.

Can you take a step back and explain a bit more how you and your team is using Conpherence? Basically, I'm trying to understand how come there are so many active threads at once for an individual and what the nature of these threads is...?

This is just a regression caused by D13058.

But how will you get SEV0 bugs if you don't dabble in infinite recursion?

It looks like the site only gets to send one desktop notification at a time?

Taking it out of your queue for now.

Oh whoops, I guess I took awhile to submit that comment and missed the update notification. :/

That is an example URI and would be different for your Phabricator installation. For example, for this installation, https://phabricator.example.com/oauthserver/client/create/ is https://secure.phabricator.com/oauthserver/client/create/

Just filed T8488 which may make this better.

Submitted that a bit early. Basically I think the distinction here is adding some confusion. Very very open for discussion. :D

See also T7589, which for the durable column plans to improve the recent room / messages switcher.

This is again by design. @chad - please note this task.

That sounds fine to me, but I think I iterated to @chad's dream state... I actually think we used to have "(No Title)" or something for a time...

Thanks for the persistence @sshannin. :D

(confirmed did not repro when I made another new task either)

Repro'd for me then I edited the field and it didn't repro anymore. Maybe I had a daemon error or something, or all the changes here fixed it?

I'm updating my instance but will confirm it still repros when its back up

{"mycompany:estimated-hours": {"name": "Estimated Hours", "type": "int", "caption": "Estimated number of hours this will take.", "search" : true}}

That mfilter() pattern is (was?) in many an editor me thinks...

I'm not saying its the best design in the world, just that it was intentional. Also, this install would have tons of junk rooms if it was as easy to make as a message, and I don't think enough value would have been created to offset all that spam / giant junk listing of rooms to wade through for all users for all time. This is just this install though and maybe frequently creating new rooms / making sure new users know how to make more than one room first thing right away is important.