Page MenuHomePhabricator

Redirect legacy language codes for Toki Pona to tok.wikipedia.org
Closed, ResolvedPublic

Description

In T404457, we have, for the first time ever, a previously-deleted Wikipedia returning to Wikimedia servers. When the Toki Pona Wikipedia last was hosted here, there was no ISO code for the language, and according to T30504 it used thee different pseudo-ISO-codes at different times:

  • tp.wikipedia.org
  • tokipona.wikipedia.org
  • art-tokipona.wikipedia.org

Given that there remain off-platform links to the old domains, and that in cases where a wiki got an ISO code we have renamed the wiki and created a domain-level redirect (see generally T125073), I think we should do the same here, even if this differs in the intervening steps of the wiki being deleted and then (soon) re-created. Note that tp could be a valid ISO 639-1 code, but it happens to not be. As far as I know no new 639-1 codes are being created, so I don't think this should be a blocker to restoring that code as a redirect.

I'm not putting this as blocked by T404457, on the basis that the tok.wikipedia.org domain does already exist, even if it currently points to Incubator.

Event Timeline

So as far as I can tell, these domains have been dead for at least 12 years.. how many links are there realistically still out there referring to those names?

There are any number of historical links, on-wiki, on the mailing lists, and indeed on Phabricator, referring to tokipona.wikipedia.org. Externally, here is an article by academic and Wikimedian Stanislav Kozlovsky referencing it; here is a blog post by someone else referencing it, and another.

The tp code has fewer backlinks, but is the name that @bvibber originally created the wiki under, and in that context shows up in this book on p. 254.

Both of these codes are also referenced in any old revisions containing [[tp:]] or [[tokipona:]] langlinks, so there's a backwards compatibility aspect too.

I can't see any usage of the art-tokipona code anywhere but a few internal technical discussions, though, so I'm fine dropping that part of this request. But I think there's a good case that it's conceivable someone could find resources mentioning a Toki Pona Wikipedia located at either tokipona.wikipedia.org or tp.wikipedia.org, type that in, and then (if no redirect is created) be misled into thinking that there is no such wiki.

Both of these codes are also referenced in any old revisions containing [[tp:]] or [[tokipona:]] langlinks, so there's a backwards compatibility aspect too.

That's technically a completely separate thing; the interwiki map is a separate construct from what domains exist, so a "tp:" langlink can work or not completely independently of whether "tokipona:" works or not.

Per the task description. This is not actually blocked on the wiki creation, nor is this required for the wiki itself to actually function properly, thus not a post-creation task.

This type of redirect/rewrite would likely have to be handled in the appserver apache config rather than the CDN. That would mean serviceops team is more appropriate than traffic team.

edit: well, it would need both. first DNS records (traffic) and then apache virtual hosts and rules (serviceops).

This technically wasn't stalled, but there wasn't much reason to get around to it till now, so, noting that T404457 has now been resolved and tokwiki exists.

Change #1212577 had a related patch set uploaded (by Majavah; author: Majavah):

[operations/dns@master] Add former Toki Pona language codes

https://gerrit.wikimedia.org/r/1212577

Change #1212578 had a related patch set uploaded (by Majavah; author: Majavah):

[operations/puppet@production] mediawiki: Add redirects for old Toki Pona aliases

https://gerrit.wikimedia.org/r/1212578

Change #1212577 merged by Majavah:

[operations/dns@master] Add former Toki Pona language codes

https://gerrit.wikimedia.org/r/1212577

Change #1212578 merged by Majavah:

[operations/puppet@production] mediawiki: Add redirects for old Toki Pona aliases

https://gerrit.wikimedia.org/r/1212578

taavi claimed this task.