In (non first party) RSS clients, such as unread or reeder, even though I have disabled story revisions they still show crossed out words. Is this something they have to implement through the api, or should disabling story revisions on the web, also disable them in the api?
2 Likes
Any guidance on this issue?
Ah yes, this is a known issue with third-party clients. Right now story revisions are handled client-side, which is a bit unfortunate for clients like Reeder or Unread or ReadKit. They need to add a preference for the CSS required. It’s next to no work, but they haven’t really done it.
I could add it server-side, but that would require a bit of finagling. I’d be happy to do it, provided some more people vote on this thread.
If you’d like to see this happen, just make a mention here and I’ll integrate it. It’s not trivial but I think there might be a way.
I’d really like to see this implemented. There are issues which keep me from using the native NewsBlur app, so I use Reeder, and the revisions can really be annoying.
Yep, since I brought it up +1 here. 
This change launched today. Thank you so much!!
Yes, this finally launched. It took a bit more finagling but I got it done and now all clients can request the fully marked up story revision based on a story flag, as the web now does.