I’m… torn on the utility, benefit, and overly subjective nature of the request, but… I get the hypothetical concern too. I looked through the first 2 pages of lists, and don’t see a single even mildly spoiler-y list title. Can you find an example of one? (Put under a details fold or something here)
Specifically I’m not convinced that changing list privacy is a desirable behavior - especially since the list creation and pages say nothing about naming conventions or spoilering, and lists are externally linked - they have a function outside the individual book pages. people may have specific reasons for the name or privacy settings - and I think people should have maximum possible freedom (which is of course very subjective to define).
I would rather see this dealt with by:
Assign a spoiler tag/attribute to said list (which should also be a checkbox on the add/edit list pages)
I guess all we really need is the ability to report lists and reviews. And then on the librarian side, the ability to filter those list/review reports by language, so that we can all deal with reports for languages we don’t speak so that even if we get spoiled, it’s less likely to be for a book we would’ve liked to read.
It would be nice to organize though, have the functionality ready if it’s ever needed. We wouldn’t need to remove the review/list, just confirm that it is a spoiler and then have the option to add that spoiler tag.
Ah cool. Unfortunately I can’t reply there now, bc it’s past the 7 days. so I’m gonna re-ask here
This is great, but can you please add an X to it on mobile, or have it go away after a certain amount of scrolling, so it doesn’t take up a bunch of the screen the while way down?
This is a good shout! After discussion with @nikoru we think just surfacing that big warning on first save and then maybe a one line warning on subsequent ones is the solution here. Does that sound right?
The discussion seems to be about something completely different from the main request I don’t think how we treat spoilers is relevant at all to a reporting function, because AFAIK Natively doesn’t have a spoiler policy yet. A spoiler in a list would be annoying, but not against the rules.
I do think we need a report function for lists (and everywhere else where users can contribute text), to be able to flag ordinary abuse like spam first and foremost. And as a necessary part of introducing a reporting feature, clear guidelines should be drawn up about what does and doesn’t constitute abuse of the system. Those guidelines should probably include a spoiler policy, but it’s beside the core issue of how to deal with potential abuse.
As an Amazon Associate, Natively earns from qualifying purchases through any Amazon links on the site.