All The Tropes Wiki Project, Part XXVIII

[GethN7]

I've just noticed that I'm no longer able to "unwatch" threads on talk pages by clicking the star to the right of the thread title.  It just greys out and I get a spinner when I hover over it.  I have to go to my watch list to successfully unwatch them.  Has anyone else run into this?

I've had the same problem.

I can't try another browser - I only have firefox installed.

It works normally on Brave, which uses a Chrome base.

[robkelk]

I've whittled this list of lint errors down to ten entries. Somebody else, who's more familiar with what the Help page on the list is supposed to be saying, will need to fix the rest of these errors.

EDIT: Once we have images loading again and can see the results of the edits, of course.

Images are back! (I think it's been an hour or two, now.)

[robkelk]

Is "the writer really doesn't want the work being read any more" a valid reason to remove an entry from a Fanfic Recommendations page?

Because I got a board-to-board about an edit to "The Wheel of Time/Fanfic Recs" that I rejected in moderation because the fic wasn't actually gone - it's in the Wayback Machine.

I'm tempted to just send the writer to All The Tropes:FAQ for Creators#How can I get you guys to stop mentioning my work?, but if our positions were reversed, I'd find that sort of reply to be rude. I''m thinking that we should say more than just "read this".

[Bob Schroeck]

Hm. I would start by explaining the part of that policy that requires an extraordinary reason to pull mentions of a work from the wiki before pointing him at the policy. You might also want to note that we still document Relatively Absent in considerable detail despite its author's rather comprehensive (and mostly successful) efforts to wipe it off the face of the Net fifteen or so years ago. Not to sound snarky, but if he hasn't made at least the effort Shurtleff did, why should we do something we didn't do for Shurtleff? (There's probably a much nicer way to put that.)

[GethN7]

If it's still in existence in some tropable context, it's tropable. Unless the work is something that for legal reasons we cannot touch at all (and it needs to be illegal for reasons of content like child porn, like certain movies with sex scenes with minors, and even then it has to be illegal even discuss academically, and that's a high bar), just because someone doesn't want it read is no defense. If it exists and can be legally troped, it must suffer the eye of critique like every other work made available to the public, at least that's my position.

[robkelk]

For those who don't get pinged when the "{{admins}}" template is used on ATT, here's my reply.

[robkelk]

I am not happy with WikiTide's attitude toward fixing reported bugs at Mirqaheze.

I am tired of waiting, and have started complaining in public.

No donation from me until the issue's fixed.

[robkelk]

It's fixed. Shame I had to go to such lengths to have it acknowledged as existing.

---

I tossed together a new franchise navbox: "Tolkien's legendarium"

Of course Undocumented Features gets it.

[Bob Schroeck]

UF will almost inevitably get every franchise navbox, sooner or later.

EDIT: Would Bored of the Rings count as a fan work?

[robkelk]

EDIT:  Would Bored of the Rings count as a fan work?

I'd say so. You have to know the property very well to write that detailed a parody of it, after all.

[Bob Schroeck]

Well then, if you haven't already beaten me to it, I'll have to add it to the navbox.

[robkelk]

A present for the "Names to Know" project

We really should get back to that project one of these years...

[Labster]

Let me start with the good news: Miraheze data is transferring over much faster than we expected. In fact, everything was going swimmingly for a full migration to our new servers by Tuesday or Wednesday.

Then we had a problem where a MariaDB server was having issues dropping packets and communications and being generally unresponsive, which was the one holding metawiki and loginwiki. The Director of Site Reliability Engineering declared an emergency, ordering an immediate extraction of our assets still in the field. Which is to say, we shut down all database servers so that we could migrate as fast as possible, rather than our original plan of letting databases replicate before switching for minimal downtime.

We believe that all data is intact, and that it was a software stability problem, but at this point no one really trusts our old servers, so we're just going to move right now.

[robkelk]

I assume nobody has any idea how long this is going to take. I've been through too many system-crash incidents in my day to expect anybody knows the timetable for service restoration.

Ah, well. So much for cleaning up more lint errors on ATT this weekend.

[Labster]

Actually, almost everything is moved over now except images, which are still doing their slow migration across the seas.  All databases have now been baptized by the waters of the Atlantic and have made it over, and were restarted.  You should be able to do anything that doesn't involve images on a much faster system today.

It wasn't a crash exactly, it's that mysql server on a central database would run but then refuse or drop connections to it.  I think the call was made that instead of trying to debug or upgrade the server — which may well be a hardware failure in progress — it was better just to shut down the db servers and send the entire MariaDB directories.  Considering that we didn't even bother to delete some binlogs, it went pretty fast.  The more I think about the decision, the better it seems, since we could have had an equal amount of downtime trying to diagnose what went wrong, not moved any data in the process, and if it was a disk failure we could have lost data instead of uptime.

[robkelk]

Oh, I agree with the call -- don't waste time troubleshooting a dying system when you can migrate to the replacement instead.

And a seven-hour outage isn't horrid, all things considered. Consider how long Orain's been down...

[Bob Schroeck]

Okay, why the hell is Think of the Advertisers! appearing as a blank page for me even though its source shows it's all there? (And so far no other pages I've looked at tonight are affected.) Is anyone else seeing this?

EDIT: Correction: It's only coming in blank for me in Chrome. SeaMonkey and Librewolf both render the page properly.

[Bob Schroeck]

Okay, why the hell is Think of the Advertisers! appearing as a blank page for me even though its source shows it's all there? (And so far no other pages I've looked at tonight are affected.) Is anyone else seeing this?

EDIT: Correction: It's only coming in blank for me in Chrome. SeaMonkey and Librewolf both render the page properly.

Further update: It's coming in blank on a different copy of Chrome on a different machine entirely. It is readable, though, on Chrome for Android. Again, is anyone other than myself seeing this?

[GethN7]

Okay, why the hell is Think of the Advertisers! appearing as a blank page for me even though its source shows it's all there?  (And so far no other pages I've looked at tonight are affected.)  Is anyone else seeing this?

EDIT:  Correction:  It's only coming in blank for me in Chrome.  SeaMonkey and Librewolf both render the page properly.

Further update:  It's coming in blank on a different copy of Chrome on a different machine entirely.  It is readable, though, on Chrome for Android.  Again, is anyone other than myself seeing this?

Looks fine on Brave. Also looks fine on Edge.

[robkelk]

I don't have Chrome installed anywhere, sorry. The page comes up fine in Edge (using inPrivate browsing mode) and Firefox.

Maybe, possibly, something in Chrome itself might not like something on the page...? I might be thinking that since I've been cleaning up a lot of lint errors lately and that sort of thing is the first thing I think of right now.

[Bob Schroeck]

Hm. I'll have to check what the other dev tools in Chrome have to say after work tonight.

[GethN7]

I sent in a query on if we can get Cirrus Search working this time, it will make searches for data a LOT faster and enable a few fun features we could use to spruce up our wiki to pull stunts even TV Tropes couldn't do, turns out they are seriously looking into it:

https://phabricator.miraheze.org/T11743

If they get it up for us (and they want to) site speed will jump dramatically and API calls to data will be much faster, which means we are more efficient in general.

[Bob Schroeck]

Guys, could you please take a look at this set of changes to the page on Tumblr? I can't put my finger precisely on what, but something about it rubs me wrong, and I'd like to know if it's just me or not.

Thanks.

[Bob Schroeck]

Hm. I'll have to check what the other dev tools in Chrome have to say after work tonight.

I didn't have a chance to do this yet, as we got caught up in some business with my mother-in-law that kept us out for most of the evening. Maybe tonight.

In the mean time I've discovered a second page that comes in blank on Chrome -- Headscratchers/Advertising. Maybe I can find something common between the two.

[robkelk]

Guys, could you please take a look at this set of changes to the page on Tumblr? I can't put my finger precisely on what, but something about it rubs me wrong, and I'd like to know if it's just me or not.

Thanks.

First, the grammar suxs. ("it's" for "its", "overtime" for "over time", etc.)

Continuing to read, it's obvious to me that the troper is writing in a way to imply being non-het is as bad as being a fetishist.

Vote to revert, and to let Biomaster know that being non-het is not evil.