羽田のスターフライヤーも最果てなので罠
View quoted note →
takuya(iqbqioza)
_@iqbqioza.com
npub1taku...qwf4
I'm a frontend and backend developer based in Niigata, Japan. I built nostrfy, an engine for running Nostr relays. The internet is for everyone, not big tech.
I built a software:
nostrfy
https://github.com/iqbqioza/nostrfy
bondar
https://github.com/iqbqioza/bondar
I'm operating a relay:
wss://relay.nostrfy.org
.
貴殿におかれましては、民法第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 →
U-NEXT は3ステップで解約できるようになってた
View quoted note →
Zenn で記事を書きました。
Nostr リレーサーバ nostrfy が WebSocket イベント一斉配信86万件/秒を達成した|Zenn
p.s.
Thanks, @Matt Corallo and @Alex Gleason

Zenn
Nostr リレーサーバ nostrfy が WebSocket イベント一斉配信86万件/秒を達成した
I’m developing the Nostr relay server engine, nostrfy, and the Ditto client is extremely helpful. This is because Ditto correctly renders the “kind” fields of numerous NIPs and offers a wide range of features. I believe that creating a relay server engine that fully supports the Ditto client will result in a cutting-edge and robust solution.
nostrfy will be a cutting-edge, next-generation relay server. I’m starting to look for sponsors.

GitHub
GitHub - iqbqioza/nostrfy: High-performance Nostr relay engine written in Rust. Fast, memory-efficient, and built for modern relays.
High-performance Nostr relay engine written in Rust. Fast, memory-efficient, and built for modern relays. - iqbqioza/nostrfy
てことは香港リージョンは「まだそこまで管理されてない」でいいのかな?最近の香港と中国の「ワンチャイナポリシー」がどこまでなのか分からなくなってきた
Beijing と Hong Kong のリージョンの差は何?
中国リージョン(beijing)で Nostr リレー立てたらどうなるか試してよ
View quoted note →
わしが運用しているリレー relay.damustr.com にも流してくれない?
View quoted note →
trystero ってどうなん
View quoted note →
Nostr のここのコミュニティで Vim/Nvim 使ってる人どのくらいおるんやろ?