悲報: Damus は kind 1111 対応する気なさそう(ソースは僕の投稿のリプ)
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 relays:
wss://relay.nostrfy.org
wss://whois.nprofile.me
.
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 →
Is about a scammer Damus Airdrop?
View quoted note →
Zenn で記事を書きました。
Nostr リレーサーバ nostrfy が WebSocket イベント一斉配信86万件/秒を達成した｜Zenn
p.s.
Thanks, @npub185h9...wrdp and @Alex Gleason
Zenn
Nostr リレーサーバ nostrfy が WebSocket イベント一斉配信86万件/秒を達成した
I'm stepping away from GAFAM too.
Switzerland's Federal Government is Replacing Microsoft on 3,000 Computers
It's FOSS
Switzerland's Federal Government is Replacing Microsoft on 3,000 Computers
This is the pilot phase, with 3,000 workstations moving away from Microsoft 365. The federal administration has over 54,000 computers.
GM
日本語訳めんどくさいので
View quoted note →
Japanese guys in Nostr are talking about the muscles around the anus but they're also talking about asshole and shit things. Just I'm in the toilet and going to say goodbye to my shit. This is Nostr. This is the Internet everyone really wants. It is a good alternative to big tech.
気がついたら肛門の話見逃してた。インターネットはこういうのでいいんだよな。
スレッズ面白すぎてアンインストールした
レスしてる人実在してる人？
View quoted note →