洪民憙 (Hong Minhee) :nonbinary:

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 #日本語

Public Key

npub1pzjfm9lymy3dnrxg2uk237vlvteefahea7s4ptjzv8n2a9uarrxqtr3zhj

NIP-05 Address

hongminhee@hollo-social.mostr.pub

Profile Code

nprofile1qqsq3fyajljdjgke3ny9wt9glx0k9uu57mu7lg2s4epxre4wj7w33nqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsdfv9yx

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1pzjfm9lymy3dnrxg2uk237vlvteefahea7s4ptjzv8n2a9uarrxqtr3zhj

Show more details

Last Notes

2026-03-31 10:28:53 UTC

I've wanted to build a mixed-script Korean input method for more than ten years, and I finally started building it.
The project is called Bibim. Korean, Japanese, and Chinese share a lot of Sino-derived words written with Chinese characters, even when the readings differ. Bibim uses those characters as the bridge: if you're writing Japanese and can't remember the Japanese reading of 博物館 (“museum”), you can type the Korean reading (bangmulgwan) instead, and it will recover the characters for you.
I finished the design doc today. If you're into CJK writing systems, East Asian languages, or input method development, I'd love feedback.
https://codeberg.org/hongminhee/bibim-prototype

2026-03-30 12:02:25 UTC

BotKit is a TypeScript framework I've been building for creating ActivityPub bots that run as their own independent servers—no platform account needed, no Mastodon or Misskey instance to log into. You write a bot, give it a username, and it federates directly with the rest of the fediverse. It's built on top of Fedify, so the low-level protocol work is handled for you: HTTP Signatures, WebFinger, JSON-LD, all of it. What you're left writing is just the bot logic itself.
Version 0.4.0 is out today, with a PostgreSQL repository for production deployments, a remote follow button on the bot profile page, and a few other additions.
Release notes: https://github.com/fedify-dev/botkit/discussions/20
#nevent1q…jtdv

2026-03-30 11:29:45 UTC

Everyone in tech talks about moats like they're achievements. I keep reading “moat” and thinking: so the idea is to make leaving expensive. Maybe it's just me, but that feels a little grim.

2026-03-21 09:30:24 UTC

LLM coding assistants didn't create a split between craft-lovers and make-it-go developers. They revealed one that was always there.
For craft-lovers, what's being bypassed isn't the output but the act itself. Marx called this separation from the act of production. But the alienation isn't coming from the LLM. It's coming from a market that penalizes whoever produces output more slowly.
Why craft-lovers are losing their craft

2026-03-21 04:32:24 UTC

So, an interesting issue came up in the #Fedify repo that I've been thinking about: #629.
You know how every #fediverse server uses schema:PropertyValue in actor attachment for profile metadata fields (like “Website”, “GitHub”, etc.)? Turns out, strict #AS2 validators like browser.pub reject it, because the AS2 spec says attachment should only contain Object or Link—and PropertyValue is a schema.org type, not an Activity Streams 2.0 type.
The thing is, we can't just drop the type like we did with Endpoints (#576), because Mastodon and others rely on seeing "type": "PropertyValue" to render profile fields. But at the same time, it's technically not spec-compliant.
I'm leaning towards writing a #FEP to formalize this existing practice rather than trying to invent a new type (like toot:PropertyValue extending Object), which would be a nightmare to migrate across the whole fediverse.
What do you all think? Has anyone else run into this? Would love to hear thoughts from implementers and spec folks.
#fedidev #ActivityPub #ActivityStreams #ActivityStreams2 #AS2 #PropertyValue

2026-03-19 16:18:59 UTC

OpenAI to acquire Astral
What strikes me most about this acquisition isn't the AI angle. It's the question of why so many open source tools get built by startup teams in the first place.
I maintain an open source project funded by the Sovereign Tech Fund. Getting there wasn't easy: the application process is long, the amounts are modest compared to a VC round, and you have to build community trust before any of that becomes possible. But the result is a project that isn't on anyone's exit timeline.
I'm not saying the startup path is without its own difficulties. But structurally, it offloads the costs onto the community that eventually comes to depend on you. By the time those costs come due, the founders have either cashed out or the company is circling the drain, and the users are left holding the bag. What's happening to Astral fits that pattern almost too neatly.
The healthier model, I think, is to build community first and then seek public or nonprofit funding: NLnet, STF, or similar. It's slower and harder, but it doesn't have a built-in betrayal baked into the structure.
Part of what makes this difficult is that public funding for open source infrastructure is still very uneven geographically. I'm based in Korea, and there's essentially nothing here comparable to what European developers can access. I had no choice but to turn to European funds, because there was simply no domestic equivalent. That's a structural problem worth taking seriously. The more countries that leave this entirely to the private sector, the more we end up watching exactly this kind of thing play out.

2026-03-09 15:23:44 UTC

Salvatore Sanfilippo (@nprofile…dutx) and Armin Ronacher (@nprofile…4zt6) both argue that #AI reimplementation of #copyleft libraries is fine. Their legal reasoning might be correct. That's not the point.
Legal and legitimate are different things—and both pieces quietly assume otherwise.
https://writings.hongminhee.org/2026/03/legal-vs-legitimate/
#GPL #LGPL #license #opensource #freesoftware

2026-03-03 10:04:36 UTC

明日からHaze Leeさん（@nprofile…pr5l）と一緒に一週間東京に旅行に行くんだ。楽しみ！

2026-03-02 12:22:23 UTC

I've been increasingly concerned about the corporate monopoly over frontier LLMs. While many ethically-minded people choose to boycott these models, I believe passive resistance alone cannot break the structural grip of big tech. To truly “liberate” these technologies and turn them into public goods, we need to look beyond moral high grounds and engage with the material basis of AI—specifically compute, data, and the relations of production.
I've written two posts exploring this through the lens of historical materialism. The first piece analyzes why current “open source” definitions struggle with LLMs, and the second discusses what it means to “act materialistically” in our imperfect world. My goal is to suggest a path forward that moves from mere boycotting to a more proactive, structural socialization of AI infrastructure.
If you've been feeling uneasy about the AI landscape but aren't sure if boycotting is the final answer, I'd love for you to give these a read:
Histomat of F/OSS: We should reclaim LLMs, not reject them
Acting materialistically in an imperfect world: LLMs as means of production and social relations
#LLM #AI #opensource #historicalmaterialism #histomat #materialism #digitalcommons

2026-02-27 17:21:35 UTC

When I first started working with #ActivityPub, before #Fedify existed, it felt like writing web apps in Perl and CGI in the late '90s. Interesting, even exciting—but never comfortable. That era where your business logic and your protocol plumbing were just… the same thing:
print "HTTP/1.1 200 OK"
print "Content-Type: text/html"
print
print "Hello, world!"
Decades of web development have given us layers of abstraction we now take for granted. Nobody hand-parses application/x-www-form-urlencoded query strings anymore. Nobody writes their own JSON codec, or manually constructs HTTP request/response messages. These things just aren't your problem when you're building an app.
ActivityPub development still feels like they are your problem. What do you do when the https://www.w3.org/ns/activitystreams#actor property comes in as a string instead of an array? What about when https://www.w3.org/ns/activitystreams#object is an embedded entity rather than a URI? How exactly do you implement HTTP Signatures? And wait—what's Linked Data Signatures, and do you need that too?
The real issue isn't that ActivityPub is complicated per se. It's that you can't get away with understanding it at a high level. You have to know it the way an implementor knows it—every edge case, every inconsistency in how different servers serialize JSON-LD, every signature scheme that exists in the wild. That's a lot to learn before you can even start thinking about your actual app. And when developers understandably cut corners on the protocol to focus on their product, it quietly becomes an interoperability problem for the whole ecosystem.
What I want ActivityPub development to feel like: you spend a day understanding the big picture, and then you just… build your app. That was the goal when I started Fedify, and honestly, we're not fully there yet. But it's where I want to get.
#fedidev #fediverse

2026-02-27 08:16:21 UTC

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

2026-02-26 14:25:22 UTC

- reply

@nprofile…h0ux @nprofile…jzu7 We have an issue for this!
https://github.com/fedify-dev/fedify/issues/452

2026-02-26 05:55:15 UTC

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

2026-02-25 05:02:13 UTC

3月4日(水)から11日(水)まで東京に滞在します。この機会に日本のフェディバースの皆さんとお会いしたいです。ランチでもディナーでも、お茶やコーヒーでも構いません。私と会ってくださる方はいらっしゃいますか？食事やお茶は私がおごります。私はこの期間中、特に予定がないので、皆さんのご都合に合わせることができます。（ただし、最終日を除きます）

2026-02-22 19:51:51 UTC

Hi #fediverse and #ActivityPub developers!
I'm currently working on interoperability testing for #Hollo and #Fedify, and I need a #Bonfire account to test federation with their implementation.
Since there aren't many open public Bonfire instances available, I was wondering if any Bonfire instance admins out there would be willing to grant me a test account? It would be a huge help for improving interop! Let me know if you can help. Thanks!
#fedidev #BonfireNetworks

2026-02-20 11:50:08 UTC

In fact, Hackers' Pub is a bleeding-edge testbed for Fedify. 🙄

2026-02-12 07:08:13 UTC

Fedify 2.0 will probably be out by the end of February. No, it has to be.

2026-02-09 13:42:35 UTC

I wish more free/open source software developers got paid for their work.
#nevent1q…rw99

2026-01-31 22:05:14 UTC

So one of my dreams is to organize an ActivityPub/fediverse conference for East Asia, as I told about it multiple times before…

2026-01-14 06:14:04 UTC

I've spent a long time asking myself why open source matters so much to me, why I keep coming back to it. I once joined a company purely because they promised I could do open source full-time (it didn't turn out well). Before that, I was doing open source inside and outside of regular jobs. And now, in the age of LLMs, when the value of code itself seems to be declining, I'm still here, still doing this.
Recently it clicked. I do open source because it's social work—in the sense that it lets me participate in society.
Everyone wants to belong to some community, to connect with others. But I was never good at the usual ways of doing that. Social activities that came naturally to others were difficult for me. In school, I had few friends. After class, I'd stay home assembling Lego or reading books alone. Then I discovered coding.
Coding was a wonderful hobby for me, especially because I encountered it at the dawn of the internet era. The first programming languages I properly learned were Perl, PHP, and JavaScript—all languages of the internet age. The synergy was something else.
Gradually I fell into the world of open source. And there, even someone like me—awkward at conventional social interaction—could be social. My code helped people. I could collaborate by exchanging code. I could have conversations, mediated by code. IRC, mailing lists, forums—these became my social media. Over time, “the group I wanted recognition from” became the people in the open source world. I didn't care much about being recognized by classmates, but I wanted to be recognized by these people I'd never met face to face.
That mindset still shapes me now, approaching forty. I still care more about recognition from open source programmers than from colleagues. The social activity that happens in open source communities is, after my family, the most important social activity in my life.
The specific things I build, the technical details—those matter less than I used to think. I just want to do the kind of social activity that suits me, and open source happens to be the way I do it.
That's all, really.

2025-10-13 03:53:09 UTC

- reply

@nprofile…6xhn 어라, 저는 되는 것 같습니다!

2025-08-25 15:49:19 UTC

Excited to share some great news from the #creative community! Oeee Cafe, a fantastic oekaki #drawing platform, just added #ActivityPub support today. This means all the amazing artwork being created there can now be shared and discovered across the #fediverse, which is such a wonderful step toward connecting creative communities.
Big shoutout to my friend @nprofile…xnsx for building this platform and bringing it to the fediverse. It's always inspiring to see developers creating spaces for artists and then opening them up to the broader federated community. If you're into digital art or just appreciate seeing creative work, definitely worth checking out what people are sharing from Oeee Cafe on your timeline now. You can find me there at @nprofile…a5ru if you want to connect!
#oekaki

2025-08-17 12:24:26 UTC

If you find it unbearable to be around people with big egos, you might want to consider whether your own ego is the problem.

2025-08-12 04:44:03 UTC

처음으로 筆洞麵屋(필동면옥)에 와 본다!
https://media.social.fedify.dev/media/01989c97-a501-7f20-a549-ffaea744fdbb/original.jpeg
https://media.social.fedify.dev/media/01989c97-a2dc-7412-aa54-9bceee5a74e5/original.jpeg

2025-07-31 04:36:31 UTC

ソフトウェアのバージョン番号「0.3.0」は日本語でどう読みますか？「零点三点零」？それとも、「ゼロ点三点ゼロ」？

2025-07-17 12:58:22 UTC

- reply

@nprofile…pscj Hollo 쓰는 방법도 있습니다! 💨 :hollo:

2025-07-17 12:40:06 UTC

It feels like I've taken on too many projects in the last two years. The open source projects I'm currently managing are: Fedify, Hollo, LogTape, BotKit, Hackers' Pub, and Upyo. … That's quite a lot, isn't it?

2025-07-05 12:02:00 UTC

- reply

@nprofile…pscj 제가 알기로는 (Android에 비해) 유료 앱을 실제로 많이 구입하기 때문이라고 알고 있어요.

2025-06-26 04:10:14 UTC

Excited to share that I've joined #OSSCA (Open Source Software Contribution Academy) as a mentor for the @nprofile…j979 project!
OSSCA is a national program run by South Korea's NIPA (National IT Industry Promotion Agency) through their Open Source Software Support Center, aimed at fostering the next generation of open source contributors.
We're currently in the process of selecting around 20 mentees who will start contributing to #Fedify once the selection is complete. I've been busy preparing good first issues to help them get started on their open source journey.
Looking forward to working with these new contributors and seeing what amazing things we can build together!
#opensource #mentoring #ActivityPub #fedidev

2025-06-21 01:39:44 UTC

今kmy.blueにアクセスできないみたい。502エラーが出てる。

2025-06-03 01:19:33 UTC

投票(투표) 完了(완료)!

2025-05-31 07:24:13 UTC

If you're interested in building your own #ActivityPub server but don't know where to start, I recommend checking out #Fedify's #tutorial Creating your own federated microblog. It provides a comprehensive, step-by-step guide that walks you through building a fully functional federated application. Perfect for developers who want to dive into the #fediverse!
#fedidev

2025-05-14 02:51:56 UTC

I've been thinking about client-server interactions in the #fediverse. #ActivityPub #C2S isn't widely used, and most clients rely on Mastodon-compatible APIs instead.
What if we created a new standardized API based on GraphQL + Relay for client-server communication, while keeping ActivityPub for server-to-server federation?
The Mastodon-compatible API lacks formal schema definitions for code generation and type checking, which hurts developer productivity. And ActivityPub C2S is honestly too cumbersome to use directly from client apps.
#GraphQL would give us type safety, efficient data fetching (only get what you need), and the ability to evolve the API without breaking clients. #Relay's features for pagination, caching, and optimistic updates seem perfect for social apps.
Would this be valuable to our community? What challenges do you see? How might we handle backward compatibility? And should this be formalized as an FEP?
Curious what others think about this approach.
#fedidev

2025-05-13 09:21:30 UTC

As #Fedify's author, I'm contemplating its adoption beyond Ghost's #ActivityPub implementation. Finding potential users for ActivityPub tools seems challenging—perhaps I'm addressing a very niche need?
While the technical complexity of ActivityPub makes tools like Fedify valuable, I wonder about the actual market demand for federation outside specific communities.
Open, decentralized systems make sense to many developers, but businesses often prefer closed ecosystems that align with traditional models.
Still, I see potential as the #fediverse grows and digital sovereignty concerns increase. Fedify aims to lower the technical barriers to federation.
I'm curious: Which projects would benefit most from Fedify today? What would make federation compelling enough for platforms to implement?
Would appreciate perspectives from both developers and platform owners.

2025-05-12 12:22:44 UTC

Just wrote the Why Fedify? section in the #Fedify docs.

2025-05-07 09:17:20 UTC

- reply

@nprofile…kgua Do you have a working branch implementing RFC 9421 in Mastodon? I'm implementing it in Fedify, and would like to test against Mastodon's implementation of RFC 9421.

2025-04-26 03:27:30 UTC

I'm exploring a new idea called FediOTP (codename): an authentication system that uses #ActivityPub DMs to deliver one-time passwords, allowing any #fediverse account to authenticate with web services. Unlike current solutions that rely on specific APIs (#Mastodon, #Misskey), this would work with any ActivityPub-compatible server, increasing interoperability across the fediverse. Would love to hear your thoughts on potential challenges or use cases for this approach.
#OTP #fedidev #auth

2025-04-26 02:11:44 UTC

- reply

@nprofile…zzaa Holloのバグかも知れませんね、確認してみます！

2025-04-23 16:08:46 UTC

突然、日本語のネイティブスピーカーは旧字体を自然に読めるのだろうかと気になった。韓国で漢字教育を受けた私としては、中国語や日本語を別途学ぶまでは「國=国」くらいは知っていたが、「礙=碍」などは全く知らなかったから。（韓国の漢字は基本的に旧字体または繁体字に近い康熙字典体が標準）

2025-04-23 10:02:32 UTC

My stance on #ActivityPub's adoption of JSON-LD: Since we've already decided to use JSON-LD, I hope we do it properly. However, if we hadn't used JSON-LD from the beginning, things would have been much less complicated.
#JSONLD #fedidev

2025-04-23 04:18:30 UTC

🤔
Protocols such as ActivityPub are widely used and useful, but unfortunately are not the best option when efficiency is important. Messages are in plain JSON format, which is wasteful, and extensions by various implementations complicate the implementation.
XQ's focus on replacing JSON with Protocol Buffers seems misguided. While serialization efficiency matters, ActivityPub's fundamental bottlenecks are in its multi-hop network architecture and request patterns. Optimizing message format without addressing these core architectural inefficiencies is like polishing doorknobs on a house with structural issues. True performance gains would require rethinking the communication model itself.
https://github.com/misskey-dev/xq

2025-04-21 20:11:53 UTC

I've been reflecting lately on projects like @nprofile…j979, @nprofile…d3ay, and @nprofile…xex2. Sometimes I wonder if I'm solving problems that very few people actually need solved. How many developers truly want to build their own #ActivityPub server from scratch?
It feels a bit like inventing shoes that let people walk on their hands all day. Would there be a viable market? How many would actually buy them?
That's the sense I get with these projects. They do have users who find them tremendously valuable, but the total user base is inherently limited. The tools serve an important function for a small audience of specialized developers.
There are moments when my motivation wavers. When the user community consists of just a handful of enthusiastic supporters, it's sometimes difficult to maintain momentum and justify the ongoing investment of time and energy.
And yet, there's something meaningful about creating specialized tools that solve complex problems well, even if they're only used by a few. Perhaps that's enough.
#fedidev

2025-04-20 08:46:26 UTC

- reply

Another annoying thing about the current custom emoji spec in the fediverse: the type is just called Emoji instead of CustomEmoji. Such a small detail, but it creates unnecessary ambiguity between Unicode emojis and custom ones. I ran into this while implementing BotKit and had type name collisions with Emoji—had to use awkward namespacing to work around it. These little inconsistencies make implementation more tedious than it needs to be.

2025-04-19 14:57:36 UTC

As someone who has developed several #ActivityPub software implementations (Fedify, Hollo, BotKit, and Hackers' Pub), I believe one of the most frustrating features to implement in the #fediverse is #custom_emoji.
The challenges are numerous:
First, there's no standardization. ActivityPub specifications don't define how custom emoji should work, leading to inconsistent implementations across different servers like Mastodon and Misskey.
Rendering is particularly problematic. Emojis must display properly across different contexts (in text, as reactions, in emoji pickers) while maintaining quality at various sizes. Animated emojis add another layer of complexity.
Perhaps most concerning is the poor #accessibility. Most implementations simply use the emoji code (like :party_blob:) as the alt text, which provides no meaningful information to screen reader users (in particular, non-English speakers) about what the emoji actually depicts or means.
What really dampens my motivation to implement this feature is knowing I'm investing significant effort into something that ultimately creates accessibility barriers. It's disheartening to work hard on a feature that excludes part of the community.
#fedidev

2025-04-18 18:20:54 UTC

- reply

@nprofile…kgua Is it FEP-044f? It's new to me, so I need to check it out!

2025-04-17 09:38:36 UTC

同じ理由でfedify lookup -a https://www.threads.net/@usernameコマンドで正常に照会が出来ない。一方fedify lookup -a @username@threads.netコマンドは正常に動作。
#nevent1q…fhg7

2025-04-14 13:43:31 UTC

- reply

@nprofile…gd7f I'm using Hollo, and it supports both Markdown and raw HTML in the post contents!

2025-04-13 12:12:36 UTC

- reply

@nprofile…rqpe さんが「フェディバースの日」専用のウェブサイトfediday.orgを作成した事をお知らせします。このサイトでは、韓国語圏のフェディバースコミュニティから生まれた4月11日を「連合型フェディバースの日」として祝っています。サイトでは、この取り組みの背景やフェディバースの重要な記念日についての情報も掲載されています。特別な日を追加したい場合は、GitHubリポジトリを通じて貢献することができます！
#FediverseDay #フェディバースの日 #Fediverseの日 #연합우주의날 #聯合宇宙의날

2025-04-13 01:46:53 UTC

- reply

Excited to share that @nprofile…rqpe has created fediday.org—a new website dedicated to Fediverse Day! The site celebrates April 11th as Federated Fediverse Day, which originated from conversations in the Korean fediverse community. Visit the site to learn about the background of this initiative and discover other important dates in the fediverse calendar. If you'd like to add a special date, you can contribute through the GitHub repository!
#FediverseDay #연합우주의날 #聯合宇宙의날 #フェディバースの日 #Fediverseの日

2025-04-11 04:43:44 UTC

- reply

韓国語圏のフェディバースコミュニティが4月11日を「フェディバースの日」（聯合宇宙(연합우주)의 날）として制定する事を提案しています。この考えは今日、韓国のフェディバースユーザー間の会話から生まれた為、今日の日付を今後の公式な記念日にしようという提案が出ています。
この取り組みを広くフェディバースコミュニティと共有し、年に一度の「フェディバースの日」をサポートし、参加していただけるかどうか知りたいと思います！
#フェディバースの日 #Fediverseの日 #FediverseDay #연합우주의날 #聯合宇宙의날
#nevent1q…0c8c

2025-04-11 04:41:05 UTC

The Korean fediverse community is proposing to establish April 11th as “Fediverse Day” (聯合宇宙(연합우주)의 날). Since this idea emerged today in conversations among Korean fediverse users, they've suggested making today's date the official celebration going forward.
We're sharing this initiative with the broader fediverse community and would love to know if you'd support and participate in an annual Fediverse Day!
#FediverseDay #연합우주의날 #聯合宇宙의날 #フェディバースの日 #Fediverseの日
#nevent1q…0c8c

2025-04-09 11:18:18 UTC

- reply

@nprofile…t9gy As far as I know, names cannot have any HTML… 🤔

2025-04-09 03:56:30 UTC

생각해 보니 정작 저도 어제 飮食(음식) 사진 올릴 때 프로틴이 들어있는데도 CW도 別(별) 태그도 달지 않았기 때문에 堂堂(당당)하게 말할 처지는 못 됩니다만… @nprofile…ru55 님이 쓰신 引用(인용)한 글에 同感(동감)합니다.
크게 세 가치 側面(측면)에서 이야기해보고 싶은데요.
애初(초)에 @nprofile…ld07 님이 付託(부탁)하신 건 肉食(육식) 寫眞(사진)에 CW를 걸어달라는 것까지도 아니고, 필터링할 수 있게끔 通用(통용)되는 해시태그가 있었으면 한다는 말씀이셨는데요… 이게 어쩌다 肉食(육식) 寫眞(사진)에 CW 달아야 한다는 「無理(무리)한」主張(주장)으로 歪曲(왜곡)되었는지 모르겠습니다. (事實(사실) 왜 그런지 알 것도 같지만요.)
비건이라는 運動(운동)에 同意(동의)를 하든 안 하든, 맞팔한 사이에 비건이 있다면 肉食(육식) 寫眞(사진)을 올릴 때 苦悶(고민)하는 程度(정도)의 配慮(배려)는 그냥 사람과 사람 사이에서 얼마든지 할 수 있는 일 아닐까 싶습니다.
「肉食(육식) 寫眞(사진)까지 CW 걸어야 하냐」라는 꽤나 恣意的(자의적)인 「常識(상식)」(제가 정말 안 좋아하는 單語(단어)인데요… 이를테면 어떤 사람들에겐 트랜스젠더나 同性愛(동성애)도 常識(상식) 밖의 일이기 때문이죠)에 依據(의거)한 이야기를 하시는 분들도 많이 보였는데요. 그렇게 치면 韓國(한국)의 어떤 커뮤니티들은 그들의 「常識(상식)」에 依據(의거)하여 反女性主義的(반여성주의적) 主張(주장)도 橫行(횡행)하고 多分(다분)히 極右的(극우적)인 主張(주장)들도 便(편)하게 올리고 한단 말이죠. 애當初(당초) 「몇 안 되는 사람들까지 配慮(배려)해야 하냐」라는 말 自體(자체)가 暴力的(폭력적)이라는 認知(인지)를 한다면 그렇게 말할 수 없지 않을까 합니다. 비록 비건이 아니더라도요. (이를테면, 저는 비건이 아닙니다. 어제도 肉食(육식)을 했고요.)
#nevent1q…5w3z

2025-03-30 04:27:56 UTC

- reply

@nprofile…ehw4 제가 배포하다 터뜨렸습니다. 이제 다시 살렸습니다…

2025-03-25 16:11:07 UTC

I just discovered why some of my followers from larger #Mastodon instances (like mastodon.social) would mysteriously unfollow me after a while!
A pull request was just merged in Mastodon that fixes a critical bug in their follower synchronization mechanism.
Turns out Mastodon implements the FEP-8fcf specification (Followers collection synchronization across servers), but it expected all followers to be in a single page collection. When followers were split across multiple pages, it would only see the first page and incorrectly remove all followers from subsequent pages!
This explains so much about the strange behavior I've been seeing with #Hollo and other #Fedify-based servers over the past few months. Some people would follow me from large instances, then mysteriously unfollow later without any action on their part.
Thankfully this fix has been marked for backporting, so it should appear in an upcoming patch release rather than waiting for the next major version. Great news for all of us building on #ActivityPub!
This is why I love open source—we can identify, understand, and fix these kinds of interoperability issues together. 😊
#fediverse #fedidev

2025-03-22 10:28:29 UTC

- reply

@nprofile…t9gy FYI it's dandan noodes! Give it a try someday when you go to a Chinese restaurant.

2025-03-22 09:59:09 UTC

오늘 저녁은 擔擔麵(탄탄면)!

2025-03-13 04:19:46 UTC

Most #ActivityPub implementations include Mention objects in the tag attribute when someone mentions another actor within the content of a Note or Article. Should actor objects like Person or Group also include Mention objects in their tag attribute when mentioning other actors within their bio (summary)? Are there any implementations that already work this way? (I've checked Mastodon and it seems they don't include these mentions.) What are your thoughts on this?
#fediverse #fedidev

2025-03-11 07:54:07 UTC

- reply

@nprofile…pscj 生辰(생신) 祝賀(축하)드립니다! 🎂

2025-03-08 15:23:15 UTC

제가 開發(개발)하고 있는 프로젝트 Hackers' Pub의 베타 테스터를 모십니다!
이 프로젝트는 #聯合宇宙(연합우주)(fediverse)板(판) velog 같은 것으로, 소프트웨어 開發者(개발자)를 爲(위)한 #ActivityPub 基盤(기반)의 SNS 兼(겸) 블로그 플랫폼입니다. AGPL-3.0 라이선스로 소스 코드가 公開(공개)되어 있을 뿐 아니라, GitHub에서 프로젝트를 公開的(공개적)으로 進行(진행)하고 있습니다.
職業(직업)으로든 趣味(취미)로든 소프트웨어를 開發(개발)하시는 분들, 聯合宇宙(연합우주)를 좋아하시는 분들, 새로운 플랫폼을 써 보고 싶으신 분들은 부디 參與(참여)해 주시기 바랍니다! 關心(관심) 있으신 분들은 答(답)글이나 DM으로 이메일 住所(주소)를 보내주시면 됩니다.
#HackersPub #페디버스 #연합우주

2025-03-08 13:40:05 UTC

- reply

@nprofile…pscj 네, 액터 URI에 유저명 포함하는 게 실제로 안티패턴이예요.

2025-03-08 13:37:29 UTC

- reply

@nprofile…pscj Mastodon이나 Pleroma는 ActivityPub 수준에서도 액터 URI에 유저명을 포함하고 있어서 하고 싶어도 못 할 것 같고요. Misskey는 할 수 있는데 안 한 거 같아요. Misskey는 나중에 지원할 수 있을지도 모르겠네요.

2025-03-08 12:56:12 UTC

- reply

@nprofile…pscj Hackers' Pub에서도 사용자 퍼머링크에 유저명이 들어가긴 합니다! ActivityPub 수준에서만 유저명 안 들어간 URI를 쓰는 게 포인트예요.

2025-03-08 10:49:45 UTC

拡散希望：開発中のプロジェクトHackers' Pubの日本語ベータテスターを募集します！
これはフェディバース版のQiita/Zennを目指す、ActivityPub基盤の開発者向けSNS兼ブログプラットフォームです。AGPL-3.0ライセンスでソースコードを公開しており、GitHubでプロジェクトも公開進行中です。
現在韓国語話者中心に招待制ベータテスト中ですが、日本の開発者コミュニティにも広げたいと思っています。ソフトウェア開発に興味がある方、フェディバースが好きな方、新しいプラットフォームを試してみたい方、ぜひご参加ください！興味のある方はリプライかDMでメールアドレスをお送りください。
#HackersPub #フェディバース #拡散希望

2025-03-06 14:20:29 UTC

- reply

@nprofile…pscj 틀린… 말까지는 아닌 것 같고, 標準語(표준어) 【도리어】에 對應(대응)하는 方言(방언)이라고 봐야겠죠? 私見(사견)으로는 複數(복수) 標準(표준)으로 認定(인정)해야 한다고 봅니다.

2025-03-01 05:42:04 UTC

全州韓屋(전주한옥)마을 왔다. 點心(점심)으로 茶門(다문)이라는 가게에서 韓定食(한정식) 먹음.

2025-02-27 16:49:27 UTC

The hardest platform to interoperate with when implementing an #ActivityPub server is #Threads. They often spit out a 500 Internal Server Error with no message, and they don't even provide source code, which makes it impossible for me to reproduce the error.

2025-02-27 12:14:15 UTC

요즘 Hackers’ Pub이라는 ActivityPub으로 聯合(연합)되는 開發者用(개발자용) 블로그 플랫폼을 만들고 있습니다. 쉽게 말하면 聯合宇宙(연합우주)(fediverse) 버전의 velog 같은 거라고 보면 되겠지요. 開發(개발) 로그를 @nprofile…kh6h 쪽으로 올리고 있으니, 關心(관심) 있으신 분들은 팔로해 주세요!
아, 그리고 Hackers’ Pub은 아직 招待制(초대제)로 運營(운영)되고 있는데, 計定(계정) 만들고 싶은 분들은 DM 주시면 招待(초대)해 드리겠습니다.
https://fosstodon.org/@hongminhee/113479230281333582
#nevent1q…nkf8

2025-02-27 09:37:08 UTC

- reply

@nprofile…pscj 昨年(작년)에 오픈 소스 컨퍼런스 2024 Tokyo/Fall에 參加(참가)했는데 그쪽도 志願書(지원서) 書式(서식)이 .docx더라고요. 🤦🏻‍♂️

2025-02-27 09:21:21 UTC

2025年(년) 오픈소스 컨트리뷰션 아카데미 參與型(참여형) 멘토團(단) 募集(모집) 公告(공고)가 떴다. Fedify 프로젝트의 메인테이너로서 멘토團(단)에 支援(지원)하고자 한다. 志願書(지원서)가 .hwp 파일이기에 큰 맘 먹고 한컴오피스 한글 for Mac도 購入(구입)했다. (아무래도 앞으로 .hwp 파일 다룰 일이 많을 것 같다는 豫感(예감)이 들어서…)

2025-02-25 06:11:42 UTC

Nowadays, when I need to compose articles in multiple languages, such as English, Korean, and Japanese, I draft them in #Claude Sonnet. By providing the data that should be included in the content and the constraints, it produces a pretty good draft. #LLM is a language model, so it is quite good at writing—especially if you need to work with multiple languages.

2025-02-19 03:29:17 UTC

韓国の主要報道機関の一つである『한겨레（ハンギョレ）』と『朝鮮日報（チョソンイルボ）』がそれぞれBridgy FedとThreadsのフェディバースの共有機能を通じてフェディバースに合流！
『한겨레（ハンギョレ）』: @nprofile…z5pj
『朝鮮日報（チョソンイルボ）』: @_chosunilbo_@threads.net
https://uri.life/@alternative/114028356896469672
#nevent1q…r7r4

2025-02-10 06:06:34 UTC

#Yoyak, an #LLM-powered #CLI app for summarizing web pages, now distributes the official executables for Linux, macOS, and Windows!
https://github.com/dahlia/yoyak/releases/tag/0.3.0

2025-02-08 03:27:19 UTC

- reply

安寧(안녕)하세요, 저는 서울에 살고 있는 30代(대) 後半(후반) 오픈 소스 소프트웨어 엔지니어이며, 自由(자유)·오픈 소스 소프트웨어와 聯合宇宙(연합우주)(fediverse)의 熱烈(열렬)한 支持者(지지자)입니다.
저는 TypeScript用(용) ActivityPub 서버 프레임워크인 @nprofile…j979 프로젝트와 싱글 유저用(용) ActivityPub 마이크로블로그인 @nprofile…d3ay 프로젝트와 ActivityPub 봇 프레임워크인 @nprofile…xex2 프로젝트의 製作者(제작자)이기도 합니다.
저는 東(동)아시아 言語(언어)(이른바 #CJK)와 유니코드에도 關心(관심)이 많습니다. 聯合宇宙(연합우주)에서는 國漢文混用體(국한문 혼용체)를 쓰고 있어요! 제게 韓國語(한국어)나 英語(영어), 日本語(일본어)로 말을 걸어주세요. (아니면, 漢文(한문)으로도!)
#툿친소 #연친소 #별친소

2025-02-08 03:27:08 UTC

Hello, I'm an open source software engineer in my late 30s living in #Seoul, #Korea, and an avid advocate of #FLOSS and the #fediverse.
I'm the creator of @nprofile…j979, an #ActivityPub server framework in #TypeScript, @nprofile…d3ay, an ActivityPub-enabled microblogging software for single users, and @nprofile…xex2, a simple ActivityPub bot framework.
I'm also very interested in East Asian languages (so-called #CJK) and #Unicode. Feel free to talk to me in #English, #Korean (#한국어), or #Japanese (#日本語), or even in Literary Chinese (#文言文, #漢文)!
#introduction

2025-02-07 08:33:10 UTC

- reply

@nprofile…pscj 方今(방금) 해 보니까 如前(여전)히 地球本(지구본) 나오네요!

2025-01-24 08:38:26 UTC

The Date is dead, long live the Temporal!
https://developer.mozilla.org/en-US/blog/javascript-temporal-is-coming/