Re: [Wikitech-l] New [[Main Page]] for Wikitech

[Steinsplitter Wiki]

Well done! :-)

> Date: Fri, 29 Jan 2016 12:55:40 +0100
> From: puro...@blissenbach.org
> To: wikitech-l@lists.wikimedia.org
> Subject: Re: [Wikitech-l] New [[Main Page]] for Wikitech
> 
> Well done!
> Purodha
> 
> On 29.01.2016 07:25, MZMcBride wrote:
> > Bryan Davis wrote:
> >>I've been working on a little redesign project for the Main Page on
> >>wikitech [0] and three key sub pages it points to since 2016-01-01 in
> >>my User space. Tonight I decided that although it is far from perfect
> >>it is better enough. I hope that some of you like it better than the
> >>old page and that none of you hate it with a fiery passion that
> >>compels you to revert it rather than helping me make it better.
> >>
> >>[0]: https://wikitech.wikimedia.org/wiki/Main_Page
> >
> > Very nice! Thank you for doing this.
> >
> > MZMcBride
> >
> >
> >
> > ___
> > 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] Scope of ArchCom

[Faidon Liambotis]

On Thu, Jan 28, 2016 at 10:53:27AM -0800, Rob Lanphier wrote:
> > This is especially true given that ArchComm really has absolutely no say
> > in resourcing and a given feature may not have secured funding (people,
> > hardware etc.)
> 
> Awwwyou're mail was so great, and then you ended with this!  Are you
> saying that the only real power in this world belongs to people with
> control of the money?

That's kinda stretching what I said, doesn't it :)

What I'm saying is that there is a (probably unavoidable) disconnect
between the ArchComm's and WMF's (or WMDE's, or other orgs' for that
matter) decision processes and cadences.

The ArchComm isn't in the path of resourcing and generally does not vet
RfCs based on whether e.g. they are backed by fully-staffed teams (or
even whether the required infrastructure for implementing them exists or
can be procured, under our constraints). My understanding is also that
as a purely technical body, it doesn't do much of a cost/benefit
analysis either. The ArchComm thus tends to judge ideas on their merits
and their merits alone -- and not unreasonably so.

This effectively means that some of the ArchComm-"approved" ideas may be
unimplementable -- at least until some organization or department
decides to foot the bill, possibly going via their budgeting process
(which can even be on an annual basis), etc.

So -- yes, I think there is a particular amount of "power" that the
ArchComm doesn't have and cannot really have; I don't think that's a
problem per se, but I do think it needs to be recognized and planned
for. This could example be to generally limit the scope of the committee
(e.g. to architecture direction and not feature planning; or to
MediaWiki/software architecture and not infrastructure planning, etc.)
and/or by ensuring budget owners are attending and influencing the
decision-making process.

Faidon

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] New [[Main Page]] for Wikitech

[Purodha Blissenbach]

Well done!
Purodha

On 29.01.2016 07:25, MZMcBride wrote:

Bryan Davis wrote:

I've been working on a little redesign project for the Main Page on
wikitech [0] and three key sub pages it points to since 2016-01-01 in
my User space. Tonight I decided that although it is far from perfect
it is better enough. I hope that some of you like it better than the
old page and that none of you hate it with a fiery passion that
compels you to revert it rather than helping me make it better.

[0]: https://wikitech.wikimedia.org/wiki/Main_Page


Very nice! Thank you for doing this.

MZMcBride



___
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] [Labs-l] New [[Main Page]] for Wikitech

[Jamison Lofthouse]

I like it. I think it's great you make the divisions between Wikitech, WM
Labs, and tool labs immediately clear. It should make the differences more
apparent for new users right from the beginning.

Negative24

On Thu, Jan 28, 2016, 10:55 PM Bryan Davis  wrote:

> I've been working on a little redesign project for the Main Page on
> wikitech [0] and three key sub pages it points to since 2016-01-01 in
> my User space. Tonight I decided that although it is far from perfect
> it is better enough. I hope that some of you like it better than the
> old page and that none of you hate it with a fiery passion that
> compels you to revert it rather than helping me make it better.
>
> [0]: https://wikitech.wikimedia.org/wiki/Main_Page
>
> Bryan
> --
> Bryan Davis  Wikimedia Foundation
> [[m:User:BDavis_(WMF)]]  Sr Software EngineerBoise, ID USA
> irc: bd808v:415.839.6885 x6855
>
> ___
> Labs-l mailing list
> lab...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/labs-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] New [[Main Page]] for Wikitech

[MZMcBride]

Bryan Davis wrote:
>I've been working on a little redesign project for the Main Page on
>wikitech [0] and three key sub pages it points to since 2016-01-01 in
>my User space. Tonight I decided that although it is far from perfect
>it is better enough. I hope that some of you like it better than the
>old page and that none of you hate it with a fiery passion that
>compels you to revert it rather than helping me make it better.
>
>[0]: https://wikitech.wikimedia.org/wiki/Main_Page

Very nice! Thank you for doing this.

MZMcBride



___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Labs-l] New [[Main Page]] for Wikitech

[Bryan Davis]

On Fri, Jan 29, 2016 at 9:28 AM, Alex Monk  wrote:
> Nice. What is needed to get other labs projects listed on the front page
> like tools?

An edit? :) I'd love to see portals created for Beta Cluster and
deployers for example. I'm sure there are some other really useful
projects in Labs that could use highlighting as well. Tool Labs ended
up with top billing based on my presumption that it is the most widely
used Labs project and one of the top reasons that a new viewer who
isn't already familiar with finding things on wikitech would end up
there.

I need to kill my table formatting and replace it with something that
is actually mobile friendly too. The page I made looks horrible on my
phone. :(

Bryan
-- 
Bryan Davis  Wikimedia Foundation
[[m:User:BDavis_(WMF)]]  Sr Software EngineerBoise, ID USA
irc: bd808v:415.839.6885 x6855

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] MediaWiki Language Extension Bundle 2016.01 release

[Kartik Mistry]

Hello all,

I would like to announce the release of MediaWiki Language Extension
Bundle 2016.01. This bundle is compatible with MediaWiki 1.25.x and
1.26.x.

Next MLEB is expected to be released in 3 months. If there are major
changes or important bug fixes, we will do intermediate release.
Please give us your feedback at
[[Talk:MLEB|https://www.mediawiki.org/wiki/Talk:MLEB]].

* Download: 
https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2016.01.tar.bz2
* sha256sum: 7a46bb96f852aa42f728c68e4e21558878c8cba703ce9f8f6c2316af7bbe03e3

Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://phabricator.wikimedia.org/
* Talk with us at: #mediawiki-i18n @ Freenode

Release notes for each extension are below.

-- Kartik Mistry

== Babel, CleanChanges and LocalisationUpdate ==
* Localisation updates only.

== CLDR ==
* Hebrew names for Cebuano and Norwegian are fixed.
* cldr converted to extension registration. Please update your
LocalSettings.php!

== Translate ==
* Old custom tokens were deprecated in favor of using regular "csrf"
(previously known as "edit") token. If you are using Translate WebAPIs
you might need to migrate.
* Special:Translations no longer shows PHP notices for pages with
invalid language codes
* Special:Translate now longer shows deprecation warnings about access
keys in the JavaScript console.
* Translate is now syntactically compatible with PHP7.
* Message group selector on Special:SearchTranslations no longer has
glitchy behavior after selecting a group.
* MessageIndex code was optimized. It now ignored messages not in
$wgTranslateMessageNamespaces. By default this should be fine, but if
you have translations in custom namespaces, check that they are
included.
* Pages with  now load faster with cold caches.
* MachineTranslationAid no longer throws uncaught exceptions with
default configuration that broke other translation aids.

== UniversalLanguageSelector ==
* ULS now uses extension registration and thus requires MediaWiki 1.25 or later
* Input methods should now work inside Visual Editor.

* Fonts:
** OpenDyslexic font updated to latest upstream.
** Akkadian font should work again.

* Input Methods:
* New input methods:
** Rodali (Assamese) layout.
** OdiScript (Oriya) layout.
** Yoruba layout.

* Updated input methods:
** Updated Oriya Lekhani layout.
** Digit fixes in Southern Kurdish layout.
** Minor fixes in Sinhala layout.

-- 
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Labs-l] New [[Main Page]] for Wikitech

[Alex Monk]

Nice. What is needed to get other labs projects listed on the front page
like tools?

On 29 January 2016 at 05:55, Bryan Davis  wrote:

> I've been working on a little redesign project for the Main Page on
> wikitech [0] and three key sub pages it points to since 2016-01-01 in
> my User space. Tonight I decided that although it is far from perfect
> it is better enough. I hope that some of you like it better than the
> old page and that none of you hate it with a fiery passion that
> compels you to revert it rather than helping me make it better.
>
> [0]: https://wikitech.wikimedia.org/wiki/Main_Page
>
> Bryan
> --
> Bryan Davis  Wikimedia Foundation
> [[m:User:BDavis_(WMF)]]  Sr Software EngineerBoise, ID USA
> irc: bd808v:415.839.6885 x6855
>
> ___
> Labs-l mailing list
> lab...@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/labs-l
>
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] [Mediawiki-api] [Engineering] Deprecating rest.wikimedia.org in favor of /api/rest_v1/

[Gabriel Wicke]

Luigi,

On Thu, Jan 28, 2016 at 2:09 AM, XDiscovery Team  wrote:
> I tried /rest_v1/ endpoint and it is terribly fast.

that is great to hear. A major goal is indeed to provide high volume
and low latency access to our content.

> @Strainu / @Gabriel , what does  'graph' extension do ?

If you refer to
https://en.wikipedia.org/api/rest_v1/?doc#!/Page_content/get_page_graph_png_title_revision_graph_id,
this is an end point exposing rendered graph images for
https://www.mediawiki.org/wiki/Extension:Graph (as linked in the end
point documentation).

> I have few questions for using proxy cache:
> 1# Is it possible to query a page by page_ID and include redirect?

We don't currently provide access by page ID. Could you describe your
use case a bit to help us understand how access by page id would help
you?

> /page/title/{title}
> allow to get metadata by page, including the pageID , but I would like to
> have final page redirect (e.g. dna return 7956 and I would like to fetch
> 7955 of redirected 'DNA' )

We are looking into improving our support for redirects:
https://phabricator.wikimedia.org/T118548. Your input on this topic
would be much appreciated.

> /page/html/{title} get the article but page_ID / curid is missing in source
> I would like to get the two combined.

This information is actually included in the response, both in the
`ETag` header and in the  of the HTML itself. I have updated the
documentation to spell this out more clearly in [1]. The relevant
addition is this:

The response provides an `ETag` header indicating the revision and
render timeuuid separated by a slash (ex: `ETag:
701384379/154d7bca-c264-11e5-8c2f-1b51b33b59fc`). This ETag can be
passed to the HTML save end point (as `base_etag` POST parameter), and
can also be used to retrieve the exact corresponding data-parsoid
metadata, by requesting the specific `revision` and `tid` indicated by
the `ETag`.

> 2# The rest are experimental:
> what could happen if a query fail?
> Does it raise an error, return 404 page or what else?

The stability markers are primarily about request and response
formats, and not about technical availability. Experimental end points
can change at any time, which can result in errors (if the request
interface changed), or return a different response format.

We are currently discussing the use of `Accept` headers for response
format versioning at
https://www.mediawiki.org/wiki/Talk:API_versioning. This will allow us
to more aggressively stabilize end points by giving us the option of
tweaking response formats without breaking existing clients.

> I am thinking if possible to use api.wikipedia as fallback, and use proxy
> cache as primary source any ajax example for doing that to handle possible
> failures?

Yes, this is certainly possible. However, you can rely on end points
currently marked as "unstable" in the REST API. Basically all of them
are used by a lot of production clients at this point, and are very
reliable. Once we introduce general `Accept` support, basically all of
the unstable end points will likely become officially "stable", and
several `experimental` end points will graduate to `unstable`.

> 3# Does /rest/ endpoint exist also for other languages?

Yes, it is available for all 800+ public Wikimedia projects at /api/rest_v1/.


[1]: 
https://github.com/wikimedia/restbase/pull/488/files#diff-2b6b60416eaafdf0ab45f6c9ffb8be3aR225

-- 
Gabriel Wicke
Principal Engineer, Wikimedia Foundation

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Bot operators: Please check your configuration

[Brad Jorsch (Anomie)]

It currently still works to POST to the API via http instead of https. But
we'd really like to stop allowing that, see
https://phabricator.wikimedia.org/T105794. Thus, the API will now return a
warning if https was expected but not used.

If you run a bot, please check your configuration to make sure that you're
using https rather than http. If you're using a distinctive user agent for
your bot (which you all are, right?[1]), you can now check whether your bot
is using http by going to
https://www.mediawiki.org/wiki/Special:ApiFeatureUsage, entering your agent
(or any useful prefix of it), and looking for "https-expected".

If for some reason your bot cannot support https, you really should upgrade
it to make that happen.

 [1]: https://meta.wikimedia.org/wiki/User-Agent_policy

-- 
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] VisualEditor deployment to 1000+ users: who wants the feedback?

[Pine W]

I think the Editing team would be interested in this! Pinging James
Forrester.

I am glad to see the interest in tables. Table editing is much easier in VE
than in wikitext and I'd love to see additional table editing functionality
in VE, including the ability to import tables from spreadsheet applications
with text and cell formatting.

Pine

On Fri, Jan 29, 2016 at 12:22 PM, Daniel Barrett  wrote:

> Within the next few weeks, I'll be deploying VisualEditor for 1000+
> authors here at Cimpress/Vistaprint, in a wiki with 225,000 articles.
>
> I plan to collect feedback from our users on what works and what doesn't.
> What would be the best way to communicate this feedback to Wikimedia?
>
> Here are some early, informal comments from our pilot group of 20 users:
>
> "I am in love!"
>
> "TemplateData integration is awesome."
>
> "How do I insert  tags?"  (He didn't notice the "More" link in the
> font menu.)
>
> "How do I set the width of a table column?"
>
> "How do I copy and paste table rows?"
>
> "Editing links is fiddly" (https://phabricator.wikimedia.org/T124305)
>
> "I didn't see the editing tools at first because they're white on a white
> background."
>
> "Can we save the page without having a pop-up?"
>
> Thanks,
> DanB
>
>
> ___
> 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] [Engineering] Announcing mediawiki-containers, a Docker-based MediaWiki installer

[James Forrester]

On 27 December 2015 at 11:52, Ori Livneh  wrote:

> On Thu, Dec 24, 2015 at 3:57 PM, Gabriel Wicke 
> wrote:
>
>> I am writing to announce mediawiki-containers [1], a simple installer for
>> MediaWiki with VisualEditor, Parsoid, RESTBase and other services, using
>> Linux containers.
>>
>
> This is very nice work -- kudos. Is it too soon to envision running this
> (or rather, some future iteration) in production at Wikimedia? What would
> need to happen?
>

​Ping on this. I for one would be interested too. :-)​

J.
-- 
James D. Forrester
Lead Product Manager, Editing
Wikimedia Foundation, Inc.

jforres...@wikimedia.org | @jdforrester
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] *unclear-"now"-timestamp* (was Re: Bot operators: Please check your configuration)

[Brad Jorsch (Anomie)]

On Fri, Jan 29, 2016 at 1:41 PM, Bináris  wrote:

> 2016-01-29 18:56 GMT+01:00 Brad Jorsch (Anomie) :
>
> > by going to
> > https://www.mediawiki.org/wiki/Special:ApiFeatureUsage, entering your
> > agent
> > (or any useful prefix of it), and looking for "https-expected".
> >
>
> What does *unclear-"now"-timestamp* mean here?
>

For various API timestamp-typed parameters, you can pass unusual values
such as the empty string or "0" and it will be interpreted as meaning
"now", which doesn't make very much sense except for the fact that it has
always done that. If you really mean "now", you should pass that as the
value instead.

action=edit even has to hack around this to avoid spurious edit conflicts
if you do it for the 'basetimestamp' parameter. Ideally we'd make empty
string and '0' be rejected as invalid timestamps, but first people have to
stop passing them in.


-- 
Brad Jorsch (Anomie)
Senior Software Engineer
Wikimedia Foundation
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Parsoid entrypoint http://parsoid-lb.eqiad.wikimedia.org being decommissioned

[Subramanya Sastry]

Hello everyone,

The public Parsoid endpoint http://parsoid-lb.eqiad.wikimedia.org is 
being decommissioned  [1] once we migrate over all straggler references 
to that endpoint [1] possibly as soon as 3 weeks from now.


As far as we know, there are very few requests to that endpoint right 
now, but if you have been using that endpoint, please switch over to 
using the RESTbase service instead. You can access Parsoid HTML for the 
wikimedia wikis via their REST API endpoint. For example, 
https://en.wikipedia.org/api/rest_v1/?doc is the REST API url for 
English Wikipedia content.


Thanks,
Subbu.

1. https://phabricator.wikimedia.org/T110474

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Unable to log into phabricator

[Devang Gaur]

 I registered into phabricator with my Mediawiki account initially . Now
when I opt for "login or register via mediawiki" . It takes me to a new
account registration page whereas I have an existing phabricator account
(@dg711) already linked with that same mediawiki account . Is that a bug or
what ?

Please help me resolve this .

Thanks , 
Devang Gaur


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] [FINAL COMMENT PERIOD] [RFC]: Defining a policy for REST API result format versioning / negotiation

[Gabriel Wicke]

This is now entering its final comment period, so please weigh in at
https://phabricator.wikimedia.org/T124365.

Based on your input, the Parsing, Editing & Services teams will make a
decision on this next Wednesday, Feb 2nd.

Thanks,

Gabriel

On Thu, Jan 21, 2016 at 4:29 PM, Gabriel Wicke  wrote:
> Hi,
>
> we are considering a policy for REST API end point result format
> versioning and negotiation. The background and considerations are
> spelled out in a task and mw.org page:
>
> https://phabricator.wikimedia.org/T124365
> https://www.mediawiki.org/wiki/Talk:API_versioning
>
> Based on the discussion so far, have come up with the following
> candidate solution:
>
> 1) Clearly advise clients to explicitly request the expected mime type
> with an Accept header. Support older mime types (with on-the-fly
> transformations) until usage has fallen below a very low percentage,
> with an explicit sunset announcement.
>
> 2) Always return the latest content type if no explicit Accept header
> was specified.
>
> We are interested in hearing your thoughts on this.
>
> Once we have reached rough consensus on the way forward, we intend to
> apply the newly minted policy to an evolution of the Parsoid HTML
> format, which will move the data-mw attribute to a separate metadata
> blob.
>
> Gabriel Wicke



-- 
Gabriel Wicke
Principal Engineer, Wikimedia Foundation

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] VisualEditor deployment to 1000+ users: who wants the feedback?

[Daniel Barrett]

Within the next few weeks, I'll be deploying VisualEditor for 1000+ authors 
here at Cimpress/Vistaprint, in a wiki with 225,000 articles.

I plan to collect feedback from our users on what works and what doesn't.  What 
would be the best way to communicate this feedback to Wikimedia?

Here are some early, informal comments from our pilot group of 20 users:

"I am in love!"

"TemplateData integration is awesome."

"How do I insert  tags?"  (He didn't notice the "More" link in the font 
menu.)

"How do I set the width of a table column?"

"How do I copy and paste table rows?"

"Editing links is fiddly" (https://phabricator.wikimedia.org/T124305)

"I didn't see the editing tools at first because they're white on a white 
background."

"Can we save the page without having a pop-up?"

Thanks,
DanB


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Bot operators: Please check your configuration

[Bináris]

2016-01-29 18:56 GMT+01:00 Brad Jorsch (Anomie) :

> by going to
> https://www.mediawiki.org/wiki/Special:ApiFeatureUsage, entering your
> agent
> (or any useful prefix of it), and looking for "https-expected".
>

What does *unclear-"now"-timestamp* mean here?


-- 
Bináris
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] *unclear-"now"-timestamp* (was Re: Bot operators: Please check your configuration)

[Bináris]

2016-01-29 20:06 GMT+01:00 Brad Jorsch (Anomie) :

> On Fri, Jan 29, 2016 at 1:41 PM, Bináris  wrote:
>
> > 2016-01-29 18:56 GMT+01:00 Brad Jorsch (Anomie) :
> >
> > > by going to
> > > https://www.mediawiki.org/wiki/Special:ApiFeatureUsage, entering your
> > > agent
> > > (or any useful prefix of it), and looking for "https-expected".
> > >
> >
> > What does *unclear-"now"-timestamp* mean here?
> >
>
> For various API timestamp-typed parameters, you can pass unusual values
> such as the empty string or "0" and it will be interpreted as meaning
> "now", which doesn't make very much sense except for the fact that it has
> always done that. If you really mean "now", you should pass that as the
> value instead.
>
> action=edit even has to hack around this to avoid spurious edit conflicts
> if you do it for the 'basetimestamp' parameter. Ideally we'd make empty
> string and '0' be rejected as invalid timestamps, but first people have to
> stop passing them in.
>
>
>
Thank you! I know it's from Pywikibot because that was the string I
entered. :-)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Unable to log into phabricator

[Chris Steipp]

Hi Devang,

I see from https://phabricator.wikimedia.org/p/dg711/ that the MediaWiki
account you're associated with is
https://www.mediawiki.org/wiki/User:Devang_gaur. Just making sure that's
the account you're logging in with on wiki, right?

Due to issues with sessionmanager on wiki, you might try deleting all your
wiki cookies and logging in on wiki again. Just to make sure that's not an
issue.

On Fri, Jan 29, 2016 at 12:27 PM, Devang Gaur  wrote:

>  I registered into phabricator with my Mediawiki account initially . Now
> when I opt for "login or register via mediawiki" . It takes me to a new
> account registration page whereas I have an existing phabricator account
> (@dg711) already linked with that same mediawiki account . Is that a bug or
> what ?
>
> Please help me resolve this .
>
> Thanks ,
> Devang Gaur
>
>
> ___
> 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