Add topic
From Miraheze Meta, Miraheze's central coordination wiki
Latest comment: 2 months ago by Karakorum in topic Donation barometer

Donation barometer[edit source]

Wouldn't it be useful to have the donation barometer updated on a frequent basis or are you all assuming that $0 will induce pity? Or are The Powers That Be too lazy to update? Or have you taken my donation and already spent it on takeout food?

Zero donations does not encourage confidence in Miraheze; as does a nine-month-old discussion page associated with it with no discussions about it. Do you really need to have that told to you? Apparently so, so that the sarcasm here is a waste. La. --Karakorum (talk) 22:52, 7 January 2024 (UTC)Reply[reply]

Unfortunately, the donation barometer does not update automatically. It is dependent on a volunteer with knowledge of the actual donations received to update it when they have the opportunity to do so. – Jph2 (talk) 23:13, 7 January 2024 (UTC)Reply[reply]
Please avoid such negative assumptions on the day of a fundraiser's launch, as said above numbers are manually entered and the volunteer who does so is a US-based individual/generally available to do so only a few times daily. I'm blown away that our community has already gotten us past 14% of goal in three days, and look forward to the service improvements that funding will bring. --NotAracham (talkcontribsglobal) 07:13, 11 January 2024 (UTC)Reply[reply]
The sarc was to tell somebody that something needed attention. Being civil or reticent about making complaints has really not worked in the past. The past history of Miraheze's response to problems big or small, say on phabricator, has been silence, an idiot jumping in to respond with worthless comments, or an obtuse explanation that sounds more like an excuse. You are making excuses. At this point, you'll have to earn any respect, volunteer or not. The structure to properly launch the fund raiser., i.e., someone to take care of the barometer and update, should have been begun at launch. Not that hard. I don't require instantaneous updates, but showing some kind of progress like barometer updating, and thus a break with the old way of doing things, would have given me some confidence in the new old order.
"Blown away": It sounds like you have never participated in online fundraising before, since in most every case, the bulk of donations are made early in the appeal. Let's see what happens down the road before getting too excited. The first $10k sounds like a "hard" requirement and it's not there yet. Fingers crossed. --Karakorum (talk) 22:04, 26 January 2024 (UTC)Reply[reply]
When this comment was published, the fundraiser had just started and most volunteers were away for the day. We'd all appreciate it if you did some some extra our way to spend on takeout food though :) Agent Isai Talk to me! 01:09, 14 January 2024 (UTC)Reply[reply]
Something like this needs to be put into the hands of one or two admins that would be dedicated to the task. Heck, if I knew it was about to happen, I would have volunteered to update since I'm onsite much every day. But I also figured that financial data would not be accessible to me.
All kidding aside, that's not a bad idea. Down the road when 2024's basic appeal is done, consider adding a tip jar that would convert into food credit cards, something useful that admins scattered everywhere on the globe could potentially use. --Karakorum (talk) 22:04, 26 January 2024 (UTC)Reply[reply]

Increase[edit source]

I noticed that the goal was increased from $10,000 to $20,000 a few days ago and was wondering what the extra money would be used for. (I don't mean to imply anything negative by asking this - I'm genuinely curious.) --SummerShores (talk) 00:44, 14 January 2024 (UTC)Reply[reply]

Initially, I augmented it as a test to get the cache purged as it was taking a while for it to purge and the amount raised is reflected in Fundraiser 2024/amount. I had tried a null edit but it didn't work (I assume it was because mwtask141, the server in charge of the jobqueue, was disconnected during that time and jobs were being handled by mwtask181 which is across the ocean and has a slow database/jobqueue connection for now). I meant to revert it to $10,000 but fell asleep as it was around 2am by then. Our fundraisers have never gotten to 100% of their goal so we all aren't holding our breath for it to reach the $10,000 mark but if it did and exceeded it and reached $20,000, we'd procure even more servers to future-proof the service, we'd buy up additional hardware to add to our servers to triple their capacity, especially in terms of storage so as to ensure redundancy on all servers, and perhaps even adding more cores to allow for more processing power. In addition, IP costs are high. We've had to buy some more IPv4 addresses in order to use them for our bastion servers (they connect our IPv6-only MediaWiki servers to the IPv4 world, this is extremely required because we use services like GitHub to pull the latest MediaWiki version, extensions, our Puppet config, MediaWiki config, etc.), NS servers, cache proxies, mail server, and more. As stated, we also plan to launch more caching servers which will help reduce load times across the globe. Users in places like Australia, East Asia, East Europe, and South America, all suffer abysmal load times because our only cache servers are in Canada and the United Kingdom, far from a good portion of our global users, due to very few financial resources and the cache proxies we do have are overloaded and underprovisioned to deal with tens of millions of daily pageviews. And of course, a big goal is to simply have a cushion to fall on. If next year's fundraiser isn't as successful, we wish not to panic both our volunteers and our users with the idea that Miraheze is on the brink of collapse. This scenario happened last year where we had to have a fundraiser sooner than expected because the one held a few months back simply wasn't enough. This is a terrible thing to occur because it means Miraheze cannot expand its services when it is gasping for air. Had we had some wiggle room to improve and expand, we could've avoided the db141 corruption incident in 2022 and the general slowness that Miraheze traverses through. Agent Isai Talk to me! 01:09, 14 January 2024 (UTC)Reply[reply]
I see! Thank you for the explanation! --SummerShores (talk) 02:17, 20 January 2024 (UTC)Reply[reply]

Why should I donate when you can't fix a simple issue?[edit source]

I never had to wait three weeks to have a Phabricator ticket fixed before the merger, not even during the second half of 2023. But ticket T11619 sat untouched until I directly asked Labster about it... and nothing has happened since Agent Isai ran a backtrace.

Instead of making plans to add new and sexy features, how about fixing the wiki that you're building on first?

I had $500 in US dollars set aside to contribute once the issue was fixed. That's now $300 in Canadian dollars. Keep dragging your feet, and I won't donate at all. Robkelk (talk) 16:10, 21 January 2024 (UTC)Reply[reply]

@Robkelk: I understand your frustration but I don't think a threat of not donating if we don't resolve a task is appropriate. While we very much appreciate donations, we don't resolve tasks based on how much people donate. Besides, donations are purely for infrastructure and don't go to volunteers. The fact is we unfortunately have a lot of tasks and are also working towards a merger so no one has been able to fully resolve your task yet. As you have seen, two volunteers have engaged with it but have simply not found a solution yet. Reception123 (talk) (C) 16:46, 21 January 2024 (UTC)Reply[reply]
You have missed my point. Why should I pay for worse service than I was previously getting? (And those "two volunteers" are both Board members, not techs.) And it's a statement of fact, not a threat. [User:Robkelk|Robkelk]] (talk) 16:58, 21 January 2024 (UTC)Reply[reply]
Again, we understand your frustration. And I bet you are not the only one with an unfinished ticket. Right now, we cannot quite give the same quality of service as we used to. That's because we are still in process of combining Miraheze with WikiTide. I am sure all this will go away after some time. We just need time and maybe more volunteers. (I don’t know, I don’t work with Phabricator) Please be patient. Commetian Empire (talk°•◇•°CentralAuth) 18:32, 21 January 2024 (UTC)Reply[reply]
Oh, I'm sure that I'm not the only one with an unfinished ticket. The frustrating part is that I had to escalate the issue to upper management in order to get even an acknowledgement that the ticket had been received, let alone queued for later investigation... and there' still no indication that anybody has volunteered to look at it, even with the question that Labster asked in the ticket indicating that there may be a straightforward and simple fix for the issue. It takes less than a minute to tell somebody "we're looking at it" -- which, by the way, still hasn't happened.
As for being patient, I have been waiting for three weeks already. I see zero indication that any technical volunteer even knows that the issue exists. Is anybody even looking at the ticket queue? Does anybody know?
This is poor IT service management.
You've got a fundraiser going to purchase/rent even more hardware/cloud when you can't even support what you have. You definitely need more volunteers before you should even think about getting more tech. It appears that this fundraiser was started prematurely. Robkelk (talk) 19:10, 21 January 2024 (UTC)Reply[reply]
> You definitely need more volunteers before you should even think about getting more tech. It appears that this fundraiser was started prematurely.
Ideally, this would be the case but it's not. Why do I say that'd ideal when the described scenario is still negative? Well, our servers are on their last leg and that last leg is shaking, on the verge of failing. An infrastructure engineer described it as being "on life support". This past week, all images went down due to yet another disk failing. As it stands, our servers are also super slow which is why you'll have bouts where wikis take half a minute to load. We're not upgrading servers because it'd be fun to do, we're upgrading them because we have to do that ASAP or else we get another month long db141-esque outage. Hopefully once we tackle tech, we'll be able to focus on volunteers. It is certainly hard to recruit people to man a ship when the ship is about to capsize. Agent Isai Talk to me! 19:50, 21 January 2024 (UTC)Reply[reply]
> Ideally, this would be the case but it's not. Why do I say that'd ideal when the described scenario is still negative? Well, our servers are on their last leg and that last leg is shaking, on the verge of failing.
That answers the question that I initially asked. Thank you. Robkelk (talk) 00:33, 23 January 2024 (UTC)Reply[reply]
PayPal didn't give me a chance to identify myself during the donation. Transaction ID 93J51178AT1855505 is me. Robkelk (talk) 00:47, 23 January 2024 (UTC)Reply[reply]
Thank you for generosity! Hopefully in a month or less, wikis should be much faster once we upgrade hardware. Agent Isai Talk to me! 00:57, 23 January 2024 (UTC)Reply[reply]
This issue is resolved now. Your point about poor IT service management is well taken, and we rely on volunteers to fill all of the roles, and there is really no separation between technical team and consumers of the service. In ways this is good, but it means we don't always get end user priorities right. Here we clearly failed, and I'm sorry about that.
On the other hand, you seem to be expecting a payment for services model here. Unfortunately, we are an all-volunteer operation, and can't provide that. If that is what you really feel you need, I suggest that you take your money and your wikis somewhere else, because at our current level of donations we cannot afford to hire anyone (beyond the occasional remote hands for service installs).
It's not a case of spending money for servers where we can't support what we have, it's that our servers are barely running under the load, hard drives keep dying, and we are at increasing risk of losing your data by trying to save our 10 year old pet servers from dying. Moving is the highest priority, and we need to transfer services in able to ensure that the service continues to exist at all, without significant degradation from where it already is. Your ticket was important, but certainly less critical than that. Labster (talk) 19:54, 21 January 2024 (UTC)Reply[reply]
Sorry about that. As I explained on the task, no one knew why this issue popped up suddenly and we thought it may have been an extension bug but we spent some time reviewing the extension code and saw no recent breaking changes or faulty extension code. It appears it was due to some very out of date SQL that needed to be fixed as your wiki grew beyond what the SQL could accomodate. We've since corrected that so we apologize for the delay. Agent Isai Talk to me! 19:45, 21 January 2024 (UTC)Reply[reply]

How do I see the **real-time** donation counter?[edit source]

the topic explains itself, because I want to be constantly updating it to be as accurate as real-time. 2607:FB90:79BF:C42F:7911:5609:D025:E9F8 14:32, 25 January 2024 (UTC)Reply[reply]

Hi there,
Miraheze does not currently employ the use of a real-time donation counter. The current counter is instead updated every few days when a Director has time to update the page. BrandonWM (talkcontributionsglobalrights) 14:45, 25 January 2024 (UTC)Reply[reply]