A little tangential, and maybe it goes without saying, but I really like
that MediaWiki API points to documentation in-band when fetched via browser
(without the format option). For example:
https://en.wikipedia.org/w/api.php?action=query&prop=pageimages&piprop=thumbnail&pithumbsize=96&pilimit=5
+S (not sure if you're on this list)
On Thu, Apr 30, 2015 at 3:27 AM, Joaquin Oltra Hernandez <
jhernan...@wikimedia.org> wrote:
> Personally, I would love hand crafted awesome documentation and full
> versions of the API. From developers, to developers, with care.
>
> As an example, the github a
+1
> On Apr 30, 2015, at 10:29 AM, Joaquin Oltra Hernandez
> wrote:
>
> Hi!
>
> I've been feeling that the signal to noise ratio on #wikimedia-mobile since
> the addition of wikibugs and our new apps engineers (more grrrit-wm spam) is
> turning to be 0 (that is, no signal because of too much
Bryan Davis, 30/04/2015 22:42:
My only $0.02 is that pushing bots to another channel generally ends
up being functionally the same as muting the bots entirely unless
people setup watches on particular words to see pings from them.
And I'll point out that if you want to move bots then the easies
Thanks Kaldari & Joaquin! Tomorrow, I'm planning on making a shell script
that compares head to whatever branch and then makes it pretty with links.
Ideally, copy / paste format into a wiki page.
On Thu, Apr 30, 2015 at 3:11 AM, Joaquin Oltra Hernandez <
jhernan...@wikimedia.org> wrote:
> Thanks
My only $0.02 is that pushing bots to another channel generally ends
up being functionally the same as muting the bots entirely unless
people setup watches on particular words to see pings from them.
I do things in my client to make bots less obtrusive, but I totally
understand that doing so is (a
I would favor having the bots on a separate channel as well.
On Thu, Apr 30, 2015 at 1:09 PM, Brian Gerstle
wrote:
> I think the point is that it's unrealistic to expect people to handle this
> on the "client side" and they should "opt in" for those
> notifications/messages by joining that chann
Just a thought: as long as we primarily link to webchat.freenode.net from
https://meta.wikimedia.org/wiki/IRC/Channels the traffic in the channels
should be suited after that tool rather than what some power user have
available.
*Med vänliga hälsningar,Jan Ainali*
Verksamhetschef, Wikimedia Sver
I think the point is that it's unrealistic to expect people to handle this
on the "client side" and they should "opt in" for those
notifications/messages by joining that channel (i.e. separating events on
the server side, so it applies to all clients).
On Thu, Apr 30, 2015 at 4:03 PM, Bahodir Mans
I use LimeChat, but haven’t tried hard enough to filter out bots. I don’t mind
creating a new channel and directing bots there. XChat advanced settings
related to “Text Events”, which maybe what you want. Not sure about the backlog
support though.
> On Apr 30, 2015, at 3:36 PM, Joaquin Oltra He
Bryan that's exactly what I'd like. Direct the bots to other channels and
join those if you want the notifications. I personally will because I find
them very useful.
Baha the reality is not that easy. I want backlog so I've moved to the
irccloud chat, and there I can only ignore users. The proble
I personally detest them now I am working with mostly a remote team.
They are useful occasionally but not missing messages from team
members is far too important for me.
I've not found a good way to filter these out (look at the pink lines
that mean pings in my irc client - http://imgur.com/MsYk9O
I think they should stay and everyone should be able to configure their client
to hide specific message from showing.
> On Apr 30, 2015, at 1:50 PM, Brian Gerstle wrote:
>
> Totally agree, having *important messages only* in IRC would be nice. Another
> idea would be to have notifs go to more
Totally agree, having *important messages only* in IRC would be nice.
Another idea would be to have notifs go to more specific chat rooms based
on the project.
On Thu, Apr 30, 2015 at 1:45 PM, Corey Floyd wrote:
> I think this is a good idea… the only thing I think should be in the main
> channe
+1, as a newcomer, the bots create quite a bit of interference. And another
+1 for making the bot channels more specific (Android, iOS, etc).
On Thu, Apr 30, 2015 at 11:29 AM, Joaquin Oltra Hernandez <
jhernan...@wikimedia.org> wrote:
> Hi!
>
> I've been feeling that the signal to noise ratio on
I think this is a good idea… the only thing I think should be in the main
channel is something like breaking the build (at least for the apps guys)
On Thu, Apr 30, 2015 at 1:29 PM, Joaquin Oltra Hernandez <
jhernan...@wikimedia.org> wrote:
> Hi!
>
> I've been feeling that the signal to noise rati
Hi!
I've been feeling that the signal to noise ratio on #wikimedia-mobile since
the addition of wikibugs and our new apps engineers (more grrrit-wm spam)
is turning to be 0 (that is, no signal because of too much noise).
It is really difficult to talk about anything when somebody else is working
Fwd, forgot to press answer all :(
Gesendet mit meinem HTC
- Weitergeleitete Nachricht -
Von: "Florian Schmidt"
An: "Aaron Halfaker"
Betreff: AW: [WikimediaMobile] [Wikitech-l] Anonymous editing impact on mobile
Datum: Do., Apr. 30, 2015 16:26
Great to read this, thanks Aaron :)
Ges
Personally, I would love hand crafted awesome documentation and full
versions of the API. From developers, to developers, with care.
As an example, the github api is very good:
https://developer.github.com/v3/issues/ for example.
And for me the gold in api docs is the stripe ones :
https://stripe
Thanks Adam. Subscribed!
On Thu, Apr 30, 2015 at 1:01 AM, Adam Baso wrote:
> Hi, realized I should share this on mobile-l.
>
> Just wanted to quickly recommend that engineers and others with an
> interest sign up for the following lists:
>
> https://lists.wikimedia.org/mailman/listinfo/mediawiki
Thanks for the info Rob!
I recommend you have a pass at the mobile frontend release changelog,
there's cool info there on generating changelogs. I just added a couple of
new comments:
https://phabricator.wikimedia.org/T95324#1188899
https://phabricator.wikimedia.org/T95324#1188899
https://phabric
A simple first step would be to tag the FIXMEs with a small set of tags,
like half of Jon's examples already are.
–Sam
On Wed, Apr 29, 2015 at 7:10 PM, Brian Gerstle
wrote:
> Great thinking, Jon! I'm sure that didn't even catch everything. I know
> there are some comments like that in the iOS r
22 matches
Mail list logo
