@cory Getting people to click through to my site—and read the latest version of the post, and check out the other parts of the site that aren't part of the feed—is the end goal, though?
@convexer @cory It might be! If that is your end goal, then you probably fall into the category I mentioned where you have a good reason to not provide full text.
For me personally as a blogger who is not selling anything or running any ads on the site, there's no extra benefit of driving traffic to the site. When I write a blog post, I hope that post itself sparks inspiration, is educational or entertaining or gives the reader something worth their time - no matter where or how they read it.
@convexer @cory I also believe that providing the full text will in the long run end up leading more people to visit your site every now and then because they find your writing valuable and may want to see what else there is.
Getting someone to visit the site because they want to is a much better starting point than having them do it because they must.
@hamatti @cory It's not about ads or money (my goals are similar to yours, in fact), but about the integrity of my writing and image. My posts have a lot of katex, code, and formatting that *will* break in common RSS readers. I also don't want people reading cached copies of posts that I have updated with better information.
@cory @convexer A friend built these nice progressive enhancements for code examples a few years back: https://fotis.xyz/posts/resilient-code-examples/
The code blocks are readable in RSS and print styles but on the web, can be turned into interactive CodePen sessions.
I think those are really cool.