Re: [Wikidata-l] WikiData change propagation for third parties

2013-04-26 Thread Sebastian Hellmann
Dear Jeremy, please read email from Daniel Kinzler on this list from 26.03.2013 18:26 : * A dispatcher needs about 3 seconds to dispatch 1000 changes to a client wiki. * Considering we have ~300 client wikis, this means one dispatcher can handle about 4000 changes per hour. * We currently have

Re: [Wikidata-l] [Wikidata-I] [GSoC 2013] Mobilize Wikidata Proposal Draft

2013-04-26 Thread Daniel Kinzler
On 26.04.2013 06:06, Pragun Bhutani wrote: Hello, I've been having discussions about my GSoC 2013 project with the Wikidata group on the IRC(#mediawiki-wikidata) for a few days and have completed the first draft of my proposal. I'd really appreciate some feedback on it. I welcome any

Re: [Wikidata-l] WikiData change propagation for third parties

2013-04-26 Thread Dimitris Kontokostas
Hi Daniel, On Fri, Apr 26, 2013 at 6:15 PM, Daniel Kinzler daniel.kinz...@wikimedia.de wrote: On 26.04.2013 16:56, Denny Vrandečić wrote: The third party propagation is not very high on our priority list. Not because it is not important, but because there are things that are even more

Re: [Wikidata-l] WikiData change propagation for third parties

2013-04-26 Thread Daniel Kinzler
On 26.04.2013 17:31, Dimitris Kontokostas wrote: What we do right now in DBpedia Live is that we have a local clone of Wikipedia that get's in sync using the OAIRepository extension. This is done to abuse our local copy as we please. It would be owesome if this Just Worked (tm) for

Re: [Wikidata-l] [Wikidata-I] [GSoC 2013] Mobilize Wikidata Proposal Draft

2013-04-26 Thread Pragun Bhutani
I agree with you on that. I did make that mistake while writing down my proposal at first, but Sumanah corrected me early on and advised me to limit the scope to 6 weeks. Which is why I've decided to limit my project to Make Wikidata usable on mobile devices. If that's sorted well in time, I'd