This may work simply because it is self-policing, since self-submiting on a topic in a gray area would risk hell-banning. I am curious if you ever choose not to exercise the outsourcing for a post that wouldn't be of interest.
Related discussions as to why people prefer HN as their commenting system here: http://news.ycombinator.com/item?id=5247226
I did not take the description to mean that every post would have a link to "comment on HN" connected to a pre-spun-up HN post. (And, with HN's relatively recent changes to headers to disallow framing  in compliant browsers, there won't be any framed HN threads.)
I think that for the latter to occur (as opposed to not -- the current situation), would very likely go against the management wishes and objectives of HN. For several reasons: Relevance (or not); the ban on excessive self-promotion; the implications for HN should this become at all widespread.
TL;DR: HN is not Discus, and per my reading of OP, raganwald is not treating it like Discus, so all's fine.
 Last I checked, HN is now setting X-Frame-Options to "deny". Or, they have been, and I noticed more recently when it started borking a client-side extension I was using.
Only then do I add a link back to HN, not a frame of some kind.
If my blog was a magazine, I wouldn't want to drag people into my home office to read it and discuss it, I want them to take the magazine to their book club and read it and discuss it there.
 - http://worrydream.com/MagicInk/#p72
Alternatively, people could provide a link back to the place in the essay and use the :target CSS selector to highlight the footnote link to make finding their place easier.
Edit: also, the return link from a footnote hides the footnote behind the header. I'll point out, though, that overall the theme looks very good and I like the idea. I'll probably do something similar in my own migration away from Posterous.
What prevents me from putting a CNAME file with that in my own repo, out of curiosity?
But all I'm getting at http://oscin.es is a 404.
I can see it works for you, not sure why it doesn't for me.
UPDATE: Now it's working! Ok, I need to update my blog post. Thanks!
I feel like the web has moved away from feed consuming and more towards consuming content curated through social networking (think Twitter or HN).
Still I do believe some sort of API is in order, so I now mostly implement dynamic JSON output. It's not standard, but at least I don't have to deal with XML.
it’s a win for everyone if the comments praising my writing are alongside
those pointing out where it could me, um, “even better.”