Google Code-in

Problem

There has been much discussion on why we allow anonymous users to create maps, as it creates complications. See #445.

We have decided to move forward with anonymous users & continue improving our implementation of it.

We would like to document the why & how in a new wiki file. This is a research issue and should align with MK's overall purpose.

Solution:

Focusing around this quote:

"We have had input from community partners that people who may be vulnerable or are concerned about being connected to data produced on MapKnitter.org may be more comfortable producing maps anonymously, despite the drawbacks. So we have continued to allow this although we are getting better at explaining why it presents difficulties like this one, and trying to help people make a good decision about whether to use an anonymous map or not."

Please cover:

• Conceptual: what type of impact might MK have environmentally, & why might people want to be anonymous in their contributions to this? You can reference MK's roots in the BP oil crisis.
• User experience: what privileges do anonymous authors have/lose?
• Code architecture: what is the current architecture we use for anonymous users (authentication, etc)? What are the possible downfalls & future solutions to make it more sophisticated?

Additional

Feel free to discuss this prompt with any mentors or @jywarren and @ebarry!

Please find further information on completing this task / getting help on the linked issue.

Thank You 😊