Um, that's exactly what I meant. A post stops being available via RSS the second the security level changes to any of the non-public choices and upon locking, the entry disappears from the source feed (unless you're logged in/authenticated as someone with permission to see it) are roughly equal statements.

Also, there is no known way to prevent RSS from allowing anyone [should have also said "any spider/any search engine"] to scrape your public posts (at least, not on DW) except to not post publicly is again roughly equivalent to that does nothing about the remote site keeping a copy cached.

If you post publicly, and if your DW is set to be spidered by search engines, the post can and likely will be cached. Changing security status on said post will remove DW's public RSS feed for it immediately but will not have any effect on third party actions already taken (screen shots, screen scrapes, search engine caches, manual re-postings; all stay in place anywhere from some time afterward to indefinitely).

So yeah, I could've/probably should've been a little more precise, but it seems we're pretty much on the same page.