cf a very similar discussion about default fonts in GNOME at https://gitlab.gnome.org/GNOME/gsettings-desktop-schemas/-/issues/52 regarding aspects to take into consideration

I'm triaging as "wishlist" for now, but realistically - I don't believe will ever reach a point where we'll try to fix this -- see https://secure.phabricator.com/T13154 for discussion.

Marking as "obsolete" because this has graduated to T15722

In D25501#15033, @valerio.bozzolan wrote:

Maybe we can simplify things introducing a commodity "if viewer exists" method like:

This seems reasonable.

Noto seems like a reasonable choice. I personally really like DejaVu Sans a lot.

Or what about Inter? It is open source and looks very readable: https://rsms.me/inter/

So apparently the ferret search engine doesn't really have any sort of dynamic ranking. The ranking is entirely based on how many ngrams match the query...with one singular exception - all user results are boosted above everything else.

I'll try to figure out a architecturally-appropriate way to do this. The users do get grayed out in the typeahead search, just not on the results pages.

can confirm, https://we.phorge.it/D25342?id=1111 does show an error for me in an incognito window.

Probably, something should "Attach" these files by default to that Diff, during the upload phase.

A workaround is to make all files as "Public". I fixed for example the diff D25079: Trigger: Add Sound "Coin" by setting the audio file F1271256 as public.

What a lovely day to run a git rebase master to shine

Partially related, from the mentioned search it's easy to recognize closed Tasks, but Users are not greyed out when Disabled.

I’m not sure about Permalink being a top-level button. Maybe under the View Options menu?

This basically works

In T15726#15436, @Matthew wrote:

My concern with removing the applications outright is that they may be in use. Something like ChatLog was deprecated for years before it was removed. I think it might be smart to leave it deprecated for a couple of months.

Another thing: deletion of transactions. If by some misfortune they're around, they mess up during certain things, like T15125.

In T15726#15431, @valerio.bozzolan wrote:

Should we deprecate these first, before complete removal? (if easy)

I never totally understood what the jobs of Fund and Phortune really were, and they weren't explained very well in the documentation, as if they were very Phacility-only tools that happened to be in Phabricator.

@valerio.bozzolan Thanks. I guess I owe you a drink next weekend :)

Believe me or not but I've spent 15 intense minutes to use my big eyes to check all 571 files to catch whatever line that had not the very same class name A/B.

@valerio.bozzolan: Which problem would that solve? :)

Should we deprecate these first, before complete removal? (if easy)

I have landed my solution.

Old upstream WONTFIXed this in https://secure.phabricator.com/T13154

Test Plan still to be fully executed thus setting "Plan Changes"

In D25529#15137, @aklapper wrote:

I admit I did not test what happens when setting a (deprecated) timezone in Phorge to be removed by this patch, and then applying this patch.

Makes sense.
Fund: Going to http://phorge.localhost/fund/create/ and creating a New Initiative anyway yields

EXCEPTION: (RuntimeException) Undefined array key "totalAsCurrency" at [<arcanist>/src/error/PhutilErrorHandler.php:273]
arcanist(head=master, ref.master=6c7caf3572f4), phorge(head=master, ref.master=c0191a039293)
  #0 <#2> PhutilErrorHandler::handleError(integer, string, string, integer) called at [<phorge>/src/infrastructure/storage/lisk/PhabricatorLiskDAO.php:345]

+1 for "delete". Also Fund (which is basically a demo for Phortune).

I admit I did not test what happens when setting a (deprecated) timezone in Phorge to be removed by this patch, and then applying this patch.

I believe it was originally made for Phacility to accept donations and then process payments for paid support, neither of which we want at Phorge, and I doubt is used elsewhere. Removing seems fine to me.

Counter-diff: Keep the hackiness confined

The more I look at the code, the less I understand the comment about "just use getIsNewObject()".

In D25517#14978, @valerio.bozzolan wrote:

In an ideal world 1030-1313 could become just:

I was able to recover the layout in PNG at least. Imagine this 3''x2''. Here:

I'M REALLY SORRY FOR WHAT YOU ARE GOING TO SEE - I'M NOT A DESIGNER