洪 民憙 (Hong Minhee)

Es bedarf Zeit und Erfahrung, bevor der Arbeiter die Maschinerie von ihrer kapitalistischen Anwendung unterscheiden und daher seine Angriffe vom materiellen Produktionsmittel selbst auf dessen gesellschaftliche Exploitationsform übertragen lernt.

—Karl Marx, Das Kapital, Bd. I, Kap. 13, Abschn. 5

@hongminhee I'm reading this thread as a relative noob, but what I see again and again: almost no one "properly" implents #ActivityPub largely because #JSONLD is hard but also because the spec itself is unclear. Most people who get stuff done have to go off-spec to actually ship.

This seems a fundamental weakness of the #fediverse - and that disregarding the limitations coming from base architecture. Seems to pose a mid/long-term existential threat.

What can we do to help improve things?

@mariusor It's barely documented, but has worked well so far!

https://github.com/fedify-dev/fedify/tree/main/packages/vocab-tools

@silverpill @mariusor But if you omit @context, wouldn't it fail to work correctly in some implementations that rely on a JSON-LD processor? Fedify is actually one of those cases.

‘급진적으로 존재하기’에서 시각장애인 천문학자가 음향화 기술을 활용해 다시 연구에 복귀한 이야기를 읽으면서 문득 장애인들에게 최근의 AI 기술은 어떤 영향을 미치고 있을까 궁금해졌다. 삶에 변화가 생겼다고 느낄지. 이조차도 장애인들은 피해 갔다고 느낄지.

@silverpill @linos That's good to know! Thanks!

@kodingwarrior You might be interested in this?

@hongminhee I don't know about Mobilizon but @linos considers adding related features to the Events FEP

https://codeberg.org/linos/fep/issues/18

@computersandblues Actually, this question came up when my acquaintance, @kodingwarrior, mentioned wanting to use a fediverse-based event hosting service for an event he's organizing, which is when we started talking about Mobilizon. The main scenario we envisioned was allowing only those who have paid the participation fee to RSVP. And, of course, they would need to be refunded if they cancel.

@kodingwarrior, are there any other requirements besides this?

어떤 點(점)들을 어필할 수 있을까?

• 聯合宇宙(연합우주)를 이루는 소프트웨어 自體(자체)가 大部分(대부분) 오픈 소스이다?
• 海外(해외)의 많은 오픈 소스 소프트웨어 開發者(개발자)들이 聯合宇宙(연합우주)를 쓰고 있다?

또 뭐가 있을까…?

早晩間(조만간) 소프트웨어 엔지니어 커뮤니티로서의 聯合宇宙(연합우주)를 어필하는 韓國語(한국어) 글을 하나 써 봐야겠다.

Ishmael Ensemble - Search For Peace
#JazzDeVille #Jazz #NowPlaying #IshmaelEnsemble

Does Mobilizon currently support hosting paid events that charge a participation fee? If not, is there a roadmap for a future feature update that will make this possible?

#Mobilizon #fediverse

@evan I don't remember exactly, but I think I came across it while doing research before developing Fedify. I probably didn't use it because the TypeScript type definitions were missing. In the end, I ended up making something similar in Fedify anyway.

아무래도 時差(시차) 適應(적응)에 完全(완전)히 失敗(실패)한 듯… 이제 일어났다.

@lkanies @jalefkowit To be honest, I'm not too sure myself. I just know that JSON-LD was originally planned as a foundation for the Semantic Web. I can only guess that if ontology is useful in a certain area, then JSON-LD would probably be useful there too.

I never thought this little rant of mine would be read by so many people. 😲

@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.