headers
Harry Burt | 1 Apr 2012 11:39
Picon

GSoC -- TranslateSvg: Bringing the translation revolution to Wikimedia Commons

Hey all,

Now I have more of the details sorted out, I'd like to invite feedback on
my Google Summer of Code proposed project, entitled *TranslateSvg: Bringing
the translation revolution to Wikimedia Commons *.[1]. Obviously the
deadline for submissions is rapidly closing in, but comments would still be
very welcome, either before or after that deadline.

To quote from my proposal:

> TranslateSvg has the potential to revolutionise the ability of Wikimedia's
> diverse groups of image maintainers to work together creating and improving
> the same communal set of SVG (vector) images. At the moment, providing
> alternative translations of SVG files typically requires "forking" the
> image. This drastically increases the image's maintenance burden and
> thereby discourages image improvement. Where such improvement does take
> place, it is seldom shared between different language versions.
> TranslateSvg would completely change this suboptimal workflow by removing
> the need for the image to be forked; instead, translations (provided using
> a streamlined special page) would be saved inside the image itself, in
> accordance with the SVG 1.1 specification. The file, complete with these
> embedded translations, could then be displayed in either the language of a
> wiki, the user's preferred interface language, or any given arbitrary
> language. If the SVG file were to be served directly, it would helpfully
> display in the user's system language where such a translation was
> available, aiding reuse possibilities. When I originally raised this idea
> it received the support of several Wikimedia Commons users as well as WMF
> developers.
>
Thanks!
(Continue reading)

Permalink | Reply | 5 comments |
headers
David Gerard | 1 Apr 2012 12:06
Picon
Gravatar

Time to redirect to https by default?

Lots of monitoring going into place:

https://en.wikipedia.org/wiki/Wikipedia:List_of_articles_censored_in_Saudi_Arabia
http://www.bbc.co.uk/news/uk-politics-17576745

What are the current technical barriers to redirection to https by default?

- d.
Permalink | Reply | 40 comments |
headers
Petr Bena | 1 Apr 2012 12:55
Picon

Re: Time to redirect to https by default?

I see no point in doing that. Https doesn't support caching well and
is generally slower. There is no use for readers for that.

On Sun, Apr 1, 2012 at 12:06 PM, David Gerard <dgerard <at> gmail.com> wrote:
> Lots of monitoring going into place:
>
> https://en.wikipedia.org/wiki/Wikipedia:List_of_articles_censored_in_Saudi_Arabia
> http://www.bbc.co.uk/news/uk-politics-17576745
>
> What are the current technical barriers to redirection to https by default?
>
>
> - d.
>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l <at> lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Permalink | Reply | 12 comments |
headers
David Gerard | 1 Apr 2012 13:01
Picon
Gravatar

Re: Time to redirect to https by default?

On 1 April 2012 11:55, Petr Bena <benapetr <at> gmail.com> wrote:

> I see no point in doing that. Https doesn't support caching well and
> is generally slower. There is no use for readers for that.

The use is that the requests themselves are encrypted, so that the
only thing logged is that they went to Wikimedia. You did read the
linked articles, right?

- d.
Permalink | Reply | 1 comment |
headers
Svip | 1 Apr 2012 13:20
Picon

Re: Time to redirect to https by default?

On 1 April 2012 13:01, David Gerard <dgerard <at> gmail.com> wrote:

> On 1 April 2012 11:55, Petr Bena <benapetr <at> gmail.com> wrote:
>
>> I see no point in doing that. Https doesn't support caching well and
>> is generally slower. There is no use for readers for that.
>
> The use is that the requests themselves are encrypted, so that the
> only thing logged is that they went to Wikimedia. You did read the
> linked articles, right?

Obviously, I cannot confirm whether Mr Bena read the linked articles
or not, but he did provide an answer regarding the technical
restrictions.

Wikimedia already spends an incredible amount of time caching its
content, because *so many* users use Wikipedia and its sister projects
daily.

And since most of the content is fairly static, caching makes a lot of sense.

However, HTTPS does not support caching (at least not well), which
means each page would suddenly have to be generated for *each* page.
It's true that MediaWiki itself supports caching, but its own caching
is no where near as fast as a caching server like Varnish (although I
believe a less powerful caching server is used on Wikimedia's
servers).

The trade off is that the service would be slower for everyone or we
would need more servers.  And I am not sure Wikimedia has that kind of
(Continue reading)

Permalink | Reply | 0 comments |
headers
Svip | 1 Apr 2012 13:23
Picon

Re: Time to redirect to https by default?

On 1 April 2012 12:06, David Gerard <dgerard <at> gmail.com> wrote:

> http://www.bbc.co.uk/news/uk-politics-17576745

Also, this article was written on 1 April and is far beyond any
monitoring scheme ever suggested in the Western World.  And I am sure
we would have heard about it being mentioned up until this point, if
it was real.

So I would take that article with a grain of salt.  Particularly the
statement about 'real time'.  That's not even feasible.
Permalink | Reply | 12 comments |
headers
David Gerard | 1 Apr 2012 13:59
Picon
Gravatar

Re: Time to redirect to https by default?

On 1 April 2012 12:23, Svip <svippy <at> gmail.com> wrote:
> On 1 April 2012 12:06, David Gerard <dgerard <at> gmail.com> wrote:

>> http://www.bbc.co.uk/news/uk-politics-17576745

> Also, this article was written on 1 April and is far beyond any
> monitoring scheme ever suggested in the Western World.  And I am sure
> we would have heard about it being mentioned up until this point, if
> it was real.

It would be nice, but if it's a prank then (a) lots of other
newspapers are in on it (b) ORG flagged the programme described
several weeks in advance:

http://wiki.openrightsgroup.org/wiki/Communications_Capabilities_Development_Programme
http://www.openrightsgroup.org/issues/ccdp

So no, it's in no way a joke. This is absolutely real.

> So I would take that article with a grain of salt.  Particularly the
> statement about 'real time'.  That's not even feasible.

That a desired monitoring regime would require a violation of physics
has *never* stopped a legislative push for such.

- d.

_______________________________________________
Wikitech-l mailing list
Wikitech-l <at> lists.wikimedia.org
(Continue reading)

Permalink | Reply | 11 comments |
headers
Petr Bena | 1 Apr 2012 14:52
Picon

Re: Time to redirect to https by default?

I said there is a little benefit for most of users, of course there
would be some who could find it usefull, however that's no reason to
redirect all users. I use wikipedia a lot, and I don't care if someone
see which pages I open. If someone does care, they should switch to
https themselves.

On Sun, Apr 1, 2012 at 1:59 PM, David Gerard <dgerard <at> gmail.com> wrote:
> On 1 April 2012 12:23, Svip <svippy <at> gmail.com> wrote:
>> On 1 April 2012 12:06, David Gerard <dgerard <at> gmail.com> wrote:
>
>>> http://www.bbc.co.uk/news/uk-politics-17576745
>
>> Also, this article was written on 1 April and is far beyond any
>> monitoring scheme ever suggested in the Western World.  And I am sure
>> we would have heard about it being mentioned up until this point, if
>> it was real.
>
>
> It would be nice, but if it's a prank then (a) lots of other
> newspapers are in on it (b) ORG flagged the programme described
> several weeks in advance:
>
> http://wiki.openrightsgroup.org/wiki/Communications_Capabilities_Development_Programme
> http://www.openrightsgroup.org/issues/ccdp
>
> So no, it's in no way a joke. This is absolutely real.
>
>
>> So I would take that article with a grain of salt.  Particularly the
>> statement about 'real time'.  That's not even feasible.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Svip | 1 Apr 2012 14:53
Picon

Re: Time to redirect to https by default?

On 1 April 2012 13:59, David Gerard <dgerard <at> gmail.com> wrote:

> On 1 April 2012 12:23, Svip <svippy <at> gmail.com> wrote:
>
>> On 1 April 2012 12:06, David Gerard <dgerard <at> gmail.com> wrote:
>>
>>> http://www.bbc.co.uk/news/uk-politics-17576745
>>
>> Also, this article was written on 1 April and is far beyond any
>> monitoring scheme ever suggested in the Western World.  And I am sure
>> we would have heard about it being mentioned up until this point, if
>> it was real.
>
> It would be nice, but if it's a prank then (a) lots of other
> newspapers are in on it (b) ORG flagged the programme described
> several weeks in advance:
>
> http://wiki.openrightsgroup.org/wiki/Communications_Capabilities_Development_Programme
> http://www.openrightsgroup.org/issues/ccdp
>
> So no, it's in no way a joke. This is absolutely real.

Still *kind of* a joke.

>> So I would take that article with a grain of salt.  Particularly the
>> statement about 'real time'.  That's not even feasible.
>
> That a desired monitoring regime would require a violation of physics
> has *never* stopped a legislative push for such.
(Continue reading)

Permalink | Reply | 9 comments |
headers
Piotr Jagielski | 1 Apr 2012 16:04
Picon
Favicon

correct way to import SQL dumps into MySQL database in terms of character encoding

Hello,

I'm trying to import categorylinks.sql dump into my MySQL database. I'm 
able to import it and query for articles in specific categories as long 
the category name contains only English-language characters. I don't get 
any results if I try to query for non-English category name. My 
understanding is that the dump is in UTF-8 format so I tried the following:

create the database using the following command:
CREATE DATABASE wiki CHARACTER SET utf8 COLLATE utf8_general_ci;

import the dump using the following command:
mysql --user root --password=root wiki < 
C:\Path\plwiki-20111227-categorylinks.sql --default-character-set=utf8

set my data source URL to the following in my Java code:
jdbc:mysql://localhost/plwiki?useUnicode=true&characterEncoding=UTF-8

It still doesn't work. What am I missing? Are there any instructions on 
how to correctly import the dump anywhere?

Thanks,
Piotr
Permalink | Reply | 7 comments |

Gmane