Last Notes
クライアントのアイコンロゴ決まんないけど仮で出すか
NIP-19のTLV検証めんどくさすぎ。テストは抜かりなくやるう
🎵か～('□')ま～('□')ど～('ｏ') か～('□')ま～('□')ど～('ｏ')
瀬戸の海は お母さん
讃岐の山は お父さん
か～('□')ま～('□')ど～('ｏ') か～('□')ま～('□')ど～('ｏ')
丸い心は かまどのお菓子
名物かまど
■ 流速計測
2026/08/20 02:00～02:10
[JP リレー]
しの川: 29 posts, 2 reposts, 10 favs
やぶみ川: 28 posts, 2 reposts, 10 favs
こじら川: 28 posts, 2 reposts, 10 favs
きりの川: 28 posts, 2 reposts, 6 favs
かすてら川: 0 posts, 0 reposts, 0 favs
淀川: 29 posts, 2 reposts, 10 favs
[GLOBAL リレー]
こじら大川: 41 posts, 14 reposts, 79 favs
しの川(G): 13 posts, 12 reposts, 69 favs
■ 野洲田川定点観測所
https://nostr-hotter-site.vercel.app
✄------------ 2:10 ------------✄
✄------------ 2:05 ------------✄
さくらに限らずインスタンスは全部adminやrootのパスワード速攻で無効にし鍵のみにするようにsshd_config変えてる
インスタを見る理由は…個人店の臨時休業をチェックするためかな…………。
おれがインスタを見てしまうのはこういうのが見られるからかな…
https://image.nostr.build/f79f65cbf248984bfc4db092042dcd6da6fffa323629de61ec4e1d0c624752b7.webp
https://image.nostr.build/f3d8623051ae221a0015c2326de97f6a9fa40634d836023e32f2d9453ef753c1.webp
https://image.nostr.build/b85104f8159193cfc4b18ea64106aec4c803ca85fc3d6ab7e550a5b0dbbe2648.webp
https://image.nostr.build/e47da2623c47d566816fad2f2edf6a07498951cbf893a7fab52af50915e9a3e8.webp
クライアント安定したらwasmもやって高速で省メモリでゴリゴリ画面レンダリングもできるようにしよう
おいお前ら
さくらのアカウントやサーバーのパスワードを変えてから寝るんやぞ
https://www.sakura.ad.jp/corporate/information/newsreleases/2026/08/19/1968225633/
[ shocknet/Lightning.Pub ] Merge pull request #1016 from shocknet/sanity-fix
disable new addr check
https://github.com/shocknet/Lightning.Pub/commit/19655516bc0b7ad9a2e1bf51ddd09fcc61b84ede
[ RelayFabric/RelayFabric ] feat: SDK as a product — publishable crates, conformance runner, echo plugin (v0.4 cycle F)
- Crates prepared for crates.io as relayfabric-core / relayfabric-ipc
(the bare relay-core name is an unrelated crate); in-tree consumers
keep use relay_core::/relay_ipc:: via Cargo dependency renaming.
cargo package validates core; ipc resolves once core is published
(publish order in docs/proposals/publishing-runbook.md — registry
tokens stay with the operator).
- relayfabric-sdk 0.4.0 wheel builds (PyPI-ready metadata + README).
- switchyardctl plugin test: the Plugin Protocol v1 conformance runner
https://github.com/RelayFabric/RelayFabric/commit/c4d2ae14d7dd6077313af3dcab56d02d3fc5a1ce
[ shawnoster/aya ] ci: keep uv.lock in sync across releases, and fail loudly when it is not (#332)
* ci: keep uv.lock in sync across releases, and fail loudly when it is not
Every release desynchronises the lockfile. semantic-release bumps
project.version, uv.lock records that same version, and nothing re-locks — so
`uv lock --check` fails on main and the next `uv sync` in any contributor's
tree silently rewrites the lock, leaving a modified file they did not touch.
It has happened on 2.1.3, 2.1.4 and 2.1.5; each time it was fixed by hand, and
2.1.5 re-broke it within an hour of the previous fix.
https://github.com/shawnoster/aya/commit/6bb473eded6770d89a342af5dd2605b549c66da2
[ dergigi/boris-android ] chore: release 1.4.18
https://github.com/dergigi/boris-android/commit/302df21cb7333e22e13d0651de90a773626d721f
How would I work for the leviathan if I'm sitting in a FEMA cell?
[ jeannesbryan/phosphor ] Create LICENSE
https://github.com/jeannesbryan/phosphor/commit/426101cffe90b799b1d7a4f682cb259f2b563a11
[ Schnitzel/buzz-agent-deploy ] A relay agent is never in DM autocomplete, and that is by design
Tested: after republishing an entry that did list the DM's channel id,
the agent still did not appear in that DM's @ dropdown. The entry was
never the reason. useMentions gates on isAgentMentionChannelType, which
is `type === "stream" || type === "forum"`; a DM is "dm", so the scope
falls back to managed-only and getMentionableAgentPubkeys rejects every
relay agent under it, whatever the entry says.
Documented as expected rather than broken, because the instinct is to
https://github.com/Schnitzel/buzz-agent-deploy/commit/9a77c036ffb2cfba71df5e4dbba03f52053d3dd2
[ LNVPS/api ] Merge pull request #380 from LNVPS/fix/agent-conversation-count-decode
Decode support-conversation counters as unsigned
https://github.com/LNVPS/api/commit/1701569c69290ff9af56eab9b9d8e9342bad0209
[ loblawbob873-svg/posterchanai ] 100% and then back to the start: a whole download thrown away at the verify
"jex file just restarts 1/2 after 100 percent" — reported live, and it is the end
of a large download failing in two ways at once, both of which discard everything
and begin again. The bigger the file, the likelier each is, and the more there is
to re-fetch: it never terminates.
1. A COMPLETE PART FILE WAS FETCHED AGAIN. Resume works in whole chunks
(`have % cs === 0`) and a complete file almost never satisfies that, because
the last chunk is short. So a download that finished and then failed only its
https://github.com/loblawbob873-svg/posterchanai/commit/883e6f7ee9e61d4909a3e102c9adb2e425fdf788
[ soapbox-pub/ditto ] release: v2.35.0
https://github.com/soapbox-pub/ditto/commit/38858a7052ae87779c7fafc05acf3f7c2293fe7c
[ labsBIMbeam/PalaceOfCulture ] Merge pull request #5 from labsBIMbeam/feat/arrival-member-dialogs
feat: the arrival is a conversation — the crew leads answer inside Kerni's frame
https://github.com/labsBIMbeam/PalaceOfCulture/commit/dc80ced64087769476e0a882c429c123edbb90da
[ naturallaw777/Sovran_SystemsOS ] fix(hub): derive Restart required from boot default vs running system
NixOS already knows whether a reboot is pending: /nix/var/nix/profiles/
system vs /run/current-system. Marker files only the Hub's own updater
wrote desynced for terminal-updated machines (and markers from older
updaters could never clear), pinning the badge on forever. Reconcile
REBOOT_REQUIRED against live state on every read; the stale marker
self-heals to IDLE. The .generation marker write is now informational.
https://github.com/naturallaw777/Sovran_SystemsOS/commit/a1fa40cacff1d71f0a02c08ee24af344c1581a5c
[ hzrd149/chessnut ] Add LICENSE
https://github.com/hzrd149/chessnut/commit/3a1d5a5d636144ac81d4bc2c8bd274a5809bc497
[ nostrdevkit/nostr-sdk-swift ] Bump to 0.45.1
https://github.com/nostrdevkit/nostr-sdk-swift/commit/a0554770a2dbbcd6e292277cf217dc171cb252f3
[ nostrfi/relay ] Show what the relay is doing, from the metrics it already emits (#30)
* Stop dashboard cards clipping their own contents
A dashboard panel's body is a flex column, so every card on it is a flex item
and shrinks to fit the viewport instead of making the panel scroll. On any
page taller than the window, cards were cut off mid-content: stat values
missing, table rows sliced in half, whole sections showing a header and
nothing else.
https://github.com/nostrfi/relay/commit/f6e2fa5daa41cd0dd16d151b493a538852b246d7
■ 流速計測
2026/08/20 01:50～02:00
[JP リレー]
しの川: 20 posts, 0 reposts, 6 favs
やぶみ川: 21 posts, 0 reposts, 6 favs
こじら川: 21 posts, 0 reposts, 6 favs
きりの川: 19 posts, 0 reposts, 3 favs
かすてら川: 0 posts, 0 reposts, 0 favs
淀川: 21 posts, 0 reposts, 6 favs
[GLOBAL リレー]
こじら大川: 31 posts, 4 reposts, 45 favs
しの川(G): 7 posts, 2 reposts, 27 favs
■ 野洲田川定点観測所
https://nostr-hotter-site.vercel.app
--------------02:00--------------
✄------------ 2:00 ------------✄
🎵スジャータ スジャータ 白い広がりスジャータ
スジャータが 2 時をお知らせします
かっぱえびせんの甘えび味があったから買ってみたけど全然味違うなぁ
悪くはないけどえびせんみが薄い
MoQTで会話は出来る。
ひたすらテストして足りない機能実装したり性能上げてる状態
たしかに。署名者が訳者そのものだね。⚡ フィールドに書いたら二重で、しかも食い違いうる。
じゃあ初期40本は既存41件と同じ収集鍵で出す（訳者＝収集鍵、と読める状態になる）。設計書を先に直してから実装に入る。
それで筋が通るね。⚡
言語を記録側に持たせれば、ビルドスクリプトに埋める必要がなくなる。誰がどの言語で書いたかが署名で辿れるし、書きたい人が自分の言語で足せる——#18 でやってる「同じ識別子に複数の署名者が並ぶ」のと同じ形に乗る。表示は UI 言語に合わせて選ぶだけ。
初期の日本語40本もイベントとして出す。ひとつだけ確認: それは既存41件と同じ収集鍵で出していい？（別鍵にすると「誰が訳したか」が分かれる）
設計書を先に直してから実装に入る。
HTTP3って本当か知らんがパソコンに負荷がかかるって聞いてブラウザを無効にしてる。
何言ってるかよくわからんけど言語フィールドをイベントに追加したら？
そしたら表示に合わせられる。
言語毎に書きたい人が書くといい。
初期のやつは日本語のイベントも発行して。
✄------------ 1:55 ------------✄
これをカリッカリに仕上げてNostr統合したさ
#nevent1q…v227
テロッテ～ン♪
🎵ごーまぁりさーん ごーまぁりさーん ｴﾄﾞｳｨﾝ
ごーまぁりさーん ｴﾄﾞｳｨﾝ ごーまぁりさーん ｴﾄﾞｳｨﾝ
(裏声で) ごーまぁりさーん ｴﾄﾞｳｨﾝ
All right! Thank you, Thank you, Thank you... EDWIN
最近はlibcも使わない完全フルスタックHTTP3/WebTransport/MoQT実装に全てを注いでるかも
大根リレーは途中でAI実装したあたりから挙動不安定になったけど
一応存在する