I guess your point is if this idea is implemented, posts in question could be set on the server side to not be crawled/indexed/cached and/or for the public RSS feeds to be disabled before posting (no user action required, default post behavior, strictly unchangeable). And those are pretty intuitive add-on features to expect, so good point. But none of that stops screen caps, screen scrapers, or reposters from reposting, and so on. Privacy leak capability? Still huge. An access time-bombed post can *behave* like a normal access-limited post right out of the gate as far as behind-the-scenes security features go, but it cannot actually be one while its security is set to public. So even if DW did implement the idea exactly the way you might envision it, that still does nothing to ensure enhanced front-end security while the post is living its shortened public life out there for all to see.