1. Usability & feature‑driven feedback
Users are actively shaping the app’s experience. Requests for font size, keyboard navigation, follow/block, content filtering, and notes dominate the conversation.
“I would love keyboard‑driven navigation!” – numbers
“I need a way to adjust text size.” – IronsideXXVI (reply)
“One feature I'd love to see is to follow/block users.” – putlake
2. Security, privacy and trust in open‑source
Because the app is built from the ground up, many commenters probe its safety and licensing. They ask about ad‑blocking lists, permission scopes, and whether the code can be audited.
“I sympathize with the desire to release programs/code anonymously or semi‑anonymously on the internet.” – big_toast
“I want to know how to trust oj‑hn as a vendor.” – big_toast
“I want to run it in a separate profile.” – latchkey
3. Platform support and the native‑app vs web‑app debate
The discussion frequently turns to which operating systems the app should run on, memory footprints, and why a dedicated app is preferable to a browser tab.
“I don’t have/want a Mac so I can’t really use it.” – ranger_danger
“It uses 85 MB of working memory… not some Electron thing.” – taude
“Why would I want to browse the web in this app as opposed to a web browser?” – luma
These three themes—feature requests, security/trust, and platform/UX debate—capture the bulk of the conversation.