Show HN: I made yet another UI to browse HN(hn.sayan.page) Primarily built this to learn how NextJS works and also a bit about Tailwind CSS.
Also has request caching using the WebCache API + expiration which is quite a hacky implementation. Let me know what you think! Source is at https://github.com/say4n/hn, pull requests welcome! |
Also Octal has some weird bugs like not removing the downvote button after 24 hours so you just get an odd error when you click it. And the thing that bugs me the most where if you swipe back then change your mind you can’t swipe forward to go back to the comment thread you were on (a la Apollo, RIP). What makes it worse is swiping “forward” changes the “tab” you are on losing your scroll place in the list of HN posts. My muscle memory will never stop doing this though.
It’s a pretty bad app unless you’re just reading. I assume the developer never touched it again after deploying it which wouldn’t be an issue if you didn’t have to pay to unlock comment writing (its worst implemented feature).
Thanks... I see nothing. Next is really doing well, eh.
I wanted to do it all locally / serverless but I struggled to find a good client friendly library for parsing meta tags that was 0 deps and typed so I wound up making a cloudflare worker to bypass cors and manually streamed the html to extract and parse the head element with a bit of regex and elbow grease.
It worked out, but I wish the HN api would cache and provide that stuff once to save the authors from the extra load of all the clients like mine that need to make extra requests to each articles home page.
Standard privacy settings in Firefox.
React error claims to be "Objects are not valid as a React child (found: [missing argument]). If you meant to render a collection of children, use an array instead."
Probably useless information... looks to die in the hydration of the page. There's a flash of the HN header and "Loading..." before it dies.
What prevented you from fetching the top stories and caching on the server? Couldn't the server render the react components for all pages/comments? Why does it even need to run anything client side?
Page doesn't do anything useful with JS disabled.. you should be able to at least render the stories/comments/etc.