Show HN: Hyvor Talk v3 – Privacy-first commenting platform
talk.hyvor.comWe've just released version 3 of Hyvor Talk, a privacy-first, fully-featured commenting system.
Some highlights of the new version
- We re-wrote the embed from scratch. We now use Web Components instead of iframes. - In-built dark mode support - Page-level configurations - APIs for moderation and public data - Paid memberships feature
We are 2 founders, and a small part-time team. We currently handle 100 million+ pageviews per month with 20 million+ unique monthly users on about 8000 online communities/websites.
I am happy to answer any questions :)
Thank you. This is actually really interesting that you switched over to using Web Components instead. Makes total sense for performance and other reasons, of course. But does this basically mean that you now provide the entirety of the code to users? This includes HTML and JS, since it now lives entirely on the host site, easily accessible to the developers of the host site. Is this something that was discussed and was eventually agreed upon? I would be curious to learn why it was ultimately decided that you are OK with users having the raw HTML and JS code that powers your product. Furthermore, it also makes it more difficult for users to receive UI updates. If there is an important bug fix or enhancement, users would need to upgrade to the latest HTML/JS "package" that controls the web component, correct? Of course with an iframe, any updates are seen immediately on the user side. Curious to hear your thoughts! Hey! Great question. The installation code has two parts: <script> that registers the element
<hyvor-talk-comments> element in the place user needs to load comments The script is hosted in our servers so we can push updates anytime we want. I hope that makes sense? (Our installation guide: https://talk.hyvor.com/docs/install) Good point, I guess that’s true. So regarding your users being able to see your raw JS? What helped that decision be made? I assume that since it’s not your actual React code that makes it a bit better? Sorta? Not sure if I understood the questions. In both iframes and Web Components, a Javascript code (Preact in our case) rendered the comments element, there is no much difference. Maybe we are not on the same page? No I think you are right. I guess in this regard it really is not so different after all. Thank you for your responses, I will definitely think about migrating over from the iframe I am using. This is a very useful and cool commenting platform but is a bit pricey, a plan from 2,3$/months for something like 10,000 pages/months would fits better for more people who don't have 100,000 pages/months view.