#and many contextual clues confirm this to be correct

[skalidris]

i love lxc for many reasons but i've never seen anyone express a reason for his relationship to asking questions/accepting answers (he does both, btw) that's even vaguely aligned with the interpretation i've come to prefer

[hollowwhisperings]

VLD Retrospective: My POV as a Queer Biracial Asian Aspie

I don't generally enjoy listing my demographics in public spaces but for a Voltron Retrospective, I find it Quite Necessary to better convey how much VLD meant to me personally. This is one fan reconciling with a work I enjoyed for years, remain saddened for, and felt betrayed by. lf I'm good for anything, it's my being a Living Statistical Outlier.

VLD gave me explicit representation within its main cast: it gave me Shiro, who I clocked as chronically ill well before it was confirmed (Like Knows Like) & struggled with mental illness too (I'm not a war vet but Shiro's implicit Medical Trauma was Also There). Shiro is also, very obviously, an Asian &, as later revealed, a Queer Asian. There are few Queer Asians in western media who are Actual Characters: Shiro was (& remains) fun to have on board. It was, primarily, his struggles with his physical & mental health that most resonated with me.

Pidge is someone a lot of fans identified with, being a quirky genderbender maligned for her relative youth: I'm an autistic female who is gender "meh" so Pidge was "Representation" but she wasn't New nor Almost Unprecedented like Shiro or, as I'll elaborate further on, Keith. Every AFAB, every youth has felt undermined by their assumed gender & their youth: this is Not New. Pidge is fun but she wasn't Groundbreaking, not to me.

Keith and, to a lesser degree (as in assocoation with him), the "Half-Galra" Misfits were who I most identified with. Even before Keith was having Existential Crises over being Half-Galra, Keith read as someone biracial: his name, "Keith Kogane", makes him a white-passing Asian . I think current consensus is that Keith's Dad was "Mixed Asian*" but Keith's "orphan" (& secret alien) status prevented him from engaging with his heritage.

I am Not Galran (so far as I know) but I am a white-passing Asian & someone of "Two Worlds" (half white, half east asian). Star Trek's Spock established how most subsequent works of the sci-fi genre depicts half-human aliens: all the vibes of being Biracial, existential crises about Passing & feeling Disconnected ("rejected") by either/both halves of one's identity. Keith checks those boxes and Lotor's Halfsie Squad are similarly Coded (to lesser degrees).

Aliens, half-human ones especially, are very easily read as Neurodivergent as in "has ADHD &/or ASD": Keith continued this tradition & it further isolated him from his peers, especially because (like many of us on The Spectrum) he grew up "Undiagnosed". Keith knew he was Different but no one had the correct Context for his "Difference": this lead him to feeling Wrong, Rejected and Alien. This is an experience Familiar to anyone belatedly recognised as having ASD and also to Literally Any Queer Person.

To summarize the above: Shiro meant A Lot to me because he struggled with his health in silence (& was Asian); Keith meant a lot because his Human Demographics & Coding match almost entirely with my own. Shiro became "more" Important to me through his being Keith's Most Important Person (KH fans: you see where this is going): I was already Attached to Shiro, Keith made me invested in him.

KH fans knew from my invoking of "Taihetsu no Hito" [JP for "Most Important Person"] that, through being Invested in Keith & thus Shiro, I quickly Recognised that Keith? Desperately in love with Shiro. I did not, however, consider Shiro likely to Act on any Reciprocating of such feelings (which he did show signs of developing, as early on as that Stranded From Everyone Else and "when I die, you be Black Paladin" episode) due to the implied age gap between them. I knew Shiro was Younger Than Assumed (very early 20's at oldest, I figured from Contextual Clues), that Lance & Hunk were about 17 & that Keith was Older than Lance (so, 18). The age gap between Shiro & Keith was never that much of an issue: it was their difference in Rank & the ages they were at their First Meeting that were the "real" obstscles, to my mind. Season 6 or 7 did a Flashback that made Keith 14 when he first met Shiro: that very much explains why Shiro was reluctant to acknowledge attraction to Keith & unlikely to act on it. Keith did, however, read as Crushing On Shiro pretty much from their first encounter (Keith stealing Shiro's car was a very obvious effort to gain Shiro's attention & respect: something Keith was unlikely to recognise as Crush Evidence but Shiro definitely did).

And then Shiro lost 3 years to Time Dilation while Keith gained 2: their Reunion post-Space Whale was very telling. For the first time, Sheith actually seemed genuinely plausible to me. Keith had had a Glow Up that allowed Shiro to stop thinking of Keith as the kid he'd been when they first met & actually admit that his excuses to not act on any attraction had stopped holding weight. I remain completely convinced that "Kuron" had fallen, equally & just as desperately, in love with Keith over the series and that the Aggression Kuron exhibited toward Keith was as much caused by That (Gay Pining he refused to act on, even as Keith ran around in his Infamous Blades Uniform) as it was by Haggar (& Kuron's growing suspicions on his "true" nature).

Then there was the "You're my brother... I love you!" scene. Initially, given The Current Events of the time, I was irritated by the Abrupt Brother-Zoning from the Very Obviously Pining Keith to Shiro.

Then I noticed the order of these sentences: first, "you're my brother" (neither Shiro nor Keith have any siblings: in asia, there's MLM equivalent to "they were Roommates" in "they're sword/sworn brothers") and THEN, more desperately and while at the cusp of death... "I love you".

VERY ON BRAND, KEITH. It's also the "I love you" that gets through Kuron's programming enough for Keith to save them both. From my observations of VLD, the sole remaining obstacles to Sheith sailing were "will Shiro retain Kuron's memories and, if so, will he accept Kuron as being another Him" and "will the writers be able to get the execs to sign off on TWO queer paladins being queer with EACH OTHER"?

and then... the love confession was never addressed & Shiro stopped interacting with any of the Paladins beyond a professional setting.

By then, a lot of the show was looking Off and I actually looked at the online Voltron fandom to see if other people were Connecting Dots: some Meddling had happened, Shiro was being OOC as all heck, Allura and Keith seemed pretty miserable, Romelle was Sus as Heck, why was Allurance happening, where the heck is Lotor (etc)....

I was, like everyone else, greatly upset by Allura's needlessly being Killed Off and by Shiro's Stock Photo husband. I was also Not Impressed by the alleged "happiness" found by any of the Paladins: Shiro retiring his greatest dream, of flying and exploring the galaxy when he had just found out he Wasn't Going To Die from his Chronic Illness? Jim Kirk, another charismatic spaceship captain who loved to explore the universe, had a similar "retirement" ending for its Heroic Captain.

The first Star Trek film, set post-series, conveyed exactly how Shiro's "happy" ending played out for a character Shiro was almost certainly inspred by: Captain James "Jim" Tiberius Kirk.

Captain Kirk's "happy ending" was introduced in TMP as being: a promotion/retirement, marriage, & settling on Earth. Sound familiar, Shiro? TMP then shows how that "happy ending" plays out for someone like Jim (or Shiro): barely a handful of years later, Jim is miserable in his "retirement" (he was Promoted to a desk job); his Very Sudden marriage to a Previously Unknown Character is crumbling (& is even implied as being arranged by Starfleet's Brass to keep their Poster Boy on earth!); he clearly misses his Team (his Found Family) & at his first "valid" opportunity to get his Team together to fly into space again? That's exactly what Jim does.

Star Trek: TMP also, incidentally, features Jim living out some kind of Space Divorce Drama with his Right-Hand Man, the Half-Human Alien Spock. The two had apparently spent all those years apart and Spocks's "logical response" to [everything post-TOS] was... becoming a Vulcan Monk in order to Purge All His Emotions. (Krolia, please tell me that the Galra do not have an Equivalent to Vulcan's kolinahr & that, if it DOES, you Forbade Keith From Doing It).

Jim & Kirk saved each other, often very impossibly, in every other episode of TOS. They were also so widely shipped by fans that the "founding" of modern fandom cukture is often attributed to those first K/S shippers.

The easy Parallels between Spock/Kirk to Keith/Shiro were something that seemed to increase as VLD continued, likely as its creative team started recognising how naturally Keith & Shiro played out that epic space romance. The relationship between the Black Paladins was consistently emphasized within the series (until it abruptly Wasn't) and their bond was considered the strongest shared by any two paladins. A Sheith required very little effort from VLD's creative team and, given the Time Dilation plot point, that effort WAS made: Keith shows up Older & Blade-ier, Shiro Visibly Reacts and seems perfectly set up to Reevaluate his relationship with Keith, both of them visibly Adult and already established as "Equals".

Reading the research done by Team Purple Lion helped me understand the many degrees of unpleasantness caused by the Forced Removal of Lotor from VLD's endgame: the series' overall plot, key themes and multiple character arcs were contingent to the ugly consequences of Voltron's [murdering] him, the emotional effects Lotor had on Allura, the ways Lotor was integral to the show's themes of Redemption & Recovery & Love (of all forms). Just about every main character (and the imexplicable presence of several other characters) had their Arc underminded by Lotor's staying [murdered]: Lotor (obvs), Allura (VLD's Actual Main Character), Lance (who suddenly became Every Creepy "Nice" Guy), Pidge, Axca, Romelle, Merla, Yzor & her girlfriend, Honnerva...

I was invested in the plot, characters and themes of VLD: its ending wasn't just upsetting, it was contradictory to its own story. Though I am not invested in any VLD ships other than Sheith (for the way the characters are individually Important to me, the ways Shiro is important to Keith, the ways their relationship parallels K/S down to the syllables), the series had set certain ships up through its Themes and within its plot: Allura/Lotor, a reclamation of Allura's agency & a thematic resolution to the major conflicts of the series; Shiro/Keith, a love story the series spent 7 seasons telling; the tentative beginnings of Lance/Pidge, a Chekhov's Gun that would round their individual character development through better understanding each other; Hunk & Recognition of his Ingenuity, Bravery, Compassion (which would, incidentally, feature Hunk/Shay and Hunk's central role in the intergalactic Recovery proces). All of these ships serve a Purpose within VLD's plot, aid individual character development, reinforce the series' overarching themes, and have a solid basis within the text of VLD (as well as outside of it, in interviews and statements from the creative team).

I was able to "recover" from the betrayal of how VLD ended, largely through the detective work of fans like Team Purple Lion and reading many "fix-fic" wherein Allura Lives and Shiro is not OOC as all heck. VLD was one of many series, at the time, whose Betrayal of its themes & characters made Waves all over Fandom. It was, however, one of the Betrayals that hurt me more "personally". It was also a fantastic example of Creatives having horrid working conditions, Corporate Interests actively Hurting their consumers, of Fans being forced to Play Detective due to the modern Media Landscape: the culture of creatives being under strict NDAs, of their being without Unions, of how abruptly Projects can be undermined by the Whims of singular entities (creating additional work on an already overworked labour force, often in ways that betray their own work).

So, uh, surprise: this was a Retrospective inspired by the current Writers Strike & growing awareness (that we have known & ignored for years) of how unethical the working standards of animators are. There are Actual Americans and Actual Artists who can speak on these issues more specifically, as well as the best ways to help the affected: this was a more individual Take, from One Fan, and the ways that media has affected That Fan emotionally (though, being an Aspie, i'm pretty distanced from articulating any Specifics beyond "upset" because "this is narratively inconsistent"). The purpose of writing this was personal catharsis, a means of discovering how I feel about VLD all these years later, and perhaps as an act of microcosm within a greater fandom macrosm RE: engagement with media & correctly identifying how the faults of its business structure sabotage excellent works of fiction from staying "excellent" or becoming "magnificent".

*"Korean-Japanese" seems to ne the current consensus but as Sourced outside the text of the series. It is not his "exact amounts of Asian" that Keith is "relevant" to me but his being both Mixed & disconnected from his asian Heritage.

[violexides]

Slavmaeda- My (Hopefully Only) Statement

Note: The times listed here are mostly in EST. If it is in another time, it will state in parentheses. The other time will usually be Polish time.

Another Note: @slavmaedasaga exists, now, for all the posts. I don’t know who made it.

Possible Blackened-

Fir (aka Firanka)

Sunflower

Marshpy

Daniel

Jago

People who follow Sunflower / Marshpy / Fir / Jago

Gay Nagito Komaeda 

Experiencecarrots

Slavmaedasaga

Monokuma File- At an unspecified time this morning, Sunflower received an anon, posting “Slavmaeda rights” continuously until hitting the character limit. At 9:12 AM, Firanka confirms to receiving a similar ask. At 9:17 AM, Fir announces the case to a public discord server, “Danganronpa 2: Tropical Despair”. At 3:50 PM (POLISH TIME), Marshpy receives this ask. At 10:13 AM (or six minutes later, according to Fir), Jago receives a Slavmaeda rights ask. Then, everything went to hell.

TRUTH BULLETS

Alternate Anons: Other anons during this initial period of time were sending Sunflower asks.

“Fir”: One of these anons, not sent by Fir, uses her nickname.

Marshpy’s Account: She states to not having enough bastard energies, as well as her identity as “not Slavic” as proof of her innocence.

See: Marshpy’s Confession.

Marshpy’s Confession: Marshpy admits to sending the asks that went to sunflower and Fir, but none others.

She says she thought it would be funny.

Jago’s Account: [Jago’s] main line of defense is the website & the fact [Jago is] managing a group RP at the same time, [Jago] didnt even have tumblr opened until the situation started.

Jago proves in a screenshot that the first time she opened tumblr was at 10:12 AM.

Sunflower’s Account: She was typing up a character analysis, talking on a server, and answering other posts. Therefore, she did not have time to post these.

Worth noting that later, she would mark the times she was on/off tumblr.

Fir’s Account: She claims to being “confused the entire time”, which she admits herself is a weak alibi. She also states which specific anons she sent sunflower, none of these being the Slavmaeda posts.

See: Fir’s Confession.

Typing Patterns: The first ask was the same set of three “Slavmaeda rights” copy pasted, meaning that every third “Slavmaeda rights”, starting from the first one, had a capital S.

The second was in this same pattern.

The third was in all caps.

The forth had alternating letter capitalization.

Note: After this point, so many asks were coming in that it is hard to establish which typing patterns were used. However, it is worth saying that there were different typing and capitalization patterns.

Notes (Kind of useless but I typed it so whatever): As of typing this, Jago’s post received no notes.

Marshpy’s only received Sunflower and Fir’s declarations of innocence.

Sunflower’s posts received scattered notes.

Fir’s received an unspecified number of notes.

Sunflower’s posts, later, were reblogged frequently by the account “slavmaedasaga”

Daniel’s Account: Daniel is a bastard.

They have no tumblr account, so they can’t leave notes.

Anons can be sent without a tumblr account.

See: Daniel’s Confession.

Jago’s Website: “[It’s] not finished and navigation still is wonky but I can show if I need to prove [I’m] not really paying attention to tumblr rn”

It’s a really dope website not going to lie.

Just. Well done, Jago.

However, this could have been an alibi, planned, as Jago has been watching but suspiciously not contributing much.

Class Trial Rules: Only the first blackened gets punished.

This has nothing to do with anything.

We aren’t a class so technically it’s not a class trial.

But this is still an interesting point, motivation wise.

RickRolling Part One: Daniel is a bastard and a Mikan Kinne.

Deleted Message: Fir paraphrases it as “[trial participants] haven’t noticed something.”

This was deleted.

Daniel sent it.

Threat: “The Slavmaeda Revolution will continue without you” was sent to Marshpy at 10:31 AM.

Daniel claims this was not them.

Fir’s Confession: Fir claims to have sent the Slavmaeda asks to Jago and Marshpy, but did not send the Slavmaeda Revolution asks.

Rickrolling Ask: Someone copy and pastes the lyrics to “Never Gonna Give You Up” and sends it to Fir. After maybe a minute, she receives another Slavmaeda Rights ask.

This Slavmaeda Rights has the same typing patterns as Marshpy’s, except it cuts itself off at the end with a dash.

Threat Redux: Sunflower receives an ask that says “the slavmaeda nation shall remain eternal”

Gay-Nagito-Komaeda’s Account: They just follow Fir and are confused.

They’re innocent it’s just worth noting.

They later joined the Tropical Despair Discord Server.

Sunflower’s Ask: “slavmaeda is inevitable. succumb.”

10:55 AM.

Unsettling Truth: There is no way to track this, because, while certain asks have to have been sent by people in the server contextually, there could be people following Sunflower sending her asks, Fir sending her asks, etc.

Re: The Unsettling Truth: “Slavmaeda has already infiltrated your little trial. You are not safe there. Submit to the revolution.”

10:58 AM

Sunflower’s New Ask: The same Slavemaeda Rights that came with the Rickroll Fir received.

Sunflower’s Time Off Tumblr: 11:07 AM-11:09

11:20 AM-

Other Shit: “Rick rolling is the Slavmaeda National Anthem” (11:09 AM) (Fir)

Slavmaeda Rights (Robyn) (11:11 AM)

“Slavmaeda Slavmaeda Slavmaeda Slavmaeda” (Fir) (11:13) (not an anon, sent as daniel)

Daniel’s Confession: This fucking Mikan Kinnie.

Sent “a lot of [fir’s asks]” and “sent the revolution one to marshpy”

Experiencecarrots: “slavmaeda is the only alibi :)”

I’m gonna be honest, nobody on this server claims to be carrots.

So I have no fucking clue what is going on.

By the way, [I] is Sunflower.

THOUGHTS BEFORE POSTING:

It’s so fucking hard to track so I’m not sure if this is even accurate. This is the most information I’ve got. I’m also tired, so I haven’t looked through this in too much depth. But I think this is correct.

HANGMAN’S GAMBIT

_ _ _ _ _ _ _ _ _ _

r e v o l u t i o n

WHITE NOISE

Lyrics to Never Gonna Give You Up

EDIT ONE - The server this is on is Danganronpa 2: Tropical Despair. 

EDIT TWO - Ignore the Hangman’s Gambit and White Noise, I got carried away.

EDIT THREE - Experiencecarrots confirms to not be on the server. I sort of figured because I think we were mutuals long before this happened, but at the same time, I’m confused as all hell.

EDIT FOUR - Maybe the real culprits were the friends we made along the way.

EDIT FIVE - Carrot’s Account (via tumblr): “Hey hey hey! I only liked the post because I refresh my feed every 2 seconds and like whatever’s there. And I follow pretty much anyone I find, so ha. Also thanks for letting me be a suspect, quite the honor if I say so myself :)” This is regarding claims of being suspicious due to being the first likes on posts, as well as following slavmaedasaga.

EDIT SIX - Gay Nagito Komaeda’s Confession: They sent Fir the rickroll ask, which was incredibly coincidental, considering that they were not in the Tropical Despair Server at the time they sent it, nor at the time Daniel rickrolled us. That was pure fucking luck. Holy shit.

EDIT SEVEN - slavmaedasaga is, most likely, on Tropical Despair. They updated the rickroll post with, in the tags, “komaeda”, meaning that they knew that it was Gay Nagito Komaeda. HOWEVER, I am aware that I updated my post with this information. We have no actual timestamps of who did what exactly, but it was within minutes of each other. My personal thoughts are that this is a person on the server, but I’m not certain.

EDIT EIGHT - slavmaedasaga claims to be a single person. It is worth considering that they could not be, but I have a feeling like they are a single person. 

EDIT NINE - Daniel knows who slavmaedasaga is. It’s probably Daniel, isn’t it. We should have seen that coming. (But I will hold my suspicions until they say it themself.)

EDIT TEN - I want to make a public apology for mistreating my spaghetti. I understand that, in the light of recent allegations regarding slavmaeda and the trial ongoing to find the blackened, it may have appeared as if I have been so caught up in the information that I forgot to treat my spaghetti with care. I assure you in the future that I will never hurt my spaghetti again. 

EDIT ELEVEN - There is now a tumblr blog called “slavmaeda rights”, which is entirely focused on slavmaeda rights. I’m losing my mind.

EDIT TWELVE - Slavmaedarights deleted their post that had “Slavmaeda rights” over and over.

EDIT THIRTEEN - Worth clarifying. There are technically two “og Slavmaeda” people. One is Fir, who started all of this by mentioning the concept of slavmaeda. The other is Marshpy.

EDIT FOURTEEN - Slavmaedasaga is in Tropical Despair. We raised suspicions in this server (More specifically, Gay Komaeda Nagito did) that they were the same as slavmaedarights. They very quickly made a post denying this. Therefore, they have to have been in the server. 

EDIT FIFTEEN - Slavmaedarights posted again (just slavmaeda rights over and over) then deleted it. I never saw this with my two eyes. Marshpy and Gay Nagito Komaeda are eye witnesses. Some of the “S”s in rights were capitalized, according to Marshpy, which is vital to consider. Marshpy claims that there is no isolated S in this post, but she isn’t certain. Also worth considering. A deviation from a familiar pattern, which is interesting. 

EDIT SIXTEEN - TWO CRUCIAL BITS OF INFO! The description of Slavmaedasaga is “Hope” in Bulgarian. Also, Daniel bluffed when they said, in the Tropical Despair server, that they knew who “Saga” is. They just wanted clout. This is important info-- we have no leads on Slavmaedasaga. But we do know that it was likely not Daniel. Daniel accuses Marshpy. who knows. 

EDIT SEVENTEEN - Marshpy was shopping when "Saga” started, and Daniel sent a cryptic smiley face. They claim they were wrong about accusing Marshpy. 

EDIT EIGHTEEN - SLVRights = Damien. They aren’t the same person as SLVSaga. Daniel has shown evidence that they only have one blog. I’m getting funky anons. One anon is the same person, sending theories. There are some others. The theory anon also called me sun, which isn’t explicitly odd but I guess you can consider it. Not sure what else to say. 

EDIT NINETEEN - Haven’t been updating this enough. I’m getting a lot of messages and asks. “Beg. Beg for the answers. Slavmaeda is an unforgiving god. -Damien” was posted, then deleted, on the SLVRights blog in binary. I have an anon in binary. I’m inclined to believe they aren’t the same person. Someone on the server, not related on the tumblr side but helpful on the server side, has a theory. They have yet to say. I have a new ask.

EDIT TWENTY - Firanka wanted me to say that a lot of Tropical Despair people are having wifi issues. I highly doubt this is relevant. Damien posted something. I won’t type it here, because it is long, but I’ll see if I can reblog it. If not, I’ll write a transcript. Thanks for sticking with me. 

EDIT TWENTY ONE - A lot has gone on. Worth saying, I turned off my anonymous asks. Nothing happened. As in like, nobody sent any asks. One of my friends did as a test. I kept it like that for a while. But, as Daniel put it, cryptid hints are better than no hints. 

EDIT TWENTY TWO - Further clarification, for those lost. According to present information, Binary, Saga, and Damien are all separate people. That is as far as we know. I don’t know everyone who did this, so I apologize if I leave certain people out, but Daniel, Nebby, Firanka (there is still suspicion), Glitter (on server), and I have shown screenshots proving we only have our one blog. There are likely loopholes, but... worth considering.

EDIT TWENTY THREE - New stuff surfacing. I’m worried people are getting anxious because of some of this. If you are, please prioritize yourself. Like, literally, even if you’re a huge part of this, if you’re getting stressed? Take a breather. Stay safe. Alright? Not to be the mom of this situation. But it’s important. Take care of yourself. I’m leaving this pinned, but as it winds down, i’m probably gonna unpin this post. But, still here if you ever want to figure stuff out. 

EDIT TWENTY FOUR - Approaching 400 posts. That’s interesting. Also, the suspect list on here isn’t updated. Updated information is in the edits alone. I haven’t even looked at the truth bullets since posting.

EDIT TWENTY FIVE - “Binary” was run by @experiencecarrots. We don’t know who Saga or Damien (now going by just “B”) is. But. Most of this has settled down.

EDIT TWENTY SIX - “Saga” was @firankamipinska. Still waiting for B.

EDIT TWENTY SEVEN - No closer to finding out B. A new day has started. Slavmaedanation has been created. They “declared war” against B. 

EDIT TWENTY EIGHT - @gayer-nagito-komeada was Rights. To be honest. I don’t know how we didn’t see that one coming. But. There you go. They’re Damien/B/Rights. Now it’s just Nation to figure out. 

EDIT TWENTY NINE - Nation is @firankamipinska. I’m not really surprised, probably because she told me she was Nation. Nation was essentially supposed to figure out who Damien was. I was too tired to give much of a shit. I woke up at 7 yesterday. I had no fucking spoons. Zero. 

FINAL EDIT - Four blogs, a discord server, a channel in a discord server, and many friends were made through the Slavmaeda experience. Thank you all for embarking on this crazy ass experience with us. I can’t believe that the day after my birthday, I helped create a meme. Have a nice day. 

[wordpress-guides]

WordPress Help Today! 24/7 WordPress Support, Help | About Troubleshooting Support WordPress

With expert WordPress assistance, you can reclaim your time.

How much does a single day of downtime cost your company? Don't wait until it's too late to respond after it's happened. Since your website is so important to your company's success, it deserves first-rate WordPress support. Save time, money, and stress by entrusting your website to Australia's best WordPress developers.

Monitoring of uptime 24 hours a day, 7 days a week

With a team of local developers on hand to get you back up as soon as possible if your website goes down, you'll be the first to hear. We'll send you an email notification and keep track of your website uptime in site care reports.

Aid for WordPress developers support

Do you want assistance with enhancements and fixes? It's easy. Simply send us an email with your message, and we'll take care of it. Up to 30 minutes of service time per month is included with membership. Help time may be purchased as required for larger projects at reduced rates.

WordPress Help Today!

Backups are made automatically every day.

Do you know how to get your website back up and running if anything goes wrong? Do you know where you can get a backup of your website? We offer free regular cloud backups and restores, as well as a 90-day backup history for peace of mind.

Speed Scanning for malware on a regular basis fix

Hackers are actively attempting to take advantage of your website. We search your website for suspicious activity on a daily basis, using cutting-edge technology to detect even the most sophisticated WordPress malware.

Updates on vulnerabilities

Almost every hacked WordPress website contains a security flaw in the heart, plugins, or theme. We search your site for known vulnerabilities in the WPScan Vulnerability Database and submit security patches as soon as possible.

Report on the condition of the site

We'll submit a monthly site care report for maintenance and performance management, in addition to comprehensive responses to help tickets. Any time we make a change to your website, you'll be notified.

There are 79 WordPress tutorial videos available.

From WordPress tutorials to WooCommerce, Yoast SEO, and Google Analytics, we've got you covered. Up-to-date WordPress videos, like the Gutenberg editor in WordPress 5.

Check the health of your website ($99 value!)

We run 21 basic health checks on your website while getting to know it, all of which have an effect on security and efficiency. It's our way of saying thank you for joining us, and it's worth $99!

How Does It Work?

We will assist you with anything WordPress-related, from content updates to performance and protection, with just a fast email. We're here to help you get back to work with reliable WordPress support.

Send us an email with your help request.

Send us an email or use the members area to submit a support desire. We get down to business. We'll get to work; most small jobs are finished in under eight hours. Make a schedule for your free time! While we take care of WordPress, you can focus on running your company.

Anything is possible for us. WordPress is a content management system (CM)

We don't just do easy 30-minute jobs; we also do the tough things. Only the top 2% of WordPress developers are hired, ensuring high-quality, productive support for...

• Google Analytics for WordPress • WordPress plugin selection • WooCommerce support • WordPress hosting transfers • Fixing compromised WordPress websites • Plugin and theme updates • 500 Internal Server problems• Database link probllmes.

Whatever it is, we will assist you with WordPress. Here are 50+ support tasks for which our clients will receive immediate assistance.

The Art of WordPress Troubleshooting

It may seem difficult to find out why anything isn't working as planned if you're new to WordPress or even if you have some experience. It would be great if we could just wave a magic wand and have everything “fixed” instantly, but in fact, diagnosing and resolving problems takes a little more effort. Since it would be difficult to outline troubleshooting steps for every possible problem, this post will stick to general troubleshooting. The purpose here is not to clarify how to solve all of your problems, but rather to walk you through the fundamentals of WordPress troubleshooting. Remember that troubleshooting is more of an art than a science, but there are tried-and-true tactics and steps to follow if you get stuck.

The fundamentals

The measures below will help you troubleshoot your WordPress issue.

You should be aware of what you're doing. WordPress has simplified the method. It's possible that it's too easy. As a result, a lot of people are jumping in with no idea what they're doing. You wouldn't get behind the wheel of a car without first learning the fundamentals. For example, learning how to accelerate, brake, move, turn, and so on. Similarly, knowing at least the fundamentals of WordPress is important. Anything, including troubleshooting, becomes simpler with a good understanding of WordPress. And the good news is that there are a zillion different ways to learn WordPress fundamentals. So either do your own research and put it together, or get a copy of my book, The Tao of WordPress, where I bring it all together in a straightforward, succinct manner.

Check out the documentation.

For all themes and plugins, read the readme.txt and/or documentation. Most of the questions I've got in my years working with WordPress are answered in the readme.txt file. A readme.txt file must be included with almost every plugin or theme hosted on WordPress.org. The only way to solve problems is to stop them in the first place, as is the case with many things. Always read the readme.txt and/or other available documentation to ensure you have the knowledge you need to prevent errors when successfully using the plugin or theme. So take a look at the documentation; the answer may be right there waiting for you.

Look under the Help tab.

To get contextual information at any time, go to the Admin Area's "Help" tab. In the upper-right corner of almost every screen in the WP Admin Region, there is a Help tab. By clicking it, you'll get access to valuable information that will help you answer any questions you may have. Good plugins also have healthy Help menus on their websites, which are very helpful for learning how things function and configuring things.

WordPress Codex is a good place to start.

The WordPress Codex is another good source of knowledge. It goes into great depth on almost every aspect of WordPress. Take some time to read the related pages at the Codex if you get stuck with something or intend on doing something that you may get stuck. It's difficult to go wrong with official documents.

Look for hints.

Getting a handle on a tricky bug or problem may seem to be an impossible task. Especially if you're new to the game and have no experience with the script or issue at hand. Try looking for some relevant details to help you come up with a solution. There is a wealth of WordPress information available online, and chances are that someone has already been there, done that, and written about it. Seriously, WordPress powers over 20% of the Internet, so there's a decent chance you'll find some useful information through a search engine. So look up a few keywords related to your problem and see if someone else has posted a solution, clues, or something else that may help.

Clear your browser's history.

Your browser saves a lot of information about the sites and resources you visit. Be sure to clear your browser's cookies, cache, form info, and/or anything else you're working with to ensure you're checking the most recent code. I prefer to use several browsers, with most of them running in “clean” mode all of the time, with no saved history or results.

WordPress should be updated.

Make sure you're using the most up-to-date versions of WordPress and all of your plugins. It's the most effective way to rule out incompatibility problems caused by running obsolete models.

Make sure you have copies.

Always ensure that you have checked and full backups of your website. Files and databases can both be backed up. It makes no difference how you get there as long as you have backups that can be used to restore previous features if necessary. Remember that backing up your site isn't enough; you still need to verify the backups to ensure that they're complete and functional. Again, regardless of bugs or difficulties, these are the most important things you should be doing. In general, sound advice. Continue reading to learn more troubleshooting methods, tricks, and tips once you've covered these basics.

Consider the facts.

When troubleshooting, think like Spock and try to solve the problem logically. Remember that you're dealing with scripted logic at the end of the day, so finding the source of a problem is technically always possible. In general, troubleshooting entails identifying and replicating the problem, removing irrelevant variables, and running enough tests to confirm the hypothesis. Here's a fast rundown of each of these principles, which will help you break down problems and find possible solutions.

a description

It's nice to be able to explain or identify what you're trying to address in order to grasp it. Using the phrase "Oh noes!" as an example. The phrase “WordPress isn't working!” is simply meaningless. Something more concrete, such as “My homepage is not loading,” would be preferable. “My homepage is not loading the right theme template,” for example, would be even better. Continuing this argument, the definition of the problem would ultimately point to a solution, such as: “When my Reading settings are set to show a static posts page for the front page, my homepage does not load the correct theme template.” In this case, the description necessitates a solution, which would include ensuring that the theme contains the appropriate template file. The better prepared you are to address a problem, the more succinctly you can describe it.

Reproduction

It must be possible to continuously reproduce the problem in order to find a solution. It is possible to test and observe a problem after it has been repeated. Let's say you're using an e-commerce plugin that's having trouble processing those transactions. It works in some cases, but not all of them. Sure, you might start fiddling with settings and codes in the hopes that anything would work. However, being able to reproduce a failed transaction and limit the research to that case would be preferable. Replication means that the decisions you're doing are resulting in the desired result.

Getting rid of something

It's critical to remove as many irrelevant variables as possible before isolating and determining the problem. Let's say you've only triggered 50 plugins all at once (ouch!). And now your front-end pages are not loading. To figure out the plugin (if any) is causing the problem, start by removing as many variables (plugins) as possible. Disabling all plugins and reloading the homepage will reveal whether the problem is caused by one or more of your numerous plugins. If the homepage unexpectedly loads, you can start re-enabling plugins one by one before you find the culprit. The elimination process is a useful tool for troubleshooting almost any problem.

Examining

You are now prepared to begin validating potential theories using these techniques. When it comes to troubleshooting, you're basically using the same principles and concepts that are used in scientific research: evaluating current situations, identifying a hypothesis, conducting experiments, analyzing data, and coming to a conclusion. Any beginner literature on the scientific method should be queued up for more serious learning in this area. It's decent material, and it's also a lot of fun :)

Things to stay away from

There's a list of "important" things that will make your life easier with WordPress, and there's a list of things that will make your life more difficult:

Support in Activation of several plugins in bulk

Don't turn on a slew of plugins at the same time. This is something I see all the time. People install a slew of plugins and then turn them all on at the same time, expecting it to just "run." It's rare that this is the case, so take your time and trigger one plugin at a time. You can then configure the plugin and test its features in a tidy, systematic manner. Otherwise, if you just mass trigger a bunch of plugins and something goes wrong, you won't know which one is to blame and will have to spend a lot of time trying to sort it out.

Plugins and themes with a shady reputation

Get your plugins and themes from WordPress.org whenever possible. If you do use a third-party website, make sure it is credible and reliable. You're taking a huge gamble if you go any lower. Malicious code is often found in plugins and themes distributed via "warez" and "pirate" style "sharing" pages. It's never a good idea to download unauthorized copies of something that involves code (or illegal copies of anything, for that matter). Ignorant people find it far too simple and enticing to inject shady exploit scripts and other malicious nonsense. Sticking to the official source and avoiding shady sites will help keep your site clean and send you peace of mind.

Having a zillion plugins active support

So many times I've logged into someone's site to assist with a problem, only to be confronted with the nightmare scenario of "WAAYY TOOO MANNY PLUGINZZ!!!" Seriously, 10-20 WordPress plugins to get the work done is understandable, but 50 plugins?!?! There are 100 plugins?! There are several exceptions, such as when using plain, dedicated plugins that concentrate on a single/specific mission, but in general, it's better to keep the number of plugins to a minimum. Aside from lectures, I advise people to take a more cautious approach and install only the plugins that are absolutely appropriate. Activating an excessive amount of plugins can just complicate things, increase maintenance load, and waste valuable resources including bandwidth, memory, and time unless you're cautious. In general, more plugins equals more risk.

WordPress support provided by third parties

So, in general, using third-party services and integrating them with your WordPress-powered site is fine and secure. However, it is important to consider the possible drawbacks and repercussions of doing so. Before allowing open access to your database and information, make sure you completely understand what every 3rd-party functionality is doing.

If you're having trouble with something and can't figure it out, check to see if any third-party scripts or plugins are involved, as they may be causing problems. It's one thing to keep track of what you're doing on your website, but it's another to know exactly what improvements Facebook, for example, is making to their API, widgets, and other features. APIs are constantly changing, so if you use one, keep an eye on what it's doing.

Changing the core

Never make changes to the core files while operating with WordPress. The same is true of plugins and themes. Make no changes to the main files. This would just cause further issues and should not be considered a solution to the bug or issue you're trying to fix. If you need to modify core features, use a plugin or the functions.php file in the theme. After all, that is why they live in the first place.

Examine the fundamentals.

It's always a good idea to go through all of the basic troubleshooting measures when in doubt:

Examine the documentation. Relevant details can often be found in the theme or plugin documentation. Known bugs are often documented, along with potential workarounds and solutions. Still, always, always, always, always, always, always, always, always, always, always This is something I can't stress sufficiently.

Examine all options.

Examine all of the settings and choices of a plugin or theme before using it. Frequently, there will be some mysterious (or obvious) setting that alters the plugin's behavior. So, if you're trying to diagnose and fix a problem, going through each plugin's settings could reveal a quick, one-click fix.

Examine the error logs.

Any website should have an error-logging and access-logging system in place. The ability to examine what, where, where, and why errors and other problems occur on the server is provided by error and access logs. They are a treasure trove of knowledge and are truly indispensable resources for those working online. If you're not sure where your site's access/error logs are, ask your host; they should be happy to point you in the right direction.

Examine the functions.php file.

Check any custom scripts that might have been added via the theme's functions.php file if you're trying to diagnose a theme-related problem. To decide whether any code in functions.php is at fault, look for any newly implemented functions or use the halving process.

Check for grammatical errors.

How many times have you tracked down a problem to a simple syntax error? This has happened to me many times. Take a fresh look at the code you're dealing with while you're troubleshooting and look for any subtle typos or other coding errors. Take a break before doing so to refresh your eyes and look at the code from a different angle, or ask a coworker to look at it for you. Hopefully, whatever code-editing program you're using includes syntax highlighting, making any mistakes easy to find.

Additional information

Also, note to verify the following while troubleshooting:

• wp-config.php directives with custom directives • Custom directives in the php.ini configuration file • Custom directives in any.htaccess file (s) • The server's control panel can be used to set up settings and instructions.

If any of these things are present, they can cause problems. Make a comprehensive investigation!

Return to the previous place.

If you get lost when working on your blog, go through your previous acts again. This is known in web development as "rolling back" to a previous version or build. For example, if you recently updated an excellent plugin and the new version is causing issues, you may want to roll back to the previous version, at least until the error can be recorded and fixed (i.e., don't stick with an old version). Similarly, if anything stops working properly when you're making improvements to your site, try "undoing" any previous measures. You know, revert to the last documented working state and start over. This will often expose any errors or incompatibilities.

Mode of debugging

Running WordPress in "debug" mode is another perfect way to troubleshoot. Debug mode displays bugs, alarms, and notes that can reveal valuable details about what's going on (or not going on) underneath the hood. You can allow debug mode by setting WP DEBUG to true in the wp-config.php file, as described in the WP Codex: allow debug mode with define('WP DEBUG', true); After you've completed your checks, convert true to false (without the quotes) to switch off debug mode. For more details, see the WP Codex. There are some excellent debugging plugins available at the Plugin Directory, in addition to WordPress' built-in debugging functionality:

• AskApache Debug Viewer • Debug Bar • Debug Objects

Debugging code is a vital part of the creation process, and if the authors of your themes and plugins are doing their jobs correctly, debugging should show that everything is as clean as possible. Contact the creator if you find a flaw in a theme or plugin. If you find a bug in the WordPress center, follow the steps outlined in the WordPress Codex's Reporting Bugs guide.

Create a default WordPress installation.

If a plugin or theme on your current WordPress site isn't running, try setting up a test installation of WordPress. Most themes and plugins are tested at least on a default WordPress setup, so replicating that environment will give you a baseline and allow you to check that all is working as intended. It also allows you to compare the discrepancies between a standard WordPress site and a site where a theme or plugin isn't working.

No modifications should be made to the default installation, which should be exactly as it came out of the package. Make no changes to the settings, plugins, or themes. This provides you with a suitable forum for checking theme and plugin functionality. Let's assume you're designing a WordPress site and you've tweaked the settings quite a bit. Then you install a new plugin, and something goes wrong or the plugin doesn't work as it should. Having a default WordPress installation available makes it simple to see if the plugin works in the first place. Simply install and trigger it on a standard WordPress installation to see how it works. If it works, you should start looking into the inconsistencies between your site and the test site. Continue by recreating your site on the test site, checking each step to see if the plugin (or whatever script) stops working. This will show you which part of your configuration is interfering with the plugin. If, on the other hand, the plugin does not function with the default WordPress installation, you can contact the plugin creator for assistance.

The database should be reset.

If you're working on a new site with no content, you may want and try resetting the database to see if that helps. There are a few good plugins for doing this (see links below), but you can also do it manually by deleting the old database and visiting the installation file, /wp-admin/install.php, in your browser. As a result, the installation process will begin and the database will be recreated from scratch.

Resetting the database after playing with a bunch of new themes and plugins is a perfect way to clean up any leftover data before finalizing configuration and customization for output, even though there are no problems with your site. • Database Reset for WordPress • WordPress Reset Other options and tools for interacting with the WordPress database can be found in the Plugin Directory.

Restart the method.

If all else fails and the problem is too complex to troubleshoot or reverse engineer, try installing WordPress from scratch and rebuilding your site piece by piece. Yes, setting up a new database and installing WordPress takes time, but it allows you to identify the problem when it arises in the timeline of your site's growth. In certain cases, simply resetting the database and uploading a new collection of files would solve the problem. When things get too difficult, starting over might be the answer.

Plugin troubleshooting

If something stops working after you trigger or upgrade a plugin or theme, it's most likely the plugin or theme that's to blame. This is why it's a good idea to install and configure plugins one by one, checking for proper functionality as you go. If you're not sure which plugin or theme is causing the problem, there's a tried-and-true method for figuring it out. Here's how it works in general:

1. Some features aren't working properly. 2. Temporarily disable all plugins to diagnose the problem. 3. Then, one by one, reactivate each plugin, checking for proper functionality after each.

If you're troubleshooting a specific plugin, you can switch off all other plugins except that one. The aim is to eliminate variables so that you can figure out which plugin (if any) is causing the problem. Here's a diagram to help you imagine the procedure: I've used this tool dozens of times to separate problematic plugins on client pages with a large number of plugins. It could be easier to set up a test WordPress installation if your site has a lot of plugins.

Themes troubleshooting

Essentially the same concept as troubleshooting plugins, but with themes instead of plugins. Switching to one of the default WordPress themes, for example, will help you figure out whether your theme is to blame for a tricky bug. If the bug persists, it's not your theme's fault. If the bug vanishes, the problem is most likely with your theme.

Troubleshooting basic problems examples

These basic examples demonstrate several troubleshooting measures for diagnosing specific issues. Following the reasoning behind each move can give you a better understanding of how to apply this approach to general troubleshooting.

The shortcode does not work.

A recent support desire provides an excellent illustration of the troubleshooting process. The desire was to assist in determining why a shortcode on the web was not working. Here's the gist of my answer, which describes some rational steps to take to rule out extraneous variables and pinpoint the problem's source: • Try some other 3rd-party shortcode to see if shortcodes work • Try the shortcode on a different Post/Page to rule out location as the problem • To rule out location as an issue, use the shortcode in any widgetized sidebar. • To see if there's a problem, try placing the shortcode in the WP text widget. • Try the shortcode in the default WP theme to rule out any theme-related issues?php echo do shortcode('[shortcode]');?> in theme template • Disable plugins to see if there are any problems in that department. This isn't an exhaustive list of items to look for while troubleshooting shortcodes, but it was enough to get the individual to figure things out and fix the problem.

Email is not working properly.

But you're having trouble getting email to work in WordPress? (or anywhere else for that matter). It seems that WordPress isn't sending the emails. Alternatively, the emails could have been sent but not received. Or, if only Hotmail or another special service is used, the message is not sent (s). When dealing with email problems, bear in mind that there are a number of factors to consider, including:

• WordPress • Active WP theme • Plugins • Custom scripts • Server software • Hosting rules/policy • DNS/domain protocols • Network features • Spam-blocking scripts • 3rd-party providers such as Gmail, Hotmail, and others • Email headers

Email is one of the most complicated items to troubleshoot because of all of these factors. Check Email is a plugin that can help rule out a few of these possibilities. You can start there and work your way up until you've figured out what's wrong. The check-email plugin determines whether the problem is caused by WordPress or something else. Unfortunately, fixing email problems necessitates some detective work, so roll up your sleeves and get to work ;)

The updates aren't running.

There are a number of things to consider when it comes to automatic/one-click updates: • Look for any revealing mistakes in the site's error log. • Troubleshoot active theme • Troubleshoot plugins (security plugins, firewall plugins, and so on) (custom scripts in functions.php, etc.) • Look for any custom code in wp-config.php • Look for any relevant.htaccess directives • Check the server for any firewall or interfering rules • Check the web host for any firewall or interfering rules

Check out DigWP.com's What to Do When Auto-Update Fails for a more in-depth look at the different factors that may be causing this issue. In addition, the following tools may be useful when diagnosing outbound HTTP requests:

• HTTP Requests Testing • License Activation Troubleshooting • Server Test Plugin

Tags: site, however, take care, woocommerce, take, call, contact, team, desires, call us, speed, issue, error, need, hosting, necessary, one, fix, free  Wordpress, small job for websites, need job, need experts, need experts, error fix, woocommerce info, great things about woocommerce, however take care, things, experts for error or issue fix, great woocommerce job, however contact for issue, however contact for error fix, speed issue, necessary team to fix the error, need strong team, experts to fix problem, build a free Wordpress, free for Wordpress, WordPress problem fix, support, WP Website Help, free wordpress help or help, fix error, website help, WP fix, wordpress help, take wordpress help, things contact, help contact, take care, take care support or plans, small plans for hosting, hosting plans, things of work, take care, task, contact for task, free Wordpress plugins, fix Wordpress, Wordpress plan, add Wordpress team, Wordpress speed, fix wrodpress hosting issue, Wordpress hosting, Wordpress service, Wordpress best site, add Wordpress best site, free Wordpress site, free Wordpress websites speed check, Wordpress team for help, wordpress speed checking, support for wordpress, help for wordpress, help for free wordpress, take support of help , wordpress site, high speed, fix speed test, team for wp site, plugins for WP, free chat for plugins, chat on hosting support or wordpress support, best wordpress support, ongoing platform,

Getting Support with WordPress Help

There are several resources available to assist you with WordPress. Of course, doing a few fast searches for your favorite search engine is the fastest way to find out what you're searching for. If you're having trouble with a particular plugin, for example, check the Web for the plugin's name as well as any related keywords. If you can't find something useful, here are some general tools for assistance:

• WordPress Support Forums • WordPress Codex Guide to Troubleshooting • WordPress 3.5 Master List • WordPress Codex Guide to Finding Aid • WordPress IRC Live Help • WordPress Questions • List of WordPress Developers & Designers

As you progress with WordPress, familiarizing yourself with these tools will be beneficial. You should be able to find almost everything if you're good at searching. If you can't find something useful, you might need to contact a developer.

Prior to requesting support,

After you've exhausted all possible troubleshooting options, you may want to seek assistance from a developer or another support source. Here's what you should include in your help desire:

• Any appropriate screenshots showing what's happening • The name and context of any associated error messages • A straightforward, concise description of the problem and how to replicate it • • Any measures or possible solutions that you've already attempted • The URL of your blog and/or any related articles or pages • The name(s) of any relevant plugin or theme

It's also a good idea not to bombard your developer with too many desires at once. It's far easier to seek assistance with one problem at a time. It is polite to do so, and it also helps to keep contact coordinated and on track.

Keep it genuine.

Working on the internet necessitates troubleshooting. Bugs and problems are an unavoidable part of our work. Debug and troubleshooting routines are well-established among experienced developers, and beginners should put their skills to the test as much as possible. The next time you get stuck, use this guide to help diagnose and resolve the issue. Troubleshooting on your own is a valuable skill to have, and it will save you a lot of time in the long run.

Details to Know Follow:

https://wptangerine.com/wordpress-help/

Additional Resources:

https://wordpress.com/learn/

https://wordpress.org/support/article/new-to-wordpress-where-to-start/

https://en.wikipedia.org/wiki/WordPress

[animerunner]

This actually genuinely pisses me off as someone whose been in both fandoms.

For reference:

July 07: Deathly Hallows (the last book) released

Oct 07: Rowling first mentions Dumbledore is gay

As someone who read the books backwards and forwards growing up. There was never any real contextual clues that Dumbles was anything but straight.

Heck before this came out McGonagal/Dumbledore had a rather decent sized following. Lord knows how many fics with those two together I read.

There were definitely LGBT ships in the fandom, pretty popular ones too. But ones with Dumbledore? Practically unheard of in my experience. Though I know they were out there.

There was nothing distinctly to really give us any context that Dumbles might not be straight. And considering the time period and what we know about Rowling now. It makes sense.

It for all itense and purpose appeared to have been done just to earn brownie points. (Though it being 07 makes that a bit odd)

But it’s not like she hasn’t done stuff like this elsewhere. Making Hermione black was still a decision I’m almost certain was reaction pandering. Since most early descriptions have her described in passages as being pale white.

And to be clear I’m not invalidating anyone who says Harry or Hermione as a POC. How you think Hermione or Harry looks isn’t the issue.

Oh and then there’s the time Rowling tried to make the werewolf thing a metaphor for AIDS. Which considering how werewolves are usually viewed in the series...that’s a very bad metaphor and is just below the terf stuff in the ‘How the hell does she think doing that is okay?’

It’s Rowling who has always been more reactive then proactive. And this is another examples along with Dumbles.

Dana on the other hand:

16-17 starts creating Luz with the intent to be ND something she says herself in the interview

2020- Owl House S1 runs and many including myself pick up on the ADHD tendencies

NYE 2020 - Dana says in a Q & A that it wasn’t her intent for Luz to be ADHD she says how we view her as valid.

April 2021 - Dana now says that she believes Luz is ADHD after having done more research since the NYE Q&A.

There are two major differences here. 1) Timing. 2) Dana did actual research both first when creating Luz. And then when fans asked her about the possibility of her being ADHD. She changes her mind because she didn’t fully understand what it encompasses.

And you know I’ve seen people with ADHD not realize something isn’t part of it. So I buy Dana just genuinely didn’t know originally.

And there’s also the fact, ya know, the shows still going!!

Dana confirmed the contextual clues. While Rowling started pulling rep out of her ass.

Multiple times may I remind people.

Also coming from a disabled viewer I would love for this fandom. To not compare the show runner who has written in arguably two canonically disabled characters that they handled well. With the person who has been quoted as saying there is no such thing as a disability in the magical world.

Apparently there’s now a wheelchair user in a mobile game. But again see my whole thing about how Rowling is more reactive then proactive. And I’m guessing that the wc user came about due to some backlash at some point.

Which actually gets hilarious when you remember that Harry has glasses. Because needing corrective eyewear even if it doesn’t make you completely blind is still technically a form of disability.

Old link to the disability thing and she’s apparently changed her mind since. Which just proves my point. She isn’t proactive in her inclusion. She’s REACTIVE: https://marauders4evr.tumblr.com/post/107374030237/accio-representation-how-jk-rowling-secluded-a

Do not compare the person who has been inclusive since the beginning. To the person who only becomes so when under pressure.

DO NOT DO THAT.

Apparently people are unironically trying to say that Dana Terrace is pulling the same shit as J. K. Rowling, and I'm just wondering how many people I'm gonna have to fight.