洪 民憙 (Hong Minhee)

@jupiter_rowland Full nomadic identity—the kind Forte and (Streams) have—is something I'd like to support in Fedify eventually. But for now, I'm focusing on the more modest goal: server-independent object identifiers that survive a server disappearing. The multi-server synchronization side of things feels premature to build out seriously until the relevant specs (FEP-ef61 itself is still DRAFT, after all) stabilize a bit more. Once the standardization catches up, I'd like to revisit.

Thanks for the context on @mikedev and the history here—I wasn't fully aware of how deep the roots of nomadic identity go.

@silverpill

@shimon1024 おお…すごいですね！素晴らしいです！ぜひお会いしていろいろと学ばせていただきたいです。

ところで、今回の東京行きにご一緒するHaze Leeさん（@nebuleto）も同席してもよろしいでしょうか？（日本語は話せます）

@shimon1024 おお、モンゴル文字対応ですか…興味深いですね！モンゴル文字については浅学ですが、もっと深くお話ししたいです。私は自作のActivityPub実装であるHolloに、漢字混じりの韓国語（所謂「国漢文混用体」）に振りハングル（振り仮名のハングル版）を付ける機能を実装したことがあります。もしよろしければ、DMで具体的なお約束を決めませんか？

@silverpill Thanks for the clarification! I think I was overcomplicating it—I was imagining a scenario where gateway A forwards a received activity to gateway B, and wondering how B could trust that A hadn't tampered with it. But of course, since portable activities must carry FEP-8b32 integrity proofs, the authenticity of the activity itself can always be verified regardless of which server forwarded it. No separate gateway-to-gateway authentication mechanism is needed.

And the gateways-based trust makes sense now as a mechanism specifically for unauthenticated collections—if a collection comes from a server listed in the actor's gateways array, proof verification can be skipped; otherwise it's required.

Jiwon (@z9mb1), one of our core contributors, drew a Fedify dino! How cute!

https://oeee.cafe/@z9mb1/2b5b0baf-466b-4c65-a1e0-d3588f0666f4

Fedify dino for notice

https://kre.pe/CKwN This is a paid request :) fediverse logo was attached afterwards.

Started laying out a rough plan for implementing FEP-ef61: Portable Objects in #Fedify—server-independent #ActivityPub identities backed by #DIDs, multi-server replication, and client-side signing. It's going to be a long road (13 tasks across 5 phases, with a few open questions that need answering before we even begin), but I think it's worth doing right.

https://github.com/fedify-dev/fedify/issues/288#issuecomment-3971459585

#fedidev #fediverse #PortableObjects

I have so much fun tin the fediverse, this is a very cozy place.

@hyunjoon 그냥 字體(자체)가 다른 건데… 어느 쪽이 좀 더 《康熙字典(강희자전)》 字體(자체)에 가깝냐를 基準(기준)으로 쓰고 있습니다. ㅎㅎㅎ

國漢文(국한문)으로 韓國語(한국어) 쓸 때 「産(산)」 代身(대신) 「產(산)」을 쓰는 便(편). 비슷하게 「畵(화)」 代身(대신) 「畫(화)」를 쓴다거나, 「査(사)」 代身(대신) 「查(查)」를 쓴다거나 하는 게 있음. 아무도 神經(신경) 안 쓰겠지만… ㅋㅋㅋ

슬슬 Fedify 스티커도 좀 더 生產(생산)해야…

Here's a cat drawn by @hongminhee that you can look up here by its URL to interact with https://oeee.cafe/@hongminhee/ed323b59-557c-4843-aad2-5a83df0e3006

RE: https://planet.moe/@oeee_cafe/115615511184864588

Oeee Cafe is a Korean federated community drawing app that recently launched mobile apps on iOS and Android. You can follow users there from here in the fediverse already but not sure if you can submit drawings remotely yet.
#fedidev

Instead of using git as a database, what if you used database as a git?

https://nesbitt.io/2026/02/26/git-in-postgres.html

I making auto-translated FEP document for Japanese, trying local models...

@liaizon @julian @rick To be honest, I'm not really waiting for FEP standardization. It's more likely that the task of adding the GTS interaction policy vocabulary to Fedify will be included in the roadmap for the next version. (Or maybe the one after that.) Only after that prerequisite work is done can support for Mastodon-style quote posts be added to Fedify, I think.

@silverpill Ah, I see. In that case, it would be great if canonical permalinks could be decided for the FEP documents first!

@liaizon @rick We have an issue for this!

https://github.com/fedify-dev/fedify/issues/452

There's now a proper rendered web interface for FEPs at https://fediverse.codeberg.page/fep/fep/*/, which is much nicer to read than the raw Markdown source on Codeberg. But the canonical permalink, https://w3id.org/fep/*, still redirects to the Markdown file rather than the rendered page.

Would it make sense to update the w3id.org redirect to point to the rendered version instead? It seems like the better experience for anyone following a FEP link, and arguably what a “permanent” link should resolve to—something human-readable.

I'm not sure who manages the w3id.org/fep/ redirect configuration. (It lives in the perma-id/w3id.org GitHub repo, so it would just be a PR, but I'd want to get community consensus first rather than just send one in unilaterally.)

#fedidev #fep #fediverse #ActivityPub

There's now a proper rendered web interface for FEPs at https://fediverse.codeberg.page/fep/fep/*/, which is much nicer to read than the raw Markdown source on Codeberg. But the canonical permalink, https://w3id.org/fep/*, still redirects to the Markdown file rather than the rendered page.

Would it make sense to update the w3id.org redirect to point to the rendered version instead? It seems like the better experience for anyone following a FEP link, and arguably what a “permanent” link should resolve to—something human-readable.

I'm not sure who manages the w3id.org/fep/ redirect configuration. (It lives in the perma-id/w3id.org GitHub repo, so it would just be a PR, but I'd want to get community consensus first rather than just send one in unilaterally.)

#fedidev #fep #fediverse #ActivityPub

日本かアジア圏でActivityPubとかオープンデータとかシビックテックのカンファレンスやイベントがあればちょっとずつ参加していきたいな。英語もまた話せるように鍛え直さないと…

シビックテックで取り組んでる課題をチームの皆で話してて、データはJSON-LDで記述したほうが良さそうとか、いずれシェア機能が欲しいねとか、コンテンツはオープンデータ化を前提としてデータの帰属は市民や地域コミュニティとしたいね等々を話し合う中で、「なんか…ActivityPub感…」と思った。
ActivityPubをオープンデータの流通・蓄積・活用の際に用いている取り組みとかって、あるのかな？
Open GLAMなどでありそうな気もするけど、どうなんだろ。

AIがバイナリを吐きだすとかの妄言が意味わからないのは、効率の問題もあるけど(バイナリより高級言語のほうが情報のせられる)、開いた状態のものを閉じた状態に戻そうとするからだし、たぶん並列AIに対して関心がもてないのもそこで、AIが理解すればいいだけになると過程全体が閉じてるからだとおもう。

ソフトウェアがソフトなのは、その生産過程が開かれた状態のままだから。これが近代の製品と違う。

成果物と成果物を生成するシステムがある意味交換可能で可視的というのは、現代の特徴かもしれない

Starting with Deno 2.7, you can now use the Temporal API without the --unstable-temporal flag!

https://deno.com/blog/v2.7

@hypolite That last point about oxygen in the room is, I think, the most important thing you've said in this whole exchange—and I find myself largely agreeing with it. The current concentration of resources around a handful of private models is itself what makes the political organizing you'd need for a public alternative so difficult. We agree on the diagnosis more than it might appear.

Where I'd push back, gently, is on the sequencing. “We can't build the structures now, so we wait for the collapse” assumes that the aftermath will be more legible than it probably will be. The people who made billions, as you say, won't go silently—and they'll have a head start on shaping whatever comes next. I'd rather that there be some idea of what “next” should look like, articulated now, even imperfectly, than have that conversation start from scratch in the wreckage.

On the hubris point: I share your discomfort with “built to create God.” But I'd distinguish between the AGI ambitions of specific companies and the underlying technology. The former is what I'd most want to see deflated. What survives that deflation is the open question.

Today I found

• Stegodon #stegodon
• Hollo #hollo #hollosocial
• snac2 #snac2

I have archived the apmodel repository. While developing apkit, I encountered the problematic aspects of apmodel, so I plan to redesign it. This does not mean I intend to abandon apkit.