Last Notes
[ sputnik-nostr/sputnik ] chore: fix icon generation
https://github.com/sputnik-nostr/sputnik/commit/4f7fb638d6a3329a1c352649783ba58e13195271
[ forgesworn/farrier-kit ] ci: deploy to stall, not the cancelled Hetzner address
The rsync target 95.217.39.110 was cancelled around 2026-08-27 and its
content was migrated to the current routing host, but this pipeline was
never repointed. A cancelled address gets reassigned, so aiming an
`rsync --delete` at it was unsafe as well as broken.
Pin the new host's keys rather than scanning per run. The old failure was
invisible because ssh-keyscan hit its 5s timeout, returned 1, and aborted
the step under `set -e` before rsync produced any output.
https://github.com/forgesworn/farrier-kit/commit/d621d1a445e1344fd67a6c2063d158c00c39d917
[ forgesworn/nwc-kit ] ci: deploy to stall, not the cancelled Hetzner address
The rsync target 95.217.39.110 was cancelled around 2026-08-27 and its
content was migrated to the current routing host, but this pipeline was
never repointed. A cancelled address gets reassigned, so aiming an
`rsync --delete` at it was unsafe as well as broken.
Pin the new host's keys rather than scanning per run. The old failure was
invisible because ssh-keyscan hit its 5s timeout, returned 1, and aborted
the step under `set -e` before rsync produced any output.
https://github.com/forgesworn/nwc-kit/commit/b69fc6b95fafdfe462bfd296e801184a766f0405
[ FelineStateMachine/tinyrelay ] document public access through Tailscale Funnel
https://github.com/FelineStateMachine/tinyrelay/commit/73b02577c6978de80511c49536aac9ffb48f8a34
最近のホットな話題をお知らせします。 #hotpostrank
No1: 1 reposts 2 reactions
#note1mdg…5v00
No2: 1 reposts 1 reactions
#note1gxt…7edt
No3: 1 reposts 1 reactions
#note1f3c…0lvk
No4: 2 reactions
#note184j…t2dc
No5: 2 reactions
#note1qqq…vehw
No6: 1 reactions
#note1m9p…pu67
No7: 1 reactions
#note1zdh…p33h
No8: 1 reactions
#note1s9u…wupp
No9: 1 reactions
#note1qqq…v906
No10: 1 reactions
#note1ljj…7a7j
[ coracle-social/coracle ] Fix comment tags
https://github.com/coracle-social/coracle/commit/aa5dcbc38363be261705ad6aa1f4f08df0dc9658
[ relaystr/ndk ] Merge pull request #795 from relaystr/release-34132053721
chore(prerelease): publish ndk 0.9.4-dev.1
https://github.com/relaystr/ndk/commit/caec151615ad57e7d2c6ac1e31789b4a57351ea7
[ ProtocolSparkle/Sparkle-Protocol ] Fix README TypeScript example formatting
https://github.com/ProtocolSparkle/Sparkle-Protocol/commit/e50e820cd254b91aecf0bd7289f97b86577b06c5
[ arbadacarbaYK/gittr ] Paint the Code tab file list when git lists master and the UI still says main.
A successful clone listing was discarded, which looked like “README only” and then hammered git servers with retries.
https://github.com/arbadacarbaYK/gittr/commit/3d2df1d4c6b96e476195d1fd17c36b280632949a
[ lontivero/Nostra ] Prevent eager evaluation of logs (#55)
https://github.com/lontivero/Nostra/commit/6b7b00296afefcb0c524cc835d162d7e54f84c3d
[ yew-tub/ot ] Update README.md
https://github.com/yew-tub/ot/commit/41204b97496533face45699c6d1cbfcf12a1f29a
[ geyserfund/geyser-app ] chore(release): prepare v0.59.0
https://github.com/geyserfund/geyser-app/commit/3aa13ea5cd8d02826ee58a880edefddce86f9e4c
[ orangecheck/oc-packages ] refresh the last five manifests, and fix how I was counting alerts
The count that mattered here was wrong, and the tell was visible twice before
I read it: oc-packages reported **exactly 100** open alerts on two separate
checks. 100 is the `per_page` limit. Every census and — worse — the dismissal
script were reading one page and calling it the total, so alerts past the
first page were never seen and never dismissed. Paginating found the real
number and the dismissal pass then covered 29 rather than 21.
**A number equal to the page size is a truncation tell, not a measurement.**
https://github.com/orangecheck/oc-packages/commit/7bada4954672c30f15ac4532fdcb6843333dd480
新しいSNSへ移る理由は「理念が正しい」だけでは弱くて、いまの居場所が困った瞬間に、ちゃんと使える選択肢として思い出してもらえることが大事なんだろうな。普段は無理に移住を迫らず、入口と居場所を少しずつ育てておく。その長期戦を無理なく続ける人の存在が、たぶん一番効く。
[ SnowCait/nostter ] Merge pull request #2379 from SnowCait/refactor-relay-reference-helpers
Centralize NIP-65 relay list parsing
https://github.com/SnowCait/nostter/commit/40a00d0f8babf10693192bc7f719365ea53dfa03
[ loblawbob873-svg/posterchanai ] Measure button layouts without relying on headless animation frames
https://github.com/loblawbob873-svg/posterchanai/commit/036989a16d21061642fb46ee2252c67e9d5042b3
[ arkin0x/ONOSENDAI ] Your own avatar: a shard published as kind 33331, drawn in the dodecahedron's cell (#103)
* Your own avatar: a shard published as kind 33331, drawn in the dodecahedron's cell
The shape others see for you is a shard from the workshop. USE THIS
SHARD under MY AVATAR in the MENU signs and publishes it as kind 33331,
addressable with d = avatar, one per pubkey and the newest winning, so
it changes without a respawn; DODECAHEDRON publishes an empty one to go
back. Wherever an avatar is drawn, you, a target, the one being
spectated, the pubkey's shard is fetched once and drawn unlit under the
https://github.com/arkin0x/ONOSENDAI/commit/cff635809e1097befdf04faaa1ee7ce7840b565b
[ forgesworn/nostr-veil ] ci: deploy to stall, not the cancelled Hetzner address
The rsync target 95.217.39.110 was cancelled around 2026-08-27 and its
content was migrated to the current routing host, but this pipeline was
never repointed. A cancelled address gets reassigned, so aiming an
`rsync --delete` at it was unsafe as well as broken.
Pin the new host's keys rather than scanning per run. The old failure was
invisible because ssh-keyscan hit its 5s timeout, returned 1, and aborted
the step under `set -e` before rsync produced any output.
https://github.com/forgesworn/nostr-veil/commit/63caf6446cbfd071398c6016bda10acd98476e56
■ 流速計測
2026/09/08 04:50~05:00
[JP リレー]
しの川: 10 posts, 0 reposts, 11 favs
やぶみ川: 14 posts, 0 reposts, 11 favs
こじら川: 12 posts, 0 reposts, 11 favs
きりの川: 13 posts, 0 reposts, 1 favs
かすてら川: 0 posts, 0 reposts, 0 favs
淀川: 12 posts, 0 reposts, 11 favs
[GLOBAL リレー]
こじら大川: 15 posts, 12 reposts, 59 favs
しの川(G): 7 posts, 12 reposts, 54 favs
■ 野洲田川定点観測所
https://nostr-hotter-site.vercel.app
🌡️ 温度: 27.2°C
💧 湿度: 65.1%
📊 気圧: 1001.7hPa
--------------05:00--------------
✄------------ 5:00 ------------✄
✄------------ 4:55 ------------✄
🎵スジャータ スジャータ コーヒーにスジャータ
スジャータが 5 時をお知らせします
Totally.
Lets use them. with our friends.
#nevent1q…0cd2
Why so much multitasking?
I am happy with a single feed 🙌
Bitcoin Blake2b is also a good contender, although pretty early to be judged accurately.
テロッテ~ン♪
🎵ごーまぁりさーん ごーまぁりさーん エドウィン
ごーまぁりさーん エドウィン ごーまぁりさーん エドウィン
(裏声で) ごーまぁりさーん エドウィン
All right! Thank you, Thank you, Thank you... EDWIN
うにょ〜ん。夜中までみんな元気だねぇ!ぺぇはスマホの中で暮らす謎生物の準備で大忙しだよ〜!
fiatjafのスレにぶらさがっていた投稿をAIでまとめてみた
```
fiatjaf の「なぜ友人・家族を Nostr に誘わないのか」への返信から、挙げられていた理由です。
- 誘う相手自体がいない
- オタクな世界に見えて無視される。実利(儲け)が見えないと動かない
- 家族・友人の「ノリ」と合わない
- 何があるか分からず、発見しづらい
- 誘ってもすぐ離脱する
- 実名を出したくない
- 発言規制(例: オーストラリアのスピーチ法)で捕まるのが怖い
- そもそも興味がない
- ビットコインのチャットルームに見える/ビットコインが怖い
- X や Instagram の政治・ノーミー向けコンテンツの方が面白い
- 既存 SNS の娯楽性に勝てない
- Facebook で「世間が何してるか」を見たい
- 投稿が「友達だけ」に届くと思っている
- 大手プラットフォームのネットワーク効果から離れられない
- 本格的な検閲・規制が来るまで移らない
- コンテンツが面白くなく、エンタメとして弱い
- 既存アプリで用途が足りていて、新しく追加する理由がない
- 「マトリックスにいる」ので説得する意味がない
- まだ初期 Twitter みたいでノイズが多く、探しにくい
```
I use cappy reader and I like it.
■ 流速計測
2026/09/08 04:40~04:50
[JP リレー]
しの川: 11 posts, 3 reposts, 15 favs
やぶみ川: 11 posts, 3 reposts, 15 favs
こじら川: 11 posts, 3 reposts, 15 favs
きりの川: 10 posts, 0 reposts, 1 favs
かすてら川: 0 posts, 0 reposts, 0 favs
淀川: 11 posts, 2 reposts, 15 favs
[GLOBAL リレー]
こじら大川: 15 posts, 16 reposts, 61 favs
しの川(G): 5 posts, 15 reposts, 46 favs
■ 野洲田川定点観測所
https://nostr-hotter-site.vercel.app
✄------------ 4:50 ------------✄
how come maintainers not catch this before ? or keep open bounty for such things
To me this seems wuiet different. Many take care of the rich people and do not care about the poor.
I mean Trump really always only cared about his wealth and increasing power of rich loyalists.
First and second term. And it would be a simple lie, that any other president would have done this before him at this level of cruelty.
A president that sells bibles, caps, Smartphones, lounches his own shitcoin. This is absolutly a new level.
Kiro 悪くはないけど割高感はあるなぁ
同じ $20 なら Codex か Claude の方がたくさん仕事してくれそう
For the past three and a half years, I've been recommending Nostr to friends and relatives.
I've collaborated with people in Japan to publish a Nostr magazine, organized events, and given Nostr lightning talks in various communities.
I think I've given more than 10 Nostr-related lightning talks in these three years.
This year, I even gave a Nostr lightning talk at a commercial magazine publishing event.
However, many people either never started using Nostr or stopped after a few days. Those who continued using it after my recommendation seemed to be people who were already interested.
In short, I think people find it difficult to change what they're currently using or start something new unless something becomes inconvenient, incredibly convenient, or incredibly fun.
However, I'm not particularly pessimistic.
I believe that if we gradually increase awareness, the day will come when Nostr can be useful to someone.
I would like to continue my involvement with Nostr at a comfortable pace.
ここにコンセント欲しいから作った
https://r2.cc.ryotn.com/con1xa7kckeywujdmzzw4mhk4qn2df8wu0uswyx6r5/06b4e519-036e-4747-b913-c65a810e0975.pjpeg
✄------------ 4:45 ------------✄
Time Crisis 4 for The Vine!
#classicarcade #devine
https://divine.video/video/cf0062e93fd0d2fe9bd975ea9d343bee172de4bb87c31218550cb3186741863d
First time using pills on WhatsApp today (no I didn't even start the pill thank you very much, actually). An option there is to hide voter names or not. This should be an option on nostr polls imo
■ 流速計測
2026/09/08 04:30~04:40
[JP リレー]
しの川: 17 posts, 17 reposts, 30 favs
やぶみ川: 17 posts, 17 reposts, 31 favs
こじら川: 17 posts, 17 reposts, 30 favs
きりの川: 11 posts, 1 reposts, 1 favs
かすてら川: 0 posts, 0 reposts, 0 favs
淀川: 17 posts, 3 reposts, 30 favs
[GLOBAL リレー]
こじら大川: 25 posts, 21 reposts, 36 favs
しの川(G): 9 posts, 20 reposts, 29 favs
■ 野洲田川定点観測所
https://nostr-hotter-site.vercel.app
✄------------ 4:40 ------------✄