洪 民憙 (Hong Minhee)

The #CFP for the Fediverse & Social Web track at COSCUP 2026 (Taipei, Aug 8–9) is now open! If you're working on #ActivityPub, the #fediverse, or anything in the open social web space, we'd love to hear from you. The deadline is May 9. #COSCUP is free to attend.

👉 https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp

(Boosts appreciated!)

#SocialWeb #fedidev

#COSCUP 2026（台北、8月8–9日）Fediverse & Social WebトラックのCFPが始まりました！#ActivityPub、#フェディバース、オープンなソーシャルウェブに関わる方のご応募をお待ちしています。締め切りは5月9日、参加費は無料です。

👉 https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp-ja

#fediverse #SocialWeb #fedidev

RE: https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp-ja

#COSCUP 2026(타이베이, 8월 8–9일) Fediverse & Social Web 트랙 발표자 모집이 시작되었습니다! #ActivityPub, #연합우주, 오픈 소셜 웹 관련 주제라면 무엇이든 환영합니다. 마감은 5월 9일이고, COSCUP 참가는 무료입니다.

👉 https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp-ko

#페디버스 #SocialWeb #fedidev

RE: https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp-ko

The #CFP for the Fediverse & Social Web track at COSCUP 2026 (Taipei, Aug 8–9) is now open! If you're working on #ActivityPub, the #fediverse, or anything in the open social web space, we'd love to hear from you. The deadline is May 9. #COSCUP is free to attend.

👉 https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp

(Boosts appreciated!)

#SocialWeb #fedidev

RE: https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp

他の言語で読む：English（英語）、한국어（韓国語）。

FediLUGとFediDev KRは、COSCUP 2026 フェディバース & ソーシャルウェブトラックを開設し、発表の提案を募集します。

COSCUP（Conference for Open Source Coders, Users, and Promoters）は、台湾・台北で毎年開催される無料のオープンソースカンファレンスです。東アジア版のFOSDEMとイメージしていただければわかりやすいかと思います。今年は8月8–9日に国立台湾科技大学にてUbuCon Asia 2026と共同開催されます。

フェディバース & ソーシャルウェブトラックは1日間、計6時間を予定しています。東アジアの主要なオープンソースカンファレンスで開かれる初のフェディバース専用トラックとして、東アジアのフェディバースコミュニティが定期的に集まる場になることを願っています。

発表形式

発表時間のデフォルトは30分です。それより長い・短い時間が必要な場合は、提出時に希望する時間をお知らせください。

トピック

フェディバースおよびオープンなソーシャルウェブに関するテーマであれば、幅広く歓迎します。

• ActivityPub または関連プロトコルの実装
• ActivityPub 対応ソフトウェア向けクライアント
• フェディバース開発のためのライブラリ、ツールキット、フレームワーク
• 検索・オンボーディング・モデレーションなどの支援サービス
• インスタンスの運営・管理
• ガバナンス、ポリシー、連合コミュニティ運営の社会的側面
• より広いオープンソーシャルウェブと相互運用性

重要な日程

• 募集開始：2026年3月28日
• 募集締め切り：2026年5月9日（AoE：世界のどのタイムゾーンでも当日中）
• 採否通知：2026年6月9日
• カンファレンス：2026年8月8–9日

提出方法

https://pretalx.coscup.org/coscup-2026/cfpから提出できます。トラックのドロップダウンでFediverse & Social Webを選択してください。

提案は英語または中国語でご記入ください。COSCUPはセッションの説明を英語と中国語の両言語で掲載しますが、翻訳は採択後に行われるため、提出時に両言語を用意する必要はありません。

すべてのセッションは録画され、CC BY-SA 4.0のもとで公開されます。録画や当該条件での公開が難しい内容が含まれる場合は、提出時にその旨をお知らせください。

行動規範

すべての発表者と参加者は、COSCUP 行動規範（英文）を確認し、遵守してください。

お問い合わせ

トラック、トピック、フェディバース全般に関するご質問は、contact@fedidev.krまたはフェディバースアカウント「@fedidevkr」までお気軽にどうぞ。

다른 언어로 읽기: English (영어), 日本語 (일본어).

한국 연합우주 개발자 모임(FediDev KR)과 FediLUG(일본)이 COSCUP 2026 연합우주(fediverse) & 소셜 웹 트랙을 열고, 발표 제안을 받습니다.

COSCUP은 매년 대만 타이베이에서 열리는 무료 오픈소스 컨퍼런스입니다. FOSDEM의 동아시아판이라고 생각하시면 됩니다. 올해는 8월 8–9일 국립대만과학기술대학교에서 UbuCon Asia 2026과 공동 개최됩니다.

연합우주 & 소셜 웹 트랙은 하루 종일, 총 6시간 진행됩니다. 동아시아의 주요 오픈소스 컨퍼런스에서 열리는 첫 번째 연합우주 전용 트랙으로, 이 자리가 동아시아 연합우주 커뮤니티의 정기적인 모임으로 이어지기를 바랍니다.

발표 형식

기본 발표 시간은 30분입니다. 더 길거나 짧은 시간이 필요하다면 제출 시 희망 시간을 적어주세요.

주제

연합우주 및 오픈 소셜 웹과 관련된 주제라면 무엇이든 환영합니다.

• ActivityPub 또는 관련 프로토콜 구현
• ActivityPub 기반 소프트웨어용 클라이언트
• 연합우주 개발을 위한 라이브러리, 툴킷, 프레임워크
• 검색, 온보딩, 모더레이션 등 지원 서비스
• 인스턴스 운영 및 관리
• 거버넌스, 정책, 연합 커뮤니티 운영의 사회적 측면
• 더 넓은 의미의 오픈 소셜 웹과 상호운용성

주요 일정

• 제출 시작: 2026년 3월 28일
• 제출 마감: 2026년 5월 9일 (AoE, 세계 어느 시간대 기준으로도 해당 날짜 내)
• 결과 통보: 2026년 6월 9일
• 컨퍼런스: 2026년 8월 8–9일

제출 방법

https://pretalx.coscup.org/coscup-2026/cfp에서 제출하실 수 있습니다. 트랙 드롭다운에서 Fediverse & Social Web을 선택해 주세요.

발표 제안은 영어 또는 중국어로 작성해 주세요. COSCUP은 세션 설명을 영어와 중국어로 함께 게시하지만, 번역은 채택 이후에 이루어지므로 제출 시 두 언어를 모두 작성할 필요는 없습니다.

모든 세션은 녹화되어 CC BY-SA 4.0으로 공개됩니다. 녹화하거나 해당 조건으로 공개할 수 없는 내용이 포함되어 있다면 제출 시 명시해 주세요.

행동 강령

모든 발표자와 참가자는 COSCUP 행동 강령(영문)을 숙지하고 준수해야 합니다.

문의

트랙, 주제, 연합우주 전반에 대한 문의는 contact@fedidev.kr 또는 연합우주 계정 @fedidevkr 쪽으로 연락해 주세요.

Read it in other languages: 日本語 (Japanese), 한국어 (Korean).

FediDev KR and FediLUG (Japan) are pleased to announce the Fediverse & Social Web track at COSCUP 2026, and invite participants to submit proposals for talks.

COSCUP (Conference for Open Source Coders, Users, and Promoters) is a free, community-run open source conference held annually in Taipei, Taiwan. Think FOSDEM, but in East Asia. This year it takes place August 8–9 at the National Taiwan University of Science and Technology, and is co-hosted with UbuCon Asia 2026.

The Fediverse & Social Web track runs for a full day, six hours in total. It is the first dedicated fediverse track at a major open source conference in East Asia, and we hope it becomes a regular gathering point for the fediverse community in the region.

Format

The default talk length is 30 minutes. If you need more or less time, note your preferred length when submitting.

Topics

We welcome proposals on anything related to the fediverse and the open social web, including:

• Implementations of ActivityPub or related protocols
• Clients for ActivityPub-enabled software
• Libraries, toolkits, and frameworks for fediverse development
• Supporting services: search, onboarding, moderation tooling
• Instance administration and operations
• Governance, policy, and the social dimensions of running federated communities
• The broader open social web and interoperability

Important dates

• Submission opens: March 28, 2026
• Submission deadline: May 9, 2026 (AoE)
• Acceptance notifications: June 9, 2026
• Conference: August 8–9, 2026

Submissions

Submit proposals at https://pretalx.coscup.org/coscup-2026/cfp. Select Fediverse & Social Web from the track dropdown.

You can write your proposal in English or Chinese. COSCUP publishes session descriptions bilingually in English and Chinese, but that translation happens after acceptance; you don't need to provide both languages when submitting.

All sessions will be recorded and released under CC BY-SA 4.0. If your talk contains material that cannot be recorded or released under those terms, please note this in your submission.

Code of conduct

All speakers and attendees are expected to follow the COSCUP Code of Conduct.

Contact

Questions about the track, topics, or the fediverse in general are welcome at contact@fedidev.kr or @fedidevkr on the fediverse.

„The question isn't whether to use LLMs or adapt to them; that ship has sailed. The question is who owns the models. Who benefits from the commons that trained them? If millions of F/OSS developers contributed their code to the public domain, should the resulting models be proprietary? This isn't just about centralization or market dynamics. It's about whether the fruits of collective labor remain collective, or become private property.“ https://writings.hongminhee.org/2026/01/histomat-foss-llm/ #links

“I want my code to be used for LLM training. What I don't want is for that training to produce proprietary models that become the exclusive property of AI corporations. The problem isn't the technology or even the training process itself. The problem is the enclosure of the commons, the privatization of collective knowledge, the one-way flow of value from the many to the few.” https://writings.hongminhee.org/2026/01/histomat-foss-llm/

📢 Call for Proposals is Now Open!

Every year the tracks get packed to the max (don’t believe us? Check it out 👇)
👉 [https://s.coscup.org/26cfp]

Go ahead and pick the topics you want to share 👀

@sou7 おお、韓国語の勉強を始められたんですね！日本語話者にとって韓国語は学びやすい言語ですから、少しずつでもコツコツ続ければ、すぐに上達しますよ！頑張ってください！

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

Another day, another supply chain attack, this time Axios: https://github.com/axios/axios/issues/10604

Makes me glad I'm lazy and intentional about dependency updates. But it's a worrying trend. Soon we'll be tracking these things by the hour.

@silverpill Fair, but a lot of the celebrated ones (network effects, data gravity, ecosystem lock-in) work by making you hard to leave. The competitive advantage and the trap are often the same mechanism.

The fediverse is full of real life superheros.

Let's shed some light on a few:

@aral - Building https://kitten.small-web.org + @gazaverified

@quillmatiq - Building https://brid.gy + @anewsocial

@silverpill - Managing FEPs + @mitra

@julian - Building @nodebb

@jesseplusplus - Building @frequency

@jaz - Building @teamtoot + @iftas

@thisismissem - Building https://fires.fedimod.org

@benpate - Building https://emissary.dev

@koen - Building https://procolix.eu

Show em' some ❤️

This article is also a great example of confirmation bias. The bias being that AI is destroying the planet, so this article *must* be correct and factual.

The researchers are trying to attribute the heat increase to the servers running within the data centers, when we know from other research that this likely isn't the case. We have other explanations, they just didn't fit the narrative for this story.

Many datacenters have switched to closed loop cooling systems & have realised that the heat the servers produce is actually a resource they can sell, whether through heat exchange programs or municipal heat networks, or to industrial users who often need heat. Not capturing that heat your datacenters are producing would literally be throwing money away, burning cash.

So I'm seeing this article from NewScientist going around here too, and I'm begging people to use their critical thinking skills for just one minute. This article is misinformation, it is correlation without causation, and honestly, New Scientist should be ashamed at publishing it.

https://www.newscientist.com/article/2521256-ai-data-centres-can-warm-surrounding-areas-by-up-to-9-1c/

They've now put it behind their paywall, it's quite literally clickbait to convert people to subscribers. Let's look at some of the claims:

”Marinoni says that areas including the Bajío region in Mexico and the Aragon province in Spain saw a 2°C (3.6°F) temperature increase in the 20 years between 2004 and 2024 that couldn’t otherwise be explained.“

I can think of one very easy reason why temperatures in these two regions may have gotten warmer, and it's not data centres: climate change.

We know that climate change on average increased temperatures 1-2°c, meaning some areas saw higher increases than others.

As someone else called out "the Bajio region has a metric fucktonne of oil processing in Salamanca and is a plateau region ringed by mountains so yeah"

yeah, I'm sure it was the data centres and uh, definitely not those oil refineries.

In the most extreme case, the researchers said "temperatures increased by 9.1°C", now, unless we're talking about Elon Musk's data centres which are breaking EPA rules by using multiple truck-sized gas turbine generators, maybe there's another reason for this increase?

Let's have a think about where datacenters are built: they tend to be built on greenfield sites, because that is where land is cheapest.

Once one datacenter moves in, other providers usually follow, so we're looking at temperature increase data for land that has gone from literally being a green field with trees, to a concrete, asphalt roads, and metal roofs with very little green space nor tree coverage.

We know the built environment without tree coverage causes the urban heat island effect, where neighborhoods in the same city with and without tree coverage show significantly different temperatures.

"The urban heat island effect can make the country's most populated cities 20 degrees Fahrenheit warmer than nearby areas" – CBS News explaining heat island effect.

@dansup Thanks!! 🥰

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

https://github.com/fedify-dev/botkit/discussions/20

샤라웃되었다. 끼얏호우~

BotKit 0.4.0 is out! This release adds @fedify/botkit-postgres, a PostgreSQL-backed repository for deployments where SQLite isn't enough; a remote follow button on the bot profile page, so visitors can follow directly without manually searching from their own instance; and Session.republishProfile(), which lets you push profile changes to followers without waiting for the next post. It also upgrades the underlying Fedify dependency to 2.1.2, with a few small breaking API changes.

Full release notes:

https://github.com/fedify-dev/botkit/discussions/20

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.

🚀 Spaces has landed on Element X!

Navigate chats by department, project or interest - no more overwhelming room lists.

✨ What’s new: filtered chat lists, dedicated Spaces tab, flexible room creation and previews with context.

👉 Download Element X and explore Spaces today!

https://element.io/blog/spaces-has-landed-on-element-x/

After a pretty long break, I'm back to working on @botkit. The upcoming v0.4.0 isn't going to be a big release—mainly a major @fedify version bump and some general cleanup—but it felt like time to dust it off.

An excellent "Introduction to Writing Systems & Unicode" and its "Large character sets", by Richard Ishida @ri

https://r12a.github.io/scripts/tutorial/part2

#Unicode #WritingSystems #CharacterSets #r12a

《標準國語大辭典(표준국어대사전)》 MCP 서버를 만들었습니다.

旣存(기존)에도 《標國大(표국대)》 MCP들이 있긴 한데, 그냥 標題語(표제어)랑 뜻풀이만 덜렁 주는 데다가, 每番(매번) stdict.korean.go.kr 서버에 要請(요청)하는 式(식)으로 作動(작동)해서 레이트 리미트에 걸리더라고요. 제가 만든 건 아예 全體(전체) 辭典(사전) 데이터를 맨 처음에 받은 다음에 그걸 SQLite에 넣고 照會(조회)합니다.

"But I fundamentally disagree with the conclusion.
The proposed solution is denial and isolation: block the crawlers, withdraw from centralized forges like GitHub, make our work inaccessible to AI scrapers, shun those who use these “anti-ethical tools” from our communities. I understand the anger behind it. But I think it misses something important and misreads the historical pattern that has shaped FLOSS itself."

We should reclaim LLMs, not reject them

https://writings.hongminhee.org/2026/01/histomat-foss-llm/

@jnkrtech Oh, “crazy” and “sane” hadn't crossed my mind, but you're right, and those are everywhere in tech. “Sanity check” especially; I use it without thinking. Good point.