Should we restrict access to the create-list endpoint?

[escottalexander]

Sam said:

Now that we're exposing an API route to create data, do y'all think we should restrict access a bit more to prevent any potential spam?

Record your thoughts on whether this should/shouldn't be done and the best approach if you think its a good idea.

[swellander]

Here's what I'm thinking, generally

Pros:

• Better safe than sorry. Would be a bummer to have spam-related issues while the app's getting a lot of use.
• Would be nice to deliver as robust of a product as we can.

Cons:

• Could take away time from working on potentially more relevant features.
• Might not be necessary at all. Not sure what the visibility of the project will be and what kind of traffic it will receive.

[0xChijioke]

From my perspective, restricting list creation to badgeholders makes sense. It could serve as a measure to maintain order and deter spam from abusing the platform.
Considering that badgeholders are more likely to curate lists that resonate with other badgeholders, it could ensure that lists created are both relevant and of high quality.
However, it's worth considering the possibility of exceptions for non-badgeholders who may also have valuable insights.