User talk:Bongo Cat

Add topic
From Miraheze Meta, Miraheze's central coordination wiki
(Redirected from User talk:Bukkit)
Latest comment: 1 year ago by Bukkit in topic Patroller granted - 2023-03-2
Hello. Welcome to my talk page. If you'd like to:

Please remember the following things:

  • Be civil and remember to sign your posts with ~~~~.
  • If you see this page is being vandalised, you're welcome to undo.
Click here to add a new topic

Archives: 1

Final warning regarding duplicitous abuse of multiple accounts[edit source]

Hi Bukkit,

Regrettably, I've had to  lock your undisclosed alternate account, 29TB. The behavioural evidence was particularly compelling, with your requesting an IP block exemption. Indeed, this very act of doing so, with or without identifying Bukkit as your master account, was a serious breach of user accounts policy. However, you even agreed that only your main account, being Bukkit, shall request an IP block exemption of some sort. Given 29TB also repeated the same same pattern of editing in violation of Bukkit's local block, I contemplated locking your main account, but that seems a bit bureaucratic to require you to appeal and place you under a global user restriction.

Accordingly, you are now  indefinitely globally restricted from/to:

  1. Creating alternate accounts logged out. Any alternate accounts must be created while logged in to your main account, ideally on Meta Wiki; and,
  2. Using open proxies/VPNs/Tor on Miraheze, without prior consent from Stewards

As an aside, perhaps most troublingly, as 29TB, you apparently expressed interest in becoming an SRE MediaWiki Engineer volunteer, something you also expressed interest in as Bukkit. This lack of forthright disclosure for the most trusted role on Miraheze is particularly troubling.

Dmehus (talk) 20:08, 30 January 2022 (UTC)Reply[reply]

 Ack'd -- Cheers, Bukkit ( TalkAll Contribs ) 23:57, 9 February 2022 (UTC)Reply[reply]
@Dmehus: when would a good time to appeal the restrictions? -- Cheers, Bukkit ( TalkAll Contribs ) 20:21, 18 February 2022 (UTC)Reply[reply]
When would you want to create accounts while logged out or use open proxies/VPN/TOR? Naleksuh (talk) 20:27, 18 February 2022 (UTC)Reply[reply]
I’m actually contemplating locking my alts (except for my public account), but I’ll do TOR possibly within the next few months. -- Cheers, Bukkit ( TalkAll Contribs ) 20:30, 18 February 2022 (UTC)Reply[reply]
Bukkit, thank you for the {{ping}}, which I've only seen just now by coincidence of clerking one of your self-requests for deletion. With regard to removal of the arguably minimal global user restrictions, given that this occurred only a few weeks ago, I would personally not be willing to consider a full removal of the restrictions requiring you to publicly log any alternate account creations while logged into your main account for a minimum of at least three (3) months. I don't think it's a significant hardship for you to create any alternate accounts you require for your purposes, ideally on Meta Wiki. Hope that helps. Dmehus (talk) 00:19, 22 February 2022 (UTC)Reply[reply]

Tip regarding Twinkle[edit source]

Hi Bukkit,

Noticing this edit, I thought I'd point out a potentially helpful tip regarding the Twinkle gadget. If you navigate to your Twinkle preferences, you actually have the option of disabling notifications to user talk pages of the original page creating user, if you wish. Alternatively, I believe you can also simply uncheck the box to notify a given user talk page when tagging a page for deletion (this is particularly helpful with nominating your own page creations for deletion).

Dmehus (talk) 00:25, 22 February 2022 (UTC)Reply[reply]

Thank you, I forgot about how Twinkle works, since on WP I used RedWarn, and I rarely used Twinkle on Meta. -- Cheers, Bukkit ( TalkAll Contribs ) 00:41, 22 February 2022 (UTC)Reply[reply]
No problem. Do you go by the same username on English Wikipedia? I've never used RedWarn, but it looks quite decent. I don't personally use Twinkle, but do use BrandonXLF's Restorer user script. Dmehus (talk) 00:43, 22 February 2022 (UTC)Reply[reply]
On Wikipedia, I’m Bongo Cat -- Cheers, Bukkit ( TalkAll Contribs ) 00:48, 22 February 2022 (UTC)Reply[reply]
Ah, cool. Thanks. Dmehus (talk) 00:52, 22 February 2022 (UTC)Reply[reply]

Question[edit source]

Hi Bukkit,

Looking through your main account's contributions, as well as those of your alternate account, I noticed that you have chiefly adopted using your alternate account and ceased using your main account, and was just wondering if you could share any insight on why that seems to be the case? Noting that your alternate account is named per the cross-platform convention that it is (a) to be used less than one's main account and (b) in locations that are considered less secure (i.e., Internet cafés [do those still exist?], public wifi hotspots, and airport lounges). Noting that the timestamp of the apparent switch to your alternate account was closely in line with the imposition of an indefinite global user restriction, my concern here would be with regarding to evade scrutiny. While your restriction did not limit you to using only one account, globally or on Meta Wiki, on Miraheze, as it only prohibited you from using VPNs/open proxies and to creating alternate accounts logged out or in an otherwise non-transparent process, if I were to get the sense that this were the case (i.e., to evade scrutiny), this restriction would be expanded.

Thank you for your understanding, and for your attention to this message. :)

Dmehus (talk) 16:57, 19 March 2022 (UTC)Reply[reply]

I've been using my alt account recently during school-hours, however I have decided to make a new project whilst on a break, and I have not migrated it to my Bukkit account. The sudden change with accounts had nothing to do with avoiding scrutiny at all. Thank you for reach out to me regarding this apparent change of accounts, and I would like to wish you an amazing day. -- Cheers, Bukkit(Public) ( TalkContribs ) 17:14, 19 March 2022 (UTC)Reply[reply]
Bukkit, thank you for your quick response. That is helpful. When you say you "decided to make a new project whilst on [...] break," is this something I can assist with you with, by transferring or adding any local rights originally assigned to your alternate account to your main account, so you can resume using your main account? Additonally, noting you've replied from your main account, would you mind replying from your main account to provide a confirmation edit, so I know you still have access? Dmehus (talk) 17:21, 19 March 2022 (UTC)Reply[reply]
Hello, thank you for asking, however my project is my alts global.js, and I can put it in my main. Again, thank you for asking. -- Cheers, Bukkit ( TalkAll Contribs ) 17:27, 19 March 2022 (UTC)Reply[reply]
Thank you for the confirmation edit. Dmehus (talk) 17:28, 19 March 2022 (UTC)Reply[reply]

Dump files[edit source]

I noticed that you have got some dump files of the Qualitipedia wikis. What do you plan on doing with them? FatBurn0000 (sandbox | CentralAuth) 21:00, 5 September 2022 (UTC)Reply[reply]

Make them readily available to the general public, might locally host the wikis as well. -- Bukkit[cetacean needed] 21:14, 5 September 2022 (UTC)Reply[reply]
Oh okay. If you do import them somewhere, could you please import them with all revisions copied and all edits assigned to users if they exist locally? Also, what will happen with RWW and FWW? FatBurn0000 (sandbox | CentralAuth) 23:03, 5 September 2022 (UTC)Reply[reply]

A question[edit source]

Are you actually going to host the wikis independently, since FatBurn0000 said that you are. If so, that is a relief because I thought the wikis would be gone altogether, but they will just be off of Miraheze. Since there are still other Reception Wikis here on Miraheze I will stay here as well. Blubabluba9990 (talk) 23:15, 11 September 2022 (UTC)Reply[reply]

An explanation[edit source]

Let me explain everything. I am not obsessed. And I just like Miraheze and Qualitipedia. It is not against Qualitipedia policy to like Qualitipedia. Besides, Qualitipedia will be gone in three days. And where else will I discuss my plans for a revival. Here? I guess I have no choice but to make a new reception wiki central wiki. But I can't gather users there. Please. Blubabluba9990 (talk) 19:21, 24 September 2022 (UTC)Reply[reply]

I would dare say you have an unhealthy obsession with Qualitipedia. It's 100% true that there's nothing wrong in liking a project and being passionate about it but your messages have worried various community members as you exhibit excessive attachment and obsession with the wikis. You need a wikibreak. Agent Isai Talk to me! 20:28, 24 September 2022 (UTC)Reply[reply]
There is no excessive attachment or unhealthy obsession. This is all a reckless exaggeration. People are worried for no reason. Also there is barely any local administration to begin with. Blubabluba9990 (talk) 22:13, 24 September 2022 (UTC)Reply[reply]
@Blubabluba9990 You have to surrender the Qualitipedia as these wikis are about to close anyway due to numerous problems with these wikis described on this RfC and you actually having unhealthy obsession with reception wikis in general (frankly a bad idea) despite his global user page and comments says otherwise. TF3RDL (talk | contribs | FANDOM | Wikipedia) 00:18, 25 September 2022 (UTC)Reply[reply]
Original block vote was almost entirely unanimous (one oppose) and most concerns expressed are regarding your obsessiveness. I've been there before, trust me when I say you're lying to yourself. You're trying to convince staff, and yourself, that you aren't obsessed merely to be unblocked. It's very much needed in order to keep your mental health intact, we've done this multiple times on the discord server, and given that it's needed on-wiki, we've done it this time as well. I'm sorry, but it's going to stay. -- Bukkit[cetacean needed] 01:10, 25 September 2022 (UTC)Reply[reply]
The facts are simple. You don't think you're obsessed. Pretty much everyone else thinks you are with a long history to point to. Everyone else outweighs your statements unless you bring something genuinely new. Therefore you should let go until a later time. By replying now you are only wasting everyone's time. --Raidarr (talk) 13:17, 25 September 2022 (UTC)Reply[reply]
There is no obsessiveness! Blubabluba9990 (talk) 01:10, 26 September 2022 (UTC)Reply[reply]
Did you hear that? Denying with nothing to back it up doesn’t help anyone, if you want us not to think you’re obsessed, tell us why other than the generic "I’m not obsessed because I say so!" -- Bukkit[cetacean needed] 05:11, 26 September 2022 (UTC)Reply[reply]
I have said numerous times why I am not obsessed, and explaining what I said and that it does not make me obsessed. Blubabluba9990 (talk) 19:15, 28 September 2022 (UTC)Reply[reply]

Wiki creator helpful tips[edit source]

Hi Bukkit,

First off, I want to start by welcoming you to the wiki creator team. Thank you for volunteering! As you are no doubt aware, the Content Policy is our key global policy that guides us in creating wikis for our users. Essentially, every wiki needs to have both a clear purpose, a valid, discernable scope, and a topical focus. This is the main criterion that helps us to determine whether a wiki will have any potential Content Policy problems.

Second, I wanted to share with you a few tips that I found helpful when I first joined as a wiki creator:

  1. Study the wiki creator's guide. It contains many best practices, some of which are required steps wiki creators are required to undertake in approving requests.
  2. Private wikis. Private wikis can generally have a shorter description and a less specific purpose, scope, or topic, but they do still need one. If you have some reservations about approving it as, say, a public wiki, due to that vagueness, you can tell them, in your comments prior to approving it, that you're approving it only as a private wiki and remind them to ensure their wiki complies with all aspects of Content Policy;
  3. Subdomains. Subdomains are critical parts of wikis and shouldn't be overlooked. Make sure that each wiki request features a valid subdomain and, if a wiki request is not in English, that their subdomain clearly reflects their non-English affiliation, mainly when the subdomain requested occupies a generic, broad, non-specific English word such as "humans," "italy," and so forth. Subdomains such as "mywiki," "wiki," "wwwwiki," and so forth should not be accepted.
  4. Eurovision song contest and fictional worldbuilding wikis. These are two types of wikis that have few, if any, problems with them. So, as long as there's a clear sitename, URL, and at least a few words in the description that indicates this as the purpose, it's fine to approve them;
  5. Minecraft, Polandball, and Roblox. Many communities related to these games are seeking hosting at Miraheze. While it's great that wikis choose us to host them, what's not great is that they tend to be some of the messiest wikis. Due to these games' target audience (consisting mainly of persons under 18), drama tends to be abundant and userbases are sometimes rowdy. Hence why additional scrutiny is sometimes given to wikis embarking scopes related to these games. Personally, I almost always ask that requestors certify, under penalty of wiki closure, that they have read the Content Policy and Code of Conduct and promise to abide and enforce it on their wikis. This assures us that they've read global policy and are aware that any sort of disorderly conduct is prohibited on Miraheze. Wikis which seem to be schisms of larger communities should be paid extra attention as these generally end up causing plenty of drama and usually tend to be results of disagreement within wiki leadership;
  6. Reception wikis. Many of the Reception wikis tend to give us the most the grief, especially in terms of content that is very negative about users. Presently, it appears to be the near universal consensus of wiki creators to decline these sorts of requests, due to the heated nature of the reception wiki scene, especially after the closure of Qualitipedia. As such, should you encounter a request for one, it is up to you to approve or decline it as you think is best noting that presently, most wiki creators are not accepting these requests. As usual, recreation attempts of these should be declined per the Content Policy's forking clause which prohibits direct project forks;
  7. Duplicate wikis. Whenever possible, try to Google the topic which a wiki focuses on to ensure no duplicates already exist on Miraheze about that same topic;
  8. Google topics! If you're unsure about a topic references in a request, please Google it. If it weren't for Google, I personally would have approved a wiki related to white supremacy, harassment, and gray area topics, all because I was unsure about what a topic mentioned in a wiki request was about. If in doubt, Google the topic that the wiki request mentions to make sure what you're approving. This is vital of wiki creators;
  9. East Asian language wiki requests. These ones are tricky, but cause us arguably the most grief, particularly when they publish personal information of real people without their consent. Stewards have, in the past, closed swaths of Chinese language wikis following a detailed report on Stewards' noticeboard. If you are unsure about an East Asian language wiki request, feel free to decline and ask for more information as many times needed. Because we lack the proper manpower to oversee these wiki sometimes, it is particularly difficult to moderate them from a global perspective thus necessitating that you deeply scrutinize these sorts of requests;
  10. NSFW wikis. These wikis are sometimes our biggest sources of headaches because of the vast complexities of the topic. Accordingly, we scrutinise these requests extra to ensure proper compliance with the law and to ensure smooth sailing. Previously, we asked wikis to agree to certain conventions voluntarily on their wikis but now, per the new Content Policy, those conventions which were voluntary are now globally required. Please read over the new Content Policy's NSFW wikis clause and ask users if they promise to abide by the rules there under penalty of wiki closure and ask them to certify that their content is legally allowable in the United Kingdom;
  11. Copyright. Remember, Miraheze is a British company. As such, we use the fair dealing system, not fair use, which is stricter. If in doubt about how a wiki would be licensing their content, feel free to ask them if they're aware of the system and to certify that they'll comply with British copyright law;
  12. Conditional approvals exist. Remember, you can conditionally approve a wiki. If they deviate from this approval, it is within your right to request the wiki be closed for deviating from the approved scope and conditions. If iffy about a request, you can set conditions on the wiki approval which sets boundaries on the scope and focus and restricts a wiki in what they can focus on;
  13. Google Translate. Don't hesitate to use Google Translate to review non-English public and private wikis. Notwithstanding the above point, most of these wikis' descriptions translate surprisingly well. As you've probably already noticed, I like to copy and paste the translated to English description into "request comments," so other wiki creators can see it easily. This is optional, but it's a good practice; and,
  14. Don't hesitate to reach out on Discord and ask for a second opinion. If you are still unsure about approving a wiki, or just want a second opinion, don't hesitate to reach out to any wiki creator on Discord on #wiki-creators. This might be the most important guideline.

Agent Isai Talk to me! 06:24, 12 October 2022 (UTC)Reply[reply]

I'd just like to note that while available and if I succeed (or not) in my ongoing request, I'll also avail myself as a second opinion here or on discord when needed. --Raidarr (talk) Raidarr (talk) 13:17, 12 October 2022 (UTC)Reply[reply]

A kitten for you![edit source]

Best of luck to Miraheze in your new assignment :)

Hey Türkiye message? 08:15, 12 October 2022 (UTC)Reply[reply]

Wiki requests[edit source]

There's no need to decline requests to ask for more info. The on hold status works perfectly now due to commit change by Universal Omega here : - this applies to User:Agent Isai as well. Naleksuh (talk) 19:58, 13 October 2022 (UTC)Reply[reply]

On hold is meant to mark a request as "A wiki creator has seen it but wants someone else to also review it too so don't approve it" or "They've seen it but they asked the requestor a very important question so don't approve it." It's not meant to be used in cases such as where we're asking for more info. Agent Isai Talk to me! 20:03, 13 October 2022 (UTC)Reply[reply]
It's not meant to be used in cases such as where we're asking for more info. It absolutely is meant for exactly that, and the on-hold canned messages corroborate this. I was also the one who asked for the on-hold status in the first place, so I think I would know what my own idea was meant to do. Naleksuh (talk) 20:07, 13 October 2022 (UTC)Reply[reply]
And you are implying decline is meant for that? Because that's the misuse right there. Declining is supposed to be for, uh, you know, declining. Naleksuh (talk) 20:20, 13 October 2022 (UTC)Reply[reply]
I disagree that that's misuse. It seems we differ in standards. Agent Isai Talk to me! 04:33, 14 October 2022 (UTC)Reply[reply]
Okay, now I am confused; I would have thought on hold applied to any circumstance where the request is frozen to offer more information and to minimize the confusion of being outright declined for something that just requires correction. I don't see why 'very important question' and 'please provide more so we can make a better judgement' wouldn't fall in the same use. It would be best to minimize outright declines unless there is something in the request that makes the very concept impossible to be accepted. If the on hold system is written somewhat into a corner in this regard then it should be broadened and permit usage that accounts for this. --Raidarr (talk) 11:41, 14 October 2022 (UTC)Reply[reply]
Yeah, I agree. There's an on-hold for pending response, I see that ask more info should be an on-hold reason for that reason. -- Bukkit[cetacean needed] 20:30, 13 October 2022 (UTC)Reply[reply]
@Bukkit: When I wrote that response, I wrote it to mark requests (primarily NSFW requests) as 'A WC has seen it but I'm waiting for their response on an important question so don't approve' as it had happened before that I had asked a question in the comments and someone approved the request later on. This also predated the freeform field hence why I wrote it as "Needs more details" was not correct in those situations and there was no other response that could be selected.
I actually predate you in the proposal of an 'on hold' status and I myself was the one who wrote the 'on hold' message, last November hence why I am speaking from the position as writer of the original 'on hold' canned responses. Agent Isai Talk to me! 04:33, 14 October 2022 (UTC)Reply[reply]
what is happening here? All I see is people arguing about wiki creation. The user who loves human heads on alien/animal bodies in cartoons for no reason (talk to me uwu!) 05:13, 14 October 2022 (UTC)Reply[reply]
This is a discussion about the wiki creation system, which you may not understand if you are not privy to how the system works (and how it's changed, flexible or has different interpretations, as per above). If you'd like to get up to speed, check out Special:RequestWikiQueue. --Raidarr (talk) 11:42, 14 October 2022 (UTC)Reply[reply]

Patroller granted - 2023-03-2[edit source]

Hi, Bukkit. An administrator on Meta has granted you the patroller user group permission, which gives you the ability to patrol recent changes and new pages of other Miraheze users (both registered and anonymous) who are not either autopatrolled or an administrator. In addition, this group also means that your edits are autopatrolled, so other patrollers or administrators don't have to patrol your edits. You should also be aware that the granting of this user group is at the discretion of Meta administrators, so different administrators will have slightly different criteria for granting. Likewise, just as it is a discretionary appointment, revocation is also at the discretion of Meta administrators and, again, each will have their own criteria for revocation.

In the medium-term, plans are in the works to develop a Meta Patrollers School, likely led by one or two active administrators, that will provide a comprehensive set of guidelines for patrollers and answers to commonly asked questions.

Nevertheless, the following are some of the main guidelines for patrolling. If you follow these guidelines completely, it is unlikely your patroller user group should ever be revoked. In technical terms, even when you find content that requires deletion by an administrator or otherwise requires remediation, undoing, reverting, or rolling back (if you are also a rollbacker, of course), you should always first mark as patrolled any revisions regardless of whether that content is destined to remain extant to the page or even on Meta entirely.

  1. When patrolling talk pages, user talk pages, and noticeboards (in Main and Meta namespaces), you should first check to see whether the user properly signed their posts using four tildes (~~~~). If they have not, you should add {{unsigned}} by substitution ({{subst:Unsigned|username|00:01, 31 August 2020 (UTC)}}), where username is the user's username or IP address and the timestamp is the full timestamp from the diff page. As a best practice, you should also link to the diff in your edit summary, so other administrators and patrollers can easily tie your modification to the original edit being modified. To speed up this process, you can copy the diff-permalink user script from line 5 of this page into either your (a) common.js or (b) global.js page (the latter applying globally on all Miraheze wikis);
  2. When patrolling the noticeboards, ask yourself whether this topic is on the correct noticeboard. If it is not, you should move it to the correct noticeboard, by either undoing the edit or manually removing the topic (if there have been intervening edits), again linking to the original noticeboard of the topic and the new noticeboard where it was moved in your edit summary. On the new noticeboard, you would simply paste in the topic (including the section header), linking to the diff page as in the first step. An example edit summary might be Moved [[Special:Diff/######|this discussion]] from [[Stewards' noticeboard]] to [[Community noticeboard|here]], where ###### represents the numeric revision ID of the originally posted topic;
  3. Also when patrolling the noticeboards and talk pages (including user talk pages), as a best practice, take care to kindly fix any formatting mistakes (such as excess line breaks or incorrect wiki code), per WP:LISTGAP;
  4. If something requires deletion, you can add {{delete}} to the top of the page in question, taking care to follow the instructions on that template page;
  5. If you come across a user who repeatedly makes the same mistakes, send them a guidance note on their user talk page, informing of the steps need to edit and post constructively on Meta; and, finally,
  6. If in doubt whether something requires remediation or not, patrol it, and then ask any administrator via their user talk page or at Meta:Administrators' noticeboard if any further action needs to be taken.

If you have any questions, please don't hesitate to reach out. Thank you! --Agent Isai Talk to me! 07:36, 2 March 2023 (UTC)Reply[reply]

Thank you! -- Bukkit[cetacean needed] 12:12, 2 March 2023 (UTC)Reply[reply]