Does this implementation really require this robust of infra / setup?
The entire stack feels overkill for a repo that has 2 followers and 29 stars.
I also am probably not the target demographic though, I just download things that I want to preserve and completely forget about them in a folder called 0_archive.
I just feel like in 2013 some fella would have had this project running on an old laptop in his garage hooked up to FTP and the uptime would be comparable.
I also love when AI adds tidbits like this:
> and staging has to pass before prod deploys.
Thanks for the clarity on that, Claude, you read my mind.
I don't think so. I have lieer + notmuch setup with a few AI generated Python scripts that will mark things as read. It also took about 5 minutes of fiddling with notmuch cli and jq to extract SNS message bodies from emails (for instance).
I think a thin layer on notmuch would get you pretty close without so much infrastructure.
On the web scraping side, scrapling seems to pretty much just work. There hasn't been a website yet it won't load in some mode--even Google SERP.
NichoPaolucci · · focus · HN ↗
The entire stack feels overkill for a repo that has 2 followers and 29 stars.
I also am probably not the target demographic though, I just download things that I want to preserve and completely forget about them in a folder called 0_archive.
I just feel like in 2013 some fella would have had this project running on an old laptop in his garage hooked up to FTP and the uptime would be comparable.
I also love when AI adds tidbits like this:
> and staging has to pass before prod deploys.
Thanks for the clarity on that, Claude, you read my mind.
nijave · · focus · HN ↗
I think a thin layer on notmuch would get you pretty close without so much infrastructure.
On the web scraping side, scrapling seems to pretty much just work. There hasn't been a website yet it won't load in some mode--even Google SERP.