もう少ししたら nostrfy v0.1.10 リリース予定。 ・たくさんの細かい NIP 違反を修正（普段使いでは気づかないレベル） ・エラーは anyhow に切り替え ・10万同時接続でも確実にデリバリー👍 ・NIP-42 完全準拠（プライバシー強化） ・リレーサーバエンジンレベルで改ざん署名拒否 ・ようやくNIP-29完全準拠（グループ） その他100コミット修正

ピクセルアートすき

GM

GN

ねむ

寒すぎて、

GM

GN

羽田のスターフライヤーも最果てなので罠 View quoted note →

わろす View quoted note →

貴殿におかれましては、民法第555条に規定される諾成・双務・有償契約たる売買契約を締結する旨の確定的な意思表示をなし、所定の金銭債務すなわち反対給付義務を自ら負担してまで、当該目的物たる特定物に対する排他的支配権である所有権の移転的承継を企図された次第でありますが、かかる財産権移転を目的とする債権行為および物権行為の効力発生を欲するに至った内心の効果意思の形成過程において、いかなる事実的ないし経済的インセンティブが決定的な誘因として作用したのか、仮に民法第95条1項2号所定の動機の錯誤が問題となり得る事案と仮定した場合において、当該動機が法律行為の基礎とされていることが黙示的であれ表示されていたと法的に構成し得るだけの特段の事情が存在したのか否かを含め、その実体的真実を構成するに至った経緯につき、論理的整合性を伴う詳細な釈明を求めます。(聞いてることは同じ) View quoted note →

悲報: Damus は kind 1111 対応する気なさそう(ソースは僕の投稿のリプ)

This is just my personal opinion, but I believe the biggest reason developers and client apps should support ⁠kind: 1111⁠ is that it drastically reduces timeline noise and enables a unified commenting experience across all types of content🔥 Specifically, here are four reasons why I highly recommend supporting it: 1. Clear separation of the main feed and comments Currently, both regular posts and replies are created using ⁠kind: 1⁠. As a result, the main timeline is often flooded with back-and-forth conversations between other users. Supporting ⁠kind: 1111⁠ allows the system to clearly distinguish between standalone posts and comments, creating a much cleaner and more readable timeline for users. 2. Generic comments for all types of content While ⁠kind: 1⁠ is primarily intended for short text exchanges, ⁠kind: 1111⁠ is designed as a universal commenting standard. It allows comments to be attached to any type of content using the same logic, whether it's long-form articles (⁠kind: 30023⁠), videos, badges, files, or even external URLs. 3. Simplified thread structure Traditional ⁠kind: 1⁠ replies often cause compatibility issues (like broken thread UI across different clients) due to the complex rules for specifying ⁠e⁠ tag ⁠root⁠ and ⁠reply⁠ markers. ⁠kind: 1111⁠ simplifies this by clearly defining what the comment is responding to, making it much easier for developers to implement and render threads properly. 4. Reduced bandwidth and relay load When a client needs to load only the comments attached to a specific post, the REQ sent to the relay becomes much simpler. Fetching only the necessary data reduces network traffic and improves overall app performance. If Damus supports ⁠kind: 1111⁠, I imagine comments would load even faster than they currently do when opening a post's detail view. Furthermore, since many other clients already support and publish ⁠kind: 1111⁠ events, Damus users are currently missing out on these comments and are forced to switch to other apps to read them. These are my thoughts on why it would be great to see this implemented. Conversely, I would genuinely love to hear your perspective and any technical or design reasons you might have for holding off on it🙏 View quoted note →

Awesome! Do you have any plans to support kind 1111 show comments and publish comment as kind 1111? Or can I configure arbitrary another Blossom image uploader? View quoted note →

GM

あ、めっちゃ面白そうなの思いついた。徹夜する

アプリの挙動によって kind 10002 壊してしまうな。完全同期せず空で publish してしまうやつある

面白い。これ nostrfy をP2P ピア検索に使えばもっといけそう View quoted note →

Oh v3 is coming

ngit documentation

v3 launches | ngit

See what shipped across ngit v3, ngit-grasp v3, ngit-ci 0.1, and GitWorkshop v4.