Nostr notes by reis

A sneak peek of my Concord client written in Go / Flutter. ...

2026-09-29T20:42:28Z

A sneak peek of my Concord client written in Go / Flutter.
https://sneakpeek.nosuta.xyz/

Android APK:
https://pub-b10b24c26581433abd94a606879c9db0.r2.dev/sneakpeek.apk

https://github.com/privkeyio/wisp

2026-06-24T02:44:07Z

https://github.com/privkeyio/wisp

that's the wot trap

2026-06-05T02:42:33Z

In reply to nevent1q…gqqq
_________________________

that's the wot trap

Distributed Erlang is pure art. The only downside is that ...

2026-05-22T07:31:43Z

In reply to nevent1q…tufu
_________________________

Distributed Erlang is pure art. The only downside is that it's a bit slow.

I know nothing about Bitcoin, but you seem cool.

2026-05-22T07:28:00Z

In reply to nevent1q…t9zr
_________________________

I know nothing about Bitcoin, but you seem cool.

My new Nostr logo. Ultra-simplified. ...

2026-05-22T07:22:45Z

My new Nostr logo. Ultra-simplified.

I don't understand on-chain or whatever but please keep the ...

2026-05-17T17:46:15Z

I don't understand on-chain or whatever but please keep the zap feature on Nostr for Super Zap I'm working on.

I feel your pain. I’ve been experimenting with a book app on ...

2026-05-16T14:29:02Z

In reply to nevent1q…ar5h
_________________________

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/

maybe proof of survival is a better name #nevent1q…m6zj

2026-05-15T15:07:36Z

maybe proof of survival is a better name

quoting
nevent1q…m6zj

The Problem with WoT Alone

Web of Trust (WoT) is the backbone of spam resistance on Nostr. If you're not in someone's trust graph, your posts simply don't reach them. This works well for existing users — but it creates a brutal cold-start problem for newcomers.

A new user joins Nostr. They post thoughtful content. Nobody sees it. Not because their content is bad, but because they haven't yet been woven into anyone's WoT. They experience Nostr as a ghost town and leave. The irony is that WoT, designed to protect quality, ends up suppressing it.

This is not a bug in WoT. It's a structural limitation. WoT is a horizontal trust model — it asks "who vouches for you?" But there's another dimension of trust that WoT cannot capture: temporal trust — "how long have you shown up?"

Introducing Proof of Presence (PoP)

Proof of Presence is a complementary trust signal based on a simple observation:

Spammers are cheap. Persistence is expensive.

Creating a throwaway keypair costs nothing. But maintaining a consistent posting history over weeks and months — while avoiding mutes and reports from the community — has a real cost. It requires genuine engagement.

PoP measures exactly that. It is a vertical trust model that asks not "who knows you?" but "how long have you survived?"

How It Works

A PoP score for any given pubkey is derived from three signals:

1. Accumulated Presence The number of days between a pubkey's first and most recent kind:1 event. A pubkey that has been posting for 180 days has demonstrated sustained commitment that a fresh spam key cannot fake.

2. Survival Under Pressure The relationship between visibility and adversarial pressure is asymmetric: the more a pubkey posts, the more exposed it becomes to reports and mutes. An account that remains active despite this exposure demonstrates something meaningful. High post volume combined with low report rate is a strong positive signal.

3. Community Reports (kind:1984) Unlike mute lists — which are local and private — reports are public events. This makes them aggregatable. A pubkey that accumulates reports from multiple independent sources in the trust graph is likely problematic. Crucially, reports can be weighted by WoT distance: a report from someone two hops away carries more weight than a report from a stranger.

The composite score looks roughly like this:
PoP Score =
  (days_active × w1)
  + (survived_posts × w2)
  - (weighted_report_count × w3)
Where weights are tunable per client.

Why Reports Instead of Mutes?

Mute lists (kind:10000) are private by design. They're great for personal UX but useless as a collective signal — you can't aggregate what you can't see.

kind:1984 (Report) events are public. One report per pubkey per reporter, published to relays, queryable by anyone. This means:

Clients can aggregate reports across the trust graph without any central coordinator

Report patterns are transparent and auditable

A "community immune system" emerges organically — if enough trusted accounts report a pubkey, it surfaces as a signal without anyone having to maintain a shared blacklist

The local mute and the public report serve different purposes and complement each other:

Mute (kind:10000) Report (kind:1984) Visibility Private Public Effect Local UX only Aggregatable signal Purpose Personal comfort Community health

PoP + WoT: Horizontal × Vertical Trust

WoT and PoP answer different questions and are strongest in combination:
WoT  → "Who vouches for this pubkey?"    (horizontal, social graph)
PoP  → "How long has this pubkey survived?" (vertical, time + community)
A new user with zero WoT connections but 90 days of consistent posting and zero reports should be surfaced — not silenced. PoP gives clients a principled basis for doing this without compromising spam resistance.

Conversely, a pubkey with strong WoT connections but a sudden spike in reports can be down-ranked. PoP acts as a check on WoT, not a replacement.

Client-Side Implementation

PoP requires no protocol changes. It is entirely computable from existing event kinds:

kind:1 — Post history (first/last timestamps, total count)

kind:1984 — Reports (aggregated, weighted by WoT distance)

kind:3 — Follow lists (for WoT distance calculation)

A client implementation could:

On startup, load the user's follow graph and compute WoT distances

Maintain a local SQLite cache of PoP scores, updated incrementally

When rendering a feed that includes unknown pubkeys (e.g. a relay's global stream filtered by topic), rank by PoP score

Surface high-PoP unknowns as "you might want to follow this person"

The scoring computation is lightweight enough to run entirely on-device — no external API, no central server, fully in the spirit of Nostr's decentralized architecture.

Resistance to Manipulation

Can spammers game PoP by posting consistently for months? Yes, but the cost is the point. Running a long-lived, low-report-rate account at scale requires either genuine human engagement or significant infrastructure investment. The economics favor legitimate users.

Can bad actors coordinate report-bombing a legitimate account? This is the main attack vector. It is mitigated by WoT-weighted report scoring — a coordinated attack from a single cluster has diminished effect compared to reports distributed across independent parts of the trust graph. The weight function can be tuned to be conservative (require high WoT proximity) or liberal depending on client preferences.

Can someone buy an aged account? Possibly. But aged accounts with clean report histories have genuine value, which means the market price acts as a cost floor. This is no different from the economics of aged social media accounts on other platforms — and notably, it doesn't undermine WoT, which requires actual human relationships.

Summary

Proof of Presence proposes that time and community survival are trust signals, complementary to but distinct from WoT. It addresses the cold-start problem for new users, creates an organic community immune system via public reports, and requires no protocol changes to implement.

WoT asks: who do you know? PoP asks: how long have you been here, and are you still welcome?

Together, they cover the two dimensions of trust that matter most in an open, permissionless network.

Conceived by Reishi Saza, drafted by Claude.

Realizing that relays are packed with encrypted events I ...

2026-05-15T15:01:33Z

Realizing that relays are packed with encrypted events I can't read convinced me that we need Super Zap to help relay providers sustain this.

cool. grouping is what we need.

2026-05-15T14:35:22Z

In reply to nevent1q…7kql
_________________________

cool. grouping is what we need.

this is a game changer ngl. i suggest to rename it with nostr ...

2026-05-09T03:01:02Z

In reply to nevent1q…mnq9
_________________________

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.

wtf clave seems to be working even after i killed the app. it ...

2026-05-09T02:44:53Z

In reply to nevent1q…d4z4
_________________________

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

testing clave with cold start

2026-05-09T02:38:59Z

In reply to nevent1q…pzuz
_________________________

testing clave with cold start

testing clave

2026-05-09T02:37:45Z

In reply to nevent1q…pzuz
_________________________

testing clave

Just implement Super Zap in Wisp ...

2026-05-08T07:46:13Z

In reply to nevent1q…n78y
_________________________

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

Planctal v1.3.0 https://planctal.com/ You can now draw lines on ...

2026-05-05T13:02:40Z

Planctal v1.3.0
https://planctal.com/

You can now draw lines on the map.

TinyGo + Wasm環境にはなぜか日本語話者が多い ...

2026-04-26T07:25:15Z

TinyGo + Wasm環境にはなぜか日本語話者が多い
https://github.com/tinygo-org/net/issues/52

You're right, and those are fair points. The concept is hard ...

2026-04-20T12:54:21Z

In reply to nevent1q…prel
_________________________

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.

Conceived by me, drafted by Claude. #naddr1qv…z8lj

2026-04-20T11:55:49Z

Conceived by me, drafted by Claude.

quoting
naddr1qv…z8lj

The Problem with WoT Alone

Web of Trust (WoT) is the backbone of spam resistance on Nostr. If you're not in someone's trust graph, your posts simply don't reach them. This works well for existing users — but it creates a brutal cold-start problem for newcomers.

A new user joins Nostr. They post thoughtful content. Nobody sees it. Not because their content is bad, but because they haven't yet been woven into anyone's WoT. They experience Nostr as a ghost town and leave. The irony is that WoT, designed to protect quality, ends up suppressing it.

This is not a bug in WoT. It's a structural limitation. WoT is a horizontal trust model — it asks "who vouches for you?" But there's another dimension of trust that WoT cannot capture: temporal trust — "how long have you shown up?"

Introducing Proof of Presence (PoP)

Proof of Presence is a complementary trust signal based on a simple observation:

Spammers are cheap. Persistence is expensive.

Creating a throwaway keypair costs nothing. But maintaining a consistent posting history over weeks and months — while avoiding mutes and reports from the community — has a real cost. It requires genuine engagement.

PoP measures exactly that. It is a vertical trust model that asks not "who knows you?" but "how long have you survived?"

How It Works

A PoP score for any given pubkey is derived from three signals:

1. Accumulated Presence The number of days between a pubkey's first and most recent kind:1 event. A pubkey that has been posting for 180 days has demonstrated sustained commitment that a fresh spam key cannot fake.

2. Survival Under Pressure The relationship between visibility and adversarial pressure is asymmetric: the more a pubkey posts, the more exposed it becomes to reports and mutes. An account that remains active despite this exposure demonstrates something meaningful. High post volume combined with low report rate is a strong positive signal.

3. Community Reports (kind:1984) Unlike mute lists — which are local and private — reports are public events. This makes them aggregatable. A pubkey that accumulates reports from multiple independent sources in the trust graph is likely problematic. Crucially, reports can be weighted by WoT distance: a report from someone two hops away carries more weight than a report from a stranger.

The composite score looks roughly like this:
PoP Score =
  (days_active × w1)
  + (survived_posts × w2)
  - (weighted_report_count × w3)
Where weights are tunable per client.

Why Reports Instead of Mutes?

Mute lists (kind:10000) are private by design. They're great for personal UX but useless as a collective signal — you can't aggregate what you can't see.

kind:1984 (Report) events are public. One report per pubkey per reporter, published to relays, queryable by anyone. This means:

Clients can aggregate reports across the trust graph without any central coordinator

Report patterns are transparent and auditable

A "community immune system" emerges organically — if enough trusted accounts report a pubkey, it surfaces as a signal without anyone having to maintain a shared blacklist

The local mute and the public report serve different purposes and complement each other:

Mute (kind:10000) Report (kind:1984) Visibility Private Public Effect Local UX only Aggregatable signal Purpose Personal comfort Community health

PoP + WoT: Horizontal × Vertical Trust

WoT and PoP answer different questions and are strongest in combination:
WoT  → "Who vouches for this pubkey?"    (horizontal, social graph)
PoP  → "How long has this pubkey survived?" (vertical, time + community)
A new user with zero WoT connections but 90 days of consistent posting and zero reports should be surfaced — not silenced. PoP gives clients a principled basis for doing this without compromising spam resistance.

Conversely, a pubkey with strong WoT connections but a sudden spike in reports can be down-ranked. PoP acts as a check on WoT, not a replacement.

Client-Side Implementation

PoP requires no protocol changes. It is entirely computable from existing event kinds:

kind:1 — Post history (first/last timestamps, total count)

kind:1984 — Reports (aggregated, weighted by WoT distance)

kind:3 — Follow lists (for WoT distance calculation)

A client implementation could:

On startup, load the user's follow graph and compute WoT distances

Maintain a local SQLite cache of PoP scores, updated incrementally

When rendering a feed that includes unknown pubkeys (e.g. a relay's global stream filtered by topic), rank by PoP score

Surface high-PoP unknowns as "you might want to follow this person"

The scoring computation is lightweight enough to run entirely on-device — no external API, no central server, fully in the spirit of Nostr's decentralized architecture.

Resistance to Manipulation

Can spammers game PoP by posting consistently for months? Yes, but the cost is the point. Running a long-lived, low-report-rate account at scale requires either genuine human engagement or significant infrastructure investment. The economics favor legitimate users.

Can bad actors coordinate report-bombing a legitimate account? This is the main attack vector. It is mitigated by WoT-weighted report scoring — a coordinated attack from a single cluster has diminished effect compared to reports distributed across independent parts of the trust graph. The weight function can be tuned to be conservative (require high WoT proximity) or liberal depending on client preferences.

Can someone buy an aged account? Possibly. But aged accounts with clean report histories have genuine value, which means the market price acts as a cost floor. This is no different from the economics of aged social media accounts on other platforms — and notably, it doesn't undermine WoT, which requires actual human relationships.

Summary

Proof of Presence proposes that time and community survival are trust signals, complementary to but distinct from WoT. It addresses the cold-start problem for new users, creates an organic community immune system via public reports, and requires no protocol changes to implement.

WoT asks: who do you know? PoP asks: how long have you been here, and are you still welcome?

Together, they cover the two dimensions of trust that matter most in an open, permissionless network.

Conceived by Reishi Saza, drafted by Claude.

Nostr event nevent1qqs2fa8g67zfy9p2tu84l9pxd8lu4vmy47see3mznwx3e65umv5kd7gzyq786y4xctm3l6w2y5njzm6jngfhhv8javqckx8nqqpexwu4xgqnu8gnxw7

2026-04-14T09:09:46Z

https://freedium-mirror.cfd/https://medium.com/@daxx5/why-most-rust-codebases-will-collapse-in-5-years-a-dependency-apocalypse-is-coming-6c2f503ce237

Go finally has an MLS package ...

2026-04-13T02:16:34Z

Go finally has an MLS package
https://github.com/thomas-vilte/mls-go

That's the way to go, sir.

2026-04-08T10:58:13Z

In reply to nevent1q…x5mu
_________________________

That's the way to go, sir.

Introducing flap. A Go x Flutter frontend template. Special ...

2026-03-20T15:32:53Z

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

Rob Pike says “fuck you AI and all people” I agree to some ...

2025-12-27T14:27:59Z

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

Yeah, it still works, but at the cost of removing several ...

2025-12-23T18:51:08Z

In reply to nevent1q…8znk
_________________________

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.

@npub180c…h6w6 Are you sunsetting Wasm support for nostrlib? ...

2025-12-23T15:02:19Z

fiatjaf (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

Holy s***t. AltStore PAL is now available in Japan. This is a ...

2025-12-18T10:42:29Z

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

It's happening! ...

2025-12-18T09:05:07Z

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

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

2025-12-12T10:40:26Z

In reply to nevent1q…hsxp
_________________________

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

love it. https://www.youtube.com/watch?v=noMEfH8WQqk

2025-12-03T14:09:36Z

love it.
https://www.youtube.com/watch?v=noMEfH8WQqk

All client-side tests have passed including sdk. Which library ...

2025-12-03T07:28:18Z

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

quoting
nevent1q…enhv
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

fiatjaf.com/nostr mod for TinyGo/Wasm has started working. There ...

2025-12-02T20:38:37Z

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

Ah, it looks like he’s already aware of the clipboard issue. ...

2025-12-01T13:05:51Z

In reply to nevent1q…puw9
_________________________

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.

Did you know Guigui? A brand new pure Go gui. I vibe coded a port ...

2025-12-01T07:55:26Z

In reply to nevent1q…fpky
_________________________

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

Ah, I thought the low memory usage was due to how the feed is ...

2025-11-27T15:38:32Z

In reply to nevent1q…vjy9
_________________________

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.

I'm excited about that. I'd prefer that simpler one. What ...

2025-11-27T14:41:32Z

In reply to nevent1q…k4sx
_________________________

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.

Planctal - Zoomable Fiction Map Generator ...

2025-11-20T14:07:30Z

Planctal - Zoomable Fiction Map Generator
https://www.youtube.com/watch?v=3KLtRFQtqbI

Nostr event nevent1qqsyrcd8lnm2tq9a2c9ctmwmhzfycmm49lqjygrfpwpq48umyvwjftgzyq786y4xctm3l6w2y5njzm6jngfhhv8javqckx8nqqpexwu4xgqnufuvuwg

2025-11-18T13:55:32Z

In reply to nevent1q…3uhz
_________________________

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

how. vps? dedicated server?

2025-11-18T13:17:59Z

In reply to nevent1q…3fw6
_________________________

how. vps? dedicated server?

holy shite. web apps suck ah.

2025-11-18T13:12:34Z

In reply to nevent1q…dycn
_________________________

holy shite. web apps suck ah.

Planctal v0.1.12 https://planctal.com/ Changes: - Jump to the pin ...

2025-11-10T08:55:47Z

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

Planctal v0.1.9 https://planctal.com/ Changes: - Images are now ...

2025-11-10T03:24:30Z

Planctal v0.1.9
https://planctal.com/

Changes:
- Images are now saved at the highest available resolution.

Before:

After:

Planctal v0.1.8 https://planctal.com Changelog: - scale: ...

2025-11-08T19:29:30Z

Planctal v0.1.8
https://planctal.com

Changelog:
- scale: scientific format
- pin list: sort by latest
- DMS coordinates

Planctal v0.1.4 planctal.com Changes: - Increased octave limit ...

2025-11-08T15:36:46Z

Planctal v0.1.4
planctal.com

Changes:
- Increased octave limit (more details when zooming in)
- Added a "Save Image" button

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

2025-11-08T13:18:26Z

Planctal v0.1.3
https://planctal.com/

Changes:
- Clamps scale

Planctal v0.1.2 https://planctal.com/ Changes: - Updates values ...

2025-11-08T10:56:32Z

Planctal v0.1.2
https://planctal.com/

Changes:
- Updates values when navigating backward or forward in history
- Improved rotation behavior near the poles

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

2025-11-06T21:05:03Z

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

Deep contour lines. ...

2025-11-05T18:53:59Z

Deep contour lines.

It takes too long to add the pin-to-map feature... ...

2025-11-05T16:29:54Z

It takes too long to add the pin-to-map feature...

Making a yet another fantasy planet generator. Deep detailed zoom ...

2025-11-03T15:53:50Z

Making a yet another fantasy planet generator. Deep detailed zoom by fBM.

If there’s a shared local database, then yes. But if each ...

2025-10-22T04:40:42Z

In reply to nevent1q…5ah2
_________________________

If there’s a shared local database, then yes. But if each client has its own local database, the total size scales with the number of clients — so, nah. I like to think of relays as the database, regardless of whether they’re local or remote.

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

2025-10-16T03:11:20Z

In reply to nevent1q…mcse
_________________________

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

I'm thinking about implementing this in my app, but a ...

2025-10-16T03:00:33Z

In reply to nevent1q…mcse
_________________________

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

Consider combining individual follow/unfollow events with ...

2025-10-16T02:57:52Z

In reply to nevent1q…7ruy
_________________________

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).

Umm... Looks like the Go + Flutter Nostr client loads fast enough ...

2025-10-12T16:26:47Z

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).

Equivalent demo for the web (Go as a web worker):
https://wasm-worker-testbed.pages.dev/

Nostr outbox consumes more power than this game. ...

2025-10-02T00:41:18Z

Nostr outbox consumes more power than this game.

https://messenger.abeto.co/

Nostr event nevent1qqsvfeqwgj94tnmz4sqewr9spc26y968kngzs5chfmmu4qu6x2skckszyq786y4xctm3l6w2y5njzm6jngfhhv8javqckx8nqqpexwu4xgqnuaye87l

2025-09-27T03:06:29Z

In reply to nevent1q…mz4n
_________________________

I mean a single line like this: ...

2025-09-27T02:58:50Z

In reply to nevent1q…4cqy
_________________________

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

You should add trimmed content as a single line in compact mode ...

2025-09-27T02:57:47Z

In reply to nevent1q…yxuu
_________________________

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

Wow, https://dev.nosotros.app/ uses OPFS with SQLite. I’m doing ...

2025-09-23T04:04:44Z

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

yeah, if you already have a community outside of Nostr, you can ...

2025-09-21T04:14:52Z

In reply to nevent1q…0zku
_________________________

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.

The problem is that you can’t build a community from scratch on ...

2025-09-21T03:34:42Z

In reply to nevent1q…lezc
_________________________

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

@npub1sg6…f63m consider adding PoW for public keys on Bitchat. ...

2025-09-21T03:18:28Z

jack (npub1sg6…f63m) consider adding PoW for public keys on Bitchat.
reference code in Go:
https://github.com/1l0/nostrlib/commit/349cb8d9c01a7067a852f613702ac2223bf92d6d

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

Nostr event nevent1qqspckvxjdkg80zzxekru84rthr9dy6e37j24jvcvsxxpdys2t6kwtszyq786y4xctm3l6w2y5njzm6jngfhhv8javqckx8nqqpexwu4xgqnuew6zqj

2025-09-18T05:10:02Z

おすすめプレイリストを流し聞きしていて、良いと思って曲をチェックすると必ずWispっていう。完全に好きですわ。

Nostr event nevent1qqsten46gwqhrv934p8pe2ps4yszqt3uwkzhu6ermluv0rjsy2fy8cgzyq786y4xctm3l6w2y5njzm6jngfhhv8javqckx8nqqpexwu4xgqnuwgdwfy

2025-09-17T02:39:27Z

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

whoa, nostr_zig's NIP-EE MLS Visual Explainer is doing an ...

2025-09-13T07:03:35Z

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

Zed is good, but it still can’t beat VS Code for me.

2025-09-08T11:01:33Z

In reply to nevent1q…erl2
_________________________

Zed is good, but it still can’t beat VS Code for me.

I don’t think this is a matter of comparison with ordinary ...

2025-09-08T10:47:42Z

In reply to nevent1q…04dn
_________________________

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.

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

2025-09-08T04:13:28Z

In reply to nevent1q…xe2w
_________________________

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

yeah, I’m convinced this would be effective against spam. ...

2025-09-08T04:06:09Z

yeah, I’m convinced this would be effective against spam. Mike Dilger ☑️ (npub1acg…p35c)

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

Maybe I’m just stupid, but if creating an account required some ...

2025-09-05T02:24:51Z

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