man I need the trusted role here

PR: https://github.com/miraheze/mw-config/pull/5716

In T12306#246501, @OrangeStar wrote:

Commenting a bit on the installation details, this looks like it could even be an unrestricted extension, unlike SMW and Cargo. I'm a bit concerned that it doesn't have 1.42 support yet, but the MediaWiki team can look at that after the review if it passes.

For someone more into verbose stuff, I can't get the extension to work in my "newest version of stack", since it specifically requires a lower version of PHP, which we can't support.

Has been a whiles is it...

So far, I have looked into ShoutWiki, Telepedia, and Fandom to see how we can approach the issue regarding integrating global profile avatars using UPV2.
The last PR on mw-config/#5645 already has these configs:

...
// UserProfileV2
'wgUserProfileV2Color' => [
	'default' => '#E1E1E1',
],
'wgUserProfileV2AvatarBorderRadius' => [
	'default' => '50%',
],
'wgUserProfileV2UseGlobalAvatars' => [
	'default' => false, //Take attention to this
],
...

AFAIK and understand, we have not even started to look into testing the extension in Betaheze yet. After researching those places, I see no reason for a global profile image for the entire Miraheze at the moment. Here I will close the task, and the extension should proceed to be installed (T12394) without global avatar capability. We may revisit this task after a while, which I can't decide, but so be it.

Reception merged the commit at mw-repo, the task would not be closed until:

• Configurations was also merged and propagated.
• Global avatar settings are set or removed by sysadmins. Abandoned 👍

Update: TranslateWiki has been integrated with the extension, and the upstream task has been marked as Resolved.

Just note to those who are working in the task, but this extension was made by @Original_Authority themselves, so someone else has to review it.

I'm closing the task until a more elegant way is discovered. Thanks to @BlankEclair (a.k.a Claire) for the solution:

I prefer to have the server do it for me as it is better to have it recognize the messages without any additional modifications to our wiki source code.

This also happened to my wiki too.

https://meta.miraheze.org/wiki/Special:RequestSSLQueue/2
Potental new feature?

For references, these links should explain my concepts here:

This is added as a reference:
UniversalOmega has already review the extension on his side and approved it. After the installing the extension and complete the initial setup that involves LocalSettings on our side, the MediaWiki namespace can be used to contain the Manifest.json and PWA-main-serviceWorker.js if configured correctly.

Request changed. Please process.

Oops, should be SSL since I control the DNS myself-

Closed as this is easy as changing some lines of records and we are done...

Let's get this thing end with...

And I though the tutorial is only apply to subdomain :)

If you say so...
And also I have checked the record. The nameserver is now from CF.
Looks like I'm will be fine if I done this as fast as I do.

In T10362#211165, @Reception123 wrote:

I will try to get this done soon but it could be sped up if you would find your wiki in https://archive.org/details/miraheze-wikibackups18122022.

Long time no see! Working on the OG wiki, feels good so far.
How is the restroration progress going 💀

Thanks, but it's just weird when I literally can't see the skin being there before calling for this task 💀

Let's hope we found them or have me a backup if Alzheimer haven't come to this part yet...

And man, the wiki is deleted 2 days before the closest .tar.gz backup...

In T10362#209652, @Reception123 wrote:

You don't happen to have a backup of the wiki do you? That would make things much easier/faster.

In T10362#209608, @Reception123 wrote:

Accidental close.

Now we wait someone to merge...

To be honest, I have no knowledge at these licenses, so as the only one who work on that wiki (and that IP address said above is also me), let's go with the CC-BY-SA 3.0.
And I make that final decision.

But unfortunally, as mentioned by Agent_Isai at Steward' noticeboard, I have to ask for a restore for lhmnfanon

I hate how much are CNAME flattering...
But yeah, let's do the fanon one...

And, you know what I mean, right? I can't just hang another .wiki subdomain and create another landing page that does not necessary, the SEO things...

How willing? I mean, I'm just wondering if they are capatible setting up URL redirect, as it's still, an DNS based settings... 🤔