Re: [Wikimedia-l] Paid API?

Hello, Why i'm recieving this message : Message not delivered There was a problem delivering your message to *don...@wikimedia.com*. See the technical details below. * Mohammed Bachounda * Leader Wikimedia Algeria UG [image: Thumbnail for version as of 13:48, 19

Re: [Wikimedia-l] Paid API?

Yes it's - donation not working for me * Mohammed Bachounda * Leader Wikimedia Algeria UG [image: Thumbnail for version as of 13:48, 19 April 2020] On Thu, Jul 9, 2020 at 2:20 PM William Chan wrote: > It's don...@wikimedia.org. > > On Thu, Jul 9, 2020, 19:05

Re: [Wikimedia-l] Paid API?

Hi, Great news: the WMF is going to charge the tech giants for using the API millions of times each day. Nothing in the free licenses we use obligate us (that is we in our movement) to provide an API for free as in beer. It is part of KAAS: Knowledge As A Service, part of the strategic direction

Re: [Wikimedia-l] Paid API?

It's don...@wikimedia.org. On Thu, Jul 9, 2020, 19:05 Mohammed Bachounda wrote: > Hello, > Why i'm recieving this message : > Message not delivered > There was a problem delivering your message to *don...@wikimedia.com*. See > the technical details below. > > * Mohammed Bachounda

Re: [Wikimedia-l] Paid API?

I tend to agree with this. I'm one of the first to criticize WMF when they deserve it (I wish they didn't as often!), but I see nothing wrong with consumers of huge amounts of data being asked to chip in to cover the costs of providing it. That is, of course, provided that there is never any fee

Re: [Wikimedia-l] Operation and oversight of OTRS system

I agree with Tomek here. And let me emphasize that not all OTRS admins have access to all queues: in fact, I think only the admins do. OTRS is a very fast system with queues per project and again per language, and access is given per queue. A queue is mostly created per Wikimedia project and

Re: [Wikimedia-l] Operation and oversight of OTRS system

On Tue, 7 Jul 2020 at 07:46, Tomasz Ganicz wrote: > > I’m unable to answer this due to the Confidentiality Agreement all OTRS > > agents sign. > Well, please do not create conspiracy theories... It's not a conspiracy theory if there is evidence of a conspiracy. > Actually, as far as I

Re: [Wikimedia-l] Operation and oversight of OTRS system

On Mon, 6 Jul 2020 at 18:52, Jonatan Svensson Glad wrote: > 1. what are OTRS' rules and policies? > I’m unable to answer this due to the Confidentiality Agreement all OTRS > agents sign. So who is able to answer it? > I believe OTRS falls under the Communications committee’s purview, There

Re: [Wikimedia-l] Paid API?

Thanks Joseph for the links. It's more clear now. I think I need to clarify something: I'm not against asking the big corps to pay. If they are using a significant amount of our computational resources (=donors money) to make even more money, they should pay. And thank you for improving the

[Wikimedia-l] [Wikimedia Research Showcase] July 15, 2020: Medical Knowledge on Wikipedia

Hi all, The next Research Showcase will be live-streamed on Wednesday, July 15, at 9:30 AM PDT/16:30 UTC. Wikipedia is one of the most important online resources for health information. This has been especially highlighted during the Covid-19 pandemic: since the beginning of the year more than

Re: [Wikimedia-l] Paid API?

Hey all. I'll reply to some of the more finer legal details tomorrow but to be clear the repo will be made available publicly and the code base will be open sourced and based on open source tech. Seddon On Thu, 9 Jul 2020, 19:06 Benjamin Ikuta, wrote: > > > I agree, the lack of transparency

Re: [Wikimedia-l] Paid API?

Worth noting, for those who may not have been tracking this issue in the media in recent years: CEO Katherine Maher has prominently and frequently highlighted how big tech companies benefit from Wikipedia and Wikimedia content, and that they pay little if anything for it. This shows up in many

Re: [Wikimedia-l] Paid API?

I agree, the lack of transparency is quite concerning, as is the use of AWS. I sure hope we're not going to be producing closed source code! On Jul 9, 2020, at 10:19 AM, Amir Sarabadani wrote: > Thanks Joseph for the links. It's more clear now. > > I think I need to clarify something:

Re: [Wikimedia-l] Paid API?

Let me just flip the perspective. The tech giants are leveraging their resources to serve the knowledge we create to even more users. In a way, they are partly furthering our mission. So rather than solely using our resources as a cost, it could instead be viewed upon as a multiplier. Now this is

Re: [Wikimedia-l] Paid API?

On Thu, 9 Jul 2020 at 21:15, Dan Garry (Deskana) wrote: > ECR and GKE. > Correction: I meant GCR, not GKE. Dan ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines and

Re: [Wikimedia-l] Paid API?

Hi, On 2020-07-09 13:15, Dan Garry (Deskana) wrote: > Which cloud provider would you recommend? Wikimedia Cloud Services, which incidentally, has the fastest network connection to Wikimedia sites by virtue of it being hosted *inside* the cluster. -- Legoktm signature.asc Description:

Re: [Wikimedia-l] Paid API?

On Thu, 9 Jul 2020 at 18:20, Amir Sarabadani wrote: > * I find it ethically wrong to use AWS, even if you can't host it in WMF > for legal reasons, why not another cloud provider. Which cloud provider would you recommend? Popular alternatives to AWS include GCP (by Google, who unscrupulously

Re: [Wikimedia-l] Paid API?

All cloud providers are approximately level in evil. The way we break it down at my day job is: * AWS: when you want it to work and want customer service * Microsoft: when you hate yourself, you're running Windows or both * Google: when you want zero customer service ever under any circumstances