[Wikitech-l] Tor relay
Hi, This is just a quick update that as of late October, WMF is officially hosting a Tor relay: https://atlas.torproject.org/#details/DB19E709C9EDB903F75F2E6CA95C84D637B62A02 This is not an exit node, and it's just a small contribution to the network. Really - anyone can do it: https://www.eff.org/torchallenge/ We want to note that editing via Tor is a whole other matter, and I would refer to previous conversations on this list if you have questions about the current state of things. We also currently have no plans to run an exit node or a hidden service, but we're open to suggestions for additional ways in which WMF can support anonymity and privacy. Sincerely, Faidon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tor relay, and freenode
Thanks for the note. Would it be within our mission scope to host a Freenode server? We use Freenode a *lot* for public and private communications. There have been previous discussions about WMF support for upstream services, and WMF has been talking about offering non-monetary support to affiliates, so I think hosting a Freenode server could make sense. Pine On Nov 10, 2014 1:11 AM, Faidon Liambotis fai...@wikimedia.org wrote: Hi, This is just a quick update that as of late October, WMF is officially hosting a Tor relay: https://atlas.torproject.org/#details/DB19E709C9EDB903F75F2E6CA95C84D637B62A02 This is not an exit node, and it's just a small contribution to the network. Really - anyone can do it: https://www.eff.org/torchallenge/ We want to note that editing via Tor is a whole other matter, and I would refer to previous conversations on this list if you have questions about the current state of things. We also currently have no plans to run an exit node or a hidden service, but we're open to suggestions for additional ways in which WMF can support anonymity and privacy. Sincerely, Faidon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tor relay
Le 10/11/2014 10:10, Faidon Liambotis a écrit : Hi, This is just a quick update that as of late October, WMF is officially hosting a Tor relay: https://atlas.torproject.org/#details/DB19E709C9EDB903F75F2E6CA95C84D637B62A02 This is not an exit node, and it's just a small contribution to the network. Really - anyone can do it: https://www.eff.org/torchallenge/ We want to note that editing via Tor is a whole other matter, and I would refer to previous conversations on this list if you have questions about the current state of things. We also currently have no plans to run an exit node or a hidden service, but we're open to suggestions for additional ways in which WMF can support anonymity and privacy. Nice, and I started a stub page on wikitech with the above links: https://wikitech.wikimedia.org/wiki/Tor_relay -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tor relay, and freenode
Always thought Wikimedia has a freenode instance, as they do for etherpad. Well then, I think its about time. On Nov 10, 2014 9:29 AM, Pine W wiki.p...@gmail.com wrote: Thanks for the note. Would it be within our mission scope to host a Freenode server? We use Freenode a *lot* for public and private communications. There have been previous discussions about WMF support for upstream services, and WMF has been talking about offering non-monetary support to affiliates, so I think hosting a Freenode server could make sense. Pine On Nov 10, 2014 1:11 AM, Faidon Liambotis fai...@wikimedia.org wrote: Hi, This is just a quick update that as of late October, WMF is officially hosting a Tor relay: https://atlas.torproject.org/#details/DB19E709C9EDB903F75F2E6CA95C84D637B62A02 This is not an exit node, and it's just a small contribution to the network. Really - anyone can do it: https://www.eff.org/torchallenge/ We want to note that editing via Tor is a whole other matter, and I would refer to previous conversations on this list if you have questions about the current state of things. We also currently have no plans to run an exit node or a hidden service, but we're open to suggestions for additional ways in which WMF can support anonymity and privacy. Sincerely, Faidon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tor relay, and freenode
Le 10/11/2014 10:28, Pine W a écrit : Thanks for the note. Would it be within our mission scope to host a Freenode server? We use Freenode a *lot* for public and private communications. There have been previous discussions about WMF support for upstream services, and WMF has been talking about offering non-monetary support to affiliates, so I think hosting a Freenode server could make sense. Pine Hello, We do since October 2013, the server is dickson.freenode.net https://wikitech.wikimedia.org/wiki/Dickson -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tor relay, and freenode
Hi Pine, On Mon, Nov 10, 2014 at 01:28:54AM -0800, Pine W wrote: Thanks for the note. Would it be within our mission scope to host a Freenode server? We use Freenode a *lot* for public and private communications. There have been previous discussions about WMF support for upstream services, and WMF has been talking about offering non-monetary support to affiliates, so I think hosting a Freenode server could make sense. We in fact, already do: that would be dickson.freenode.net. Unfortunately, the server has been taken offline since the compromise of the Freenode network back in September. We are in touch with the Freenode admins to understand the circumstances of the break-in and to what extent dickson was affected, as well as our post-breakin strategy (forensics, whether reimaging would be enough, etc.). This has taken longer than expected, unforunately. Suffice to say, the Freenode server is in a different administrative realm and is sandboxed and entirely separate from WMF production; compromises there would not have any effect to our production network. Faidon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tor relay, and freenode
Hello Antoine Thanks for pointing out. For some reason, I can't access the address. Maybe its down. Pings dont go through at all. Glad to know there's at least one freenode for Wikimedia. But if I may ask, it it official? It happens to be a sub domain of freenode. Not a bad idea, but was expecting to see something like freenode.Wikimedia.org or something like that. On Nov 10, 2014 9:35 AM, Antoine Musso hashar+...@free.fr wrote: Le 10/11/2014 10:28, Pine W a écrit : Thanks for the note. Would it be within our mission scope to host a Freenode server? We use Freenode a *lot* for public and private communications. There have been previous discussions about WMF support for upstream services, and WMF has been talking about offering non-monetary support to affiliates, so I think hosting a Freenode server could make sense. Pine Hello, We do since October 2013, the server is dickson.freenode.net https://wikitech.wikimedia.org/wiki/Dickson -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] phabricator vagrant
Interested in helping out in improving
https://phabricator.wikimedia.org/ ? Worried about getting phabricator
set up for development? Not interested in installing MySQL?
Now there is a solution! Phabricator-tools, only $0.00 (plus a few GB
tax storage) from github!
[/tongue-in-cheek]
Yesterday, I adapted[2] the existing phabricator-tools[1] repository
(which is mean to quickly get phabricator running) to work (better)
for development. To use it, do the following:
git clone https://github.com/valhallasw/phabricator-tools
cd phabricator-tools/vagrant
vagrant up
firefox http://127.0.0.1:8080
ssh -P vagrant@localhost # password vagrant
cd /phabricator/instances/dev/phabricator
# edit whatever you want
Then, if you're ready to submit a patch:
git config --global user.name ...
git config --global user.email ...
git commit all the things
arc diff # and follow the instructions, including installing the arc certificate
The Phabricator people are really quick and helpful with reviewing
patches, and the Phabricator code is easy to use (I haven't used PHP
in ages, but I had my patch[3] ready in an hour or so), so if you want
something in Phabricator to improve, {{sofixit}}! ;-)
A few Wikimedia-related requests can be found at [4].
Also, I'll be at the hackathon in Amsterdam next weekend, and I'd be
happy to give anyone a hand there getting started.
Merlijn
[1] https://github.com/bloomberg/phabricator-tools
[2] https://github.com/valhallasw/phabricator-tools
[3] https://secure.phabricator.com/D10823
[4] https://secure.phabricator.com/tag/wikimedia/
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] phabricator vagrant
Hi Merlijn, thank you for your work!
On Mon, Nov 10, 2014 at 11:25 AM, Merlijn van Deen valhall...@arctus.nl
wrote:
Yesterday, I adapted[2] the existing phabricator-tools[1] repository
(which is mean to quickly get phabricator running) to work (better)
for development. To use it, do the following:
Please consider documenting any good advice for developer at/under
https://www.mediawiki.org/wiki/Phabricator/Code
git clone https://github.com/valhallasw/phabricator-tools
cd phabricator-tools/vagrant
vagrant up
firefox http://127.0.0.1:8080
ssh -P vagrant@localhost # password vagrant
cd /phabricator/instances/dev/phabricator
# edit whatever you want
Then, if you're ready to submit a patch:
git config --global user.name ...
git config --global user.email ...
git commit all the things
arc diff # and follow the instructions, including installing the arc
certificate
I need to try this. It really looks easy.
The Phabricator people are really quick and helpful with reviewing
patches, and the Phabricator code is easy to use (I haven't used PHP
in ages, but I had my patch[3] ready in an hour or so), so if you want
something in Phabricator to improve, {{sofixit}}! ;-)
This is also good to hear, especially after all the discussion about
requiring arc for new contributors, etc.
A few Wikimedia-related requests can be found at [4].
... and there is more at
https://phabricator.wikimedia.org/tag/phabricator.org/board/
(Many of these requests need a discussion first, and you are invited to
join even if you will not be the one so-fixing-it.)
Also, I'll be at the hackathon in Amsterdam next weekend, and I'd be
happy to give anyone a hand there getting started.
Have fun!
Merlijn
[1] https://github.com/bloomberg/phabricator-tools
[2] https://github.com/valhallasw/phabricator-tools
[3] https://secure.phabricator.com/D10823
[4] https://secure.phabricator.com/tag/wikimedia/
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] [Wikimedia-l] Recognition of the MediaWiki Stakeholder's Group
Great news! Finally a formal group focused in MediaWiki for third parties, within the Wikimedia movement. Autonomous and connected. Now the sky is the limit of the memebers of this group. :) PS: Stakeholder's or Stakeholders? On Mon, Nov 10, 2014 at 7:31 AM, Nurunnaby Hasive n...@nhasive.com wrote: Welcome Congratulations! On Mon, Nov 10, 2014 at 9:34 AM, Gregory Varnum gregory.var...@gmail.com wrote: Greetings, The Affiliations Committee is pleased to announce the recognition [1] of the MediaWiki Stakeholder's Group - a user group for MediaWiki developers, admins, users, consultants, and hosting providers who cooperate in order to improve the software and advocate the needs of MediaWiki users outside the Wikimedia Foundation (WMF) and its projects. This group shows great promise and potential for helping organize folks who are interested in making MediaWiki even better and give a voice to the many non-WMF users of the software. So, now we have them joining the family of affiliates. Please, let's give them a warm welcome! More info about the group: https://www.mediawiki.org/wiki/MediaWiki_Stakeholder%27s_Group Congratulations! -greg aka varnent Vice-Chair, Affiliations Committee 1: https://meta.wikimedia.org/wiki/Affiliations_Committee/Resolutions/MediaWiki_Stakeholder%27s_Group_-_Liaison_approval,_November_2014 ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines wikimedi...@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe -- *Nurunnaby Chowdhury Hasive* Administrator | Bengali Wikipedia http://bn.wikipedia.org/wiki/user:nhasive Member | IEG Committee, Wikimedia Foundation https://meta.wikimedia.org/wiki/Grants:IdeaLab/People Moderator, Social Media Interaction | The Daily Prothom-Alo http://www.prothom-alo.com Bangladesh Ambassador | Open Knowledge http://www.okfn.org Treasurer | Bangladesh Open Source Network (BdOSN) http://www.bdosn.org Task Force Member | Mozilla Bangladesh http://www.mozillabd.org Author Translator | Global Voice http://bn.globalvoicesonline.org/author/hasive fb.com/nhasive | @nhasive http://www.twitter.com/nhasive | Skype: nhasive | www.nhasive.com ___ Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/wiki/Mailing_lists/Guidelines wikimedi...@lists.wikimedia.org Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l, mailto:wikimedia-l-requ...@lists.wikimedia.org?subject=unsubscribe -- Quim Gil Engineering Community Manager @ Wikimedia Foundation http://www.mediawiki.org/wiki/User:Qgil ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Our CAPTCHA is very unfriendly
On Sunday, November 9, 2014, Platonides platoni...@gmail.com wrote: On 07/11/14 02:52, Jon Harald Søby wrote: The main concern is obviously that it is really hard to read, but there are also some other issues, namely that all the fields in the user registration form (except for the username) are wiped if you enter the CAPTCHA incorrectly. So when you make a mistake, not only do you have to re-type a whole new CAPTCHA (where you may make another mistake), you also have to re-type the password twice *and* your e-mail address. This takes a long time, especially if you're not a fast typer (which was the case for the first group), or if you are on a tablet or phone (which was the case for some in the second group). Only the password fields are cleared (in addition to the captcha). It is debatable if clearing them is the right thing or not, there must be some papers talking about that. But I think we could go with keeping them filled with the user password. Another idea I am liking is to place the captcha at a different page (as a second step), where we could offer several options (captchas, puzzles, irc chat, email...) to confirm them, then gather their success rate. I like both of these ideas. On the general topic, I think either a captcha or verifying an email makes a small barrier to building a bot, but it's significant enough that it keeps the amateur bots out. I'd be very interested in seeing an experiment run to see what the exact impact is though. Google had a great blog post on this subject where they made recaptcha easier to solve, and instead, The updated system uses advanced risk analysis techniques, actively considering the user's entire engagement with the CAPTCHA--before, during and after they interact with it. That means that today the distorted letters serve less as a test of humanity and more as a medium of engagement to elicit a broad range of cues that characterize humans and bots. [1] So spending time on a new engine that allows for environmental feedback from the system solving the captcha, and that lets us tune lots of things besides did the user sending back the right string of letters, I think would be well worth our time. [1] - http://googleonlinesecurity.blogspot.com/2013/10/recaptcha-just-got-easier-but-only-if.html ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Autosave drafts
I would love to get autosave feature. My browser has crashed so many times, so everytime when I'm writing something longer, I have to use something like Notepad that can be easily saved anytime I want. *Stryn* 2014-11-10 0:25 GMT+02:00 Vito vituzzu.w...@gmail.com: An online autosave with certain limitations would be even better. I'm wondering about *private* autosaved drafts for registered users, allowing, for example, 3 autosaved revs (triggered by timers/big edit delta) from the 2 last articles user is editing. Vito Inviato con AquaMail per Android http://www.aqua-mail.com Il 09 novembre 2014 23:02:40 Derk-Jan Hartman d.j.hartman+wmf...@gmail.com ha scritto: Something else that I have had in the pipeline for a long while is autosave drafts. Basically, whenever you type, the article is saved to your local computer. If the browser crashes, and you visit the same article, it will prompt you for recovery. Making a Special:Autosave drafts index page would be trivial. Implementation: https://gerrit.wikimedia.org/r/#/c/5130/ https://gerrit.wikimedia.org/ r/#/c/5130/ Of this, I also have an alternate implementation: https://gerrit.wikimedia.org/r/#/c/157818/ https://gerrit.wikimedia.org/ r/#/c/157818/ https://gerrit.wikimedia.org/r/#/c/159626/ https://gerrit.wikimedia.org/ r/#/c/159626/ The original one is based on code by Joancreus and uses localStorage. It works, quite well actually, but while improving it, I became of the opinion that localStorage is basically so limited in storage and gives you so little feedback as an API and an enduser, that it's not really suited for much more than usersettings (big cookies). Not for saving potentially multiple 1MB articles, with structured details. As a storage layer, indexedDB is much nicer in that regard. API wise, it's a bit convoluted, but a jQuery plugin makes it usable and readable. There are WebSQL polyfills for platforms that don't have indexedDB, which would allow us to support browsers of the past 6 years. I would like some opinions on which way to go here. Additionally, i would love to hear what else people think would be required to make this usable for the Wikipedia audience and the naming. Would this be Drafts ? Autosave drafts ? autosave ? Would you say 'recover' when asking the user to use the version from drafts, or just 'use draft' etc? Note that the '2nd' version also has a few more improvements like a separate RL module and a preference option, but those can easily be added to the first implementation as well. DJ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Feature request.
The real-time collaboration mock ups that Pau created and we presented at Wikimania have a feature which is similar, where you can see who else is currently editing a given page (and be notified when another edit starts) even if you don't choose to start/join a collaborative editing session. But even if/when that work is implemented, I think there are better ways to handle merging edit conflicts. The VE model does actually help here some -- the patches I've been working on for VE real-time collaborative editing do provide a way to transpose actions w/r/t each other, which allows you to merge two edit histories in some cases. Possibly an early use of this feature might be to allow VE to provide a nicer edit conflict resolution screen, with the option to automatically merge your edits in certain cases. --scott ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Autosave drafts
How about when I wrap this up, I launch it as a Beta Feature.. ? DJ On 10 nov. 2014, at 17:30, Stryn@Wikimedia strynw...@gmail.com wrote: I would love to get autosave feature. My browser has crashed so many times, so everytime when I'm writing something longer, I have to use something like Notepad that can be easily saved anytime I want. *Stryn* 2014-11-10 0:25 GMT+02:00 Vito vituzzu.w...@gmail.com: An online autosave with certain limitations would be even better. I'm wondering about *private* autosaved drafts for registered users, allowing, for example, 3 autosaved revs (triggered by timers/big edit delta) from the 2 last articles user is editing. Vito Inviato con AquaMail per Android http://www.aqua-mail.com Il 09 novembre 2014 23:02:40 Derk-Jan Hartman d.j.hartman+wmf...@gmail.com ha scritto: Something else that I have had in the pipeline for a long while is autosave drafts. Basically, whenever you type, the article is saved to your local computer. If the browser crashes, and you visit the same article, it will prompt you for recovery. Making a Special:Autosave drafts index page would be trivial. Implementation: https://gerrit.wikimedia.org/r/#/c/5130/ https://gerrit.wikimedia.org/ r/#/c/5130/ Of this, I also have an alternate implementation: https://gerrit.wikimedia.org/r/#/c/157818/ https://gerrit.wikimedia.org/ r/#/c/157818/ https://gerrit.wikimedia.org/r/#/c/159626/ https://gerrit.wikimedia.org/ r/#/c/159626/ The original one is based on code by Joancreus and uses localStorage. It works, quite well actually, but while improving it, I became of the opinion that localStorage is basically so limited in storage and gives you so little feedback as an API and an enduser, that it's not really suited for much more than usersettings (big cookies). Not for saving potentially multiple 1MB articles, with structured details. As a storage layer, indexedDB is much nicer in that regard. API wise, it's a bit convoluted, but a jQuery plugin makes it usable and readable. There are WebSQL polyfills for platforms that don't have indexedDB, which would allow us to support browsers of the past 6 years. I would like some opinions on which way to go here. Additionally, i would love to hear what else people think would be required to make this usable for the Wikipedia audience and the naming. Would this be Drafts ? Autosave drafts ? autosave ? Would you say 'recover' when asking the user to use the version from drafts, or just 'use draft' etc? Note that the '2nd' version also has a few more improvements like a separate RL module and a preference option, but those can easily be added to the first implementation as well. DJ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Autosave drafts
I'll always love any idea starting from the botton, facing and eventually surviving to users' whims :D Vito Inviato con AquaMail per Android http://www.aqua-mail.com Il 10 novembre 2014 19:52:25 Derk-Jan Hartman d.j.hartman+wmf...@gmail.com ha scritto: How about when I wrap this up, I launch it as a Beta Feature.. ? DJ On 10 nov. 2014, at 17:30, Stryn@Wikimedia strynw...@gmail.com wrote: I would love to get autosave feature. My browser has crashed so many times, so everytime when I'm writing something longer, I have to use something like Notepad that can be easily saved anytime I want. *Stryn* 2014-11-10 0:25 GMT+02:00 Vito vituzzu.w...@gmail.com: An online autosave with certain limitations would be even better. I'm wondering about *private* autosaved drafts for registered users, allowing, for example, 3 autosaved revs (triggered by timers/big edit delta) from the 2 last articles user is editing. Vito Inviato con AquaMail per Android http://www.aqua-mail.com Il 09 novembre 2014 23:02:40 Derk-Jan Hartman d.j.hartman+wmf...@gmail.com ha scritto: Something else that I have had in the pipeline for a long while is autosave drafts. Basically, whenever you type, the article is saved to your local computer. If the browser crashes, and you visit the same article, it will prompt you for recovery. Making a Special:Autosave drafts index page would be trivial. Implementation: https://gerrit.wikimedia.org/r/#/c/5130/ https://gerrit.wikimedia.org/ r/#/c/5130/ Of this, I also have an alternate implementation: https://gerrit.wikimedia.org/r/#/c/157818/ https://gerrit.wikimedia.org/ r/#/c/157818/ https://gerrit.wikimedia.org/r/#/c/159626/ https://gerrit.wikimedia.org/ r/#/c/159626/ The original one is based on code by Joancreus and uses localStorage. It works, quite well actually, but while improving it, I became of the opinion that localStorage is basically so limited in storage and gives you so little feedback as an API and an enduser, that it's not really suited for much more than usersettings (big cookies). Not for saving potentially multiple 1MB articles, with structured details. As a storage layer, indexedDB is much nicer in that regard. API wise, it's a bit convoluted, but a jQuery plugin makes it usable and readable. There are WebSQL polyfills for platforms that don't have indexedDB, which would allow us to support browsers of the past 6 years. I would like some opinions on which way to go here. Additionally, i would love to hear what else people think would be required to make this usable for the Wikipedia audience and the naming. Would this be Drafts ? Autosave drafts ? autosave ? Would you say 'recover' when asking the user to use the version from drafts, or just 'use draft' etc? Note that the '2nd' version also has a few more improvements like a separate RL module and a preference option, but those can easily be added to the first implementation as well. DJ ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] VisualEditor monthly newsletter is now multilingual
(Apologies for cross-posting.) Hi all, I'm glad to announce that the *monthly VisualEditor newsletter* was recently marked for translation for the first time: we had received several related community requests. The issue for September and October [0] was delivered in 10 languages to the editors who signed up in the past months (please join them! [1]) in addition to a list of relevant pages which includes at a minimum all the Wikipedias where VisualEditor is already the default editor [2]. Future time windows for translations will be announced through the Translators mailing list [3], or personally to volunteers who want to help with this task; please contact me off-list to indicate your availability. *The November issue is now open for translations and will be delivered in a few days [4]. * Special thanks to our awesome community of translators, to Guillaume for assisting me in setting up the whole mechanism, to Whatamidoing (WMF) for providing the contents and to James F. for reviewing them. Best, Elitre (WMF) https://meta.wikimedia.org/wiki/User:Elitre_(WMF) https://meta.wikimedia.org/wiki/Community_Engagement_(Product) [0] https://meta.wikimedia.org/wiki/VisualEditor/Newsletter/2014/October [1] https://meta.wikimedia.org/wiki/VisualEditor/Newsletter [2] https://www.mediawiki.org/wiki/VisualEditor/Rollouts [3] https://lists.wikimedia.org/mailman/listinfo/translators-l [4] https://meta.wikimedia.org/wiki/VisualEditor/Newsletter/2014/November ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] recent security breach for browserstack.com
The Wikimedia Foundation has an account with browserstack.com for cross-browser testing. I do not think it sees much use, but in case anyone is using the browserstack service, they had a security breach yesterday: https://twitter.com/browserstack Browserstack says it will publish details of the breach directly to users. -Chris ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tor relay, and freenode
Thought WMF already hosts one for freenode. There is only one TOR hidden service. On Mon, 10 Nov 2014, at 20:28, Pine W wrote: Thanks for the note. Would it be within our mission scope to host a Freenode server? We use Freenode a *lot* for public and private communications. There have been previous discussions about WMF support for upstream services, and WMF has been talking about offering non-monetary support to affiliates, so I think hosting a Freenode server could make sense. Pine On Nov 10, 2014 1:11 AM, Faidon Liambotis fai...@wikimedia.org wrote: Hi, This is just a quick update that as of late October, WMF is officially hosting a Tor relay: https://atlas.torproject.org/#details/DB19E709C9EDB903F75F2E6CA95C84D637B62A02 This is not an exit node, and it's just a small contribution to the network. Really - anyone can do it: https://www.eff.org/torchallenge/ We want to note that editing via Tor is a whole other matter, and I would refer to previous conversations on this list if you have questions about the current state of things. We also currently have no plans to run an exit node or a hidden service, but we're open to suggestions for additional ways in which WMF can support anonymity and privacy. Sincerely, Faidon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tor relay, and freenode
Nkansah Rexford wrote: Glad to know there's at least one freenode for Wikimedia. But if I may ask, it it official? It happens to be a sub domain of freenode. Not a bad idea, but was expecting to see something like freenode.Wikimedia.org or something like that. Quote from the freenode website: https://freenode.net/hosting_ircd.shtml The server naming motif is science fiction and fantasy authors. Vanity names may be provided, but canonical server names and standardised geographical names will be used exclusively by freenode. If you have preferred authors, let us know and we will try to honour your preference. That said, we can make a CNAME from freenode.Wikimedia.org to dickson.freenode.net if desired. svetlana ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tor relay, and freenode
Le 10/11/2014 23:15, svetlana a écrit : Nkansah Rexford wrote: Glad to know there's at least one freenode for Wikimedia. But if I may ask, it it official? It happens to be a sub domain of freenode. Not a bad idea, but was expecting to see something like freenode.Wikimedia.org or something like that. snip That said, we can make a CNAME from freenode.Wikimedia.org to dickson.freenode.net if desired. svetlana The server hosted by Wikimedia is part of a rotation maintained by freenode. For the best service, you should connect to chat.freenode.net I am afraid adding a freenode.wikimedia.org alias would further confuse people, and if the server dies for some reason, leave users stuck or having to manually change to another one (chat.freenode.net will give you another server). -- Antoine hashar Musso ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tor relay
Great! Thanks. * Advertised Bandwidth 3.3 MB/s, what does it mean and can it be increased? * I see in puppet that there is at least some logging enabled. What is being logged and why? The best policy is to keep no logs. https://trac.torproject.org/projects/tor/wiki/doc/OperationalSecurity#MinimizeDataRetention Nemo ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Announcing the MediaWiki-Vagrant Community Survey
Calling all MediaWiki contributors! As many of you may know, there's a tool out there in the MediaWiki ether called MediaWiki-Vagrant. Whether you know what it's all about, love it, hate it, or haven't a clue—no, it isn't a fork of our wiki platform for displaced San Franciscans—we want to hear from you. One role of the Release Engineering team here at WMF is to develop and maintain tooling that reduces barriers to code contribution, accurate review/testing, and safe deployment. MediaWiki-Vagrant has emerged as one important piece of that toolchain, but with its ever growing user base it has also grown in complexity. We're dedicated to keeping it as congruent with staff and community needs as possible, but we need your help! Please complete the following survey when you have a few minutes to spare. Your answers will inform the direction we take with MediaWiki-Vagrant and related tools over the next quarter and beyond. https://wikimedia.qualtrics.com/SE/?SID=SV_eM9U3IVEt6UXqnz Thanks for your time and, most of all, your contributions to MediaWiki. -- Dan Duvall Automation Engineer Wikimedia Foundation http://wikimediafoundation.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Tor relay
On Mon, Nov 10, 2014 at 11:35:42PM +0100, Federico Leva (Nemo) wrote: * Advertised Bandwidth 3.3 MB/s, what does it mean and can it be increased? As we do not set any advertised bandwidth in our configuration, the value in Atlas is the bandwidth observed by the network. We are still in a ramp-up phase and going to continue being so for until approximately the end of 2014. Read https://blog.torproject.org/blog/lifecycle-of-a-new-relay for more. We do not plan to set an bandwidth limit at this point, either in the Tor configuration or externally, in our network. * I see in puppet that there is at least some logging enabled. What is being logged and why? The best policy is to keep no logs. https://trac.torproject.org/projects/tor/wiki/doc/OperationalSecurity#MinimizeDataRetention What logs are you referring to? If you're referring to Log notice /var/log/tor/tor.log then this just logs statistics, nothing else. torrc's manpage says on the matter: [w]e advise using notice in most cases, since anything more verbose may provide sensitive information to an attacker who obtains the logs. We do not keep traffic/usage logs in any way nor are we planning to. Faidon ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Announcing the MediaWiki-Vagrant Community Survey
I should have clarified that this version of the survey is meant for community contributors. Sorry to any WMF staff that filled this out (again). :) On Mon, Nov 10, 2014 at 2:36 PM, Dan Duvall dduv...@wikimedia.org wrote: Calling all MediaWiki contributors! As many of you may know, there's a tool out there in the MediaWiki ether called MediaWiki-Vagrant. Whether you know what it's all about, love it, hate it, or haven't a clue—no, it isn't a fork of our wiki platform for displaced San Franciscans—we want to hear from you. One role of the Release Engineering team here at WMF is to develop and maintain tooling that reduces barriers to code contribution, accurate review/testing, and safe deployment. MediaWiki-Vagrant has emerged as one important piece of that toolchain, but with its ever growing user base it has also grown in complexity. We're dedicated to keeping it as congruent with staff and community needs as possible, but we need your help! Please complete the following survey when you have a few minutes to spare. Your answers will inform the direction we take with MediaWiki-Vagrant and related tools over the next quarter and beyond. https://wikimedia.qualtrics.com/SE/?SID=SV_eM9U3IVEt6UXqnz Thanks for your time and, most of all, your contributions to MediaWiki. -- Dan Duvall Automation Engineer Wikimedia Foundation http://wikimediafoundation.org -- Dan Duvall Automation Engineer Wikimedia Foundation http://wikimediafoundation.org ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Please welcome Joaquín Oltra Hernández, Software Developer
I am pleased to announce that Joaquín Oltra Hernández joining the WMF as a Software Engineer for the Mobile Web Team! In Joaquins own words ... --- I'm spanish, living in the sunny east coast. I've been working with web frontends, UIs and javascript for about 8 years. For the last year I've been freelancing and previously I worked for 3 years for the trademarks and designs office for the European Union. I love learning about new programming languages and paradigms, and also the openness of the web front-end and how it allows us to create useful open software and interfaces that everybody can use and interact with directly. On my free time reading mind expanding books [1], riding a mountain bike, hiking up the mountain, and tinkering with small side projects with new languages and libraries. I also love to travel, seeing and learning about different countries and cultures [2]. You can find me on Freenode with the nick joakino I'll be working remotely from Alicante in Spain. --- Please welcome Joaquín! --tomasz [1] - Flow - The psychology of optimal experience Status: Anxiety [2] - https://www.flickr.com/photos/joaquinoltra [3] - https://www.mediawiki.org/wiki/Mobile_web/Team ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Revision metadata as a service?
Yes, a failed piece of rotting [configuration] code on en.wiki is called Pending changes; this doesn't mean that the extension, used by over 200 wikis, has been affected in any way. Nemo ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
