See also: https://phoboslab.org/log/2023/02/qoa-time-domain-audio-comp...
Readit NewsDeleted Comment
ers35 commented on The Quite OK Audio Format [pdf] qoaformat.org/qoa-specifi... · Posted by u/agencies
Maybe Cosmopolitan could be used with luastatic[1] to compile a Lua program to an "Actually Portable Executable":
CC="" luastatic main.lua
# Compile main.luastatic.c with Cosmopolitan Libc
ers35 commented on A prerecorded message from Richard Stallman peertube.qtg.fr/videos/wa... · Posted by u/billyjobob
Mirror: http://archive.is/ewDJq
Don’t forget to include the basics - upvote, downvote, unvote, comment, submit, save submission, save comment - and have all that sync when reconnecting to internet.
I've been focusing on reading, but it looks like there is interest in writing too. The HN API doesn't support writing, so the username and password has to be stored. It's important that reading keeps working even if HN changes their backend in a way that breaks writing. I'll think about it.
The query api at: https://hn.algolia.com is pretty amazing, searches all stories.
The biggest qualms for me would be; notifications of comments and searching my previous comments.
Other than that Hacker News is actually highly reliable and available and I've never personally needed an off-line version (except maybe on a plane)
You can search previous comments: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
What is your use case for this server that makes optimizing for LAN vs WAN latency a valuable outcome? I’ve never really noticed that latency in email clients or when using the HN website and so I’m curious what is unique to your specific scenario that makes it a priority.
(This isn’t criticism, but I definitely don’t understand why it’s a criteria in your case yet.)
HN itself is fast, but the comparison I'm making is with readers that use the HN API. See how getting each comment requires an additional API request: https://hacker-news.firebaseio.com/v0/item/22481199.json?pri...
It's more about the consistency of operating on data local to the user. For example, see this comment referencing how HN paginates threads at 250 comments for performance reasons: https://news.ycombinator.com/item?id=22231055 A local database does not have that issue.
To clarify, why is “self-hosted” an important criteria to you?
There have been many HN related websites posted over the years, but a lot end up as dead links. A self-hosted version does not depend on a third party. Another reason is to minimize the round trip latency of contacting a central server. Consider users without a good connection to the server.
Suggest considering implementing a bridge to NNTP, or SMTP mail spools. Then use offline NTTP or mail readers.
That reminds me of how https://forum.dlang.org works: https://github.com/CyberShadow/DFeed It also uses SQLite.