In T15948#21505, @Cigaryno wrote:

In T15948#21503, @Cigaryno wrote:

There must be a function that allows Conduit methods to be used by logged-out users. It's just that there are hardly any methods using that function.

There must be a function that allows Conduit methods to be used by logged-out users. It's just that there are hardly any methods using that function.

I think this makes sense - Mark All Read is about marking all search results read. (I assume; I never used it. But that's what the UI implies, it being grouped with e.g. Use Results which is definitely about doing things with the search results.) So no search results -> nothing to mark as read. The bug is in not getting any results.

Fix the URL.

If there's interest, I revived hach-que's old Docker setup and am updating it to work with Phorge because azure devops is killing my soul at work. It's suitable for both local dev environments (T15011) and production installs, and I'll be supplementing the repo with IaC for a production deployment (T15928).

I have also noticed this issue when submitting updates to a revision -

I agree that the hover behavior could be improved. Showing only after a delay could help here, though that would make it slightly worse for the times you actually want to interact with the hover.

I created D25895. Reviews welcome.

Knowing rHP will be replaced by R10, I will submit a patch to close this task.

Thanks revi. Dear @dereckson probably your nice installation is still on the legacy Phabricator? (or a Phorge before 2023 Week 17, accordingly to wiki search results)

Cannot repro on current stable (rPd3c0a7edc3fc and rARC05abd055019c as of today). Tested on local installation.

I've added the existing translations repo to https://we.phorge.it/w/community_resources/ since that's trivial. I agree something better should be done.

I think the best extra other than brush your teeth three times a day (which not everyone likes) would be review this agreement every week.

I found a number of Phabricator references in comments and error messages in \phorge\support\startup\PhabricatorStartup.php. See D25857: Replace some Phabricator references in PhabricatorStartup.php on comments and errors.

I think that for the "the name I use is not my legal name" use-case, I'm pretty sure it's fine to use the name that is actually used (because that's what the person is normally known as). It's probably easier to justify accepting a name that is used in real life then "internet handle", but ㄟ( ▔, ▔ )ㄏ

What do other CLAs do about this?

I'm... honestly not sure, I haven't signed one before. If I had to, I'd ask the maintainers before doing so ^^;

In T15121#20192, @BlankEclair wrote:

Would the CLA have to be signed with one's legal name?

Would the CLA have to be signed with one's legal name?

If I were starting today I would probably design the back-end APIs first, then make the web interface derive from those APIs, such that web requests and api requests are not really any different, at least with regard to enforcing access controls.

It seems to me that in general more information should be added to the main page: screenshots, main features, as is usually done in other large projects.

Supporting PHP 8.4 (currently planned for 2024-11-21) will require PHP syntax introduced in PHP 7.1 per T15935.

Also related: T15025

Well, I doubt we can dig more than this.

I do not understand this thing more than this. Help welcome.

I have this look on Windows for

a {
  outline-style: auto;
}

Last Chrome	Last Firefox

This is the same as Q132: Why is there an `outline-style: none;` declaration for all links within Phorge/Phabricator?

@avivey that's an excellent observation.

That "don't sign a CLA" article should be titled "don't sign away your copyrights", to be more accurate and less click-bait-y. A CLA may ask you to sign away copyrights (which I feel makes the project non-open-source) ; It doesn't have to.

I'm pretty fine with DCO (which I already do every commit via the git commit -s command) — but I'd rather not sign a CLA. (I’m pretty undecided if I will sign phorge's CLA, but phorge is not commercial entity seeking to mongodb/terraform/elasticsearch-ize the software (read: make a profit from open source, then turn it into All Rights Reserved) so I might do so… after all these incidents I'm rather wary of it.)