Recent submissions

Comment · 1 month ago
I'm done with Apple. Got rid of my iPhone and back on android (GrapheneOS) and very impresses after playing with Omarchy for a few weeks.

I think we will keep reading more and more of these Apple stories and it feels like shit is getting worse as time goes by

Comment · 2 months ago
What the hell are you talking about? What forbids?

The idea of nostr is that you can do whatever the you like. An open protocol. There is no forbidding of anything

Comment · 4 months ago
Great stuff

I found the bundle scripts already prefer VULKAN_SDK/VULKAN_SDK_ROOT, but the build script only scans ~/VulkanSDK

Comment · 6 months ago
If you want decentralized you need freedom in clients.

There are a lot of pretty good nostr clients: Primal, Amethyst, X21.social, Yakihonne, Nostrudel, Jumble. And most of them are OSS

Comment · 7 months ago
Two things reading this post:

* i'd love to hear a sample/customer call. Even if it's just a test

* a blog without rss? How can i subscribe for part 2?

Comment · 7 months ago
Cool stuff. You should make it OSS and ask a one time fee for it. I would run it on my own infra but pay you once(.com)
Comment · 8 months ago
tmux too.

Trying workmux with claude. Really cool combo

Comment · 8 months ago
Comment · 9 months ago
Prezly | Remote (Europe ±2h CET) | Full-time | https://www.prezly.com

We run a platform that handles story publishing, media delivery and newsroom workflows for hundreds of organizations, with millions of readers hitting it every month. PHP on backend (API's/app), TS/React on frontend.

Hiring: • Senior Backend Engineer (PHP, Symfony, PostgreSQL) • Full-Stack Engineer (React, TypeScript, PHP)

Why join Prezly? • Work on systems that deal with high traffic, large media libraries and evolving data models • Improve and modernize a long-lived PHP codebase without breaking production • Own features end-to-end: database → API → UI → production • Direct line to product and customers, no layers of PMs or process • Profitable, remote-first company with high autonomy

Stack: PHP (Symfony), PostgreSQL, React/TypeScript, Kubernetes on AWS. We actively use AI coding tools like Claude Code and Cursor.

Apply: https://careers.prezly.com

Comment · 10 months ago
Same point as https://news.ycombinator.com/item?id=46282964

Disagree though, people manage keys just fine, or they can be thought.

But even if there are people in the world that never get it, it could be outsourced to a central identity provider that manages your key and messages. For the end user they would have a user/password combo they can reset.

If the network becomes more popular someone will definitely build something like that.

The technical capabilities (remote signers, bunkers, ...) already exist

Comment · 10 months ago
Incorrect.

Everyone can announce to the network where they read/write from. Clients can figure out (based on the people you follow) from which relays to get the content.

I've been using it like this for nearly a year. It works

Comment · 10 months ago
Key difference is that is one relay author becomes "oligarchical" the notes just route around that (through different relays).
Comment · 10 months ago
It doesn't work like that.

Your followers fetch the note from your relays. You tell the network where they can find your notes (self hosted relay) and their client will take the effort to find your content

Comment · 10 months ago
I'm building a Nostr app (+- 2mio notes). There is a lot of spam and much worse content.

But it's kinda a solved problem (not through PoW) but through Web of Trust and not having algorithms. You see what the people/communities you follow post.

> I tried Nostr but like a lot of people here have been saying, it falls short in many ways due to the way it is structured. Relays are not really relays, they are more but also less. They are like community servers. Sure you can connect to many, have the same UI, but they are still disjoint and feels lonely.

I'd like to know more. Imho the fact that relays are dumb is a feature.

> You keep saying you can sign your messages and there is value there to people who are saying it is censorable in the ways they described.

All messages are signed. There is no way NOT to sign a message. This comes with the advantage that you don't need to trust the relays/pipes where messages go through which is an immense benefit

> This is not a personal thing, I want to like Nostr and I tried using it. I can and would probably get some use out of using it as a pubsub or message delivery infrastructure for two things I want to connect but what if the relay goes down? It is like a centralized pubsub messagebox thing. But can't even do that fully.

Relays go down all the time. There was an experiment where a major relay (Damus) just deleted the entire dataset. People barely noticed. And as any client (not just the author) and other relays can re-broadcast events the relay eventually recovers.

> There needs to be some sort of relay to relay communication (actual relaying) that needs to go on. And that wouldn't scale, even if it would work for now.

There are three mechanisms that do that:

- clients posts to multiple relays - clients/followers can rebroadcast notes (to other relays) - quite a few relays are syncing (negentropy sync)

Comment · 10 months ago
I'm building a Q&A/community on top of Nostr and using those same concepts:

Original Author posts a kind:1 note with a question

A bot sends a kind:1985 note (NIP-32 https://github.com/nostr-protocol/nips/blob/master/32.md) that labels the content.

It can be done by the author (self-label), by an app, or by third parties (moderators/curators), depending on the trust model.

Other clients can decide to use that classification/label

--

For moderation purposes. If the behavior is closer to abuse (spam, scams, harassment...), use NIP-56 (Reporting). Reporting harmful/should-be-moderated content.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton