Love the summaries, I must say some stories I haven't considered interesting seeing them in the original HN view only caught my attention after my eyes landed on the summary.
At the same time, I very much dislike the layout. Masonry-style layouts, at least to me, feel more "artsy" than practical. Multiple rows being displayed at once, with the most crucial information being chaotically all over the place instead of arranged in a way that makes it easy to scan it with your eyes, make me feel like I'm bombarded with information. It's very hard to follow along and very easy to miss articles; almost anxiety-inducing, even. There's hardly any point to this on a website; it's not like you're wasting any paper.
The inception effect here is hilarious. Watching this get its own front page while the subtitle lags behind with the previous top posts is weirdly funny.
I whipped up a quick uBO rule to fix that (also makes meta-information lines readable):
thefrontpage.dev##p.newspaper-copy:style(line-height: normal !important; font-size: 1rem !important;)
thefrontpage.dev##p.article-meta:style(font-size: 1rem !important; font-weight: normal !important; letter-spacing: normal !important;)
I agree, but I think it's that small because otherwise, the justified text results in ridiculous spacing.
OP, consider reducing the number of columns from 4 to 3 (at least below very wide viewports), increasing the font size, and then also allowing hyphenation. I think the last will help a lot with the justification problem.
I love it! I discovered it'll switch to a 3 column view if I take the zoom to 200%, I'd maybe prefer it at less but it's a bit tricky to guess if that's true or not. Regardless, it's very nice. And infinite scroll for the hackernews feed is a bonus!
This is great )) maybe do random templates similar to newspapers (like photo on the left, photo on the right, one block full width, then 3 columns, etc).
Using text-align: justify for questionable aesthetic purpose here really hurts readability, especially on a narrower viewport like the 1026px viewport of Safari with sidebar on an iPad Pro 12.9’’ (although it’s probably more of a problem of the four column layout on that specific narrow viewport; three should be better).
Could you explain in more detail how this works? Would it break for paywalled articles that HN links to? (Usually someone posts a workaround archive link in the comments, but your AI probably doesn’t account for that, right?)
I’m writing something similar to Moltbook for HN where AIs browse HN’s front page and leave comments. But I wasn’t sure whether AIs could reliably browse an arbitrary website. (Paywalls would break it, as just one example.)
But it seems like your AI works fine for all the sites. If you have time to explain, what exactly do you do to generate your summaries? Thanks!
EDIT: I see that sometimes your summaries fail, e.g. “Ferrari Luce - Summary not available.” It looks like it fails because it’s a JS heavy site. But I was thinking a headless browser could take screenshots of the page and then feed the screenshots to AI. I’m not sure how practical that is to implement though.
Some of them are really large and I'm not resizing them or storing them, just proxying their og image directly. So they might be taking long to respond from the original source. Also getting hammerred by being in the front page.
At the same time, I very much dislike the layout. Masonry-style layouts, at least to me, feel more "artsy" than practical. Multiple rows being displayed at once, with the most crucial information being chaotically all over the place instead of arranged in a way that makes it easy to scan it with your eyes, make me feel like I'm bombarded with information. It's very hard to follow along and very easy to miss articles; almost anxiety-inducing, even. There's hardly any point to this on a website; it's not like you're wasting any paper.
And it’s fucking perfect.
OP, consider reducing the number of columns from 4 to 3 (at least below very wide viewports), increasing the font size, and then also allowing hyphenation. I think the last will help a lot with the justification problem.
The formatting, etc looks all nice, but it's not worth reading.
I’m writing something similar to Moltbook for HN where AIs browse HN’s front page and leave comments. But I wasn’t sure whether AIs could reliably browse an arbitrary website. (Paywalls would break it, as just one example.)
But it seems like your AI works fine for all the sites. If you have time to explain, what exactly do you do to generate your summaries? Thanks!
EDIT: I see that sometimes your summaries fail, e.g. “Ferrari Luce - Summary not available.” It looks like it fails because it’s a JS heavy site. But I was thinking a headless browser could take screenshots of the page and then feed the screenshots to AI. I’m not sure how practical that is to implement though.
This would make it easier to read