I've created an issue over at libHN, but should we consider a libHN fork to implement support for the new official HN API? If we do a fork, we should modify it so the XPaths aren't statically coded into the library but rather fetched periodically from Github so we can update them without needing to re-submit the app. Will be valuable when/if HN starts making lots of rendering changes like they say they plan to in their official API announcement post.
I've created an issue over at libHN, but should we consider a libHN fork to implement support for the new official HN API? If we do a fork, we should modify it so the XPaths aren't statically coded into the library but rather fetched periodically from Github so we can update them without needing to re-submit the app. Will be valuable when/if HN starts making lots of rendering changes like they say they plan to in their official API announcement post.