Niel Liesmons

Still fleshing the details of that standard. Specifically the moderation part 👉 giving different "lists" of profiles different write access in different content sections (still seeing what architecture works best for this, lists, atomic events, custom relays thing, ...)

2026-05-05 06:58:28 CEST

- reply

Asking nicely doesn't work on an open protocol.
Better way is to reference your targeted audience specifically (h tags for communities for example).
Then besides publishing to the community relays, you can blast your events out to whatever other relays want to accept it. Doesn't matter, and is probably even wanted by most creators, since the event is pointing to where the activity around the event is happening anyway.

2026-05-05 06:49:52 CEST

- reply

It's almost as if React was made by and for big tech social :padme:

2026-05-04 21:43:39 CEST

Things people notice about your apps:
- They're slow af
- They're ugly (and don't have a coherent design system)
- There's no team behind them (that they can interact with)

2026-05-04 20:14:33 CEST

- reply

Interesting!
The whole space lingo is huge turn-off for me though. Takes me ages to see beyond those terms and see their actual architecture for what it is.
Design language also doesn't resonate with me. Too bad

2026-05-04 11:55:40 CEST

Blue Notes And Other Stuff :chad_headset: #drumstr
https://youtu.be/CdgzmGcO5k4

2026-05-04 10:04:22 CEST

- reply

Ain't nobody setting up different app-only relays, much less creating them.
Without communities, we remain the de-facto "centralized app platform" on Nostr. Nobody wants us in that position, ourselves very much included.

2026-05-04 10:00:50 CEST

- reply

Moving from Platform → Communities.

2026-05-03 21:10:49 CEST

For my Nostr publications, I want to target different ones to different (sets of) communities. Not ALL of them to the same exact set of #outbox relays, that apps keep bullying me into defining.
I don't want to see every fart you make on Nostr, and you don't want to "follow" all of mine.
For my inbox, I don't want it all in the same feed neither. That's taking the worst part about email and adding alerts for emoji reactions in there too, on ANY of my Nostr events 🤦‍♂.
It's a set up that can't scale beyond one use case (twitter clone) and is why all #otherstuff apps have broken (or just zero) notifications, and in turn break the ones of the twitter clones it all started with.
Proactive steps:
- Target / Filter by communities, first.
- By content type, second.
- Have communities set up in a way that they have a main relay, so you can use those relays as the scope for publishing and notifications.

2026-05-02 19:10:43 CEST

- reply

On it...

2026-05-02 09:12:15 CEST

- reply

Step 1: add emoji tags :wisp_lol:

2026-05-01 15:22:23 CEST

- reply

Have you guys looked into building on top of NewPipe and similar?
That's what I'd do.
Fork, make sexy, add Nostr social interactions, integrate moderated communities.

2026-04-30 20:41:23 CEST

- reply

Latest:
https://www.chateau.community/wiki/naddr1qvzqqqrcvgpzqesd33ux28msfplvnwxac2p7988j2ctf8hdrhgjx607nczxmkuyrqqx8xarjd9hxwttrdakx7usdljg6f
#naddr1qv…jg6f
Wrote this last year too:
#naddr1qv…8fyd
Implementations are live in Zapstore and Wisp:
https://github.com/zapstore/webapp/blob/main/src/lib/utils/color.js
I tried this existing standard too but don't find the colors work well enough:
https://xmpp.org/extensions/xep-0392.html

2026-04-29 11:28:28 CEST

- reply

Yup, I use my same scheme for file extension too: https://i.nostr.build/kgfxrBgytDVjNNrK.png
(don't think this pic is the actual coded output, but you get the gist)

2026-04-29 11:06:42 CEST

- reply

These profile colors, they are string-derived (npub) so other apps (like Wisp) show the exact same ones:
https://i.nostr.build/9YTEZkQaNWlCYkH1.png
And yes, that's designer nerd level 100, oops.

2026-04-29 10:45:22 CEST

- reply

Ok, I tried this and the colors are worse and more ugly and inconsistent than my method. Too bad.

2026-04-29 10:29:51 CEST

- reply

Fok me. There's the standard for interop string-based colors I couldn't find before (so I created my own 🤦‍♂):
https://xmpp.org/extensions/xep-0392.html#algorithm-angle

2026-04-29 10:25:01 CEST

- reply

Too many good people with bad marketing and ugly sites/apps :PepeHands:

2026-04-29 09:42:29 CEST

- reply

Never heard of Delta Chat. Interesting :wisp_eyes: .

2026-04-29 09:40:00 CEST

Open file format for Figma-type design boards, in JSON:
https://docs.pencil.dev/for-developers/the-pen-format#overview
If you wanna do :white_board: whiteboarrds in Nostr events, this might be worth looking into.
#UI #nostrdesign

2026-04-28 20:26:08 CEST

- reply

Make the group ID a keypair. Solved.
While at it, remove junk and add transparency (for moderation and content types the group handles) from the spec.

2026-04-27 14:48:28 CEST

- reply

Lol, same :wisp_lol:

2026-04-26 16:59:20 CEST

- reply

Pretty diverse gene pool so it'll vary spending on the nut sown.
6 years to never 😉.

2026-04-26 16:56:17 CEST

- reply

Bunch of bisexual hermaphrodites with huge nuts that had a party on a local orchard 😉.

2026-04-26 16:11:35 CEST

Running Castanea spp. #farmstr
https://i.nostr.build/luUutiEOMDb97qHA.jpg

2026-04-26 14:59:42 CEST

Running Castanea #farmstr https://@npub149p…722q.blossom.band/3c1598e53acd870d4f96c4422de0b9dfc4f73f557016d611e280e88c2ff8372a.jpg

2026-04-25 22:17:13 CEST

- reply

🫂

2026-04-25 15:04:33 CEST

- reply

Have you expanded somewhere on why it's not local-first? And how that would be slower or not? Curious.

2026-04-23 15:07:20 CEST

- reply

Riiight, and ain't nobody liking prisoners of war much, so we're good!

2026-04-23 15:04:51 CEST

- reply

Wait, you don't get this? :wisp_eyes:
https://i.nostr.build/Yz45TOytlGcvjAOO.png

2026-04-23 15:01:22 CEST

You know what normies see when they go look up POW, right? :padme:
Friendly reminder to not show "POW 16" or stuff like that in your UIs.

2026-04-22 13:37:39 CEST

- reply

Northern europe does allow this so well.
If we'd still be in Belgium (and not on a farm in middle of nowhere in France) we'd not have a car, easy.

2026-04-22 11:53:41 CEST

- reply

GM :wisp_pug:

2026-04-22 11:53:04 CEST

- reply

I do still (maybe naively) think I can get a #goodenough UX to work with Frost shares.
Send a share to Gmail/iCloud, one to your projects server and keep one (or two) in mobile app. There's sth to be done there that's at least less worse than the current Nostr key solutions. But it's probable you are right in the end and I'll end up agreeing with you as time goes by.

2026-04-22 10:39:38 CEST

- reply

I tried many things for keys too. Definitely fun!
https://i.nostr.build/XtioDIh71BvNlVhm.png

2026-04-21 10:13:46 CEST

- reply

What's your account?

2026-04-20 15:31:38 CEST

- reply

Just added to ZS :Check:.
As well as landscape image display for your uber-wide marketing shot :wisp_lol:
https://i.nostr.build/LWUqsaqVgOnpsP3d.png
(will all come to mobile too)

2026-04-19 20:49:29 CEST

- reply

forums ftw :forum:

2026-04-19 20:11:51 CEST

- reply

Name one npub that knows stuff about making great products :wisp_lol:

2026-04-19 20:11:01 CEST

- reply

What business then?
Or bitrefill job?

2026-04-19 16:11:01 CEST

- reply

Lol 😅

2026-04-19 10:09:07 CEST

- reply

Chicks needs safe spaces, not a public square.

2026-04-18 09:34:54 CEST

- reply

Wtf Jumble!? That's not at all how I typed it :wisp_lol:

2026-04-18 09:33:43 CEST

- reply

Dudes:
1. You have details available for the comments. Sorry if I don't push them in normies faces. Not every app can be Grimoire.
https://i.nostr.build/NcsChbknW7pTOT4w.png
2. I'll add bunker login on Monday. It has not been a priority, but it's too easy to add so yes, my bad. ( you're the first to even ask for it tho, fj).
Bigger leverage point is gonna be the normie friendly onboarding we're cooking.
3. You'll have a full dev dashboard next week with an inbox of all comments and zaps, analytics, ...
4. All comments and zaps are already being published to the Zapstore community relay + your outbox on webapp. Mobile app will do that too.

2026-04-17 10:22:27 CEST

- reply

PS: @npub107j…ncxg this idea of yours would even allow you to have super chats in Nip-29.

2026-04-17 10:20:15 CEST

I think just putting a "z" tag in comments and chat messages is the best solution for #zapversations.
The tag references the payment proof, which can be a lightning zap, fiat payment, ecash, ... And you can suffix the amount and currency in the same tag.
That gives apps the ability to fetch full comment threads and chat feeds FAST and render the zap-comments and messages optimistically.

2026-04-16 16:47:49 CEST

- reply

Beast :wisp_lazor:

2026-04-16 12:48:49 CEST

- reply

Lmao, true story :wisp_sad:

2026-04-16 10:49:04 CEST

- reply

It is. Carnal mind take-over, getting high on my own supply of :AirQuoteLeft: genius :AirQuoteRight:.

2026-04-16 10:32:07 CEST

- reply

It's the weird cousin of Lazy

2026-04-16 10:31:05 CEST

- reply

Is called Lazor :hex_lazor:

2026-04-15 16:08:05 CEST

- reply

Community-first, yes. By far best for newcomers.
Nip-29 is not the spec for it tho. It is good inspiration for how to do Rooms inside of Communities however.
A better Community + Room spec will make migrating to it easier than migrating a Nip29 to a new relay.

2026-04-15 13:32:06 CEST

- reply

It's the exact same Zapstore community that also has the Apps, Stacks, Zap Goals, etc... in them, for example.
With the same server + moderation set up behind it all. Built on the same spec that can also have communities that don't even want a forum section.

2026-04-15 13:13:58 CEST

- reply

Lol, no in related threads (often their own).
Obviously.
I'm talking communities around Apps/Tools (think Zapstore, Wisp, Umbrel, ...). For those Chat = ngmi.

2026-04-15 13:01:14 CEST

- reply

Hex, king of reqs.

2026-04-15 12:00:46 CEST

- reply

Brooooooo :lovemega:

2026-04-15 11:59:03 CEST

Forums are the best default feed for App communities.
Because you don't want people pasting error logs all over the Chat, where everyone just wants to have a good time and say GM.

2026-04-15 11:19:22 CEST

Funk is the #1 way to keep moving while coding 🥁
https://www.youtube.com/watch?v=0OOr7Qb2-d4

2026-04-15 09:46:02 CEST

- reply

→ Jaw in French

2026-04-15 09:45:45 CEST

- reply

Machoire :chad_yes:

2026-04-15 09:45:02 CEST

- reply

Failing to do so, yes :wisp_lol:

2026-04-15 09:44:20 CEST

- reply

I'm giving @npub107j…ncxg a helper character/mascot thing.
I did the logo too, no worries.

2026-04-15 09:32:18 CEST

Ok, I got his tagline.
Now I need a good @npub1era…skz0 name:
https://i.nostr.build/ENpln2zwlytPyezP.png

2026-04-14 16:17:43 CEST

- reply

https://i.nostr.build/DOCT0qxJvkVO7FFn.png
:yes: / :no: ?

2026-04-14 10:01:05 CEST

Your website/app needs "Signs of Life" now.
- faces of the team behind the project
- actual interactions
- endorsements / testimonies
- some fancy enough UI elements that :110percent: could not have been vibed

2026-04-12 20:09:41 CEST

Those Profile colors aren't random btw.
They're npub-derived, work in dark and light mode and you see the exact same ones for the same profiles in Zapstore too.
That's designer-nerd-cool in my book :wisp_lazor:
#nevent1q…zdwu

2026-04-10 20:52:15 CEST

- reply

You'll get a mascot too.
https://i.nostr.build/ucPRoaHQi1RNJtnu.png

2026-04-10 20:27:52 CEST

- reply

Ngl, :grimoire:rimoire could use this.
It looks like you're messing up that req. Would you like help?

2026-04-10 20:03:34 CEST

#yestr :zappy:
#nevent1q…xk5f

2026-04-10 15:46:25 CEST

- reply

Lmao, yes. Been there.

2026-04-10 15:25:59 CEST

- reply

Agree.
:zap: for Zap (in any currency)
₿ for Bitcoin currency amount
€ for Euro currency amount
...

2026-04-10 11:50:01 CEST

- reply

1. Moderation can be done by anyone the community needs it to be done. Profile lists managers (publishers) are independent of Community key. The Community key just attaches the whitelist to the content sections (and rooms). Can be another pubkey doing the lst, human or automated hotkey on server, etc...
3. I'll check the spec. If they are just h tagged, we can port them over too, in case that's wanted.

2026-04-10 11:12:38 CEST

- reply

1. Community = admin in this case
2. Member list = profile list(s) in this case (whitelist concept, not member concept btw)
3. Why are join/leave events needed? I don't get how that's a need (vs a wish to copy Telegram UX).

2026-04-10 11:08:14 CEST

- reply

For real? Funny coincidence indeed!
And good vid tbh, thanks :wisp_salute:

2026-04-10 11:06:37 CEST

- reply

Forgot the most important part, oops.
https://i.nostr.build/p8BCgJGAtm5dRKpl.png

2026-04-10 10:43:51 CEST

Zappy, a @npub10r8…t2p8 community mascot. Yes / No ? 😅
https://i.nostr.build/evPIuzOQor3vcbuJ.png

2026-04-10 10:41:28 CEST

- reply

No no. You just keep all chat messages as they are. Port them to new relay and now just query them by the h tag (which is the same in the new room) on the new community main relay.
New chat messages would just also add a "c" tag (community ID, pubkey) for when people find these things in the wild and need to know what community it is from. Just an extra. Not needed for the actual room to work.

2026-04-10 09:17:02 CEST

- reply

@npub107j…ncxg I know reading some more MarkDown is the last thing on your list.
But if ever, this is a Room spec that lets existing Nip29 groups move to our Community model with all their chat messages intact.
https://www.chateau.community/wiki/naddr1qvzqqqrcvgpzqesd33ux28msfplvnwxac2p7988j2ctf8hdrhgjx607nczxmkuyrqq9xummnw3ez6un0daksx8f2rt
h tags still work and events can just be ported to other relay.

2026-04-10 09:10:31 CEST

- reply

+ have a relay-independent community ID (with agency)
+ choose what profile list(s) can publish what kinds
+ have interoperable flows to join profile lists
Thank you for your consideration, have a great day.

2026-04-09 20:25:54 CEST

- reply

Ok, not guaranteeing this 100% works yet. But added you. Lemme know.
Also made it say "Room" and not channel everywhere now.

2026-04-09 18:32:18 CEST

- reply

Damnit, yes. Will edit

2026-04-09 16:30:05 CEST

What if we make it easier to migrate to a new Room spec than to a new Nip-29 relay?
#naddr1qv…f2rt

2026-04-09 13:23:36 CEST

- reply

Oh my :grimoire: !

2026-04-09 13:16:51 CEST

- reply

Me meanwhile:
Scrolling runs :PepeWhy:

2026-04-09 11:13:08 CEST

- reply

What does Community mean here?

2026-04-09 10:50:36 CEST

- reply

Lol. That's like saying: I always lie.

2026-04-08 20:44:37 CEST

- reply

Spec isn't set in stone, but It's already a step up from the other ones imo.
You can read it in an example test app here:
https://www.chateau.community/wiki/naddr1qvzqqqrcvgpzqesd33ux28msfplvnwxac2p7988j2ctf8hdrhgjx607nczxmkuyrqq8kummnw3ez6cm0d4kh2mnfw3useql3jw

2026-04-07 07:31:00 CEST

- reply

No, can't have full signing key(s) in Gmail.

2026-04-06 22:07:58 CEST

- reply

You send the nuke req with the share in your Gmail inbox

2026-04-06 22:03:34 CEST

- reply

Still got 2 shares to create a new third one.

2026-04-06 22:00:02 CEST

- reply

Other idea:
Nuke the key request.
It's not like they themselves don't have the signing ability any longer.

2026-04-06 21:58:41 CEST

- reply

One idea:
Contact the app with their Gmail (or iCloud or phone number, ....).
You could even that button ready in the email you sent them during onboarding: Leaked your share → Click here!

2026-04-06 21:49:33 CEST

- reply

Nostr key is very different risk scenarios.
As a hoster you're holding just one share.
They'd use iCloud or Google for another.
Then your app should incentivize multi-device use so that the third one is on multiple devices too.