(Regarding the original task description:)

In T15110#2655, @avivey wrote:

I'll try to force the GC to run, maybe this will delete them.

But still it is worrisome that we can configure visibility only by Administrators, yet everybody can assign the project as subscriber... Maybe that is a bug ?

@rraval Right, i overlooked this setting. I managed to hide most projects from the Subscribers Search panel. We also have reduced the number of Projects to keep things more tidy.

@Higgs You should be able to Project → Edit Details → Visible To → Project Members. Does that do what you expect?

I'll try to force the GC to run, maybe this will delete them.

We use Projects for grouping users into teams. But unfortunately every user can see all Projects and assign them as subscribers to Tasks, regardless if they are members or not. Normally (in our case) Tasks are only relevant for users in the same project. Having the other projects displayed in the subscribers selection is unfortunate in this case.

Somewhat related - see T15050

Our instance uses a ton of projects as "groups of people that need to be notified", so we use project subscribers a lot.

We do have a security task creation form and a separate space that roots have access to. See S2

• remove favicon, update css in php

Favicons are somehow cached server side:
<link rel="icon" id="favicon" href="http://localhost.localhost:8080/file/data/jvpvboup37hwjgpn3viv/PHID-FILE-xhmdncm6ydmubbkrfdj4/favicon" />

I didn't want to do this, but I'm actually going to test this change.

celerify

Could it be cached?

looks like the favicon doesn't actually work :/

For the record, I am against this change.

@speck I made this task because posts in Phame uses an ID that starts with J, and tasks in Maniphest uses T for the URL too.
I just request that the URL for posts in Phame changes to be similar to Maniphest.

Could you elaborate on what this would help with? I recall reading something in Phabricator’s past that the current url scheme is intentional as opposed to using the monogram/slug. I did a quick search and couldn’t find much, though in this change release
https://secure.phabricator.com/w/changelog/2015.51/

Removed dedicated titles/slugs. Phame posts now automatically generate readable URIs, but the slugs are no longer semantic.

We should investigate the history related to the current URL scheme before making a change. My suspicion is that it has to do with phase posts being “public” or published where having a url with part of the title is very common for linking across other content.

This task may need to be triaged as high since we started by forking the Phabricator software, see also T15006: Re-brand Phorge.

Using a repository cluster for syncing repositories to two hosts I can push fine via ssh:

We should also change the internal name to the future name of Phorge, rather than leaving leftovers. Exmaple: Some code in Fandom is still named wikia.

lint

https://phabricator.wikimedia.org/D1203 is my fix for this issue at Wikimedia's install.

I'll see if I can reproduce this error.

LGTM

I got differential working under PHP 8.1 by doing a global replace of single parameter strlen commands to add the null coalesce operator

I've git-merged everything from upstream into our rP and rARC, so there's going to be a few new emails about commits...

I don't think we have this capability right now.