Hi,
I've recently noticed the "Thank you" feature is only available for
signed-in users, while anons cannot receive "thank yous". The
anonymous users are often the ones that would need encouraging the
most, so it would make sense to me to have this feature available to
them too.
Are there significant technical problems against such a change?
Thanks,
Strainu
Strainu,
I can't recall what decisions were made about showing full IPv6 addresses, but I believe
IPv6 can be much more revealing than IPv4, so any thanks or warning messages will be more
targeted if we show full IPv6 addresses and the host networks don't take privacy measures.
https://en.wikipedia.org/wiki/Ipv6#Privacy
I recall hearing some discussion about privacy as well as about the effectiveness of checkuser
tools concerning IPv6. I don't remember how that discussion ended, but if you can find it you
might find information relevant to thanking anonymous users.
FWIW I agree with Richard that if we're going to apply warning templates to IPs then we should
also be able to thank them, and I'm glad someone is looking at this issue. Anything that helps
editor acquisition in a cost-effective and privacy-aware way is likely to have my enthusiastic
support. (:
Pine
> Message: 3
> Date: Thu, 22 May 2014 01:47:03 +0100
> From: Richard Nevell <richard.nevell(a)wikimedia.org.uk>
> To: Editor Engagement <ee(a)lists.wikimedia.org>
> Cc: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, Danny Horn
> <dhorn(a)wikimedia.org>
> Subject: Re: [EE] [Wikitech-l] That you to anonymous users
> Message-ID:
> <CAHp4nsmr5NBcgHE_tsFHhNYOzX1zbkW_yoVU-TT05kVUpfU9sg(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Considering people deliver warnings via Huggle etc to IP editors, perhaps
> allowing a thanks to be sent wouldn't be such a bad idea.
>
> I realise it's purely anecdotal, but if it was available I reckon I'd use
> 'thanks' for anonymous users making changes as often as logged in editors.
>
>
> On 21 May 2014 23:35, David Gerard <dgerard(a)gmail.com> wrote:
>
> > If only I was a developer of any sort ;-)
> >
> >
> > On 21 May 2014 21:56, Fabrice Florin <fflorin(a)wikimedia.org> wrote:
> >
> >> Hi David,
> >>
> >> I am delighted that you are interested in extending the Thanks feature we
> >> released last year, so it can be used to thank more users.
> >>
> >> I am no longer working on this project, but am not aware of any changes
> >> that would make it easier to thank anonymous users: IP addresses are still
> >> as unreliable now as they were a year ago.
> >>
> >> But I have Cc:d Danny Horn, the new product manager for core features
> >> like Flow and Notifications, so he can chime in from his viewpoint.
> >>
> >> Personally, I would love to see the Thanks feature be used even more than
> >> it is today, as it seems like such a civilized way to show appreciation to
> >> each other :)
> >>
> >> Cheers,
> >>
> >>
> >> Fabrice
> >>
> >>
> >> On May 20, 2014, at 7:56 AM, David Gerard <dgerard(a)gmail.com> wrote:
> >>
> >> On 20 May 2014 15:35, Strainu <strainu10(a)gmail.com> wrote:
> >>
> >> I've recently noticed the "Thank you" feature is only available for
> >> signed-in users, while anons cannot receive "thank yous". The
> >> anonymous users are often the ones that would need encouraging the
> >> most, so it would make sense to me to have this feature available to
> >> them too.
> >> Are there significant technical problems against such a change?
> >>
> >>
> >>
> >>
> >> I asked for this on the editor engagement list too. Fabrice said: [1]
> >>
> >> "Sadly, we couldn't make this feature available for anonymous users,
> >> as you have to be registered to receive notifications right now. This
> >> is because IP addresses cannot be trusted to deliver notifications to
> >> the users they were intended to. I don't expect we'll change that
> >> anytime soon. We should all encourage anonymous user to register if
> >> they want to enjoy the same benefits as other members."
> >>
> >> Fabrice, is this still the case? Are there ways around this?
> >>
> >> * I suppose session cookies for anons just to possibly thank them is a
> >> bit excessive.
> >> * Could limit "thanks" to a short time after the edit (limiting either
> >> sending or receiving).
> >>
> >> Any other ways we could implement this with minimal false-positives on
> >> thanking people? If that's considered a problem :-)
> >>
> >>
> >> - d.
> >>
> >> [1] http://lists.wikimedia.org/pipermail/ee/2013-July/000525.html
> >>
> >>
> >> _______________________________
> >>
> >> Fabrice Florin
> >> Product Manager
> >> Wikimedia Foundation
> >>
> >> http://en.wikipedia.org/wiki/User:Fabrice_Florin_(WMF)
> >>
> >>
> >>
> >>
> >
> > _______________________________________________
> > EE mailing list
> > EE(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/ee
> >
> >
>
>
> --
> Richard Nevell
> Assistant Office Manager
> Wikimedia UK
> +44 (0) 20 7065 0753
>
> Wikimedia UK is a Company Limited by Guarantee registered in England and
> Wales, Registered No. 6741827. Registered Charity No.1144513. Registered
> Office 4th Floor, Development House, 56-64 Leonard Street, London EC2A 4LT.
> United Kingdom. Wikimedia UK is the UK chapter of a global Wikimedia
> movement. The Wikimedia projects are run by the Wikimedia Foundation (who
> operate Wikipedia, amongst other projects).
>
> *Wikimedia UK is an independent non-profit charity with no legal control
> over Wikipedia nor responsibility for its contents.*
>
Hi.
A coworker of mine passed this along today. I thought readers of this list
might be interested.
https://jibe-hackathon.eventbrite.com/
---
Saturday, June 21, 2014 from 10:00 AM to 10:00 PM (EDT)
New York, NY
Hack the Web! Join us for the Jibe Hackathon.
Here at Jibe, we make the Web a better place. We build APIs where there
are none, we present insights from opaque data sources, and we polish and
simplify the user experience of decades-old technology.
We want everyone to do the same, so we’re hosting a hackathon for
making the web more useful. Hack the Web, build something awesome, and
potentially win a prize! Prizes are as follows:
* First place: $7,500
* Second place: $3,750
* Third place: $2,250
* Best HR-related hack: $1,500
Coding will start at 11AM and wrap up in time for demos at 8PM. Prizes
will be announced around 9PM.
There will be Jibe developers on hand to provide guidance and present on
useful technologies and techniques like scraping, data visualization, and
browser automation.
Food and beverages will be provided.
Full official rules can be found at http://jibe.com/hackathon-rules.
Please feel free to reach out to hackathon(a)jibe.com with any questions!
---
Unfortunately I know almost nothing about the sponsoring company, but it
seems that while Jibe is primarily focused on human resources-related
software, this hackathon is simply focused on creating a better Web. I
imagine there are a few Wikimedia-related projects with the same goal. :-)
MZMcBride
http://wikiconferenceusa.org
Organizers have posted the schedule for Wiki Conference USA (New York
City, 30 May-1 June). I'm giving the opening keynote address.
Tech-related topics will include: Wikidata, video content, our API, the
RAMP editor, Extension:Memento, graphics, Forward to Libraries,
cybersecurity, handling multiple languages on Commons, the Internet
Archive's interest in past revisions, and lessons for Wikimedia from
OPW. And Sunday June 1st is an all-day hackathon.
You can sign up for the waitlist since registration is full; we may see
some more slots as people's plans firm up.
http://wikiconferenceusa.org/wiki/FAQ#Accommodations and
https://en.wikivoyage.org/wiki/New_york_city#Sleep might help you plan
to come.
--
Sumana Harihareswara
Senior Technical Writer
Wikimedia Foundation
Hi, today GeoData spatial searches were switched from Solr to
Elasticsearch, for now only on testwiki. We're going to test it there
for a while before proceeding to production wikis. Suggestions where
to start are welcome - while GD is populated on many projects, it is
rarely used with a few exceptions:
5825 eswiki
2046 enwiki
223 zhwiki
216 svwiki
155 fawiki
130 ruwiki
100 dewiki
75 itwiki
61 frwiki
55 arwiki
54 jawiki
I would like to start with one project, however only itwiki and kowiki
are using Elasticsearch among large Wikipedias.
And finally, appreciation: this was made possible only thanks to awesome
help from our search team, Nik Everett and Chad Horohoe. You kick ass
guys!
--
Best regards,
Max Semenik ([[User:MaxSem]])
Hi, in Zürich I took one action to define a process to propose and select
Wikimedia hackathons. The topic came when discussing how to define the
location of the next European hackathon, and it was also mentioned when
discussing the possibility to start organizing an annual hackathon in India.
There is a draft available at https://www.mediawiki.org/wiki/Hackathons
Feedback welcome.
The page includes guidelines for candidates proposing a hackathon. Even if
this is a draft, I think they are already useful for anybody thinking on
proposing the Wikimedia Hackathon 2015 in Europe, as well as a developer
event in India or elsewhere.
As soon as we agree on the basics of the draft, we will advertize it
further at wikimedia-l to make sure that all chapters and other WM orgs are
aware of it, and hopefully budget for it as organizers and/or travel
sponsors.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Recently, Media Viewer[1] (MMV) has been switched at Wikimedia Commons
to be default.
As some people do not care a lot for beta features or new features, do
not read the mailing lists and overlook main discussion forums or are
just unable to understand English, they were surprised and confused and
wondered how they could disable the feature.
Please help me to evaluate if there are alternatives to how software
deployment is currently done. Here are some suggestions from community
member Jameslwoodward (commons adminstrator):
A Post a banner so that there is a good chance of actually reaching
everyone.
B Ensure that the internally referenced help page actually has correct
information.
C Major changes can be the default for new users, but should be opt-in
for existing users.
I think (A) could be partially done by tech-ambassadors (what a
difficult word); however when deploying something like MMV to all wikis,
isn't this worth a CentralNotice?
(B) is as obvious as important. Outdated information is confusing. Make
sure to update your help pages before going to release your software to
the wild. Or delay the release until this is done.
Suggestion (C) is interesting, although perhaps technically difficult to
implement.
If a feature that one experienced as anonymous user is good [login
cookies expire, ...], or one explicitly tested the feature or was told
by a fellow about a good feature, it is very likely that one will enable
that feature for the account, too. People will do this freely. Without
complaining. And people, who intentionally enabled a feature, usually
have a positive attitude, are willing to help and improve the feature.
They will provide you with constructive feedback.
The overall atmosphere would be a lot more positive than that we
currently experience with new tools, *the power users do not need*. So
why not actively promoting a feature until there is a critical mass
using it? It may take a lot of time but I think it's worth a test.
A personal appeal:
Please care about the power users [2]. They are the core and foundation
of the WMF projects. They create the content; manage most issues - think
about the OTRS team - in their spare time, ... so WMF can finally run
the fundraiser banners and you can get your payment.
-- Rillke
[1] https://www.mediawiki.org/wiki/Help:Multimedia/Media_Viewer
[2]
http://www.aswedeingermany.de/50SoftwareDevelopment/20MostImportantRuleOfUI…
If I search on http://www.mediawiki.org for "Search Weighting" I get as result a line:
"Search (section Search Weighting Ideas)" with links to the page and to the section.
This section contains the word "GeoLoc".
But if I search for "GeoLoc" I get just the page link.
I want to show this section link as a search result too.
Is there an easy way or is it a planned feature?
What do I have to change in the CirrusSearch extension?
Many Thanks!
Henry