Meta:Administrators' noticeboard

Archives:
 * Archive 1 (9 August 2015 - 21 December 2015)
 * Archive 2 (21 December 2015 - 13 December 2016)

Please handle Special:AbuseLog/78100
Hi, since meta is opted out from CVT, I'd like to have this case handled by a local admin. Thanks.-- 22:22, 31 August 2018 (UTC)
 * User has been globally locked. &#32; Miraheze Logo.svg CnocBride | Talk | Contribs  13:42, 1 September 2018 (UTC)

Request for autopatrolled
Can someone please add the autopatrolled flag to my account here on Meta? Thanks. Amanda Catherine (talk) 19:12, 5 September 2018 (UTC)
 * ✅ John (talk) 19:22, 5 September 2018 (UTC)

Request for adminship and bureaucrat
Hi, I'd love to request to become an administrator and bureaucrat on Miraheze. I'm really interested in reverting vandalism, save peoples user pages from vandalism. I have reverted an inappropriate edit from User:Amanda Catherine. She awarded me with the vandalism award. I'd love to step in and become a hero and join in the piece of the action, plus I have lots of knowledge and more to share. Louise3 (talk) 20:08, 10 September 2018 (UTC)


 * While I appreciate your efforts to revert vandalism and I applaud your enthusiasm, I don’t think you are active enough, both on this wiki independently, and in the global Miraheze community, to be granted these rights. Perhaps try again in a month or two once you have more experience and activity. Amanda Catherine (talk) 20:12, 10 September 2018 (UTC)
 * In light of further evidence that has now come to my attention, it is perfectly clear that the candidate is not being honest or forthcoming. Amanda Catherine (talk) 20:22, 10 September 2018 (UTC)
 * 1 this isn’t the right place for this, 2. If you want to to anti vandal/anti spam work then CVT is probobly a better option. MacFan4000 (Talk Contribs) 21:13, 10 September 2018 (UTC)

Restoration of Sovereign.miraheze
Hi all, we managed to get ourselves deleted for inactivity, even after checking and resetting the warning to let everyone know we are still active and maintaining the wiki. The majority of the Sovereign wiki is for the most part archived, meaning very few edits are now made. We have a list of role-plays that we need to maintain and can't be done by just one person (it creates an unweildly mess). Can we have this back or at the very least the data so that we can upload the information elsewhere? We're quite surprised that there was no attempt to contact us before the wiki was deleted yesterday. Enfaru (talk) 13:10, 7 October 2018 (UTC)


 * Hi, we cannot restore the wiki content as we have no backup for the wiki. Since the backup was refreshed at 00:00am utc a few hours after deleting the wiki. Your welcome to request the same wiki through CreateWiki. You could even have your wiki whitelisted in future so it's not closed. See Dormancy Policy. And we apologize for any inconvenience caused by this. Paladox (talk) 18:15, 7 October 2018 (UTC)


 * O_O no backup!? Welp, that's the last time I use Miraheze. The entire point of using Miraheze was to have an online resource that could be used for a long period in the future and we would have at least liked to have an email that the board was going to be closed before you went ahead and deleted it. I've checked my emails and there's nothing, nada, no contact from Miraheze (and Miraheze emails are white listed and filtered into an appropriate folder for priority). You've cost us months and months of work so I am distinctly not happy. Enfaru (talk) 20:45, 7 October 2018 (UTC)


 * We do have backups just we deleted your wiki before a fresh backup was done which is done every sunday. You would have received your email 4months ago about the wiki being closed. Paladox (talk) 21:01, 7 October 2018 (UTC)


 * To clarify, the backups we have are for internal use. Users must request that there wiki is backups which is then accessible through static.miraheze.org/dumps. Paladox (talk) 21:03, 7 October 2018 (UTC)


 * As I never delete my emails (for that address) I can confirm no such email was received four months ago. Who's bright idea was it to delete right before the backups are all deleted? Again, I took all necessary steps including making sure I had deactivated the notification on Sovereign at the time it was first flagged. If additional actions were required it needs to be made clearer/easier to undertake including the need to 'request' a backup of which I had no idea I would need to do. I had long been under the impression that backups would be kept for at least a week which users could request to roll back to in case of issue. You've screwed up so own it and do something about it to protect other users from suffering the same fate.


 * One last item: The email I was sent for another wiki states that I had six months from 7th June 2018 (this seems roughly like the time when I noted the wiki was marked for closure), which would mean the earliest time it should have been due for 'potential' deletion (as the email makes clear) is 7th November 2018. Not 120 days but at least six months. I've also just checked the Dormancy Policy which states that 180 not 120 days is required to elapse...which ties in with the six months. The dormancy also states that "Users will have a minimum time after each notice to fix the problem if they wish" meaning that 245 days should have passed before a flat out deletion or six months past the closure date. So much not happy. Enfaru (talk) 22:57, 7 October 2018 (UTC)
 * Replying with comments to quotes;
 * "Who's bright idea was it to delete right before the backups are all deleted?" It was no ones. However because of a lack of funding, we have to be extremely conservative with backups and it is unfortunately a consequence of this, that this happened.
 * "Again, I took all necessary steps including making sure I had deactivated the notification on Sovereign at the time it was first flagged." Looking into the logs, the wiki was never marked as active or open after it was initially closed in June. The records, therefore, that Miraheze has retained with relation to this shows the wiki was inactive since approximately April and therefore enforcing the community-agreed Dormancy Policy was within Miraheze's rights. As we were not made aware of any issue regarding the functioning of our software being defective, Miraheze has no liability regarding the deletion of the wiki and its content.
 * "including the need to 'request' a backup of which I had no idea I would need to do. I had long been under the impression that backups would be kept for at least a week which users could request to roll back to in case of issue." We have never, at any time, not said users must request their own backups. It is clear and prominent on Backups, on the FAQ with the latter being prominently linked on several high profile pages as well as every single wiki upon creation. I do not know where you have gotten this information from, however, it is not from Miraheze.
 * "You've screwed up so own it and do something about it to protect other users from suffering the same fate." Miraheze and consequently it's operations staff have not screwed up. A process has been followed which has allowed sufficient time to resolve an issue and that was not resolved on the user part. Users are protected and in 3 years, this is the only case of this happening. There was one previous case of a wiki being deleted mistakenly, however because of backups being in place by the request of the wiki community it was resolved quickly and sufficiently as soon as the issue was brought to our attention.
 * "Not 120 days but at least six months." The Dormancy Policy is clear in this regard. Wikis are closed after 60 days of inactivity and deleted after a further 120 days of inactivity. The wiki was closed approximately midnight of June 7th 2018 and therefore was eligible for deletion on October 4th 2018 (having been 120 days since it was closed, thus 180 days since it was last active).
 * "The dormancy also states that "Users will have a minimum time after each notice to fix the problem if they wish" meaning that 245 days should have passed before a flat out deletion or six months past the closure date." You are misreading the policy to put it within your favour. There is a table which shows the minimum notice periods, they are not additive as you are putting them. 180 days is the minimum period with regards to deletion not 245 days. The minimum period is never stated except within the table as a reference, it is therefore inferred the minimum period is the time between two distinct actions (inactivity warning at 45 days, closure at 60 days - therefore the minimum notice period will be 15 days. As in there will be a minimum of 15 days between an inactivity warning and a closure notice at all regards).
 * Not a quoted comment however; you are arguing that you were never notified by Miraheze that your wiki was closed yet are telling us you were aware. Your argument seems to based on a lack of proper communication however there are no required standards of communication from with regard to this matter besides the on-wiki notice. You were informed of the intended actions as required by policy and thus you confirm you were aware of both the state of the wiki and the policy at hand.
 * John (talk) 23:48, 7 October 2018 (UTC)

For some reason, www.marinebiodiversitymatrix.org does not work, but “marinebiodiversitymatrix.org” (without the “www”) does.
For some reason, www.marinebiodiversitymatrix.org does not work, but “marinebiodiversitymatrix.org” (without the “www”) does.
 * Replied via email. Reception123 (talk) ('C' ) 09:47, 22 October 2018 (UTC)

Custom domain
I am the admin of Gyaanipedia. https://gyaanipedia.miraheze.org I had followed all the steps for custom domain two days ago but it doesn't work my custom domain is http://gyaanipedia.co.in please help me Shaunak Chakraborty (talk)