We (HYVOR) are excited to launch two new products today:

Hyvor Post (https://post.hyvor.com): a simple, privacy-first newsletter platform with zero tracking.

Hyvor Relay (https://github.com/hyvor/relay): a self-hosted email delivery service. An alternative to services like AWS SES or Mailgun.

We've been working on these two projects for almost a year, and we are super excited to finally release them.

Our release announcement has more insights: https://hyvor.com/blog/hyvor-post-relay. In short, we first added newsletter features to Hyvor Talk (our commenting system), and it proved to make things complicated. So, we started working on Hyvor Post as a standalone newsletter platform. Then, we could not find an SMTP provider that does not include tracking features and has reasonable pricing - so we built our own: Hyvor Relay.

Both products are open-source under AGPLv3. Hyvor Post is cloud-only at the moment. Hyvor Relay is self-hosted only. Compared to traditional solutions like Postfix, Hyvor Relay makes it very hard to make mistakes when sending emails by having built-in health checks for DKIM, SPF, PTR, a DNS server to automate records, etc. Building Hyvor Relay was a significant undertaking for our small team, and we are very happy that we now have a reasonably stable version. We are also working to release a public cloud version in 2026 to help developers reduce email sending costs significantly.

Our team is around on HN - feel free to ask any questions!

Comments URL: https://news.ycombinator.com/item?id=46106972

Points: 4

# Comments: 0

A simple docker compose up can get a reasonably working setup [1]

[0]https://github.com/hyvor/relay [1]https://relay.hyvor.com/hosting/deploy-easy

We are currently running beta tests (really appreciate it if you can join).

[0] https://github.com/hyvor/relay

[1] https://github.com/hyvor/relay

For us, we found ourselves repeating again and again when we had multiple UI projects. It became boring and we decided to write the design system. It took us about 3-4 months to complete this.

- It takes a LOT of effort to migrate old projects. A LOT! So, make sure you really have the time and effort for a migration like that.

- In my opinion, it only makes sense to have a component library if you have multiple different projects / repos.

- Try not to reinvent the wheel. Design your components library, but follow a pattern of a popular library so you can see "hey if you have used this library, it's the same here. Just the UI is different"

- Write an extensive documentation with examples (here's ours: [1])

- In our case, integrating dark mode, docs, and i18n into the design system (in an opinionated way) saved us a lot of time.

[0] https://github.com/hyvor/design [1] https://hyvor-design.pages.dev

We initially used Redis because, well, Laravel recommends it. But, what I learned is that Redis is not a requirement until you absolutely need it.

Comments URL: https://news.ycombinator.com/item?id=39259522

Points: 2

# Comments: 0

[0] https://blogs.hyvor.com

Also, this subreddit has many information and anecdotal experience on this technique: https://www.reddit.com/r/CureAphantasia/

I have seen some shapes and a few colors for now. Most importantly, I have started to see vivid dreams in the last few days, which has never happened before (before that it was just a feeling not a visual. However, my father suggested this might just be that I have learned to remember dreams more by becoming more conscious about it, which is a possibility). It's too soon to judge. So, I'll keep doing it for a couple more weeks to see if it can help me see visuals rather than random flashes.

The article mentions Image Streaming, which I've been practising since. Interestingly, it seems to work! I've have been seeing vivid dreams, and have been able to randomly visualize shapes. Nothing to prove it "cures" aphantasia, but we'll see :)

This is absolutely true. I have been confused many times figuring out what are reactive states and what are not.

I never knew Svelte needs changes like this, but seeing this, it sounds like a good plan.

CPU Usage:

with NGINX - 15-20% with Caddy - 70-80%

I tried multiple tweaks but nothing helped to get NGINX-level performance. So, after a few weeks, we migrated back to NGINX.

That being said, I still absolutely love Caddy and use it in a few small scale apps.

- The DX it provides is amazing. - Creating a PHP-FPM reverse proxy is just a couple of lines. - Generating SSL certificates on the server is a breeze. With NGINX, you have to mess with other software like certbot. - It just works :)

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?

The installation code has two parts: