npub1qm…azvlp

"62b9408a6296d32cbc708a96175f07b538b08c0e3fea05d7e2f25251a47602dd018b39c148ba74a4c40e84595272e88c679993201ccf164795a5ef63b8bd3847"

Last Notes

2026-08-18 16:22:32 UTC

- reply

It's easy to start but gets hard with too many stuff to add, even though I'm trying to keep it minimal.
Still on a local server, I plan to publish as an nsyte for others to use, tried it before and it was buggy but I think it got updated recently.
There is also Tauri to package for desktop/mobile, should be simple but I haven't used it before.

2026-08-18 00:44:30 UTC

- reply

I haven't checked on Primal for a long time, I mean specifically their caching server, I know they also require an email for a wallet, it is a complied version of Nostr, or a platform that happens to use Nostr as you said, it is a business and I'm totally fine with that, but I will never be their user.
Some users will only want to use something like that, and at the end of the day they still own their keys and can always just use another client.
Building my own client too, fully client side and will not use a special server, has to be smart because relays are dumb.

2026-08-17 15:57:34 UTC

- reply

😂

2026-08-17 15:32:44 UTC

- reply

Your handle is familiar from Reddit 👋
If Nostr is a Twitter alternative = public square, by design it will have all the noise and the stuff you don't like, not everyone will want to deal with that, clients will have different ways for content moderation.
It's nothing like primal but I mean it is a different form of content moderation, Primal moderates content for its users, you can always use another client, the suggested feature moderates content for everyone on the network by thread author, clients that want to keep it public and not follow the author's moderation imposed on everyone can find other ways to solve this and find more content, but no guarantee as we don't know where to look. so Primal is better in that sense, at least it doesn't fight network effects.
I'm not against moderation as long normal users are aware what is going on. and this looks more a single user problem who decided to only use closed relays and keep themselves out of the public. users just should be aware of the fact.

2026-08-16 16:52:20 UTC

- reply

I don't like it but it's optional so I guess it's fine if someone wants to use that.
It's filtration, like Primal caching server, but instead of a client filtering for all its users, it is a user filtering for everyone, worse than a caching server.
Now clients that want to keep it public will have to do much more work to find all replies to that user's notes, pull from our follow list, check on every relay we know about, but that is too much for a client, it would then be easier to detect these type of users from their relay list and just add a notice for our users "NOT PUBLIC, this user controls what you can see", because the client will not go all over the world looking for replies on a thread when the author doesn't use any public relays.
a client can always have other comment sections, from the people I follow or some other relays, but we still need to detect these type of users as they are not on the public side and they won't see our replies.
but I'm happy for fiatjaf and anyone who will apply this.

2026-08-15 15:59:24 UTC

- reply

Maybe you are correct, but I take it for a fact that most people will use a client and never run their own relays, so client-side would be the only option.
Clients can set their own limits not to handle thousands of comments and mentions, use helpers like PoW, and if user doesn't want to see random public keys it would only show from follows and follows of follows.

2026-08-15 15:15:28 UTC

- reply

this is correct if the client only reads from the author's relays, it should pull from other relays to prevent the author from controlling what you see, but then also you will never know where these comments are.

2026-08-15 14:57:15 UTC

- reply

bbut there is no "inbox" marker at NIP-65 https://github.com/nostr-protocol/nips/blob/master/65.md

2026-08-13 19:03:20 UTC

🙂

2026-08-13 19:00:45 UTC

- reply

2026-08-13 18:38:48 UTC

- reply

eee

2026-08-13 15:20:57 UTC

hello