洪 民憙 (Hong Minhee)

@chomu.dev JSON-LD를 그냥 JSON으로 다뤄도 괜찮다고 보는 사람이 많은 것 같아요.

@chomu.dev JavaScript는 이미 JSON-LD 具顯(구현)이 있어서 Fedify는 안 그래도 그걸 가져다 쓰고 있어요 ㅋㅋㅋ

@douginamug Thank you so much for recognizing my hard work!

I have deeply mixed feelings about #ActivityPub's adoption of JSON-LD, as someone who's spent way too long dealing with it while building #Fedify.

Part of me wishes it had never happened. A lot of developers jump into ActivityPub development without really understanding JSON-LD, and honestly, can you blame them? The result is a growing number of implementations producing technically invalid JSON-LD. It works, sort of, because everyone's just pattern-matching against what Mastodon does, but it's not correct. And even developers who do take the time to understand JSON-LD often end up hardcoding their documents anyway, because proper JSON-LD processor libraries simply don't exist for many languages. No safety net, no validation, just vibes and hoping you got the @context right. Naturally, mistakes creep in.

But then the other part of me thinks: well, we're stuck with JSON-LD now. There's no going back. So wouldn't it be nice if people actually used it properly? Process the documents, normalize them, do the compaction and expansion dance the way the spec intended. That's what Fedify does.

Here's the part that really gets to me, though. Because Fedify actually processes JSON-LD correctly, it's more likely to break when talking to implementations that produce malformed documents. From the end user's perspective, Fedify looks like the fragile one. “Why can't I follow this person?” Well, because their server is emitting garbage JSON-LD that happens to work with implementations that just treat it as a regular JSON blob. Every time I get one of these bug reports, I feel a certain injustice. Like being the only person in the group project who actually read the assignment.

To be fair, there are real practical reasons why most people don't bother with proper JSON-LD processing. Implementing a full processor is genuinely a lot of work. It leans on the entire Linked Data stack, which is bigger than most people expect going in. And the performance cost isn't trivial either. Fedify uses some tricks to keep things fast, and I'll be honest, that code isn't my proudest work.

Anyway, none of this is going anywhere. Just me grumbling into the void. If you're building an ActivityPub implementation, maybe consider using a JSON-LD processor if one's available for your language. And if you're not going to, at least test your output against implementations that do.

#JSONLD #fedidev

apparently Mobilizon 5.2.0 broke JSON-LD stuff for the few AP implementations that care, without any announcement other than ‘bugfix: Replace joinmobilizon.org by mobilizon.org’

Thanks @_elena for taking a photo of me!

📸 6: #FOSDEM Social Web devroom pics – @hongminhee of @fedify

video: https://ftp.belnet.be/mirror/FOSDEM/video/2026/h2215/KSEUZT-fedify.mp4

@hongminhee it's no biggie - I doubt there's many projects that accept and thread correctly for this corner case - I just like to use this conversation as a test for threading. :D

Btw, I don't know if it's relevant to #fedify but I have the logic for threading (based on JWZ's old email threading algorithm) in the ONI project: https://git.sr.ht/~mariusor/oni/tree/master/item/src/js/items-threading.js

@moreal

@mariusor Oh, yeah, apparently @moreal should fix this!

Recently, @moreal built ap-thread-reader, a tool that displays threaded posts on a single page. Works with any ActivityPub platform, not just Mastodon.

Try it at https://ap-thread-reader.fly.dev/.

Built with Fedify and released as open source: https://github.com/moreal/ap-thread-reader.

More details at https://blog.moreal.dev/2026/02/ap-thread-reader-introduction/index.en.html.

@thx 感謝(감사)합니다…!

올해는 放通大(방통대) 中語中文學科(중어중문학과)에 志願(지원)했고, 日本語(일본어)와 英語(영어)로 發表(발표)도 志願(지원)했다. 卽(즉), 올해에는 3個(개) 言語(언어)와 익숙해져야 한다는 뜻이다…

@happyborg Setting GitHub aside, I just can't understand why npm still isn't a non-profit foundation. And why the JavaScript community just lets it happen.

飛行機(비행기)에서 몇 가지 技術(기술) 팟캐스트를 들으며 느낀 것 하나는… 韓國(한국) 技術(기술) 팟캐스트는 言語(언어)가 整頓(정돈)되어 있지 못하다는 것. 말투나 發音(발음) 같은 層位(층위)를 얘기하는 게 아니라, 생각 自體(자체)가 뻔하고 그걸 듣고 뭔가 배울 點(점)이 稀薄(희박)하달까? 막말로 그냥 여느 職場(직장) 同僚(동료)와의 雜談(잡담)과 크게 다르지 않은 느낌이다. 콘텐츠가 잘 準備(준비)되지 않았다고 봐야 할 지.

@bart Yeah, npm and GitHub are owned by Microsoft…

I came across a user research study by @theverge that has the fediverse listed as the top result for the question "Which of the following online spaces do you feel connected..?"

full 20mb pdf if you want to see more of the report https://assets.hyper.media/ipfs/bafybeid3uwueopzrurc7haidrvcoijz7d4jtag72c7grlve54v6k6ugdwa?filename=58bba982bba477baeae7880b939ead15.pdf

어떤 놈이 입춘첩을 입춘대길(立春大吉)로 쓰려다 입춘대설(立春大雪)로 잘못 쓴 모양이다. 용하기는 하다.

그래도 이番(번)에 유럽 다녀오면서 좋았던 것 中(중) 하나는 英語(영어) 會話(회화)에 對(대)한 負擔(부담)이 많이 줄었다는 것. 實力(실력)이 는 건 아니지만, 눈치를 훨씬 덜 보게 되었달까? 15年(년) 前(전)쯤 美國(미국) 東部(동부)에 갔을 때와 달리 사람들이 나에게 훨씬 親切(친절)했던 것과 關係(관계)가 있는 것 같다.

@teleclimber It looks like JSR is trying to add GitLab login support recently, but the options are still too limited.

One of the reasons our project can't move to a CI/CD service other than GitHub Actions or a forge service other than GitHub is precisely because of npm and JSR's dependency on GitHub. If you want to use trusted publishing for your JavaScript packages on npm or JSR, you are forced to use GitHub and GitHub Actions. This issue is likely not unrelated to the fact that npm and GitHub are operated by the same company.

@tirr 그럼 이제는 두벌式(식) 쓰고 계시나요!?

유럽 다녀오고 나서 感氣(감기)에 걸렸는데, 이게 어디서 옮은 건지, 아니면 베를린 寒波(한파) 때문에 걸린 건지… 🤧

@hongminhee I wasn’t able to join you talk on Tuesday but the slides inspired me to finally try @fedify 🙌
What a cool library thank you so much for building it. It was amazingly easy to get going.

Got inspired by @liaizon’s posts about groups earlier this week:
https://groups.louismerl.in/groups/test

Source code incoming.

Finally landed in Incheon! What a long journey…

We've now a forum on activitypub.space for the Trust and Safety Taskforce: https://activitypub.space/topic/103/activitypub-trust-safety-taskforce-forum

I'm working on getting that federated, so hopefully that'll encourage more of you to join in on the discussions.

Heya! 🥳 Super thrilled to announce XenoAtom.Terminal.UI is out in public preview: https://xenoatom.github.io/terminal/ 🚀

It's a modern, reactive retained-mode terminal UI framework for .NET - composable visuals, binding-first state updates, proper measure/arrange layout, and a fast cell-buffer renderer with alpha-blended theming (truecolor 🎨 terminals look gorgeous!).

Demos + docs are live - feedback welcome! 🙌

#dotnet #csharp #tui

Contrary to what many people are saying, I don't think this Rust code was stolen from someone else…

It's a really impressive work of Claude Opus 4.6: A C compiler written in Rust which is capable of compiling a booting Linux kernel and passing their test suites include PostgreSQL and SQLite. 😳

https://github.com/anthropics/claudes-c-compiler

I miss FOSDEM already. I can't wait for next year's FOSDEM!