On Wed, Feb 13, 2019 at 12:13 PM bawolff wrote:
> I actually meant a different type of maintenance.
>
> Maintaining the encyclopedia (and other wiki projects) is of course an
> activity that needs software support.
>
> But software is also something that needs maintenance. Technology,
>
Brian,
I think we may be talking past each other. I'm Mr. Socio-technical systems.
I thought what was being requested was a way to detect bots.
I maintain my own bots, work extensively with product teams, and have a
deep and abiding familiarity with the complexity of designing effective
tools
It is extremely easy to detect a bot unless the bot operator chose to make
it hard. Just make a model for how the user interacts with the input
devices, and do anomaly detection. That imply use of Javascript though, but
users not using JS are either very dubious or quite well-known. There are
I actually meant a different type of maintenance.
Maintaining the encyclopedia (and other wiki projects) is of course an
activity that needs software support.
But software is also something that needs maintenance. Technology,
standards, circumstances change over time. Software left alone will
Since we're discussing how the Tech Wishlist works then I will comment on a
few points specifically regarding that wishlist.
1. A gentle correction: the recommendations are ranked by vote, not by
consensus. This has pros and cons.
2a. If memory serves me correctly, the wishlist process was
Couple thoughts:
1. ORES platform (ores.wikimedia.org) was designed to host a wide range of
machine learning models, not just the ones built by Aaron Halfaker himself.
So, if there is a computer scientist out there who is interested in
training and maintaining a new bot-detection model, it can be
Hi David, do you have a question? I saw the GIF but I don't know how to
interpret it in the context of this conversation.
Thanks,
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
On Tue, Feb 12, 2019 at 5:49 AM David Barratt
wrote:
> http://gph.is/2lnp32Z
>
The tech wishlist is awesome, and they do a lot of great work.
However, I don't think this type of democratic-driven development is
appropriate for all things. If it were we would just get rid of all the
other dev teams and just have a wish-list. In this case what is needed is
an anti-abuse
http://gph.is/2lnp32Z
On Mon, Feb 11, 2019 at 5:19 PM Pine W wrote:
> Thanks for the replies.
>
> I think that detailed discussion of the pros and cons of the Tech Wishlist
> should be separate from this thread, but I agree that one way to get a
> subject like unflagged bot detection addressed
Thanks for the replies.
I think that detailed discussion of the pros and cons of the Tech Wishlist
should be separate from this thread, but I agree that one way to get a
subject like unflagged bot detection addressed could be through the Tech
Wishlist assuming that WMF is willing to devote
Stewards are just 34 people and are not enough to be a big voting power at the
wishlist like enwiki people. What we actually need cannot get it thru that way.
--
Yongmin
Sent from my iPhone
Text licensed under CC BY ND 2.0 KR
Please note that this address is list-only address and any
We've been working on unflagged bot detection on my team. It's far from a
real product integration, but we have shown that it works in practice. We
tested this in Wikidata, but I don't see a good reason why a similar
strategy wouldn't work for English Wikipedia.
Hall, A., Terveen, L., &
This may be naive, but... isn't the wishlist filling this need? And if not
through a consensus-driven method like the wishlist, how should a WMF team
prioritize which power user tools it needs to focus on?
Or is just a matter of "Yes, wishlist, but more of it"?
- Jonathan
On Mon, Feb 11, 2019
Sure its certainly a front we can do better on.
I don't think Kasada is a product that's appropriate at this time. Ignoring
the ideological aspect of it being non-free software, there's a lot of easy
things we could and should try first.
However, I'd caution against viewing this as purely a
To clarify the types of unwelcome bots that we have, here are the ones that
I think are most common:
1) Spambots
2) Vandalbots
3) Unauthorized bots which may be intended to act in good faith but which
may cause problems that could probably have been identified during standard
testing in
OK. Yesterday I was looking with a few other ENWP people at what I think
was a series of edits by either a vandal bot or an inadequately designed
and unapproved good faith bot. I read that it made approximately 500 edits
before someone who knew enough about ENWP saw what was happening and did
On Fri, Feb 8, 2019 at 6:20 PM Pine W wrote:
> I don't know how practical it would be to implement an approach like this
> in the Wikiverse, and whether licensing proprietary technology would be
> required.
>
They are talking about Polyform [1], a reverse proxy that filters traffic
with a
17 matches
Mail list logo
