Picking it up now, waiting for CA… (sorry for the delay! Was bit sick IRL)

I've temporarily closed it to prevent editing (just in case ™ ). Feel free to unclose it to do something to fix it. It seems like you (the DBA) have to fix it internally - and you have my full blessings to do that. Let's see if it happens again....

If this is approved, can you change the CSP domain to wiki-assets.sumin.wiki which I purchased to disable Cloudflare logging if it was technically feasible? Thanks!

It looks like Cloudflare won't let anyone do that.

CF. https://phabricator.wikimedia.org/T29393 (private right now, asked WMF Security to make it public) was the closest thing I could find from upstream. (Note that its status is actually duplicate, not resolved) However it only added some security aspect of it, not the "confirmation check". You probably want to deal with Upstream because this is not really specific for Miraheze.

Both urls are essentially GitHub Pages proxied thru Cloudflare.

Also maybe *css*-wiki-cdn IIRC…

Also (somewhat related): The PSA for the Discord/Slack hook security issue is probably of no interest for vast majority of the users: only Bureaucrats can act on the stuff, and the readers from external links don't even care if there's discord or slack stuff. It is probably a wise idea to implement some hacks (i.e. Wikimedia Stewards Election Call for Candidates CN banner which is only displayed if you have sysop on the wiki) so those who are simply not affected can skip it even further. (Or think of a better way to alert crats without relying on sitenotice/CN)

In T6881#135941, @R4356th wrote:

If or when this is implemented, the global robots.txt's content should be added to the robots.txt file even if wikis do not keep them in their MediaWiki:Robots.txt as there may be global incidents caused by web crawlers otherwise.

In T6810#134137, @John wrote:

Midnight UTC for us, for other users of the extension, it would be whatever they configure it to be.

The wording as it currently stated is:

No, 3857647776 is from your old hosting provider. Miraheze system currently do not have any certificate issued to your domain.

Fastest and easiest way is LE. Actually, your hosting provider also uses Let's Encrypt.

I added two because I saw no alias.php (or i18n php for translation) but for any extensions by Miraheze.

Note that .org now has this banner. It's coming soon.™️

I ended up downloading r4356thwiki and conductwiki's NS 0 xml pages, but I certify that I deleted those pages after verifying the bug.

In T6561#128819, @Reception123 wrote:

Confirmed via Discord account that is verified. Will do soon

Wiki-bot is not going through CP9.

Most relevant:

Note that they will have time limit on .com infra.

In T6402#125392, @Wedhro wrote:

But it used to work flawlessly for more than 1 year and I made no changes (except from reverting vandalism).

Note that the CA has changed:

That is because Twitter uses Twitter Cards, not OpenGraph (which is Facebook protocol).

I made a payment of $5, and only $0.47 was charged. Looks like Linode charges $5 for refunds, so can someone just kill the account entirely? Thx.

Maybe this with OpenGraphMeta could work on wiki-level, but hasn't tested.

For clarity, my final payment date is 2019-06-01.

Seems there's no progress on cp3.

IIRC EasyTimeline is insatlled by default on Miraheze. The Meta's CoCC timeline is handled by EasyTimeline.