@sillyfudgemonke@pheodore Indeed, it was declined as we have another wiki with a similar topic. If approved, how would your wiki differ from the one that currently exists?
@RobertMCutler@miraheze We strive for transparency which is why we've been constantly updating our users about the situation on the SRE noticeboard: https://t.co/4j3n5myo3E
The page includes explanations for what happened and what we're doing to prevent a future incident from occuring.
@YTChakuwiki@MirahezeStatus we can get the databases back online, we can try to merge the wikis. Otherwise, there is nothing that can be done other than waiting. (2/2)
@YTChakuwiki@MirahezeStatus Data recovery is still in progress which is why no new updates have been posted. I see you are very anxious about your wiki per your tweets so if you would like to temporarily recreate your wiki from any backup on hand, you can request so on Phabricator and then if (1/2)
@Zzh511511@adeleismahbitch@truth_hertzzz@miraheze Hi! I'm a Miraheze Steward. We didn't receive your report. Can you forward me your report so that I can look at it? Also note, ts@ belongs to Trust & Safety who cannot enforce the Content Policy, only Stewards can, and it's recommended that you contact them via reports.*. Thanks.
@iownfivewiis and stop the abuse. I've since rescinded that wide range block in favor for a smaller, /64 block which should've been there in the first place. My deepest apologies. (2/2)
@iownfivewiis You're absolutely right it's irresponsible. I'm the one who issued that global block. At the time when I initially issued the block, severe abuse was occurring from the range but I was unable to calculate what CIDR notation would correctly target the abuser in question (1/2)
@ianwiltdotcom@felix_croc@tanisthelesbiab We're 100% free always and run exclusively on donations meaning you'll never find an ad on our wikis. We give users as much control possible allowing them to tweak almost all configuration variables and allowing users to enable one of over 300 extensions or 20 skins. :)
@Niathecatgirl07 I work for Miraheze and please note that the reception wikis are just wikis hosted by us, not operated. We don't endorse any of the content on those wikis but sadly, people think Miraheze = Reception Wikis exclusively when in reality, we host over 5,000 diverse wikis
@GRAYRAVENSPGR Regarding the last point, thanks to our generous donors, we are moving towards upgrading our hardware in a month or two which should improve loading speeds. (2/2)
@GRAYRAVENSPGR We apologise for the issues. The first two issues are beyond our control and a bug report should be filed with the extension developers of MsUpload and Tabber as the latest version of these extensions are broken across all MediaWiki installs, whether you use Miraheze or not.(1/2)
@Rosespikes@legendblade It may be difficult sometimes but it has happened before. We have various wikis which out SEO Fandom and are very successful despite having a Fandom counterpart. We also like to not 'beg' too much as we know it's annoying and so we try to avoid that if possible.
@AlexSmi30515797@miraheze Yes, I just wrote it like that to prevent spambots from reading it as an email address and adding it as another target to spam with advertising :)
@AlexSmi30515797@miraheze Hi there, please ignore the other tweet, it's a scam. If you can't make an account, try emailing cvt {@} miraheze {.} org and CVT will create an account for you, thanks!
@SuccuCirno @Reception123MH@Seglegs@getFANDOM@miraheze I don't see your concern. As long as you verify all content complies with our Content Policy and applicable local laws, we're not going to bother wikis or "censor" them liberally.
@MichaelETenner @miraheze Hey there! I'm a wiki creator at Miraheze. Whenever we decline requests, there's always a reason why in the "Request comments" tab. If you shoot me a DM with your username, I may be able to check it out for you.