User talk:TigerBlazer

hi
could you check out dict ? Dictionary Wiki. Bye SperosDurrell (talk) 01:33, 5 October 2021 (UTC)

Template:User wiki creator on your user page
Hello TigerBlazer, will you please consider removing the User wiki creator template from your userpage as you are not a wiki creator. Thank you. Ma͡gogre (talk) 21:06, 25 October 2021 (UTC)
 * Thank you for that. I though the wiki creator userbox meant that you owned one on Miraheze. TigerBlazer (talk) 21:38, 25 October 2021 (UTC)

I need to discuss this with you
To address the elephant in the room, my blocks on Qualitipedia were unfair. I have been blocked indefinitely on every Qualitipedia wiki, despite the fact that I have not done anything wrong. I would like to ensure that my actions are in good faith and that I am not a bad user. My actions are extremely minor and are not worth an indefinite cross-wiki block. Furthermore, the reason why I was unblocked originally was because MarioMario456 and DuchessTheSponge repeatedly blocked me as a result of them holding grudges. Duchess hates me for some reason and I have no idea why. Also, my good contributions heavily outweigh the bad (look at my contributions on the movies and shows wikis) Also, Qualitipedia is the only place where I can express my opinions on media. If you know of anywhere else, I would like to hear your suggestions. But for the time being, Qualitipedia is the only place. Blubabluba9990 (talk) 01:50, 15 December 2021 (UTC)

Reporting Terms of Use violations and related reports in scope of the Trust and Safety team
Hi TigerBlazer,

I'm Doug, a Miraheze Trust and Safety volunteer team member. Recently, I noted your good-faith, though incorrect, local blocks of a now former Miraheze user in which you very specifically articulated to the now former user the reason for their user account being off-side with the Terms of Use and then invited them to appeal their local block to you (or, presumably, another local administrator).

While I no doubt suspect you meant well, you should note that this is problematic for several reasons:
 * 1) Similar to the Streisand effect, your block actually draws greater attention to a user, their status, and/or their eligibility to hold a Miraheze account with Miraheze Limited than if you had privately reported it to the Trust and Safety team; and,
 * 2) Similar to, but not the same as given the the different context and circumstances, how federally regulated employees are prohibited from tipping off or otherwise making the customer to which they would be filing a report with anti-money laundering regulatory authorities of their suspicions, you also should not make the otherwise ineligible Miraheze user aware of the reason, as at may encourage recidivism&mdash;perhaps in more surreptitious ways; and,
 * 3) Finally, the Trust and Safety team is solely responsible for administering enforcement of the Terms of Use and, as such, it would be inappropriate for you to direct users to local administration in terms of potential block appeals or if they have questions. Rather, users should be referred to the Trust and Safety team.

That being said, the Trust and Safety welcomes user reports of potential Terms of Use violations and other Trust and Safety-related infractions, chiefly to the  e-mail address. So, with that in mind, my ask of you, going forward, is that should you see such infractions or violations, rather than blocking the user, thereby potentially alerting them to your report, please just privately e-mail the Trust and Safety team at the e-mail address quoted and, ideally, linking to relevant revisions.

Thank you for your understanding and cooperation. :)

Cheers, Doug (talk) 06:26, 18 March 2022 (UTC)


 * Thank you for letting me know, I will do so in the future in case I find a similar situation. Have a good day. TigerBlazer (talk) 15:09, 18 March 2022 (UTC)
 * Thank you for your understanding, and for channeling any report(s) to the Trust and Safety e-mail address. While we may not always be able to reply to every report, please know that we appreciate such reports from the community, review them all, and action them accordingly. Doug (talk) 02:41, 25 March 2022 (UTC)

Why did you make the Chill Place private?
I know that you said that you have a project to work on, but there are pages on there (such as archives from the New Reception Wiki) that I need to make changes to. FatBurn0000 (sandbox | CentralAuth) 10:28, 22 April 2022 (UTC)
 * It's getting overhauled and I don't want anyone to mess with it other than users I trust. And even after that it's going to remain private from now on. TigerBlazer (talk) 02:12, 27 April 2022 (UTC)
 * Could I please become a member then? FatBurn0000 (sandbox | CentralAuth) 20:51, 27 April 2022 (UTC)
 * No offense, but you don't really qualify for being who I would call a trusted user for the wiki. I'm keeping it between certain QP users. The people I need for my project, and you're not really one of them. TigerBlazer (talk) 21:02, 28 April 2022 (UTC)
 * But what are you going to do with the NRW pages then? FatBurn0000 (sandbox | CentralAuth) 23:05, 28 April 2022 (UTC)
 * They'll stay there. Really the only place they can be. TigerBlazer (talk) 02:05, 29 April 2022 (UTC)
 * When will you be finished with it? Just asking, not trying to be rude. FatBurn0000 (sandbox | CentralAuth) 04:08, 30 April 2022 (UTC)
 * A couple of months is my best estimate, but even after it's finished it'll still be private. TigerBlazer (talk) 04:59, 30 April 2022 (UTC)
 * And will it ever be public again? FatBurn0000 (sandbox | CentralAuth) 00:50, 1 May 2022 (UTC)
 * No TigerBlazer (talk) 03:30, 1 May 2022 (UTC)
 * But I (and probably many other users) have contributions that need to be made to the old NRW pages. FatBurn0000 (sandbox | CentralAuth) 01:42, 2 May 2022 (UTC)
 * Dude, just please lay off of it. It's going in a much different direction, and I'm only going to be letting in users I trust and are needed for it. I'm sorry, but like it or not it's going to be private for as long as it's up now. TigerBlazer (talk) 04:58, 2 May 2022 (UTC)
 * TigerBlazer, I actually likely have to agree with FatBurn0000 here. As one of the three to five most active contributors to the wiki, you should not have made  private, at least not having had a discussion principally focused around existing wiki contributors being engaged. I would normally encourage you to revert this change (or at least grant all existing contributors to the wiki   access), but I also have concerns with this wiki's initial approval. Per Content Policy, what is its approved purpose, its defined scope, and what sort of content will it write about? If it's merely to create backup copies of other Miraheze wiki wiki pages, I'm not sure that's a satisfactory reason and may make it unapproved content fork wiki. Dmehus (talk) 07:36, 2 May 2022 (UTC)
 * So, where is this discussion going? FatBurn0000 (sandbox | CentralAuth) 23:46, 22 May 2022 (UTC)
 * Last I heard the wiki encountered some pretty serious demotivation at its top levels.
 * Either way I would not treat it as a reliable TNRW successor given how it is administered; it's always been somewhat more closed and autocratic, and I think the better course is to designate a new successor or straight up reopen the original - I would seriously consider the latter given the deep failures of how the original was handled. --Raidarr (talk) 12:17, 23 May 2022 (UTC)
 * So what will happen now? FatBurn0000 (sandbox | CentralAuth) 20:41, 31 May 2022 (UTC)

Why I'm Still Not Unblocked at Best TV Shows Wiki, Terrible TV Shows Wiki, Greatest Movies Wiki, Awful Movies Wiki, Awesome Games Wiki and Crappy Games Wiki?
First, I was telling DarkMatterMan4500 to unblock me, but he wouldn't listen. Then, I was telling Raidarr to tell DarkMatterMan4500 to unblock me, but he wouldn't. And now, I was going to help you. You'll have to unblock me. I'm a very good user, at all six wikis. I've created some new pages at all six wikis. Adding good images, and editing properly. If you're blocked me, I'll do it at all six wikis, without edit warring. Please, I have to promise, okay? Just unblock me. Eric Bagwell (talk) 19:05, 3 May 2022 (UTC)


 * Now you're talking to people who are in even less of a position to help, not to mention are going behind the backs of multiple people who have all told you no, take time off and stop. If you continue to bug people in this way you will bring yourself trouble on Meta wiki as well and need to plead your case before Meta admins. Please, cease. Everyone involved knows of your continuous disruption, clear insincerity and inability to stop when told. Prove me wrong about those points and that is where an appeal may begin to be considered. --Raidarr (talk) 19:14, 3 May 2022 (UTC)
 * What are you talking about? I need to get myself unblocked. Remember that? I've made the mistake all by myself at Awesome Games Wiki. You'll have to unblock me. I'm telling them the truth. If I'm being unblocked. I can do good edits. Just unblock me, please. Eric Bagwell (talk) 19:51, 3 May 2022 (UTC)
 * @Eric Bagwell:Continuing this practice will instead undermine the trust of the community. 1108-Kiju /talk 20:01, 3 May 2022 (UTC)
 * Hey, I've just told you, I've made the biggest mistake at Awesome Games Wiki. So, unblock me, please. Eric Bagwell (talk) 20:11, 3 May 2022 (UTC)

A kitten for you!
I love you, so I gave you a kitten.

Am0ngU$ (talk) 22:06, 31 July 2022 (UTC) 

Hey, um...
I don't presume you're still working on mh:qpgames:QP Games Wiki? Money12123 (contribs | CentralAuth) 02:42, 2 November 2022 (UTC)


 * I just closed the wiki a little bit before I saw it. I both have no motivation to work on it and am convinced that reception wikis really are awful ideas conceptually that this revamp wouldn't have worked either. There were no edits in the last few months anyway so nothing was keeping it alive otherwise. I don't wish for it to be reopened. TigerBlazer (talk) 11:38, 2 November 2022 (UTC)

Hello there
I don't know if you remember me, but we chatted a long time ago on one of the reception wikis. What happened over there? Btw how are you? It's been a while. IAMGOD (talk) 00:40, 28 April 2023 (UTC)