un_
Having a repository where many people can come and open issues puts a burden on my shoulders - I'll look at the page and see that I need to fix <some number> of issues, otherwise I'll look bad, or people will stop using my code.
Releasing my code in releases (so that everyone is on one release, or not on any release at all) means that I don't have to deal with people who've cloned the code half-way through the implementation of something large and complained that it won't run, or that it's full of bugs.
Releasing releases has been a solid model for me, especially as I work alone, or with a maximum of two or three other people at once.
If I was going to use a public repository, I think I'd end up using CVS.
I can't say I have not considered this, but it requires "faking" yourself, even for just a minute. It also demands that you have a high degree of Japanese language.
I don't think it's entirely unreasonable to expect people who do not look as though they know the language in a virtually homogeneous society to not know the language. I've heard that the people who encounter this "get around" it by demonstrating that they do know at least something.
I read a blog post once that language is one of the biggest barriers; seriously dedicating one's time to learning the language is something that many, many non-native speakers simply miss out on - and, in some cases, go onto assume that this response is because of xenophobia or racism.
I haven't been in Japan long enough to give my own anecdotal experience, though.
I tried DKIM, but the e-mails were still sent to Gmail's spam folders. Eventually I gave up on self-hosted e-mail.