ok more like Twitter
and Facebook; that is, they'll be opportunities for disinformation.
Risker/Anne
On Fri, 8 Dec 2023 at 05:43, Kosta Harlan wrote:
> There is an extension
> https://www.mediawiki.org/wiki/Extension:InlineComments
>
> There's some past discussion of this type
whether Tor-exempt should be an entirely separate right, because
the number of IPB-exempt editors who need Tor-exempt could probably be
counted on the fingers of one hand. Perhaps it is time to reconsider this?
Risker/Anne
On Sun, 19 Jun 2022 at 09:23, Tomy Anggara wrote:
> Open main m
(in a positive
way). I'm pleased and perhaps a bit relieved to see that the research has
borne out my impression of how it has made such a big difference in the
deployment process.
Risker/Anne
On Wed, 16 Feb 2022 at 06:01, Tyler Cipriani
wrote:
> *tl;dr:* We have open data on Wikimedia product
Mike's suggestion is good. You would likely get better responses by asking
this question to the Wikimedia developers, so I am forwarding to that list.
Risker
On Thu, 16 Sept 2021 at 14:04, Gava, Cristina via Wikimedia-l <
wikimedi...@lists.wikimedia.org> wrote:
> Hello
to expanding the list of what could be
included in a Friday backport. Limiting it to essentially "breaks the site"
or "major impact to accessibility of the content" doesn't really include
most of the noticeable user experience issues (for either edito
to notice,
until we're trying to edit logged-in from remote areas.
Risker/Anne
[1] https://meta.wikimedia.org/wiki/List_of_Wikipedias
On Sat, 9 Mar 2019 at 10:12, Eran Rosenthal wrote:
> Hi,
> Wiki communities can ask to override their default configurations
> (following
ewhere. These historical tidbits,
especially one that shows such a lovely human side to the practice of
coding and software development, can become even more meaningful over
time. Thanks, Magnus - and thanks MusikAnimal for asking the question.
Risker/Anne
On Wed, 23 Jan 2019 at 02:51, Kunal Mehta
put a lot
of effort into coming up with solutions that will help to stop the current
onslaught and prevent similar incidents in the future. There has been
exceptional vigilance to this situation, and it is noted and appreciated.
Risker/Anne
On Mon, 26 Nov 2018 at 15:58, Derick N. Alangi
wrote:
>
owser.
So no, I do not think it would be a good idea for anyone, let alone the
Wikimedia Foundation, to advocate on behalf of this software.
Risker/Anne
On 3 September 2017 at 03:22, Stas Malyshev <smalys...@wikimedia.org> wrote:
> Hi!
>
> > After Firefox and Chromium, there'
A minor suggestion from someone who is just a reader here - It would be
helpful if the same thread title is not used every week. In particular,
adding a date of the meeting will aid in searchability.
Thanks,
Risker/Anne
On 17 March 2017 at 09:52, Daniel Kinzler <daniel.kinz...@wikimedia
designers are using the same textbooks. And #ac6600 is not a colour I
really want to see on my screen; ask any parent to think back to those
first six months, and they'll explain...
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
ld go a long way to
resolving that problem. That's not to deprecate the hard work and
investment of all of the staff and volunteer developers that keeps the
place functional and brings new and desirable features to the users - thank
you all.
Risker/Anne
___
o see how this
could be accommodated.
Thanks Brion for raising the topic - and thanks to everyone in this thread,
you've all taken this idea to heart and recognized the value of user
input.
Risker/Anne
On 1 September 2016 at 13:12, Brion Vibber <bvib...@wikimedia.org> wrote:
> The last couple yea
Just noting that 1700-1800 PDT on Wednesday May 11 is -0100 UTC on
Thursday May 12. Based on the link given, this seems to be when the meeting
will be held. Please verify.
Risker/Anne
On 4 May 2016 at 21:28, Pine W <wiki.p...@gmail.com> wrote:
> Forwarding.
>
> Pine
> --
- until
they stop working. These tools are one of the hidden underpinnings that
help make the Wikimedia family of projects successful - and it's great to
see someone who is so passionate about this taking on the role.
Risker/Anne
On 15 April 2016 at 20:04, Magnus Manske <magnusman...@googlemail.
time trying to figure
out how to create a message to new users I encounter when I'm oversighting
their personal information...without templating or linking to complex
policies, but pointing them to the Teahouse. I'm pretty sure it's not going
to be very easy, but I'm going to try.
Thank you for
tes rearrange themselves periodically - and replacing
a bad link with a more secure bad link is not really helpful.
Risker/Anne
On 13 January 2016 at 13:32, Max Semenik <maxsem.w...@gmail.com> wrote:
> Fix them with a bot, for example AWB
> <https://en.wikipedia.org/wiki/Wikiped
Agree with everyone else - this looks pretty cool. Just as importantly,
it's pretty straightforward - I could figure out all of the options quickly
and intuitively. Thank you for working on it.
Risker/Anne
On 9 December 2015 at 01:02, Jnanaranjan Sahu <gyana...@gmail.com> wrote:
>
2487
-Twinkle 7
Are the negative numbers the number of users who had previously enabled the
gadget and then subsequently disabled it? If not, what are they?
Thanks for targeting the cleanup and broader distribution of those high-use
tools and gadgets.
Risker/Anne
[1] https://en.wikipedia.org/wiki/S
by an *internal* error rather
than an external attack, is a very, very big deal, but I'm not getting that
impression from anything written here, on phabricator, or in the report
itself. That disappoints me far more than that an error was made in the
first place.
Risker/Anne
On 26 October 2015 at 23:04
On 27 October 2015 at 09:57, Brad Jorsch (Anomie) <bjor...@wikimedia.org>
wrote:
> On Tue, Oct 27, 2015 at 8:02 AM, Risker <risker...@gmail.com> wrote:
>
> > The incident report does not go far enough back into the history of the
> > incident. It does not explai
Well, bluntly put, since LDAP is how most non-WMF staff sign into
phabricator, I'd say it's become an essential extension.
So yeah, this one should be taken over by WMF staff.
Risker/Anne
On 18 September 2015 at 12:54, Greg Grossmeier <g...@wikimedia.org> wrote:
>
> > Hi mayb
wikipedia.org/wiki/Code_of_the_United_States_Fighting_Force
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
ent draft of the code of conduct would
> allow you to send it here or not.
>
> On 6 September 2015 at 01:42, Risker <risker...@gmail.com> wrote:
>
> > On 5 September 2015 at 19:11, MZMcBride <z...@mzmcbride.com> wrote:
> >
> >
> > > It seems weird
Pine, given the questions at this point seem to be directed to the
Collaboration team, with the intention of clarifying what their plans are,
perhaps it would be best to encourage them to answer the questions rather
than continue the speculation.
Danny, perhaps you could take the lead on
k as they go
forward.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
On 28 August 2015 at 06:05, Quim Gil q...@wikimedia.org wrote:
On Fri, Aug 28, 2015 at 1:52 AM, Matthew Flaschen mflasc...@wikimedia.org
wrote:
On 08/22/2015 10:52 PM, Risker wrote:
Perhaps more importantlywho were the local contacts at Hackathon
2015?
I can't even dig that one
, the conferences I go to are usually full of
conservative businesswomen, and alcohol is rarely involved.
So yeah...you need a code of conduct. Because if I was even 15 years
younger, I'd never go to a Wikimedia conference.
Risker/Anne
On 22 August 2015 at 20:03, David Gerard dger...@gmail.com wrote:
I
in the event documentation.
A policy that exists but has no clear or visible support isn't worth the
bytes it's written with.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
have seen with past examples; it's
vanishingly unlikely they'd even get blocked, let alone banned.
Risker/Anne
On 11 August 2015 at 14:17, Pine W wiki.p...@gmail.com wrote:
Yeah, the same thought crossed my mind. Unfortunately, superprotect has
such a well-earned negative reputation
as well).
This would require very diplomatic discussion. And given that this is the
'anniversary' of the introduction of Superprotect, it might be better to
wait for a while to really have that conversation.
Risker/Anne
___
Wikitech-l mailing list
this kind of tracking; none of them will be perfect.
(You're engineers, you know that.) It's really important that the left hand
know what the right hand is doing.
Good luck in your choices.
Risker/Anne
On 3 July 2015 at 13:30, Arthur Richards aricha...@wikimedia.org wrote:
+teampractices
I've posted a link to your message at what looks like the proper page:
https://en.wikipedia.org/wiki/Wikipedia_talk:Freedom_of_Panorama_2015#Problem_with_banner_.22breaking.22_mobile
Risker/Anne
On 30 June 2015 at 17:49, Jon Robson jrob...@wikimedia.org wrote:
I noticed a banner on the mobile
eyes
on a situation. Thank you for your work on this, it was quite
enlightening.
Risker/Anne
On 7 June 2015 at 00:09, Neil P. Quinn nqu...@wikimedia.org wrote:
Hey Greg!
Yes, this is meant to be a one-time process. We've been spending a
significant proportion of our time on it ever since we
-solve downtimes on big
projects.
Risker/Anne
On 28 May 2015 at 07:51, Dan Garry dga...@wikimedia.org wrote:
Awesome! This will make many teams very happy since they'll be moving
faster.
What's the criteria by which you will evaluate the success of this?
Thanks,
Dan
On 27 May 2015 10:19
existing accounts every single
month just on mobile? Or does that include accounts that already existed
on a WMF site?
Risker/Anne
On 28 April 2015 at 20:00, Jon Robson jrob...@wikimedia.org wrote:
Anonymous editing was enabled on mobile web on 30th March 2015 to all users
(previous
On 24 April 2015 at 09:21, Alex Cella alexandre.wikime...@gmail.com wrote:
snip
Registration ends on the 8th of March.
I'm pretty sure that's not right.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
-written, robust,
heavily tested and used code now.
I would have thought that having to constantly write new extension-specific
code for these basic admin functions would have gotten tiresome for the
developers by now.
Risker/Anne
On 8 April 2015 at 13:58, Jon Robson jdlrob...@gmail.com wrote
, those are some suggestions for English.
Risker/Anne
On 4 April 2015 at 12:37, Brian Wolff bawo...@gmail.com wrote:
Oh look, we go full circle ;)
I haven't checked but given its implemented as a special page i doubt
Risker's cu concerns are addressed. Edits to lists do not appear
(and the execution) is
fine.
RIsker/Anne
On 2 April 2015 at 18:19, Jon Robson jrob...@wikimedia.org wrote:
I am writing to invite you to preview and hopefully contribute to
Gather [1], a new MediaWiki extension that allows users to create,
share, and discover lists of articles. Gather is currently
that, and simplification of the indentation
system/process would be desirable no matter what underlying software is
used for discussion. What is being said in this thread is that Flow does
not do this now, and in fact is currently designed to prevent this from
happening.
Risker/Anne
On 19 March 2015 at 13:28, Ryan Lane rlan...@gmail.com wrote:
On Thu, Mar 19, 2015 at 8:18 AM, Risker risker...@gmail.com wrote:
The dogfooding has been happening for a while on WMF's own office-wiki.
We
haven't heard any results about that. Is the system being used more than
leads to miscommunication, confusion and difficulty
figuring out who is saying what to whom.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
groups of staff have pretty much
abandoned talk pages on office-wiki and are now reverting to emails
instead) but without any documentary evidence or analysis it's unreasonable
to think that it is either a net positive OR a net negative.
Risker/Anne
the
same indent level.
There's also the huge waste of screen real estate - I knew it was bad on
desktop, but I was surprised to see it looks almost as bad on a tablet when
I had an opportunity to take a look.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l
On 17 March 2015 at 10:49, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
On Tue, Mar 17, 2015 at 10:35 AM, Risker risker...@gmail.com wrote:
On 17 March 2015 at 09:45, Brad Jorsch (Anomie) bjor...@wikimedia.org
wrote:
On Tue, Mar 17, 2015 at 9:37 AM, Ricordisamoa
ricordisa
On 16 March 2015 at 21:20, Ryan Lane rlan...@gmail.com wrote:
On Mon, Mar 16, 2015 at 6:02 PM, Risker risker...@gmail.com wrote:
How about just converting those threads back to Wikitext, instead? That
script already exists, I've seen it used on Mediawiki. Will it mess up
the
pages
/observations on Mediawiki, the use of Flow will
become a barrier for participation.
Risker/Anne
On 16 March 2015 at 20:51, Nick Wilson (Quiddity) nwil...@wikimedia.org
wrote:
LiquidThreads (LQT) has not been well-supported in a long time. Flow
is in active development, and more real-world use
of conditions where the access
would be withdrawn.
Risker/Anne
On 16 March 2015 at 01:29, Arlo Breault abrea...@wikimedia.org wrote:
I share Risker’s concerns here and limiting the anonymity
set to the intersection of Tor users and established wiki
contributors seems problematic. Also
through that
service.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
that sure it's an overall improvement in safety.
Risker/Anne
On 10 March 2015 at 20:40, Chris Steipp cste...@wikimedia.org wrote:
On Tue, Mar 10, 2015 at 2:58 PM, Risker risker...@gmail.com wrote:
snip
AlsoI'm a little unclear about something. If a Tor-enabled
account
creates
less control than the project has now, particularly in the ability to
address socking and POV/COI editing. Am I missing something?
Risker/Anne
On 10 March 2015 at 13:16, Giuseppe Lavagetto glavage...@wikimedia.org
wrote:
Hi Chris,
I like the idea in general, in particular the fact
having multiple accounts that were used inappropriately, including
administrator accounts, so that raises the bar even higher.
AlsoI'm a little unclear about something. If a Tor-enabled account
creates new accounts, will those accounts be able to edit through Tor,
too?
Risker/Anne
On 10
and the
proposed process is the addition of the third party and the deliberate
separation of the two accounts. (I'm trying to put this into plain
language so that it can be explained to a broader audience on a project.)
Do I have this right?
Risker/Anne
no longer be up to date
when there is no correlating action plan for updating the same information
is probably not good use of anyone's time or effort.
Risker/Anne
On 13 February 2015 at 07:57, James Salsman jsals...@gmail.com wrote:
Brian Wolff wrote:
Have you run this by Wikipedians? ... since
out-of-date information. There is
no indication at all that there is any interest on the part of Wikipedians
to review data identified in the manner you propose.
Risker/Anne
On 13 February 2015 at 12:58, James Salsman jsals...@gmail.com wrote:
Risker wrote:
... relying on suggestions from
On 13 February 2015 at 17:25, Max Semenik maxsem.w...@gmail.com wrote:
On Fri, Feb 13, 2015 at 2:23 PM, Risker risker...@gmail.com wrote:
Help me out here. Why does anyone care that the article was last edited
13
days ago by Omeganian? And even if they do, why is that the very first
was last edited 13
days ago by Omeganian? And even if they do, why is that the very first
thing that someone sees?
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
, in particular, so that signatures by
the new owner of the username won't be changed.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
with people actively harassing oversighters because of legitimate
suppressions they've carried out, and perhaps this is exactly how they've
found out it was Oversighter A who did that particular suppression.
Risker/Anne
On 9 December 2014 at 14:01, Dan Garry dga...@wikimedia.org wrote:
Speaking
It's a cool idea. Also not usable by those who are visually impaired, as
best I can tell.
I'm going to be honest, I think svetlana may be on to something.
Risker/Anne
On 3 December 2014 at 18:17, Jay Ashworth j...@baylink.com wrote:
- Original Message -
From: Ryan Kaldari rkald
On 9 November 2014 02:51, Pine W wiki.p...@gmail.com wrote:
We're talking about a test, not a broad rollout (:
I'm curious, Risker: if you don't mind my asking, what about being
required to supply a throwaway email address would have discouraged you
from opening a Wikimedia account?
Pine
Umm. No. If ever you want major pushback from the broad international
community, requiring any kind of documentation to open an account will
probably work very well. I certainly would never have signed up for an
account on Wikipedia if I'd had to supply an email address.
Risker/Anne
On 9
; Tor's blocking is a technical solution to a genuine
policy/behaviour problem.
Risker/Anne
On 1 October 2014 09:05, Derric Atzrott datzr...@alizeepathology.com
wrote:
If, as it seems right now, the problem is technical (weed out the bots
and vandals) rather than ideological (as we allow
Advocacy doorstep, but I don't
think we should expect a formal legal response about this.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
vector that is similarly problematic, and it would boggle the
minds of most users to discover that developers are more interested in
enabling another of these vectors rather than thinking about how to prevent
problems from the ones that are currently not systemically shut down.
Risker/Anne
[1
- or philosophically-driven problem editors.
Unfortunately, with our limited human resources (what with everyone being
volunteers, and most editors just editing), it doesn't take a lot of
problem editors to overwhelm our resources.
Risker/Anne
___
Wikitech-l
As someone with one of those high risk accounts, one time passwords would
be more likely to make me drop those permissions. Any administrator has a
high risk account given the opportunities that they have.
Risker/Anne
On 7 August 2014 07:59, Pine W wiki.p...@gmail.com wrote:
I think we
On 7 August 2014 10:49, Chad innocentkil...@gmail.com wrote:
On Thu, Aug 7, 2014 at 9:49 AM, Risker risker...@gmail.com wrote:
As someone with one of those high risk accounts, one time passwords
would
be more likely to make me drop those permissions. Any administrator has
a
high risk
ID sends a second password
as a text to a mobile) and means having more expensive technology) or using
technology like dongles that cannot be sent to users in certain countries.
I stick to my strong passwords and also subscribe to the xkcd password
theory.[1]
Risker/Anne
[1] https
right now so
can't give you any links.)
Hope that helps.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
from the library wi-fi); it would be a
pain to have to keep updating preferences everytime one of those situations
occurs.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Just to note, I've sent the screenshot directly to Brandon; I also
forwarded a copy to this list but because of the size the email needs to go
through moderation.
Risker/Anne
On 14 July 2014 08:55, Risker risker...@gmail.com wrote:
Thanks Brandon for letting us know about this. Since
it there; the problem isn't really the format, it's
the quality and relative importance of the information.
Risker
On 14 July 2014 16:06, Trevor Parscal tpars...@wikimedia.org wrote:
I want to suggest that we give Brandon a lot of slack here, and be as
supportive as possible.
This is a prototype of a design
distractions :)
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
, but then they'd want to be sent back
to the watchlist.
Risker/Anne
On 15 July 2014 14:49, Tyler Romeo tylerro...@gmail.com wrote:
https://gerrit.wikimedia.org/r/146515
--
Tyler Romeo
0x405D34A7C86B42DF
From: Jon Robson jdlrob...@gmail.com
Reply: Wikimedia developers wikitech-l
.
Or alternately have a log out on this device/log out everywhere option.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
to grab a screenshot and send it in.
Risker/Anne
On 14 July 2014 01:03, Brandon Harris bhar...@wikimedia.org wrote:
I have uploaded a new version of the Winter framework/prototype,
v. 0.6.
http://unicorn.wmflabs.org/winter/
This version has
for just a minute...it's essential information
for having any chance at all of identifying multiple accounts or pattern
editing; however, the tables used by checkusers are non-public so
Checkusers continuing to have access to IP data should not be an issue.
Risker/Anne
On 11 July 2014 10:25, Tyler
, or there would have been a bigger problem.
Testwiki is for testand if you must test on enwiki, do it in userspace.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
I do urge you to start such a discussion, bawolff. It would seem to me
that a one- or two-week RFC should be sufficient to opt out contributions
to MediaWiki. I'd be happy to support, even though it's more likely that
I'll star in the next James Bond film than ever write a line of code.
Risker
.
Part of the issue faced by developers is the fact that there is really no
viable method by which to label their contributions as paid. Doesn't
mean the TOU doesn't apply.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https
Thank you, Luis. I have drafted a request for comment on mediawiki.org
[1], but it can probably use some review to ensure I have included the
correct list of related projects.
Risker/Anne
[1]
https://www.mediawiki.org/wiki/Requests_for_comment/Alternate_disclosure_policy
On 16 June 2014 18:25
to content quality
reviews to RFA to any other process that isn't actually creation or editing
of content is going to be perceived as anything but the WMF sticking
its nose into areas that are none of its business.
Risker/Anne
___
Wikitech-l mailing list
.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Welcome, Danny!
Is there a specific product that Danny will be managing?
Risker/Anne
On 25 April 2014 10:58, Howie Fung hf...@wikimedia.org wrote:
Everyone,
I am pleased to announce that Danny Horn is joining the Product Development
team as Product Manager. His first day was Monday April
I thought it looked like one of those pesky commercial travel sites; it
might be the subject matter, but it just looked so void of content that I
was convinced it was trying to sell me something.
Risker
On 15 April 2014 10:47, Magnus Manske magnusman...@googlemail.com wrote:
Well, it does
such a major update because of usability and
readibility issues, there's a major problem here. Just because they aren't
English Wikipedia doesn't mean their issues are minor, and they have the
disadvantage of a language barrier to make their problems known.
Risker/Anne
On 9 April 2014 03:01, Steven
, either type of
visitor to Wikimedia sites is more or less important when it comes to
listening to feedback. Even if Nathan was right, sometimes it's hard for us
to balance the two. What I said in reply to Risker is that I don't think
there saying the change is a failure is fair or true, based
Thanks for the heads-up, Greg. However, I'm finding that I am being
repeatedly logged out...it's happened every other edit I've made tonight,
which is a real pain. Will report on IRC as well.
Risker/Anne
On 8 April 2014 16:57, Greg Grossmeier g...@wikimedia.org wrote:
FYI to this audience
projects
are growing much faster than the older, Latin-script sites. They're our
future. They have to be in the mix.
Best,
Risker
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
: it's the clear favourite of the most active users, it's
still faster after years of improving Vector, and it handles a lot of
accessibility issues much better than Vector (particularly for the visually
impaired, according to those editors I know who have to deal with this).
Risker/Anne
to Monobook.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
up to making big
differences. A line of code here, an improvement there, a side
discussion with someone to suggest a different path...all I can say is
that if I am noticing it, I'm pretty sure a lot of other people are
too.
Risker/Anne
___
Wikitech-l
, and
thinks this will be a workaround that will prevent him/her from being
blocked this time.
Risker/Anne
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
for blocking or limiting access.
Risker
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
), and they can edit. It is the social and policy-based
processes that prevent Tor users from using Tor to edit. I happen to agree
with those processes (having cleaned up major messes from unblocked Tor
nodes on enwiki), but it's not a technical problem, really.
Risker
On 30 December 2013 18:59, Tyler Romeo tylerro...@gmail.com wrote:
On Mon, Dec 30, 2013 at 6:49 PM, Risker risker...@gmail.com wrote:
I disagree fundamentally with your position here. It's technically
possible
for Tor editors to edit; all we have to do is unblock Tor nodes (or for
them
of communication processes, and giving consideration to a
quick and straightforward process to reach information that can be done
directly from any WMF wiki, would be a really significant outreach to the
primary users.
Risker/Anne
___
Wikitech-l mailing list
I also agree.
Perhaps more importantly, I don't see any actual argument for *not* using
nofollow. We're not here to drive pagerank for other websites, and our
doing so can be harmful to those sites, or to the article subject.
Risker
On 18 November 2013 09:44, Arcane 21 arc...@live.com wrote
1 - 100 of 179 matches
Mail list logo
