@hongminhee洪 民憙 (Hong Minhee) 
@cocoa甘瀬ここあ I've seen them go by before but don't have links handy
甘瀬ここあ
@cocoa@hackers.pub · 8 following · 9 followers
モジュール化されたActivityPubツールキットのapkitの作者みたいなもの。
実はMisskeyがきっかけでActivityPubに興味を持ち始めてたりしてます
Pythonista/Author of apkit. An Modularized ActivityPub Toolkit.
main (Sharkey)- @AmaseCocoa@s.amase.cc
@thisismissemEmelia 👸🏻 @hongminhee洪 民憙 (Hong Minhee) @cocoa甘瀬ここあ
FEP-844e: Capability discovery https://codeberg.org/fediverse/fep/src/branch/main/fep/844e/fep-844e.md
See also, FEP-0151 section on capability detection: https://codeberg.org/fediverse/fep/src/branch/main/fep/0151/fep-0151.md#capability-detection
Signed, a guy with links 🙂
feature-info?
まぁこれはnodeinfoのmeta使ってある程度決まったjsonを埋め込むようにすれば良さそうだけども。
こんな感じにするとか？
[
"fep:8b32",
"rfc:9421",
"protocol:activitypub"
]@cocoa甘瀬ここあ @hongminhee洪 民憙 (Hong Minhee) sorry to reply in English, but yes, there's a few FEPs along these lines, but technically you don't need nodeinfo for AP, so you wouldn't passively discover this information, unlike detecting certain properties in json-ld objects over activitypub. Feature discovery can be hard too because what features you think they have (cached) might not be the features they actually have at present, or if you're upgrading from version 1 to version 2, and you have multiple backend servers with a load balancer, you might get unpredictable results from nodeinfo as the update rolls out (e.g., node 1 gives new feature, node 2 & 3 gives old feature, you'll only get new feature 1/3 of the time and your old nodes won't be able to immediately handle new feature until you roll out the update to all nodes, which would cause unpredictable behaviour)
Hackers' Pubに興味はあるけれど、DMで招待状をお願いするのは気が引けるという方のために、Googleフォームを作成しました。メールアドレスを入力するだけで、Hackers' Pubの招待状をお送りします。たくさんのご応募をお待ちしています‼️