やばい自分のサーバーから締め出された
AmaseCocoa
@cocoa@hackers.pub · 11 following · 11 followers
日本語多め
Pythonista/Author of apkit. An Modularized ActivityPub Toolkit.
main (Iceshrimp)- @AmaseCocoa@i.amase.cc
YarukiNotFound- amase.cc
Zenn- @amasecocoa
FedLoginの認証方式
aioauth使ったOAuthの実装で詰まってるから変えるかもしれない
Thinking about building “#Fedify Studio” (tentative name)—a web-based #ActivityPub debugging & development toolkit, like a supercharged version of ActivityPub.Academy and fedify inbox command. Imagine having a proper UI for testing activities, inspecting actors, debugging federation issues… Would this be useful for other ActivityPub developers out there?
あとは全然まだ未完成だけどapkitのドキュメントみたいなものもできた
fedi-libs.github.io/apkit/
Mastodonの引用ってどういう仕様だっけ
Is htmx suitable for sns frontend, like mastodon/misskey?
(I won't a high functionality frontend, i want a simple frontend)
@hongminhee洪 民憙 (Hong Minhee) @cocoaAmaseCocoa I've seen them go by before but don't have links handy
@thisismissemEmelia 👸🏻 @hongminhee洪 民憙 (Hong Minhee) @cocoaAmaseCocoa
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"
]@cocoaAmaseCocoa @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の招待状をお送りします。たくさんのご応募をお待ちしています‼️