or MAYBE, even more evil:
commons.wikimedia.api.wikipedia.org -- where first two domains
commons.wikimedia would point to existing domain, that would actually
allow you to enable this gateway instantly on all projects for all
domains, so that you could use api of fr.wikisource using wikispecies
domain:
fr.wikisource.api.wikispecies.org
I don't know if that is actually good for anything :) but it would
surely allow you to bypass cookie restrictions everywhere (for api's
only). On the other way, I think we could just think of using some
different technology than cookies to avoid mess with DNS
On Thu, Mar 28, 2013 at 8:41 AM, Petr Bena <benapetr(a)gmail.com> wrote:
What about inserting another domain just to prevent
confusion and to
keep current redirects, which would ONLY allow api, such as
commons.api.wikipedia.org
the *.api.<project> would just be some kind of universal api gateway
for all domains
On Wed, Mar 27, 2013 at 10:07 PM, Juliusz Gonera <jgonera(a)wikimedia.org> wrote:
> On Fri, Mar 22, 2013 at 9:22 PM, MZMcBride <z(a)mzmcbride.com> wrote:
>
>> Please draft an RFC at <https://www.mediawiki.org/wiki/RFC>. :-)
>>
>
>
http://www.mediawiki.org/wiki/Requests_for_comment/Alternative_Commons_Doma…
> Please share your comments.
>
>
>>
commons.wikipedia.org already redirects to
commons.wikimedia.org (for
>> historical reasons, maybe), so that has to be considered.
>
>
> Yes, it redirects. But to solve the problem I'm describing, the API would
> need to be served from
commons.wikipedia.org.
>
>
>> I think what
>> you're proposing is also kind of confusing and I'm wondering if there
>> aren't better ways to approach the problem.
>>
>
> I'm open to suggestions, but I'd rather not wait until CentralAuth gets
> completely redesigned and rewritten.
>
> --
> Juliusz
>
>>
> _______________________________________________
> Wikitech-l mailing list
> Wikitech-l(a)lists.wikimedia.org
>
https://lists.wikimedia.org/mailman/listinfo/wikitech-l