niux

This very likely is against Cloudflare ToS

Wow this looks very sexy, thank you

Not a single example of what it does or how it works

The self-hosting solution is completely crippled, everything is paywalled. At this point, might as well go closed source.

Probably the commit history.

Have fun dodging that minefield when distributing your app.

With the insane licensing costs, I fail to see how this is still a viable choice for personal / small projects. Also, for larger projects, assuming you can afford the costs, the reality is that it's really hard to find decent Qt developers.

The admin panel requires an email and a password to check out.

It appears to have a fatal flaw: you can't actually save and restore your data, just export it to PNG.

This article is an oversimplification describing basic forms, but as soon as you try to implement any sort of advanced validation using just HTML, the whole paradigm falls apart. Browsers support JavaScript for a reason.

I thought some people might find this useful. It looks like this: https://share.cleanshot.com/4Fj7wLH9

Example: https://i.imgur.com/vNEIaUI.png

I actually use Dokploy in production, you have to literally press just one button to redeploy using the latest version of your app, straight from the repo.

What platform are you using?

Just install Bypass Paywalls Clean extension. This is the author: https://x.com/Magnolia1234B

Why not add a boolean flag and use a single exit(1) at the end? That way the user can see all the environment variables that have not been set.

I'm wondering if we'll ever reach a point where the differences you listed truly become indistinguishable.

Claude Code can also do that if you pair it with the VS Code extension.

How is it more expensive?

How might you inadvertently download illegal content while searching for legal content?

I primarily use Logseq because I've found that outliners best align with my mental model. I mainly take notes within my daily journal. When I encounter something worth saving, I simply create a new entry. A typical day looks like this: https://i.imgur.com/wAiYgSY.png

To categorize the information, I simply link the entry to a specific page. For example, if I discover an interesting React library, I create a new entry like this: https://i.imgur.com/dDlStkZ.png

A great feature is that Logseq understands page hierarchies, so if I click on [[Dev/JS]], it presents a clear hierarchical overview: https://i.imgur.com/z9hGmmh.png

Using this approach, I've stopped bookmarking sites in my browser altogether. In Logseq, I can connect useful things to each other, add entire notes, and more, as shown here: https://i.imgur.com/Krld2cS.png

If I want to remember something, I just add a #card tag to the block, and it automatically syncs with Anki via a plugin.

The reason I wrote my own tool is because I couldn't find anything for Pg17 at the time and pgbackrest seemed overkill for my needs. Also, the CLI handles backup rotations as well. Barman looks interesting though, I'll definitely have a look, thanks!

I recently deployed Postgres on a dedicated Hetzner EX-44 server (20 cores, 64GB RAM, 2x 512GB NVMe SSDs in RAID 1) for €39/month. The price-to-performance ratio is exceptional, providing enterprise-level capacity at a fraction of typical cloud costs.

For security, I implemented TailScale which adds only ~5ms of latency while completely eliminating public network exposure - a worthwhile tradeoff for the significant security benefits.

My optimization approach includes:

- Workload-specific configuration generated via PGTune (https://pgtune.leopard.in.ua/)

- Real-time performance monitoring with PgHero for identifying bottlenecks

- Automated VACUUM ANALYZE operations scheduled via pgcron targeting write-heavy tables, which prevents performance degradation and helps me sleep soundly

- A custom CLI utility I built for ZSTD-compressed backups that achieves impressive compression ratios while maintaining high throughput, with automatic S3 uploading: https://github.com/overflowy/pgbackup

This setup has been remarkably stable and performant, handling our workloads with substantial headroom for growth.

Not anymore, since the Typescript compiler has been re-written... in Go.

Can't you use another port to send emails?

Funnily, I released something similar two weeks ago with more targeted decorators (sync vs async), a more strict `Err` type and a less verbose type guard (`ok`):

https://github.com/overflowy/safe-result

Not a single screenshot - I really have no idea what this is doing aside from being a repo filled with buzz words.