Frequently Asked Questions
Can anyone write for Indymedia?
Yes, anyone! We recommend you first create an account and then you can report the news as you see it to your heart’s content.
If you need help publishing to Indymedia, see our step by step instructions.
What does it take for my article to become a feature?
Any article can become a feature. Above all, if your article is well written and is both relevant and interesting to our readership, then it stands a high chance of being promoted to a feature by an editor. It also helps if your article is correctly formatted and, where possible, that it includes high quality images (not clip art!).
Please note that it may take a few hours before your article is spotted by one of our editors and promoted.
How do I reset my password if I’ve forgotten it?
You can reset your password here. This will send you an email with instructions on how to reset your password.
What does it mean that my article has been ‘locked’?
This is totally normal. After a few weeks (depending on the type of content) your article will become locked to prevent further editing. This gives you a few weeks to re-edit or update your article but also ensures the integrity of our reporting archive on into the future.
Are there restrictions on what can and can’t be published?
Yes, please see the editorial policy. Generally it boils down to ‘don’t be an arsehole to others’. Content that violates the editorial policy will be hidden but will still be available in the submission feed.
Why was my article/comment hidden?
Your article or comment in some way violated our editorial policy. If you’d like clarification on why it was hidden or you’d like to contest this decision, please email us with a link to the article or comment in question.
Can I join the collective?
Yes, anyone can apply to join the editorial collective. See here.
What should I doI’ve noticed a bug with the site?
Please report it to email@example.com with as many details as possible including: the full URL of the page or pages where you noticed the bug; what you were trying to do or what you were expecting the site to do; and the precise behaviour of the bug you observed including any error messages (verbatim). Also, the date and time the bug occurred may help us.