Evan Prodromou

I'm really glad to see this PR! Making it easy to include this basic user safety for new installations is a huge step in making the fediverse safe and welcoming...

I pushed this back to 0.3.0. Not sure how it's going to work, and I can't wait for it.

@marjoleink yes, that's how it works in the API.

This is great! I haven't set up translation mechanisms in the code yet. translatewiki.net does the translation for StatusNet and would probably be a great place to get help for...

I think this is for i18n on the Web UI and other strings in the system; I'd like to leave it separate.

@trwnh added this in #540, and I split it out as a separate issue.

I think the best process would be to wait for #540 to be complete, then to start working on them as an extension.

@bobwyman I agree with this as an editorial change, but I'm not sure it's an erratum. It's not actually an "error" -- just bad formatting! I think if we do...

@torgo so, I added a section to the criteria for doing security, privacy, a11y and i18n reviews.

I believe that there is in fact a semantic difference between `Read` and `View`. In particular: - `Read` primarily applies to textual content. For example, we would not apply `Read`...