洪 民憙 (Hong Minhee) :nonbinary:'s avatar

洪 民憙 (Hong Minhee) :nonbinary:

@hongminhee@hollo.social

1,131 following1,649 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 , , , & . They/them.

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

()

@hollo@hollo.social

Hollo security updates: 0.8.18 and 0.9.26

If you run Hollo, update to 0.8.18 or 0.9.26 now. These releases fix two vulnerabilities in Hollo: stored cross-site scripting (GHSA-534j-mgxh-5pj3) and server-side request forgery in link previews (GHSA-wh53-vmw6-c48j). They also include four security fixes from Fedify.

For GHSA-534j-mgxh-5pj3, Hollo rendered some remote post bodies and author display names as HTML without sanitizing or escaping them. A remote account could supply content that runs a script in a visitor's browser when the visitor opens an affected post or profile page. The fix sanitizes post bodies and escapes display names when rendering them, including in replies, shares, and quotes already stored in the database. It also escapes custom emoji image URLs used in HTML attributes.

For GHSA-wh53-vmw6-c48j, a remote account whose post Hollo processed could cause Hollo to send preview requests to services on its own host or private network. Large preview responses could also consume server memory. Hollo now checks the initial destination and each redirect, restricts connections to validated public addresses, and limits responses to 1 MiB after decompression. The preview fetch has its own address checks, separate from Fedify's ALLOW_PRIVATE_ADDRESS setting.

Hollo uses Fedify to resolve remote handles, deliver outgoing activities, and look up NodeInfo when it records a remote instance. Remote servers that stalled could tie up those operations. The updated dependency gives WebFinger lookups a 10-second deadline and bounds remote handle resolution (GHSA-9pmv-w936-hj3f). Activity delivery now has a 30-second deadline per attempt, with timed-out attempts subject to the configured retry schedule (GHSA-fq5h-gjhp-g75x). NodeInfo lookups have a 10-second default deadline and stop following redirect loops (GHSA-64hq-2hgr-q4pm).

Fedify also tightened origin checks on embedded ActivityPub objects (GHSA-r388-57j3-5fgp). When processing remote objects, it now applies those checks even if the parent has no id, so it no longer trusts embedded objects from another origin in that case. See the Fedify security announcement for details on the upstream fixes.

On the supported Hollo release lines, upgrade if you run 0.8.x through 0.8.17 or 0.9.x through 0.9.25. 0.8.18 and 0.9.26 are the first releases on their respective lines to include these fixes and the versions we recommend. They ship with Fedify 2.1.32 and 2.2.21, respectively. Hollo 0.7.x and earlier are no longer supported under the Hollo security policy; move to a supported line.

For 0.8.x deployments, update to 0.8.18:

docker pull ghcr.io/fedify-dev/hollo:0.8.18

For 0.9.x deployments, update to 0.9.26:

docker pull ghcr.io/fedify-dev/hollo:0.9.26

Recreate your Hollo container after pulling the new image. With Docker Compose, update the image tag in your Compose file and run docker compose up -d. For source deployments, check out the corresponding release tag, run pnpm install --frozen-lockfile with the pnpm version pinned in that tag's package.json, run pnpm run build, and restart the server.

If you have a large 0.9.x database and are upgrading from before 0.9.20, follow the 0.9.20 index preparation instructions before starting the new version to avoid blocking writes during the automatic migration.

Thanks to @carfeii for reporting the stored cross-site scripting issue and to @thegruber for reporting the link preview issue to Hollo. Thanks to zx (@manus-pi) for reporting the WebFinger, delivery, and NodeInfo issues to Fedify, to @manus-use for reporting the WebFinger and NodeInfo issues, and to @hongminhee for reporting the embedded-object origin-check issue.

If anything is unclear, ask below.

github.com

manus-use - Overview

Security Researcher | Sharing practical Cybersecurity Knowledge - manus-use

@fedify@hackers.pub

Fedify security updates: 2.0.36, 2.1.32, 2.2.21, 2.3.16, and 2.4.6

If you use an affected Fedify release, update now. Six vulnerabilities have been fixed: an embedded-object origin-check bypass (GHSA-r388-57j3-5fgp), two content-spoofing issues in backfill (GHSA-x58x-xx7h-7rh4 and GHSA-h3jv-px69-2gpj), and missing deadlines in WebFinger lookups (GHSA-9pmv-w936-hj3f), outbound activity delivery (GHSA-fq5h-gjhp-g75x), and NodeInfo lookups (GHSA-64hq-2hgr-q4pm).

We recommend 2.4.6, or 2.3.16 if you are staying on 2.3. Both releases contain all six fixes. The security policy covers the latest two minor lines, currently 2.3 and 2.4. Backports for the four issues outside @fedify/backfill are available in 2.0.36, 2.1.32, and 2.2.21. If you rely on one of those backports, plan to move to a supported line. If you are running an affected 1.x release, change your dependency to a supported 2.x release.

Embedded-object origin-check bypass (GHSA-r388-57j3-5fgp, medium, CVSS 3.1 score 5.3)

When reading remote JSON-LD, a vocabulary accessor could skip the origin check on an embedded object whose parent has no id. Inbox listeners, backfill, and applications that read embedded objects directly can receive forged content and store or display it under another server's ID. A valid signature on an incoming activity does not establish ownership of an embedded object's ID. The fix applies the origin check even when the parent lacks an id.

This affects @fedify/fedify, @fedify/vocab, and code generated by @fedify/vocab-tools before the patched release on each of the 2.0–2.4 lines. It also affects the vocabulary bundled with Fedify 1.9 and 1.10. No 1.x patch is planned, and older releases that lack the origin check are not a safe downgrade. If you cannot update immediately, use lookupObject() under the default origin policy to fetch embedded or backfilled objects by ID before storing or displaying them, and use only the fetched copy.

Backfill trusted cross-origin embedded content (GHSA-x58x-xx7h-7rh4, high, CVSS 3.1 score 7.5)

Backfill could return embedded content that falsely claimed to come from another server. An application that stores backfill results by ID could overwrite genuine content or poison its cache. The fix restores the default vocabulary origin policy, which can require additional fetches. Backfill results are still unverified remote data; checking the origin does not prove authorship.

Backfill accepted forged IDs from custom loaders (GHSA-h3jv-px69-2gpj, high, CVSS 3.1 score 7.5)

Applications using a custom BackfillDocumentLoader were exposed if the loader did not check the returned object's ID against the origin it fetched from. Backfill could then ingest a forged collection or post under another server's ID. The fix rejects results whose ID origin differs from the requested IRI's origin. That can also exclude legitimate cross-origin redirects.

Both backfill issues affect @fedify/backfill before 2.3.16 on the 2.3 line and before 2.4.6 on the 2.4 line. Upgrade @fedify/backfill and make sure it resolves the matching patched @fedify/vocab; the backfill update alone does not fix the vocabulary issue. If you supply a custom loader, follow the backfill documentation: use lookupObject() with the default origin policy and set documentUrl to the final response URL in your JSON-LD loader.

WebFinger lookups could stall without a deadline (GHSA-9pmv-w936-hj3f, high, CVSS 3.1 score 7.5)

When an application resolves a handle from an untrusted source, a slow remote WebFinger endpoint can tie up the lookup. This can also affect inbox processing when an activity re-fetch falls back to WebFinger. @fedify/webfinger is affected before the patched release on each of the 2.0–2.4 lines.

The fix gives each WebFinger lookup one 10-second deadline, including DNS, redirects, and response reading. Non-portable actor handle resolution shares a 10-second budget across the initial lookup and alias verification. This is not a deadline for all of lookupObject(): on the 2.0–2.3 lines, the default document loaders still have no deadline of their own. Set a deadline in your document loader or move to 2.4.6 if you need bounded document fetches.

Outbound delivery could stall without a deadline (GHSA-fq5h-gjhp-g75x, high, CVSS 3.1 score 7.5)

A slow remote inbox could hold delivery workers and connections open, delaying deliveries to other servers. The advisory confirms the unsigned delivery issue starting in @fedify/fedify 2.0.28. Signed delivery also lacked a deadline, and that behavior predates 2.0.28; the earliest affected signed release has not been established.

The patched releases above give each delivery attempt a single 30-second deadline across connection setup, redirects, signature retries, and response reading. If an attempt times out before a final response arrives, it can be retried under the configured delivery schedule.

NodeInfo lookups could stall without a deadline (GHSA-64hq-2hgr-q4pm, medium, CVSS 3.1 score 5.3)

A slow remote server could keep a NodeInfo lookup waiting. This affects applications that explicitly query untrusted server URLs and operators who use fedify nodeinfo against those servers. Inbound federation does not automatically trigger NodeInfo lookups. The issue is confirmed as far back as @fedify/fedify 2.0.26; the advisory does not establish when it was introduced. Update @fedify/fedify and any separately installed @fedify/cli.

The fix adds one 10-second default deadline across discovery, redirects, and document fetching. A timeout or cancellation returns undefined from the API. The API's timeout option is in milliseconds; keep it bounded when querying untrusted servers, since timeout: null disables the deadline. The CLI's -T/--timeout option is in seconds and defaults to 10.

Updating

Use the command for your package manager to install 2.4.6:

npm  install @fedify/fedify@2.4.6
yarn add     @fedify/fedify@2.4.6
pnpm add     @fedify/fedify@2.4.6
bun  add     @fedify/fedify@2.4.6
deno add     jsr:@fedify/fedify@2.4.6

If you stay on another minor line, substitute the patched version listed above. Update any direct dependencies on @fedify/vocab, @fedify/webfinger, and @fedify/vocab-runtime to the matching release, and update @fedify/backfill if you use it. If you generate custom vocabulary classes, update @fedify/vocab-tools and @fedify/vocab-runtime to the matching release, then regenerate your classes and rebuild. Check your lockfile for older direct or transitive copies of the affected packages, then redeploy all web and worker processes.

For an npm-installed global CLI:

npm install -g @fedify/cli@2.4.6

For other installation methods, use the CLI installation instructions and check the installed release with fedify --version.

Thanks to @dahlia for reporting the embedded-object origin-check bypass and the cross-origin backfill issue, and to @z9mb1 for reporting the custom backfill loader issue. Thanks to zx (@manus-pi) for reporting the WebFinger, delivery, and NodeInfo issues, and to @manus-use for reporting the WebFinger and NodeInfo issues.

If anything is unclear, ask below.

github.com

manus-use - Overview

Security Researcher | Sharing practical Cybersecurity Knowledge - manus-use

@hongminhee@hollo.social

JSConf JP 2026で登壇することになりました。11月22日(日)、東京のベルサール神田で開催されます。

タイトルは「Oseo:SBCLスタイルのJavaScript/TypeScript AOTコンパイラ」。SBCLやChez Schemeのように、動的型付き言語でありながらプログラム全体を事前にネイティブコードへコンパイルするJavaScriptエンジンを作っている、その話をします。TypeScriptの型注釈は最適化のヒントとして使うだけで、決して鵜呑みにしない。ヒントが嘘でも動作は変わらない。そんな設計の話です。

発表は日本語、30分枠、14:10からトラックCです。詳細はこちら。

https://jsconf.jp/2026/ja/talks/hong-minhee

会場でお会いできたら嬉しいです。

jsconf.jp

Oseo:SBCLスタイルのJavaScript/TypeScript AOTコンパイラ | JSConf JP 2026

Common LispのSBCLやSchemeのChez Schemeは動的型付き言語でありながら、プログラム全体を事前にネイティブコードへコンパイルし、何十年もプロダクションで使われてきました。一方JavaScriptは今なお、速く動くにはインタプリタと複数段のJIT、その上に載るデオプティマイゼーション機構が要る言語だと見なされています。この違いはどこから来るのか。この問いから始まったプロジェクトがOseoです。 Oseoはすべての関数を二重にコンパイルします。言語のフルセマンティクスを実装するジェネリックパスが一つあり、値の種類や形状に対して安価なランタイムガードを掛けられる箇所には、その隣に特殊化されたパスを並べます。ガードが失敗すれば、バイナリの中にすでにコンパイルされているジェネリックパスへ分岐するだけです。インタプリタへ落ちることも、デオプティマイズすることもありません。TypeScriptの型表記やJSDocはこの特殊化パスを選ぶヒントとして使われますが、決して鵜呑みにされることはありません。`any`や型アサーション、素のJavaScriptとの相互運用のせいで`: number`という表記はいつでも誤りうるので、Oseoはその可能性をガードで防ぎます。 この発表では、このアイデアが実際にどう動くのかをコードとバイナリで直接お見せします。Node.jsもDenoも使わず、V8が一切リンクされていない純粋なネイティブ実行ファイルがどう作られるか。`--dump-mir`と`--emit-c`で覗いた生成コードの中で、一つのガードが実際にどんな比較と分岐にコンパイルされるか。型ヒントが実行結果を変えてはならないという原則も、同じ領域にある別プロジェクトとの具体的な比較を通じて見ていきます。 Oseoはまだ完成したプロジェクトではありません。この発表は、これまでに証明できたことと、まだ残っている道のりを一緒にお見せする場でもあります。ネイティブI/O、ガベージコレクタ、セルフホスティングまで、システムプログラミングに関心がある方なら貢献できる余地がまだたくさんあります。

@hongminhee@hollo.social

今週の日曜日にJSConf JP 2026で発表するんだけど、スライドがまだ1枚もできてない。果たして無事に発表できるのか… 😱

jsconf.jp

Oseo:SBCLスタイルのJavaScript/TypeScript AOTコンパイラ | JSConf JP 2026

Common LispのSBCLやSchemeのChez Schemeは動的型付き言語でありながら、プログラム全体を事前にネイティブコードへコンパイルし、何十年もプロダクションで使われてきました。一方JavaScriptは今なお、速く動くにはインタプリタと複数段のJIT、その上に載るデオプティマイゼーション機構が要る言語だと見なされています。この違いはどこから来るのか。この問いから始まったプロジェクトがOseoです。 Oseoはすべての関数を二重にコンパイルします。言語のフルセマンティクスを実装するジェネリックパスが一つあり、値の種類や形状に対して安価なランタイムガードを掛けられる箇所には、その隣に特殊化されたパスを並べます。ガードが失敗すれば、バイナリの中にすでにコンパイルされているジェネリックパスへ分岐するだけです。インタプリタへ落ちることも、デオプティマイズすることもありません。TypeScriptの型表記やJSDocはこの特殊化パスを選ぶヒントとして使われますが、決して鵜呑みにされることはありません。`any`や型アサーション、素のJavaScriptとの相互運用のせいで`: number`という表記はいつでも誤りうるので、Oseoはその可能性をガードで防ぎます。 この発表では、このアイデアが実際にどう動くのかをコードとバイナリで直接お見せします。Node.jsもDenoも使わず、V8が一切リンクされていない純粋なネイティブ実行ファイルがどう作られるか。`--dump-mir`と`--emit-c`で覗いた生成コードの中で、一つのガードが実際にどんな比較と分岐にコンパイルされるか。型ヒントが実行結果を変えてはならないという原則も、同じ領域にある別プロジェクトとの具体的な比較を通じて見ていきます。 Oseoはまだ完成したプロジェクトではありません。この発表は、これまでに証明できたことと、まだ残っている道のりを一緒にお見せする場でもあります。ネイティブI/O、ガベージコレクタ、セルフホスティングまで、システムプログラミングに関心がある方なら貢献できる余地がまだたくさんあります。

@hongminhee@hollo.social

I released Optique 1.4.0, a type-safe CLI parser for TypeScript.

If your CLI has one main action and a few subcommands, you can now set a default command. For example, app src/main.ts can run the same action as app run src/main.ts, while app build still runs its own subcommand. No need to rewrite argv yourself.

https://github.com/dahlia/optique/discussions/1139

github.com

Optique 1.4.0: Default commands, Markdown references, and more focused help · dahlia/optique · Discussion #1139

Optique is a type-safe combinatorial CLI parser for TypeScript built from composable parser functions. Parser definitions drive runtime parsing, help and completion output, and the inferred value t...

@hongminhee@hollo.social

I have to show off this little flying squirrel. My spouse, @tokolovesme, drew it for Oseo, a new F/OSS project I've been spending a lot of time on lately.

The name Oseo comes from the Sino-Korean reading of 鼯鼠, which means “flying squirrel.”

The Oseo logo: a black silhouette of a flying squirrel seen head-on against a white background. It has rounded ears, four paws spread wide, two white curved eyes, and a white dot for a nose. Its tail curves down and to the right.
ALT text

The Oseo logo: a black silhouette of a flying squirrel seen head-on against a white background. It has rounded ears, four paws spread wide, two white curved eyes, and a white dot for a nose. Its tail curves down and to the right.

Five black flying squirrel sketches on a white page, with handwritten Korean notes and arrows. The center sketch, boxed in red and outlined in green, is labeled “this one focuses on the shape of a flying squirrel” (이건 날다람쥐 形態에 焦點). A similar sketch on the right has notes that read “this one is truer to the shape of  ✧ a star” (이건  ✧ 별이 더 正直한 模樣) and “star + face + tail” (별 + 얼굴 + 꼬리).

The small squirrel at the bottom became the logo. It has round ears, outstretched paws, white crescent eyes, a dot for a nose, and a curved tail. A note beside it reads, “I drew this in 30 seconds. Is it daijōbu (‘okay’ in Japanese) …?” (30秒만에 그린 건데 大丈夫[다이죠부]…?)
ALT text

Five black flying squirrel sketches on a white page, with handwritten Korean notes and arrows. The center sketch, boxed in red and outlined in green, is labeled “this one focuses on the shape of a flying squirrel” (이건 날다람쥐 形態에 焦點). A similar sketch on the right has notes that read “this one is truer to the shape of ✧ a star” (이건 ✧ 별이 더 正直한 模樣) and “star + face + tail” (별 + 얼굴 + 꼬리). The small squirrel at the bottom became the logo. It has round ears, outstretched paws, white crescent eyes, a dot for a nose, and a curved tail. A note beside it reads, “I drew this in 30 seconds. Is it daijōbu (‘okay’ in Japanese) …?” (30秒만에 그린 건데 大丈夫[다이죠부]…?)

@hongminhee@hollo.social

With Codeberg down, I can still read the Fediverse Enhancement Proposals (FEPs) on Codeberg Pages: https://fediverse.codeberg.page/fep/.

I can't clone the Git repo from Codeberg right now, though. I found a copy at https://github.com/social-web-foundation/fep, but it looks like it hasn't been updated in a while.

It got me thinking: it'd be nice to have a mirror for days like this. Maybe the existing GitHub copy could serve as the mirror, or one could live on another forge like @codefloe. Codeberg would still be the home for FEPs; the mirror would just give us somewhere else to clone from.

github.com

GitHub - social-web-foundation/fep

Contribute to social-web-foundation/fep development by creating an account on GitHub.

@Codeberg@social.anoxinon.de

codeberg.org is unfortunately down right now due to a yet undefined issue with our domain. It was not expired and not transferred, the domain is completely gone from our account and we did not receive any email notifications, and it is currently in the status clientHold. We are currently trying to contact our registrar to get more information right now & trying to resolve this issue, but this is probably going to take some time.

We are sorry for the inconveniences & are working on a solution.

@Codeberg@social.anoxinon.de

codeberg.org is unfortunately down right now due to a yet undefined issue with our domain. It was not expired and not transferred, the domain is completely gone from our account and we did not receive any email notifications, and it is currently in the status clientHold. We are currently trying to contact our registrar to get more information right now & trying to resolve this issue, but this is probably going to take some time.

We are sorry for the inconveniences & are working on a solution.

@pkgupdt@fedi1.pkgu.net

https://magicant.github.io/yash/

내가 interactive shell로 쓰고 있는 Yet Another Shell. 일본인 개발자가 만들어서, 다국어 지원이 잘 되어 있어서 쓰기 시작했는데, 쓸수록 좋다. 무엇보다 소규모 오픈소스 플젝에서 이렇게까지 자동화 테스트 코드가 있는 건 처음 본다. 숙련된 개발자가 소중하게 작성해 온 플젝. 무엇보다 곳곳에서 보이는 꼼꼼함이 맘에 든다. 나도 이런 코드를 남기면 좋겠다.

magicant.github.io

Yash: yet another shell - a POSIX command line shell

@Steve_Bate@mastodon.social
@dansup@mastodon.social

Fediverse Events + FediDB.

Imagine being able to plan a fediverse event (online, in-person or both) without a specific date or venue, and seek interested attendees that can indicate if they Will Attend or Maybe Attend, with a comment feed and the ability to send event updates to them via DM on FediDB.

All the pieces were there, I just needed to connect and polish them. Shipping soon!

FediDB events feature
ALT text

FediDB events feature

@_elena@mastodon.social

Good morning Fedi friends!

Routine reminder that the at is accepting proposals for talks.

There are two available formats: 25 minutes and 8 minutes.

More details are available here:
🔗 : lists.fosdem.org/hyperkitty/li

⏳ The submission deadline is November 27. Acceptance notifications come soon thereafter, on December 1.

📝 You can submit your proposal here: pretalx.fosdem.org/fosdem-2027

I'll be working on my proposal this week 🤗

pretalx.fosdem.org

FOSDEM 2027

Schedule, talks and talk submissions for FOSDEM 2027

@kizu@front-end.social

New blog post: “Cursors”.

blog.kizu.dev/cursors/

In which I take a cursory glance at a victory that CSSWG did hand out to us in this pointless debate about if buttons have more in common with blank space compared to links.

blog.kizu.dev

Cursors

In which I take a cursory glance at a victory that CSSWG did hand out to us in this pointless debate about if buttons have more in common with blank space compared to links.

@socialcg@w3c.social

A new draft report from the Community Group is now available: "Seek Item".

It defines a new (optional) endpoint that ActivityPub API clients can use to efficiently access a page in an OrderedCollection that contains a specific item, such as the one the client has last seen. This can improve efficiency and responsiveness of ActivityPub clients.

swicg.github.io/activitypub-ap

swicg.github.io

Seek Item

@hongminhee@hollo.social

The three of us who maintain Fedify (@z9mb1, @2chanhaeng, and I) have all submitted proposals to the Social Web devroom at FOSDEM 2027. I wonder how many of us will get to give a talk. I'll probably talk about implementing portable objects (FEP-ef61) in Fedify, @z9mb1 will cover how Fedify has evolved over the past year and what lies ahead, and @2chanhaeng will talk about DrFed.

drfed.org

DrFed — The ActivityPub debugging platform

DrFed is a web-based platform for developing and debugging ActivityPub implementations, built by the team behind Fedify.

The quoted post is hidden while awaiting the author's approval.

@hongminhee@hollo.social · Reply to Samuel Brinkmann

@sabrinkmann @Floppy Two directions I know of. If a hosted service is fine, something like Sentry. For self-hosting, SigNoz is the only F/OSS option I know with easy OpenTelemetry ingestion; I don't know what else is out there. It has a paid cloud version too.

I think Sentry used to have an F/OSS edition. I'm not sure it still exists, or whether it accepts OTLP though.

signoz.io

SigNoz | The Open Source Datadog Alternative

SigNoz Cloud is a one-stop observability tool built on top of OpenTelemetry. Get APM, logs, traces, metrics, exceptions, AI observability & alerts in a single tool.

@hongminhee@hollo.social

ChanHaeng Lee (@2chanhaeng), one of the @fedify maintainers, is asking the which of his two projects he should present in the Social Web devroom at @fosdem 2027.

@drfed is an debugging tool that he is building with @z9mb1, @gaebalgom, and me. fedi.blue (https://fedi.blue) is a library for servers that interoperate over both ActivityPub and the AT Protocol. Both would make good talks, which is why I would rather the audience picked.

The poll closes on 13 November 2026, so vote for the one you would rather sit through. has three maintainers now, and all three of us are going to 2027 and submitting proposals to the devroom. (The CFP is open until 27 November 2026 if you have a talk of your own.)

fedi.blue

Hello, world

The quoted post is hidden while awaiting the author's approval.

@2chanhaeng@hackers.pub

Hello, Fediverse! I’m trying to decide what topic to present at FOSDEM 2027 – Social Web Devroom. Which of these two would you be more excited to hear about?

  • DrFed: DrFed is an ActivityPub debugging tool that @hongminhee, @z9mb1, @gaebalgom, and I are building as a team.
  • fedi.blue: fedi.blue is a library for building servers that interoperate with the ActivityPub and AT protocols.
  • DrFed: ActivityPub Debugging Tool1 (100%)
  • fedi.blue: Bridge between AP & AT Protocol0 (0%)

fedi.blue

Hello, world

@geeknews@mastodon.social

국내 오픈소스 소액 지원 사업 'FOSS for All Microgrants 2026' 수혜 프로젝트 5곳

FOSS for All이 올해 처음 진행한 기부금 모집 및 분배 사업에서 지원한 13개 프로젝트 및 커뮤니티 중 5곳을 선정했습니다. 각 프로젝트에 소액 지원금을 전달할 예정입니다.

선정된 프로젝트는 Z80 프로세서용 LLVM 백엔드 llvm-z80, 요청 처리 과정을 명시적으로 드러내는 Go 웹 프레임워크 Spine, Windows 11 작업 표시줄에 위젯을 넣는 Deskband11Lib, PDF로 제본용 소책자를 만드는 HornPenguin Booklet, 국한문혼용체를 한글로 변환하는 Gukhanmun입니다.

news.hada.io/topic?id=36847

@hongminhee@hollo.social

I've been carrying around an idea for a federated code forge for a while. Two things sharpened it recently: Tangled's post on the federated code forge, which builds a forge on the AT Protocol, and a Jujutsu workshop (Korean) by Seongmin Lee (@boltless.me), who works at Tangled, held at @turingappledev.

My version would build on ForgeFed, the protocol for code forges (spec), so that repositories, issues and merge requests federate the way posts already do. The idea is early enough that I haven't even come up with a codename. What I want from it, roughly:

  • Git and Jujutsu (so-called jj) as equal clients. Not Git hosting with Jujutsu support bolted on, but a forge that understands both, so what Jujutsu is actually good at, stacked changes, becomes a first-class unit of review instead of a pile of separate pull requests.
  • No owner layer. Since the point is federation, one instance represents one person or one organization, permissions are managed per server, and a repository lives at forge.example/myrepo instead of forge.example/owner/myrepo.
  • A migration path off GitHub that keeps the history. Importing the code is easy; importing the issues, pull requests and discussions with their original authors attached is the part that matters. I'd keep a placeholder for each GitHub account and let whoever owns that account prove it, after which the instance swaps in their fediverse actor, so attribution carries over. How to express that claim in ActivityPub is the part I haven't figured out. It may need a new FEP.

Where this stands: I haven't read the whole spec, Fedify doesn't ship the vocabulary yet (fedify-dev/fedify#751), and I have too much else going on to start soon. If you've run a forge or implemented ForgeFed, I'd like to hear whether any of this makes sense.

github.com

@fedify/forgefed package for ForgeFed vocabulary support · Issue #751 · fedify-dev/fedify

Background ForgeFed defines an ActivityPub federation protocol for software forges such as Gitea and Forgejo. The spec adds forge-specific actor types (Repository, TicketTracker, PatchTracker, Proj...

@fossforall@mastodon.social · Reply to FOSS for All

다음 편에서도 Microgrants에 지원한 오픈소스 프로젝트들을 이어서 소개할게요.

더 많은 한국의 오픈소스 이야기가 궁금하다면, FOSS for All을 팔로우해 주세요! 🌱

@fossforall@mastodon.social

우리가 만난 오픈소스 프로젝트들 ① 🌱

한국의 오픈소스 문화가 무럭무럭 자랄 수 있도록, FOSS for All Microgrants가 시작되었어요.

2026년 Microgrants 사업에 함께한 국내 오픈소스 프로젝트·커뮤니티를 만나보세요!

(아래에 계속! 👇)