reis

I feel your pain. I’ve been experimenting with a book app on Nostr, and literally, just getting the font layout right is an absolute nightmare.
https://tategaki-testbed.pages.dev/

2026-05-09 05:01:02 CEST

- reply

this is a game changer ngl. i suggest to rename it with nostr signer or something for normies then this signer will rule them all. looks solid and ready to be released. hats off.

2026-05-09 04:44:53 CEST

- reply

wtf clave seems to be working even after i killed the app. it appears working via push notifications.

2026-05-09 04:38:59 CEST

- reply

testing clave with cold start

2026-05-09 04:37:45 CEST

- reply

testing clave

2026-05-08 09:46:13 CEST

- reply

Just implement Super Zap in Wisp
https://github.com/nostr-protocol/nips/pull/2289

2026-04-20 14:54:21 CEST

- reply

You're right, and those are fair points. The concept is hard to grasp without seeing it in action. PoP isn't meant to work in isolation, designed to layer on top of WoT, not replace it. The client implementation is where it all comes together, and honestly it's easier to show than explain in text. I'm building the client right now, so you'll be able to see exactly how it works... whenever I finish it lol. No ETA yet.

2026-04-08 12:58:13 CEST

- reply

That's the way to go, sir.

2026-03-20 16:32:53 CET

Introducing flap. A Go x Flutter frontend template.
Special bonus: You can use fiatjaf's nostr (written in Go) on the web.
https://github.com/nosuta/flap

2025-12-27 15:27:59 CET

Rob Pike says “fuck you AI and all people” I agree to some extent, but it’s too convenient for me when it comes to breaking the language barrier.
https://bsky.app/profile/robpike.io/post/3matwg6w3ic2s

2025-12-23 19:51:08 CET

- reply

Yeah, it still works, but at the cost of removing several dependencies and making the codebase a bit of a mess for TinyGo. Standard Wasm should run it without any hassle. However, since I use the tinygo branch for both TinyGo/Wasm and Go/Wasm, I can't provide a minimal diff for standard Go/Wasm alone.
You can test the tinygo branch with:
GOOS=js GOARCH=wasm tinygo test
And for standard Go, use wasmbrowsertest:
GOOS=js GOARCH=wasm go test
No need to worry about this if you are not interested in Wasm. I might be the only one actually using it right now.

2025-12-23 16:02:19 CET

@npub180c…h6w6 Are you sunsetting Wasm support for nostrlib? I’m currently using the TinyGo/Wasm build, but I’m wondering if it’s time to move away from it.
https://github.com/1l0/nostrlib/tree/tinygo

2025-12-18 11:42:29 CET

Holy s***t. AltStore PAL is now available in Japan. This is a game changer.
https://x.com/altstoreio/status/2001504354105196645

2025-12-18 10:05:07 CET

It's happening!
https://x.com/j_sato/status/2001292672775143459

2025-12-12 11:40:26 CET

- reply

Same here. Old men can't recognize the difference.

2025-12-03 08:28:18 CET

All client-side tests have passed including sdk.
Which library was blocking TinyGo/Wasm support in nostrlib?
- net/http
- github.com/puzpuzpuz/xsync/v3
- github.com/mailru/easyjson
- github.com/json-iterator/go
#nevent1q…enhv

2025-12-02 21:38:37 CET

fiatjaf.com/nostr mod for TinyGo/Wasm has started working. There are likely some trade-offs. I still need to check whether everything I need will actually run.
https://github.com/1l0/nostrlib/tree/tinygo
Comparison with standard Go/Wasm:
- Binary size: < 0.1x
- Execution speed: similar or slightly slower (with opt=2)
- Memory usage: ~0.75x

2025-12-01 14:05:51 CET

- reply

Ah, it looks like he’s already aware of the clipboard issue.
https://github.com/guigui-gui/guigui/issues/22
cross-platform is hard. Thanks for giving it a try anyway. You know, I don’t plan on maintaining gnak. It's just a proposal for you.

2025-12-01 08:55:26 CET

- reply

Did you know Guigui? A brand new pure Go gui.
I vibe coded a port of vnak using Guigui and it works!
Cons: no video playback support.
https://github.com/1l0/gnak

2025-11-27 16:38:32 CET

- reply

Ah, I thought the low memory usage was due to how the feed is displayed. It seems it's heavily using IndexedDB instead. In that case, I actually prefer your way.

2025-11-27 15:41:32 CET

- reply

I'm excited about that. I'd prefer that simpler one. What I like about Fevela is not only how readable it is, but also its low memory usage.
https://image.nostr.build/b82e883338e5837400fe1975e9a557b36e9bbe2ac5d322be2db64f05eab6fcaf.png
https://image.nostr.build/f7a734cbde7b9d11a3e8c9170e10b69647f3339a7c2fadc3b5f36bcd0d98fb42.png

2025-11-18 14:55:32 CET

- reply

https://api.flutter.dev/flutter/widgets/WidgetsBindingObserver-class.html
This might be what you are looking for. You can detect fore/background state.

2025-11-10 09:55:47 CET

Planctal v0.1.12
https://planctal.com/
Changes:
- Jump to the pin on clicking itself
- Modal 'Add Pin'
- Filter for same seed
- Support iOS browser

2025-11-10 04:24:30 CET

Planctal v0.1.9
https://planctal.com/
Changes:
- Images are now saved at the highest available resolution.
Before:
https://image.nostr.build/13151e18ae19c15151330f6d135addaf79f537e2384dd54df9f505a54cd40d45.png
After:
https://image.nostr.build/e7b422b166a06ee41744e869dfde6bf2ff3237fb42602af325d0223f9ea9dbf3.png

2025-11-08 14:18:26 CET

Planctal v0.1.3
https://planctal.com/
Changes:
- Clamps scale

2025-11-06 22:05:03 CET

Planctal - early preview
https://planctal.com/

2025-11-05 19:53:59 CET

Deep contour lines.
https://video.nostr.build/96670f19b603e7ab30dbb045df288beb5dc5d032e0a67b123af6bd3d2d6a6307.mp4

2025-11-05 17:29:54 CET

It takes too long to add the pin-to-map feature...
https://video.nostr.build/2a1244a479558c1ed0706256897de394d085814d9fc86dde7fc888718309e977.mp4

2025-11-03 16:53:50 CET

Making a yet another fantasy planet generator. Deep detailed zoom by fBM.
https://video.nostr.build/92a108cef7a84e59caf575c8659b6021ed8af0dfeccd23b8c20b8a80c6a6c616.mp4

2025-10-16 05:11:20 CEST

- reply

I meant not all events. The merged follow list at that point in time.

2025-10-16 05:00:33 CEST

- reply

I'm thinking about implementing this in my app, but a specification written by the "core" members would really help me out.

2025-10-16 04:57:52 CEST

- reply

Consider combining individual follow/unfollow events with periodic snapshots that include all events at specific points in time, featuring pagination with a continuation event ID (a pointer to the next part of the snapshot).

2025-10-12 18:26:47 CEST

Umm... Looks like the Go + Flutter Nostr client loads fast enough for normies on real devices (Go as a static lib on iOS in this video).
https://video.nostr.build/ed283b89cc701a826c49c6d73711283d7c4d9ddf69edb767ae6566f7a1cd3bb9.mp4
Equivalent demo for the web (Go as a web worker):
https://wasm-worker-testbed.pages.dev/

2025-10-02 02:41:18 CEST

Nostr outbox consumes more power than this game.
https://messenger.abeto.co/

2025-09-27 05:06:29 CEST

- reply

https://image.nostr.build/561f4ea184983512e4897f118e8e75c04d34a920ef190d5f42ee120501eb3bc3.jpg

2025-09-27 04:58:50 CEST

- reply

I mean a single line like this:
https://wasm-worker-testbed.pages.dev/

2025-09-27 04:57:47 CEST

- reply

You should add trimmed content as a single line in compact mode — that would make the UX perfect. Congrats.

2025-09-23 06:04:44 CEST

Wow, https://dev.nosotros.app/ uses OPFS with SQLite. I’m doing the same in my testbed.

2025-09-21 06:14:52 CEST

- reply

yeah, if you already have a community outside of Nostr, you can bring that in as a base. but starting from scratch? no, you can’t.

2025-09-21 05:34:42 CEST

- reply

The problem is that you can’t build a community from scratch on Nostr since almost every app only supports WoT gated community.

2025-09-21 05:18:28 CEST

@npub1sg6…f63m consider adding PoW for public keys on Bitchat.
reference code in Go:
https://github.com/1l0/nostrlib/commit/349cb8d9c01a7067a852f613702ac2223bf92d6d
#nevent1q…udg0

2025-09-17 04:39:27 CEST

What the hell. macOS Tahoe is terrible in every way.

2025-09-13 09:03:35 CEST

whoa, nostr_zig's NIP-EE MLS Visual Explainer is doing an excellent job. @npub1p4k…cxf8
https://github.com/futurepaul/nostr_zig

2025-09-08 12:47:42 CEST

- reply

I don’t think this is a matter of comparison with ordinary users. The absolute number of spam messages should decrease as a result. In the current state, muting is essentially meaningless against spammers. I agree that WoT works well, but as you know, it’s a gated community.

2025-09-08 06:13:28 CEST

- reply

we should use trailing zeros for this since someone might want an original prefix for ids.

2025-09-08 06:06:09 CEST

yeah, I’m convinced this would be effective against spam. @npub1acg…p35c
#nevent1q…wjnu

2025-09-05 04:24:51 CEST

Maybe I’m just stupid, but if creating an account required some sort of PoW, wouldn’t that drastically reduce spam? #nostr-next

2025-08-25 00:41:58 CEST

- reply

The answer is an ephemeral WoT. When you hug A, you give +1 trust to A. When you slap B, you give -1 trust to B. Then, the users trusted by A (ephemerally) form a WoT that can be used to collaboratively mute untrusted people. That is collaborative moderation. It is invented by @npub1cgd…kfex, and I’m working on a topic-based feed.

2025-08-23 11:19:51 CEST

don't mix ngit and GitHub. it messes up the git config.

2025-08-21 05:48:33 CEST

- reply

Wait, you’ve abandoned go-nostr, and now we should follow you on ngit?
https://gitworkshop.dev/fiatjaf.com/nostrlib

2025-08-17 07:10:12 CEST

- reply

@npub1v0l…qj49 How about this? No server is required other than relays and Blossom servers. I’m wondering if we could achieve seamless playback of a sequence of dynamically generated .m3u8 data URIs on the fly for live streaming.

2025-08-17 06:24:13 CEST

- reply

check this out:
#nevent1q…vxtr

2025-08-16 12:02:14 CEST

- reply

👇
#nevent1q…vxtr

2025-08-16 11:46:08 CEST

I just created a demo of the nostr HLS playback.
https://github.com/1l0/video_testbed
The key point is that you can use a data URI to play the .m3u8 on the fly.
#nevent1q…jn50

2025-08-13 09:38:53 CEST

- reply

and auth
#nevent1q…kuay

2025-08-13 07:53:26 CEST

- reply

Unrelated, but your client hasn’t published the event to my inbox relays.

2025-08-13 05:25:59 CEST

- reply

Thanks for elaborating. Ultimately, it means each group should use its own relay.

2025-08-13 04:12:52 CEST

- reply

Can't relays sniff something from the combination of auth, welcome event, group ID, and IP address?

2025-08-13 00:02:58 CEST

- reply

from ip address? idk

2025-08-12 04:37:51 CEST

- reply

OK, I’d like a comment from the creator of zapddit. @npub1ltx…z40t

2025-08-12 04:27:22 CEST

- reply

Yes, my point is to treat every existing reaction, including +, -, or emojis, as an upvote to leverage existing assets before some one starts using -. Just an idea.

2025-08-12 03:48:53 CEST

- reply

I understand your thoughts, but we should try to use existing kinds as much as possible. Most reactions today seem to be positive. Of course, we’ll need to modify the NIP if we go ahead with this.

2025-08-12 03:39:37 CEST

- reply

Yeah, WoT based on the moderators list is far better than recommending moderators. My example was dumb.

2025-08-12 02:00:24 CEST

- reply

Actually, the existing WoT based on the follow list isn’t really a WoT. A WoT based on the moderators list is more deserving of the name.

2025-08-12 01:53:53 CEST

- reply

commenting on others,
In my idea, the moderators list is an addressable event with a “d” tag as a topic.
I meant that we should still use kind-7 for upvotes (no one uses this as downvotes IRL), but use a new kind for downvotes (kind-77?). When reacting to topic posts, we'd add a “t” tag as the topic.
Voting for metadata might be overcomplicated, recent from moderators might be good enough as you said.
Overall, I want to ditch the pre-existing WoT or following model in favour of the new shiny topic-based model. For example, collaborative relay selection could be based on the moderators list.

2025-08-12 01:25:05 CEST

- reply

I figured it out myself. I guess I can just give those specs a new kind. It doesn’t need to break interoperability. You only defined the kind for bans, not for moderation as a whole.

2025-08-12 01:16:07 CEST

- reply

Interesting. If a moderation means the same as a ban, then your approach is probably correct. I haven’t thought of many examples, but for instance, what if there were a type of moderation like “recommending a user as a moderator”?

2025-08-11 18:21:23 CEST

- reply

The moderation types in your specs are: an event with "p" = ban, and an event with "e" = off-topic. That seems too fragile to me, and if we separate the kinds, we could easily add new moderation types later. Sorry, I’ll comment on the rest later. It’s 1 a.m. here.

2025-08-11 16:52:32 CEST

- reply

It’s better to wait until I finish the prototype.
my idea is basically @npub1cgd…kfex 's specs
+ an independent “moderators list” per topic (instead of treating the following list as a moderators list)
+ topic-specific upvote and downvote (new kind) for posts
+ separation of kinds for banning a user and marking a post as off-topic
+ votes for topic metadata

2025-08-11 11:26:21 CEST

- reply

topic-based feeds with collaborative moderation invented by @npub1cgd…kfex I'm also working on it > curation

2025-08-11 08:41:13 CEST

TIL the only viable options for NIP-07 on mobile are Nostash/Safari on iOS and nos2x-fox/Firefox on Android.

2025-08-06 19:58:02 CEST

- reply

logged in via browser extension.

2025-08-06 19:54:23 CEST

- reply

ok, thanks. by the way, i'm not sure why, but reloading the page after logging in logs me out. looks like something account-related is still in local storage, though.

2025-08-06 19:48:00 CEST

test from Pollerama

2025-08-06 15:18:21 CEST

- reply

Very interesting feature! How does the app select relays for Topics? Is it hardcoded?

2025-08-05 15:02:28 CEST

- reply

Thank you!

2025-08-05 14:15:22 CEST

- reply

I see. Those made me realize that we might eventually have to deal with issues like abusive or hate tagging.

2025-08-05 12:27:17 CEST

- reply

Will social tagging work? I suspect that people may lack the motivation to tag others.

2025-08-05 10:32:01 CEST

- reply

no worries at all. good to hear it wasn’t something serious.

2025-08-05 10:15:19 CEST

@npub107j…ncxg chachi.chat now:
https://image.nostr.build/b32756fed97ea1568346e2af7b63f8cc49cc3874eadd264517d8485b635f5b50.png

2025-07-30 03:33:44 CEST

- reply

#nevent1q…hfzc

2025-07-29 11:19:34 CEST

- reply

wait, i can already see the custom emojis on Jumble. it's too fast.

2025-07-29 09:04:22 CEST

- reply

Never mind. It's just that the same nevent without a kind worked at the time.

2025-07-28 12:28:27 CEST

- reply

I bet specifying the kind is the root of the bug.

2025-07-23 07:17:09 CEST

introducing the nostr pubkey shape
https://1l0.github.io/hexpattern/

2025-07-20 09:30:55 CEST

my brief conclusion is that the shape matters, but the colour sucks for identifying a pubkey.
https://image.nostr.build/d4655a4c2571122c350847d4208df18b347d6ecbd25c185c43513566fff699e6.png

2025-07-18 09:41:27 CEST

エアリプですか。日本語以外が過疎ってきているのを見るとむしろこちらの使い方にNostrの光明が見えた気がします。ありがとうございます。

2025-07-18 09:02:16 CEST

yabu.meって返信ではないのに返信している様に見えるポストが見られる。日本で特殊な使い方がされているのだろうか…。

2025-07-17 09:36:03 CEST

- reply

Yeah... I'm thinking we should just use those metadata relays + own outbox to broadcast the relay list, instead of trying to spread it to as many relays as possible.

2025-07-10 02:24:00 CEST

- reply

I can’t decide whether to use NIP-117 or your approach for the double ratchet until you publish your own NIP.
https://github.com/nostr-protocol/nips/pull/1813

2025-07-02 03:51:40 CEST

- reply

Are you likely to be able to solve it?

2025-06-27 03:02:16 CEST

- reply

Are you saying that the own shard in nshard should be eliminated in this example? Aside from that, does the rest make sense?

2025-06-27 01:12:23 CEST

- reply

Thank you for the clarification. If it’s not worse in terms of security, I think it’s worth considering as a possible implementation.
@npub1xts…kk5s @npub1gcx…nj5z what do you think?

2025-06-26 13:36:51 CEST

- reply

https://github.com/nostr-protocol/nips/pull/1764

2025-06-26 13:34:38 CEST

- reply

LFG

2025-06-26 13:18:42 CEST

- reply

I just hacked TextField for notes, but AsciiDoc was a too much for me when I was exploring the Curated Publications NIP. I’d definitely use your package for AsciiDoc if you publish it.
https://textfieldhack.vercel.app/