(01-08-2026, 09:46 AM)Bob Schroeck Wrote: Just a heads up -- TVT has changed its anti-ad-blocker tactics again. Like they did a few years ago, they're now refusing to serve any content whatsoever when an ad-blocker is detected.

Unusually, it doesn't appear that this particular asshattery can be laid at the feet of TVT's administration -- it appears to be imposed from above by Chris and Drew or whatever holding company they own -- they also own Snopes.com, which is also currently displaying a notice that is virtually identical save for color and styling if you dare go there with a blocker active.

(01-17-2026, 05:09 PM)robkelk Wrote: So, Flow has been depreciated and replaced with DiscussionTools.

Assuming that we don't want to run unsupported software on our wiki, how do we migrate to DiscussionTools?

Miraheze Wrote:I wanted to share an important announcement about a major upcoming change to our login system. We are migrating to SUL3, the most recent version of MediaWiki's Central Authentication system. Once this change is live, all authentication related actions such as logging in, resetting passwords, and managing 2FA will take place on a new domain: auth.miraheze.org.

This migration does come with a few side effects that we want everyone to be aware of. All users who currently use WebAuthn will find it disabled after the migration and will need to set it up again. We previously emailed affected users about this a few weeks ago, so this is your reminder that this is expected behavior.

In addition, every user on the platform will be logged out when SUL3 goes live. This is expected and intentional. To avoid issues logging back in, please ensure the following before January 30:

• Verify that your account has a valid and accessible email address attached
  • Visit Special:ChangeEmail
    

Confirm or update your email address and ensure it is confirmed

• Make sure you have access to your 2FA methods or backup codes
  • Visit Special:AccountSecurity
    

Verify your current 2FA setup and locate your recovery codes

• Ensure you know your current password
  • Reset your password via SpecialasswordReset now if you are unsure
    

After the migration, you will need to log in again manually. If you use a password manager or browser autofill, you may need to update or re-save your stored credentials since authentication will now occur on a new domain. Being prepared for this will help prevent login issues after the change.

On the bright side, SUL3 is designed to resolve many long standing CentralAuth issues and improves WebAuthn behavior. You will no longer need to log in from the specific wiki where WebAuthn was originally set up, and random logouts should be greatly reduced. While there is still a possibility that some issues may occur, they should be far less frequent than under the current system. 

These changes will take effect on or shortly after January 30, 2026. Thank you for your understanding and cooperation.

(01-26-2026, 04:07 AM)Labster Wrote: Just in case you haven't seen it, a new Miraheze annoucement.

(02-08-2026, 03:15 PM)robkelk Wrote: Regarding this request and action

Where's the evidence? Flow doesn't allow undeletes (at least, not in any way I know about).

And the breakneck speed between somebody who has no edit history on the wiki asking somebody else be banned, and the banning itself, is reminiscent of Fast Eddie.

I can't force GethN7 to follow the rules that we've agreed upon, but I can do something about the other part of this. I am now calling for a vote:
In that it now is actively getting in the way of our administrative procedures, stop using Flow immediately.

(02-08-2026, 03:15 PM)robkelk Wrote: ... I am now calling for a vote:
In that it now is actively getting in the way of our administrative procedures, stop using Flow immediately.

Quote:The Wikimedia Foundation is on its way to undeploy Flow (StructuredDiscussions), after which the extension will be completely unmaintained. It has already caused issues with past MediaWiki upgrades on Miraheze, so we should remove it sooner than later.

The technology team plans to use an automated script to delete all Flow discussion pages and replace them with wikitext equivalents. There are two possible paths:

1. The replaced page only has a single revision and the edit history would be lost. The sequence of events can only be inferred from the timestamps on signatures.
   
2. The replaced page has the full page history reconstructed from past Flow discussions. This option presents more technical challenges but seems to be doable (albeit harder than the previous option).
   The technology team is still evaluating the feasibility of the second option. If you'd like to preserve the full edit history, please say so in the discussion section below.