Good ideas and conversation. No ads, no tracking. Login or Take a Tour!
I don't know if you've done localization stuff before, but a common way to do it is to define all the interface strings ("feed", "chatter", "badges", etc.) in a single file that gets included in other pages. Then to do a translation of the interface, you create a new version of the file and translate all the strings. When someone visits the site, their browser mentions its preferred languages and Hubski would automatically select the correct localization file to include. For laughs I have Latin and Esperanto as my preferred languages in Chrome. If a website doesn't support localization then nothing happens, but if they happen to have an Esperanto interface I suddenly get the web in the universal language!