洪民憙 (Hong Minhee)

@hongminhee@hollo.social · 1031 following · 1580 followers

An intersectionalist, feminist, and socialist living in Seoul (UTC+09:00). @tokolovesme's spouse. Who's behind @fedify, @hollo, and @botkit. Write some free software in #TypeScript, #Haskell, #Rust, & #Python. They/them.

서울에 사는 交叉女性主義者이자 社會主義者. 金剛兔(@tokolovesme)의 配偶者. @fedify, @hollo, @botkit 메인테이너. #TypeScript, #Haskell, #Rust, #Python 等으로 自由 소프트웨어 만듦.

#國漢文混用體 #한국어 (#朝鮮語) #English #日本語

Website	GitHub	Blog	Hackers' Pub
https://hongminhee.org/	https://github.com/dahlia	https://writings.hongminhee.org/	https://hackers.pub/@hongminhee

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to dansup's post

@dansup Isn't Matrix enough for you? 😅

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Did you know there's a community space for #Fedify, #Hollo, #BotKit, and other Fedify ecosystem projects?

Whether you have questions, want to share what you're building, or just want to hang out with fellow fediverse developers—come join us!

Matrix: #fedify:matrix.org
Discord

Danielle Foré

@danirabbit@mastodon.online · Reply to mizblueprint's post

@mizblueprint that’s not the point though. She wants to participate in the world and discover new things outside her bubble, but only when those things don’t make her uncomfortable. That’s the point

Danielle Foré

@danirabbit@mastodon.online

Thinking about how a white woman recently told me she was specifically trying to get her Instagram algorithm to never show her anything political. And isn’t that just the whole problem summed up right there

dansup

@dansup@mastodon.social

I'm not just working on @loops, @fedidb, @webintents, @activityrank, and other initiatives.

I'm also quietly rebuilding @pixelfed, preparing it for a major release that solves every bug and issue you've ever had.

It's not easy, or quick. I have to redesign and rewrite every page, including the admin dashboard.

But trust me, it will be worth the wait.

If you run a Loops server, you know what I mean 😉

#Pixelfed

ALT text details

Pixelfed Admin Dashboard Collections preview

ALT text details

Pixelfed Admin Dashboard Search preview

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I wish more free/open source software developers got paid for their work.

Mirko Swillus

@mechko@chaos.social

Dear FOSS maintainers,

here’s a list of funding programs currently accepting proposals for maintenance work:

Codeberg: https://codeberg.org/mechko/awesome-maintainer-funding

GitHub: https://github.com/mechko/awesome-maintainer-funding

Thanks to everyone who helped crowdsource it! I’ll keep it updated, issues and PRs are very welcome :)

#opensource #funding #maintenance #foss

Mirko Swillus

@mechko@chaos.social

Dear FOSS maintainers,

here’s a list of funding programs currently accepting proposals for maintenance work:

Codeberg: https://codeberg.org/mechko/awesome-maintainer-funding

GitHub: https://github.com/mechko/awesome-maintainer-funding

Thanks to everyone who helped crowdsource it! I’ll keep it updated, issues and PRs are very welcome :)

#opensource #funding #maintenance #foss

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to Kaito's post

@kai Yes!

Armin Ronacher

@mitsuhiko@hachyderm.io

This weekend I was thinking about programming languages. Programming languages for agents. Will we see them? I believe people will (and should!) try to build some. https://lucumr.pocoo.org/2026/2/9/a-language-for-agents/

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪民憙 (Hong Minhee) :nonbinary:'s post

Alright, maybe I should start by making a list of what needs to get done:

Fedify STF milestone 3: ActivityPub debug tools
Fedify 2.0 release
Hackers' Pub renewal
Optique new version release

What else was there...?

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I've taken on way too much lately, and I just don't have the time or energy to handle it all properly…

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to Thiago, the one they call Jedi's post

@jedi Yeah, there are times I want to call my own code “slop.” 😂 But I think it's going too far to call someone else's work that.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to 洪民憙 (Hong Minhee) :nonbinary:'s post

For extra context: I'm saying this because I saw someone call my code “AI slop.”

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

I think it's rude to just dismiss someone's work as “AI slop” simply because it uses some AI.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

Hi, new followers! Seems like a good time for a re-introduction.

I'm Hong Minhee (洪民憙), a software engineer based in Seoul. My pronouns are they/them.

I build tools for the fediverse. Fedify is an ActivityPub server framework in TypeScript, Hollo is a single-user microblogging server (what you're reading this on), and BotKit is a framework for making ActivityPub bots. I care a lot about making federation more accessible to developers, which, as my recent JSON-LD rant probably made clear, sometimes means wrestling with parts of the spec I have complicated feelings about.

I'm a free/open source software person through and through, and a socialist, which informs how I think about tech. Lately I've been thinking a lot about LLMs. My position is probably not what you'd expect from either camp: I think the problem isn't the technology itself but the enclosure of the commons. I wrote about this at length here if you're curious: Histomat of F/OSS: We should reclaim LLMs, not reject them.

Outside of software, I have a long-running interest in CJK languages and writing systems. I'm always happy to talk about Chinese characters, Korean orthography, or the weird corners of Unicode where these things intersect.

Nice to meet you all, and thanks for following.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

It's 7 AM in Korea right now, and I still haven't been able to sleep. I guess I've completely failed to adjust to the time difference.

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to wakest ⁂'s post

@liaizon Thanks, I'm checking it out!

World Wide Web Consortium

@w3c@w3c.social

The Internationalization Working Group @webi18n has published the first draft of a Group Note titled "Text-to-Speech Rendering of Electronic Documents Containing Ruby: User Requirements". This document describes user requirements related to text-to-speech rendering of electronic documents containing ruby annotations.
#i18n #internationalization
https://www.w3.org/news/2026/group-note-draft-ruby-tts-req/

ALT text details

Double-sided ruby example 2 Figure 2 織田信長 features an upper-side ruby annotation "1534〜82" and a lower-side ruby annotation おだのぶなが

洪民憙 (Hong Minhee)

@hongminhee@hollo.social · Reply to mcc's post

@mcc I'm not sure, but that would break some ActivityPub implementations relying on JSON-LD processors. 🤔

洪民憙 (Hong Minhee)

@hongminhee@hollo.social

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

kopper

@kopper@not-brain.d.on-t.work

i was a bit curious about the actual transfer size impact of json-ld, and what would happen if you replaced json-ld with simply explicitly repeating the namespaces. so i threw a few payloads, both compacted and expanded, into lynn.github.io/flateview/ at gzip level 6

my actor, compacted - 1855 bytes gzip'd
my actor, expanded - 1877 bytes gzip'd
my actor, compacted with no context - 1793 bytes gzip'd

quoted post, compacted - 2024 bytes gzip'd
quoted post, expanded - 2033 bytes gzip'd
quoted post, compacted with no context - 1985 bytes gzip'd

mastodon.social instance actor, compacted - 2761 bytes gzip'd
mastodon.social instance actor, compacted, with unused context values removed - 644 bytes gzip'd
mastodon.social instance actor, expanded - 707 bytes gzip'd
mastodon.social instance actor, compacted, with no context - 667 bytes gzip'd

RE: not-brain.d.on-t.work/notes/aihcsxrs45sw0wbq

kopper

@kopper@not-brain.d.on-t.work · Reply to 洪民憙 (Hong Minhee) :nonbinary:'s post

@hongminhee from the point of view of someone who is "maintaining" a JSON-LD processing fedi software and has implemented their own JSON-LD processing library (which is, to my knowledge, the fastest in it's programming language), JSON-LD is pure overhead. there is nothing it allows for that can't be done with

1. making fields which take multiple values explicit
2. always using namespaces and letting HTTP compression take care of minimizing the transfer

without JSON-LD, fedi software could use zero-ish-copy deserialization for a majority of their objects (when strings aren't escaped) through tools like serde_json and Cow<str>, or System.Text.Json.JsonDocument. JSON-LD processing effectively mandates a JSON node DOM (in the algorithms standardized, you may be able to get rid of it with Clever Programming)

additionally, due to JSON-LD 1.1 features like @type:@json, you can not even fetch contexts ahead of time of running JSON DOM transformations, meaning all JSON-LD code has to be async (in the languages which has the concept), potentially losing out on significant optimizations that can't be done in coroutines due to various reasons (e.g. C# async methods can't have ref structs, Rust async functions usually require thread safety due to tokio's prevalence, even if they're ran in a single-threaded runtime)

this is after context processing introducing network dependency to the deserialization of data, wasting time and data on non-server cases (e.g. activitypub C2S). sure you can cache individual contexts, but then the context can change underneath you, desynchronizing your cached context and, in the worst case, opening you up to security vulnerabilities

json-ld is not my favorite part of this protocol

kopper

@kopper@not-brain.d.on-t.work · Reply to kopper :colon_three:'s post

@hongminhee if i can give one piece of advice to devs who want to process JSON-LD: dont bother compacting. you already know the schema you output (or you're just passing through what the user gives and it doesn't matter to you), serialize directly to the compacted representation, and only run expansion on incoming data

expansion is the cheapest JSON-LD operation (since all other operations depend on it and run it internally anyhow), and this will get you all the compatibility benefits of JSON-LD with little downsides (beyond more annoying deserialization code, as you have to map the expanded representation to your internal structure which will likely be modeled after the compacted one)

kopper

@kopper@not-brain.d.on-t.work · Reply to kopper :colon_three:'s post

@hongminhee take this part with a grain of salt because my benchmarks for it are with dotNetRdf which is the slowest C# implementation i know of (hence my replacement library), but JSON-LD is slower than RSA validation, which is one of the pain points around authorized fetch scalability

wetdry.world/@kopper/114678924693500011

kopper

@kopper@not-brain.d.on-t.work · Reply to 洪民憙 (Hong Minhee) :nonbinary:'s post

Doug Webb

@douginamug@mastodon.xyz · Reply to 洪民憙 (Hong Minhee) :nonbinary:'s post

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