We don't do tracking tasks which achieve not purpose.

$wgManageWikiNamespacesAdditional?

Isn’t this already supportable?

Hi, this is the correct place and hopefully someone will get to it when they next have time to do so.

@RhinosF1 each extension having its own review task helps a lot with progress. 99% of the time we skim requests where reviews are bundled in and don’t do a lot because the time necessary to decide what we need to do outweigh the time we have usually

Extension seems fine.

In T4705#89877, @Paladox wrote:

@Reception123 no, he wants to use cloudflare which provides ssl certificates. He wants us to add his domain to his wiki i believe.

And the irony behind it is you made it out of date I believe :)

No change needs to be made.

In T4638#89191, @Reception123 wrote:

Stalling since unless a task is created/misc2 gets more memory there is nothing we can do about this task.

Not a security issue. Behaviour has been fixed in 1.34 I believe now.

In T4554#87790, @Southparkfan wrote:

The extension itself is safe, however I do not like the idea of our IPs being blacklisted because someone used reported non-spambots to the StopForumSpam site. I want to know what the other sysadmins think.

Not in git

T210

Re-open when review is possible @Paladox

Declining in line with previous issue.

How? That’s a request to make things translatable? That’s the only part which wasn’t translatable

None should be out of date?

What’s the tasks premise?

It’s a reduction of costs, it’s approved once we have NL. As said last night.

So we have two extremely similar issues, have we considered the link is infra or upstream and not two entirely separate extensions?

In T4625#87973, @Reception123 wrote:

Accessing Matomo web UI also indicates

SQLSTATE[HY000] [2006] MySQL server has gone away

In T4610#87885, @Paladox wrote:

Won't it be cached @Southparkfan by varnish ?

Should be resolved by now.

In T4613#87653, @RhinosF1 wrote:

In T4613#87651, @John wrote:

Also I don’t believe it’s realistically a security issue (that’s my opinion)

It’s borderline but we don’t know the full impact so Paladox said do so as a precaution but I’ll give you my definite opinion once I have time to review my records.

MediaWiki has atrocious handling of non existent accounts - makes a lot of sense but I feel like this should be an upstream issue to be addressed.

Nothing active on Miraheze, Security is not related

Seems fine but I strongly discourage things like this.

Priority of all dev tasks are low. It’s my highest prio task

A goal even declined is still a goal.

In T4370#87097, @Reception123 wrote:

In T4370#83365, @John wrote:

Creating “managewiki-{$settingname}-help” or -name in i18n config is how this is done.
Not a ManageWiki issue

So would the 'name' => in mw-config be replaced by "managewiki-wgAbuseFilterActions-name": "AbuseFilter Actions", in the ManageWiki repo?

Error: 1054 Unknown column 'log_comment' in 'field list'

We’ve had this extension enabled for almost 4 years.

I'm going to keep this task open for now since we're dealing with 2 separate lines of inquiry.

Anyone with Steward access can handle this.

We do ES or db5. Cost wise it’s one or the other.

No XSS.

Update?

Redis issue that was caused by a live hack which was reverted when this was reported originally and other times.

Few months left

While a valid issue, there is a solution for which a task already exists. Priority should be spent on that and if there still remains an issue, another specific task open for this.

This should absolutely have a policy before being possible. Blacklisting IPs should be a ToU action with regards to hosts only.

You were working on this yesterday?

In T4493#85255, @Void wrote:

Is there anything else that can be done in the meantime? Such as T4260? Any space we can get is space we need.