Status of the @kowordpressorg Twitter/X Handle for ko.wordpress.org


Hi Polyglots,

I’d like to share an update regarding the @kowordpressorg Twitter/X handle, which has historically been associated with the Korean WordPress community and the ko.wordpress.org Rosetta site.

As of 2024, the Korean WordPress translation team has been officially re-formed, but unfortunately, we currently have no administrative access to the @kowordpressorg account. The original account owner is unreachable, and our attempts to contact former community members via KakaoTalk, Facebook groups, and other local channels have not been successful.

While there was some informal connection to the old kopress.kr community, most of those contacts are now inactive.

In recent discussions on GitHub (Marketing Team Issue #525) and the Meta team, it was suggested that:
Issue #525

The simplest option is to regain access through the original account holder, though this seems unlikely.

Trademark claims are a long and uncertain process, especially since this is not a clear impersonation issue.

An alternative is to create a new account and share credentials with the Community team to avoid future access issues.

While the number of active contributors in the Korean Polyglots team is currently small, those involved — including myself — believe it’s important to preserve the Rosetta site’s identity by reclaiming the @kowordpressorg handle if possible.

Since the handle @kowordpressorg directly represents the Rosetta site identity, it’s something that affects the locale’s official channels and coordination.

In hindsight, I believe it would’ve been appropriate to raise this discussion on the Polyglots team blog and ping the #ko_KR team for input as well.

I also believe this should have been a topic for broader community discussion, not only within the Marketing Team but also with Locale Managers and the Korean Polyglots team.

It directly relates to our locale’s official communication channels, and any decisions about official handles should be made in collaboration with those managing the locale and translations.

We’d love to hear your thoughts, suggestions, or possible experiences from other locales who’ve faced similar issues.

Thanks so much for reading, and looking forward to your input!