Appreciate you being one of our first paid users 💜

And yeah, if you run into any bugs, friction, or missing workflows while using it, feel free to mention them. Real usage tends to expose things fast.

By default hashtags are shown in the post itself, but we also support metadata-only hashtags via a toggle.

Most Nostr clients (except Amethyst) currently don’t render metadata-only tags visually, though the posts still appear in hashtag searches.

Nostr-first is the important part.

Optional cross-posting to legacy social media may come later, but the core product direction remains deeply Nostr-native.

Appreciate you stress-testing this feature early 🫡
Still rough around the edges, but seeing real sats move through Nostr-native giveaway flows is already pretty exciting.
More improvements coming.

Hope it ends up being useful for your setup 🫡

Because it lets you stay consistent without needing to be online all the time.

It also lets you spread out your output across better posting times instead of dumping everything at once whenever you happen to be active.

Especially useful for media pages, brands, writers, researchers, meme accounts, etc.

Yeah, pretty much.

Users sign events upfront, we store them, then publish them at the scheduled time.

The interesting part is the workflow layer on top - things like Queues, where you define posting rules once and then just drop content in. Posts automatically get assigned times, so you’re building a publishing system instead of manually scheduling every post.

Exacto. Automation should protect consistency, not replace authenticity.

No lies detected.

NIP-46 on iOS has been one of the bigger UX bottlenecks in the ecosystem. If Clave nails reliability here, a lot of products downstream benefit. Respect.