Goodreads Developers discussion
feature requests
>
spoiler-tags in "currently-reading" status updates
date
newest »
newest »
message 1:
by
Carly
(last edited Mar 30, 2013 07:52PM)
(new)
Mar 30, 2013 07:51PM
Currently, the spoiler tag(< spoiler>< /spoiler>, which should appear as (view spoiler)[ (hide spoiler)]) doesn't work properly in "currently-reading" book status updates: spoiler-tagged text shows up with the spoiler and xml tag visible. Book status updates appear at the bottom of the reviews, so spoilers are a problem. The character limitation (421 chars) for updates is also irritating--is it possible to extend it, or is there a rationale for the rather stringent limitation?
reply
|
flag
Status updates don't allow for spoiler tags, this is a feature decision, we don't want users putting spoilers in statuses. This is totally not obvious and even not all Goodreads employees are aware of this.
Hi Michael, thanks for the reply. What is the reason for not allowing spoilertags in updates? It seems like that is where they would be most useful. Since it sounds like use of the tag was blocked rather than unimplemented, what is your reasoning for considering them problematic? Thanks!
I think we just don't have the room when we displayed them to properly fit the UI where we wanted to show them, and additionally they tend to often display spoilers regardless so we do a little bit of screening there. The problem isn't totally solved yet, and we need to work on it a bit more.
Michael wrote: "I think we just don't have the room when we displayed them to properly fit the UI where we wanted to show them, and additionally they tend to often display spoilers regardless so we do a little bit..."So it's been a few years now. Has this changed at all? I think spoiler tags in status updates would be a good thing.
Yah this would make the progress update a lot more useful
I think that we have all been told by fate never to see this treasured key, but I don't want to be resigned to look for opportunities. 🙃
Michael wrote: "I think we just don't have the room when we displayed them to properly fit the UI where [...]"Your use of the first person plural suggests you work[ed?] at goodreads; do you have any hints about the quickest way to file UI/UX complaints?
[I hate GitHub and this site killed its API before I even joined the API group...]
