User talk:Alolitas

LiquidThreads 3.0 release
Hi Alolita,

You're listed as the project manager for LiquidThreads 3.0, which was scheduled for release last month (August). I don't see any project updates, and I wonder if the project is still active. If so, I wonder when the stable release might happen.

thanks --Ceramic catfish 15:08, 1 September 2011 (UTC)

A kitten for you!
Thanks for making WikiLove! :D

Matt Heard (talk) 10:06, 2 March 2012 (UTC) 

LT 3.0
Nothing seems to have happened on Liquid threads in the last 5 Month - can you provide us with some information? G.Hagedorn (talk) 12:48, 17 April 2012 (UTC)

LQT?
Will there be any development around LiquidThreads or can I mark this as dead and no further development expected? --DaSch (talk) 12:43, 14 July 2012 (UTC)

Hi! Thanks for your note. Please ping Andrew Garrett on the latest on LQT. Terry Chay is now the engineering manager responsible for LQT. Cheers! Alolita

GSoC / OPW IRC AllHands this week
Hi, you are invited to the GSoC / OPW IRC AllHands meeting on Wednesday, June 26, 2013 at 15:00 UTC (8:30pm IST, 8am PDT) at #wikimedia-office. We have done our best finding a time that works decently in as many timezones as possibles. Please confirm at qgil@undefinedwikimedia.org so I can add you to the calendar invitation and I have your preferred email for other occasions. If you can't make it's fine, but let me know as well. We have left a notice to all students, but your help is welcome making sure yours is aware about it. Thank you!--Qgil (talk) 20:24, 24 June 2013 (UTC)

Indian statistics
Hello Alolita, do you know if there is any place where I can see combined statistics for Indian/Asian Wikimedia projects, to see if some of them present some interesting trends? I know of Language tools/Impact Measurement and Metrics but that's perhaps too complex and will take a while; we used to have EN_India/ and EN_India/ReportCardIndia.htm but they've been discontinued in March 2012 and in the new reportcard I can only find comScore data for India but nothing else. Does this mean that the WMF is no longer interested in such metrics for India? If there is interest but no tools yet, who should I ask to get some, and what should I focus on asking? I see for instance that a lot of stats work is being put in ad hoc limn instances like ee-dashboard, are its maintainers those to be asked? Thank you very much, Nemo 08:01, 3 August 2013 (UTC)

How about cursor hover translation as a feature of Wikimedia software
Hi Alolitas,

Krinkle has directed one of my queries to him to you.

I developed the GoogleTrans gadget, which does cursor hover translation of individual words and/or small amounts of selected text. It's been a gadget now for around 5 years. There are around 23,000 accounts that load the gadget although there is less actual use of it. I estimate there is around 10,000 translations done a month.

One of the good features of it's UI is that you need to 1) position cursor 2) hit SHIFT key to get the translation popup. This limits unintended popups, which is a problem with the actual Google Toolbar word translator.

GoogleTrans is on around 15 wikis, including the Hindi. I've recently put some romanisation in the hindi wiki, and this seems to have become popular among some of the users there.

How about a cursor hover translation feature for all of Wikipedia. The GoogleTrans gadget certainly shows it can be done.

Having all knowledge in one place for all people is a truly noble goal, but isn't overcoming language barriers an associated and also noble goal for such a project. And cursor hover translation certainly is quicker to look up a word (or small amounts of selected text -- which GoogleTrans also does) than manually looking up a dictionary.

Google isn't maintaining the word translator in the Google toolbar anymore. There is imtranslator.net, but it is a bit clunky with an extra translation window hanging around the screen. Cursor hover translation is also very good when you are trying to brush up on a language, when you know it a bit and want to get better at it, like Russian speakers in the Ukraine trying to learn a bit of Ukrainian, or English speaking Canadians trying to brush up on their high school French. The full page translations that Google does are not very good if you are actually trying to learn the source language. For instance, I can read French well, but will need to translate a word every paragraph or so. And, as for my Spanish, I need this once or twice a sentence.

Reading other wiki languages is very good for your understanding of the world. I remember reading in the eswiki that the USA had to borrow 41 cents to every dollar it spent recently. That was a very good statement that the US really was in budget problems. Such a detail would have been scrubbed out of the enwiki by legislative aids in Washington. So, as it turns out, in a world where everybody uses the enwiki, it's difficult to put embarrassing truth in an article there. This means you need to be able to read a wiki other than the enwiki to get a good view of a contraversial subject. This means you will be rewarded by reading wikis in languages you are not fully proficient in. This means that cursor hover word and selected text translation is an aid that will help this, and appropriate for an encyclopedia like Wikipedia.

As for cost, I don't think it will be that much. Google charges 20$ a million characters of translation, that's 5000 translations for a dollar if each word is 10 characters. Perhaps only allowing single word translations instead of selected text might keep the cost manageable. And there are other translation providers as well.

The help for GoogleTrans is at [].

Wikipedia is a great website, It's so useful to me that I contribute $20 a paycheck. Thanks for reading.

Endo999 (talk) 23:38, 29 August 2014 (UTC)

Projects
Here's my wish-list of Projects which would benefit minority languages:
 * 1) Get wikidata to populate existing infoboxes automatically: eg Man United's current squad automated, politicians automated at each election; at present, with only 140 regular editors, we have old info as some have not been updated.
 * 2) Automatically copy over (from en) all Templates and Modules; some languages won't use them, others will if they're copied over. At present, when we need a new template on Welsh language, we have to copy up to 120 templates, subtemlates, which takes me all day.
 * 3) Share databases between all languages: a pool of databases which could then be used using AWB etc
 * 4) New non-language logos for MediaWiki and Wikimedia Commons; the picture tells the story. No language necessary!

Many thanks fo your great work! Llywelyn2000 (talk) 15:51, 3 September 2014 (UTC)