get rid of all obsolete / policy-violating stuff so no part of the Facts application is broken;

og:title should probably be the post title.

Looks like Twitter's dialect of og tags is slightly special, but nothing too crazy:

This would also be great for Phame, so that sharing a link to a Phame post results in a title card when shared on Twitter.

I believe charts in the UI now make physical sense. They aren't very fancy/polished yet, but everything I see on this install looks cohesive (no more overlapping negative areas, weird gaps, general nonsense, etc):

The "compose(...)" function won't select input values correctly if the first function in the chain isn't a data function. For example, if we compose:

D20814 combines nearby points so we don't have tons of overlapping tiny circles. For now, the grouping is just based on X-axis distance:

In stacked area charts, when we stack areas, we accumulate some error by stacking integer points on top of interpolated points.

if prototypes are disabled, some stuff is broken, particularly "View Chart".

At the lowest levels:

This needs a lot more work, but here's very roughly where I'm trying to go with this:

D20808 fixes the two original cases (Harbormaster and Legalpad). There are probably more fields or actions which could be configured to be sometimes-unavailable, but these are probably the major ones.

For LDAP, brew install openldap + --with-ldap=/usr/local/opt/openldap/.

Here's the fate of the various issues discussed here:

This should be reworked some day (perhaps partly here) into some more cohesive API, perhaps newLink().

One other thing is that PhabricatorApplicationPolicyChangeTransaction->renderApplicationPolicy() has unconventional behaviors which are not very helpful and not consistent with normal CAN_EDIT / CAN_VIEW transactions. This is somewhat perplexing because ModularTransactions has renderPolicy() already, which has better behavior. I think it didn't exist yet when Applications modularized in D17757, and when it was introduced in D19829 I just overlooked the opportunity to update it.

In Applications → (Pick Something), if an application policy is set to "Custom Policy", the policy is not linked.

I upstreamed this to Chrome here: https://bugs.chromium.org/p/chromium/issues/detail?id=1003002

I understand this was supposed to be mentioned here: Herald ignores commits that are ancestors of permanent refs if they were previously pushed to some other non-permanent ref.

0.00000000001 is very funny and we would be losing a truly great joke at such a young age

Left Nav

There may also be no Application in contexts where we want to render a global search menu, notably the 404 page: