git rebase master

It seems H29 works lol. I've improved it a bit to do not trigger if the celerity map was already touched.

No problem! I'll send you my crypto wallet address. Once the money has arrived you'll receive your clipboard content as an NFT.

Yep thanks, I need my clipboard of the 12 of August 2024 to get back the "D25772" to copy-paste it here and attract hackers asd

My keylogger thanks you! Would you like to know anything else about your online patterns?

You clearly hacked my account lol

30 seconds for a review?! I think you broke a record.

git rebase master

Looks like a Good Starter Task.

In D25926#24899, @Cigaryno wrote:

robots.txt can have the solution for that (see below).
[...]
For search engines, the solution is to add this to robots.txt:

In theory yes if everyone behaved. In practice, robots.txt is ignored and LLM/AI crawlers are ruthless. (For example, GNOME GitLab admins recently installed Anubis to run background checks on your machine.)

(I cannot double-accept so only just one accept asd)

In D25926#24898, @valerio.bozzolan wrote:

• more search engine rabbit holes (but maybe not that bad)

robots.txt can have the solution for that (see below).

Uhm. Good points:

In D25926#24895, @aklapper wrote:

Why would a logged-out user (who does not want to or cannot create an account) want to know about Repository management log or Repository limits? I don't see how that's their business (or interest)?

In T15999#21434, @aklapper wrote:

Some items in the task description make me a bit uncomfortable in my instance.

I don't think you need to be uncomfortable on your instance (phabricator.wikimedia.org)
For Herald, it looks to be restricted to trusted contributors to restrict who can create personal rules (they actually can vandalize tasks via personal rules with the action set to claim the task), that's not something to take care of at all on your instance.
Project members, maniphest reports, user tasks and badges are actually useful for logged-out users.
But everything that's Diffusion-related sounds pointless for your instance as every repo is a read-only mirror of the repos on a Gerrit instance.

Why would a logged-out user (who does not want to or cannot create an account) want to know about Repository management log or Repository limits? I don't see how that's their business (or interest)?

Some items in the task description make me a bit uncomfortable in my instance. Why does everyone need to see Diffusion sync, pull, and push logs? Why Herald transcripts? Why repo management if you cannot manage? What are actual use cases which outweigh security implications?

In D25926#24890, @avivey wrote:

There might be some security implications to this.
Why is this needed?

There might be some security implications to this.
Why is this needed?

git rebase master

git rebase master

git rebase master

Makes sense thaanks, 0s seems also the documented default

Don't change URI path /people/tasks/{$id}/ of assigned tasks not to break potential external linking