(12-25-2024, 07:22 AM)robkelk Wrote: So, did we get a serial ban-evader for Christmas? It looks to me like "Chickeninvader" (and that name raises a red flag in and of itself) has the same writing style as "ilove*", down to quietly removing an example without explanation.

Am I being paranoid, or should we hold off on approving these (and rejecting the one that deletes an example without explanation) while we ask for a Checkuser? There's already one approved edit in the history.

(12-23-2022, 01:35 PM)GethN7 Wrote:

(12-23-2022, 10:38 AM)mrobkelk Wrote: Geth, I'm still finding pages that haven't been reverted from when gethbot replaced [[Category:{{PAGENAME}}]] at the start of the category list with  [[Category:{{substAGENAME}}]] at the end of the category list.

I thought you said that you were going to fix that...

If you can give me a list of pages to fix, I can bot run that ASAP.

I'd rather not run that blind though, so a discrete number of pages (as opposed to leaving a bot on for days to scan our massive database) would be ideal.


Bob, we need new thread, this one is at it's limit.

In the last post of the last thread, Labster said: Wrote:

(09-14-2022, 07:35 AM)Bob Schroeck Wrote: Yeah.  My nightmare scenario is someone doing something that causes the Stewards to push the TOS to full-TVT where we can't even acknowledge the existence of NSFW works.  I'm worried that even without someone doing something, they're going to inevitably creep into that territory.

Given how absolutely useless some of our alleged features are as things currently exist -- just try to use typeahead in the search prompt, or expect pop-up link suggestions while editing; you'll be waiting forever -- not to mention the random and all-too-frequent 50* errors, I agree that it's time to start shopping around for a more reliable host.

I've talked to them.  Apparently they're all freaked out by the way a former steward was dismissed by recall; even though that was a special case, no one wants to make any controversial rulings now.  They're also afraid of vote brigades.  So this is a way of forcing the vote on to everyone else before triggering the controversy, so that they can implement the moderation that was already against policy but required an (obvious) judgement call.  (I have told them that the people who are unhappy now will still be unhappy later because that's what moderation is like.)  So really, we should see this as a null policy change, but a vote to actually implement the existing policy.

I hate to admit it, but I now think my original policy was flawed because humans are cowards -- or morons, or otherwise despicable.  Is it really so hard to do the right thing when the vast majority of people support you doing the right thing?

• The Bully is a Nerd
  
• Faction Mechanics
  
• Fantastic Tribulation
  
• Shield Slinger
  
• Words act more than Actions

(10-20-2021, 10:30 AM)robkelk Wrote: We're down to sixteen entries left on "All The Tropes:No Real Life Examples, Please" that may or may not be TVT control issues. Funnily enough, they're all Sex Tropes.

We've started discussion threads on the tropes' Talk pages. Mods, if you haven't logged in lately, expect to see a lot of "mentioned you" notifications...

• NRL is stupid / TVT-control-freakery here and should be killed with fire
  
• Historical examples only
  
• Not physically posible in RL
  
• Yeah, let's keep NRL
  

Quote:Okay, before I do anything on the actual wiki, here is the new home and community pages optimized for both desktop and mobile view, so people on their computer and on their phone and tablets will see nothing too broken when they look at pages using any tabs

They were recreated using the Tabs extension with MobileTagsPlugin for the mobile view pages and TabberNeue, the fork of Tabber with support for mobile view, as default Tabber does not have mobile support and is entirely broken.

The mockups I'm linking are not perfect, but these should at least have minimal issues switching between desktop and mobile skins, compared to the original versions, which were working on desktop but completely broken on mobile:

https://allthetropes.org/wiki/File:Deskt...e_Page.jpg

I had to change a few section headers to plain wikitext and use a few hardline templates to keep things separated in mobile view while still looking good in desktop view.

https://allthetropes.org/wiki/File:Mobil...e_Page.jpg

In mobile view, the tabs are changed to an accordion-style dropdown that expands to let you read each section without spilling over other text or the dividers.

https://allthetropes.org/wiki/File:Deskt...Portal.jpg

Here I used TabberNeue for the parts using Tabber, which looks only slightly different from the classic Tabber look in desktop. Note the dropdown menu in desktop view for the page list of red links, this will not be visible until moused over and can be condensed if need be. This functionality already exists for the use of Tabs for those not aware.

https://allthetropes.org/wiki/File:Mobil...Portal.jpg

Here is the important part. All the TabberNeue tabs, you'll notice have a scroll bar for what goes off screen and will scroll over to what is off screen and back so mobile viewers can see all Tabber sections on mobile phones and tablets.

There were some minor issues with Tabs on the mobile view Community Portal (I'm on localhost, so this may not be the case on the actual wiki, but aside from some minor issues, it looks fine in mobile except for the fact the list does not condense for the list using Tabs up top), but it no longer shows raw extension code breakage like it did before.

It's not perfect, but compared to the horror show of broken Tabs/Tabber markup we had before, this looks a lot better for mobile users.

TabberNeue will replace Tabber, but they use the same syntax, so it will be an easy drop-in replacement. Tabs augmented with MobileTagsPlugin allows the Tabs extension to work better on mobile and at the very least prevents them from breaking to the point of splaying ugly extension code everywhere at worst.

I look forward to any comments before I make any changes, as I also plan to write up a new policy page for best practices so all pages can look good on mobile and desktop platforms going forward.

Note: TabberNeue may require about 24 hours even after a cache purge for the Miraheze servers to catch up, but given it will primarily affect the Community Portal and then only in the short term, this is the only possible downside of the switchover from Tabber to TabberNeue.

(05-07-2021, 11:09 AM)robkelk Wrote:

(05-07-2021, 08:04 AM)Bob Schroeck Wrote: By the way, has anyone alerted Miraheze staff just in case they're targeting other wikis?

Not I... and I know there's at least one other Miraheze wiki that uses a lot of Commons images, so they might be a target as well.