洪 民憙 (Hong Minhee)

Is legal the same as legitimate: AI reimplementation and the erosion of copyleft by @hongminhee https://lobste.rs/s/52jd6f #law #vibecoding
https://writings.hongminhee.org/2026/03/legal-vs-legitimate/

最近(최근) chardet의 MIT 리라이선싱과 關聯(관련)해서 Redis의 antirez와 Flask의 Armin Ronacher(一名(일명) mitsuhiko)가 이를 擁護(옹호)하는 글을 썼는데, 그에 對(대)한 나름대로의 反論(반론)을 써 봤습니다: 〈合法(합법)이면 公正(공정)한가: AI 再具顯(재구현)과 카피레프트의 侵蝕(침식)〉(한글).

Salvatore Sanfilippo (@antirez) and Armin Ronacher (@mitsuhiko) 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

Hey #ActivityPub friends. Are there any new ActivityPub / Mastodon features I should add to #ActivityBot?

It's a small bot-only ActivityPub server in a single PHP file.

https://gitlab.com/edent/activity-bot/

It can be followed, post images, allow quote posts, etc.

Is there anything else you would like a bot-server to be able to do?

오랜만에 中國(중국)에도 놀러 가고 싶네…

バーガー屋さんのSoul Grillに来た。

高尾山口駅まで来た。

豆腐料理店の空野に来た。

RE: https://social.coop/@scottjenson/116194411751413071

I think this every time, but also I think most of the time it's actually from older versions of mastodon, software that doesn't support the feature or or posts made before the feature existed.

ConfConf 2026 has been announced!

Website: https://confconf.org/

What: A free conference for organisers of conferences around free and open source software and hardware, and the surrounding ecosphere

Dates: June 6&7 2026

Location: Sofia, Bulgaria

Cost: free, supported by FOSDEM and Grafana Labs

If you are a conference organiser of a conference in FOSS ecosphere and would like to attend, reach out to request a voucher.

#confconf #conference

@kodingwarrior 좋은 생각!

@soapdog There's a poll-based version specced at https://fediverse.codeberg.page/fep/fep/b06c/, sadly with no notable implementations (wouldn't be interactable by Mastodon etc.), but it's an opportunity to break new ground as an implementer if you know anyone who'd like to experiment with it.

#ActivityPub #FediDev

I wish #ActivityPub was a "pull" protocol instead of a "push" protocol. The way it works, whenever you take an action, it sends that action to all followers. I would prefer if it simply stored them and then let each follower pull them when they see fit.

That would introduce latency and more async comms as your messages wouldn't pop up into someone elses feed until their software fetch the data, but I think it would make it easier to self host.

@smallcircles Thanks for suggestion!

I'm thinking of proposing a #fediverse/social web community track at @COSCUP 2026 (Aug 8–9, Taipei)—think FOSDEM's Social Web devroom, but in East Asia. Before I submit the CFP, I'd love to get a sense of what to call it. What do you think?

(Boosts appreciated!)

#ActivityPub #SocialWeb #fedidev #COSCUP

@silverpill @phnt That's a fair clarification, and worth being precise about on my end too.

I'm not arguing for historical inevitability—I don't think that's a useful frame for anyone here. What I was saying is closer to a personal read of the current situation: a lot of developers already depend on LLMs in their day-to-day work, and that number seems to be growing quickly. That's an observation, not a law of history, and I could be wrong about where it leads.

The NFT comparison is interesting and I won't dismiss it. My intuition is that LLMs are a different kind of thing—they've become embedded in actual workflows in ways NFTs never were—but I hold that loosely. Technologies do fail in unexpected ways.

What I'm more confident about is the narrower point: maintainers have real authority over their own projects, and I think there's more room in that space than “accept everything” or “reject all AI-assisted contributions.” My own approach with Fedify has been to set conditions rather than draw a line: disclose what you used, show you've actually tested it. Whether that's the right call, others can judge: https://github.com/fedify-dev/fedify/blob/main/AI_POLICY.md.

@alvan Yeah, C# is already kinda feature creep… 😭

蒙古タンメン中本に来た。

C# 15 & .NET 11 preview 3 finally got discriminated unions!

https://github.com/dotnet/csharplang/blob/main/proposals/unions.md

@silverpill @phnt

@silverpill is right that maintainers hold real authority here, and I want to build on that rather than argue against either of you.

The frustration with LLMs is largely legitimate. But “how does this look to outsiders” is a poor criterion for evaluating ethical concerns; by that standard, feminism looks like lunacy to 4chan. The question is whether the concerns are correct, not whether they're legible to the unconvinced.

That said, I don't think making LLMs socially unacceptable is a viable path, and not just because the adoption curve has run too far. The maintainer's authority is real precisely because it's specific: you decide what enters your project. Refusing AI-assisted contributions is a legitimate choice. But declaring LLM use itself impermissible starts to look like “I only accept patches written in Vim, not IDE-generated code”—a demand that grows harder to justify as the tools become ordinary. As maintainer of Fedify, I've taken a middle path: disclose what you used, show you've tested it yourself, and we're fine. See also https://github.com/fedify-dev/fedify/blob/main/AI_POLICY.md.

What worries me more is that the “total rejection vs. total acceptance” framing leaves the actual problem untouched. If we stay inside that binary, OpenAI and the others keep the models, keep the surplus, keep the compute bills externalized onto the climate—with no pressure to change any of it. The ethical problems with LLMs aren't properties of the technology; they're properties of who owns it and under what terms. I've written about this in more depth if it's of interest: Histomat of F/OSS: We should reclaim LLMs, not reject them and a follow-up Acting materialistically in an imperfect world: LLMs as means of production and social relations.

Whoa. UTF-8 is older now than ASCII was when UTF-8 was invented.

We've just added an English homepage for FediDev KR, a community of fediverse developers living in Korea or using the Korean language.

If you're interested in connecting with Korean-speaking fediverse developers, feel free to check it out: https://fedidev.kr/en/.

The Release Candidate for TypeScript 6.0 is now available!

Read up on what's coming up with 6.0 & 7.0, and try it out on your codebase today!

https://devblogs.microsoft.com/typescript/announcing-typescript-6-0-rc/

Today, I had lunch with @Yohei_Zuho and @kur0den0010 from FediLUG Japan, along with @nebuleto from FediDev KR, and it looks like something exciting is going to happen at @COSCUP 2026! Stay tuned!

明日起きたらDeno+Hono+Fedifyに入門する。
おやすも

Has anyone made a good guide for how to ask for survival money on the fediverse yet? One that outlines how tagging strangers isn't a good long term strategy. That it can temporarily work for engagement but sooner or later you will either loose your account or get blocked so much that you don't have much reach. There is this influx of people trying to crowd fund for their survival coming here and we should help provide them with the means to continue to do so sustainability.

오늘 FediLUG 日本(일본)의 @Yohei_Zuho 님과 @kur0den0010 님, 韓國(한국) 聯合宇宙(연합우주) 開發者(개발자) 모임의 @nebuleto 님과 제가 모여서 함께 點心(점심) 食事(식사)를 했습니다. 아무래도 @COSCUP 2026에서 聯合宇宙(연합우주)와 關聯(관련)된 재밌는 일이 일어날 것 같으니, 많은 期待(기대) 付託(부탁)드립니다!

@Yohei_Zuho 一緒に頑張りましょう！これからよろしくお願いします！

えらいことになってきた

Today, I had lunch with @Yohei_Zuho and @kur0den0010 from FediLUG Japan, along with @nebuleto from FediDev KR, and it looks like something exciting is going to happen at @COSCUP 2026! Stay tuned!