洪 民憙 (Hong Minhee)

夕飯は焼き鳥！

Im @Engineering cafe in FUK （＾ν＾）

今日はちょっと仕事しにエンジニアカフェに来た。福岡市赤煉瓦文化館の建物を使ってるから、趣があっていい感じ。

二日目のお昼は焼きカレー！福岡の名物らしい。

今回の旅行の初ご飯は鯛茶漬け！

福岡到着！

今日から3泊4日で福岡旅行！これから仁川空港に向かいます。

I try to be polite when I write prompts for LLMs. Especially in languages like Korean or Japanese that have grammatical honorifics, I make sure to use the formal, respectful form of speech (what's known as 敬語—gyeongeo or keigo). I joke with my friends that I'm using polite language early on to be pardoned for my sins when AI eventually takes over the world, but the real reason is that I don't want to get used to speaking to someone in a commanding tone. It makes me think I might start believing it's “okay” to order around certain intelligent beings, almost like condoning slavery.

@sirber83 @julian Thanks! You might not have been able to find it because you were searching for “JavaScript” instead of “TypeScript.” What do you mean by “standalone” by the way? Fedify is typically used in together with with other web frameworks like Express or Next.js.

Update: Just added Valibot integration as well!

https://unstable.optique.dev/concepts/valueparsers#valibot-integration

Update: Just added automatic metavar inference!

The help text now gets smarter labels based on your Zod schema:

• z.string().email() → EMAIL
• z.coerce.number().int() → INTEGER
• z.enum([…]) → CHOICE

No manual configuration needed.

https://github.com/dahlia/optique/commit/d4903dfdb88727a488dedb6a73ad8997868246e1

@mikebroberts Zod's a solid choice! The transform stuff can be tricky at first but becomes second nature.

Let me know if you end up trying Optique—always curious to hear feedback.

Community deployments 🙇‍♂️ https://github.com/cheeaun/phanpy?tab=readme-ov-file#community-deployments

Optique 0.7.0 will support Zod schemas as value parsers.

Seemed like a natural fit—same validation logic for both CLI and app code.

https://github.com/dahlia/optique/issues/39

근데 果然(과연) 이런 게 興味(흥미)로운 內容(내용)일까…? 🤔

We’re also looking ahead to what comes next. In another blog post published today, we introduced Mastodon’s new leadership team. Our Executive Director is @mellifluousbox (formerly, CFO of Mastodon gGmbH), who has already represented Mastodon on international stages.

We also shared an organisational update, and a fundraising update, in that blog post.

https://blog.joinmastodon.org/2025/11/the-future-is-ours-to-build-together/

Our Founder, @Gargron is stepping down from his position as CEO. He shared a reflection on his time building and growing Mastodon on our blog.

We want to take a moment to express the Mastodon team’s deep gratitude and admiration for Eugen, and for the technology and community he has built here. We’re thrilled he’s staying on in an advisory capacity.

https://blog.joinmastodon.org/2025/11/my-next-chapter-with-mastodon

Hey everyone, we have some pretty big news to share. You might remember that we announced a big restructuring for the Mastodon team earlier this year. Today marks an important milestone in this transition.

#Mastodon #Fediverse #SocialWeb

If you're a software developer and need to create a presentation with a lot of code, I highly recommend you consider Slidev (by @antfu.me). Especially if you need to include TypeScript code!

Slidev is web-based presentation software made for software developers. It offers a wide variety of ways to present code in your slides, like highlighting specific code in sequence, displaying TypeScript type information in tooltips through Twoslash integration, a “magic move” feature that compares the before and after of your code with a cool animation, the ability to embed the Monaco editor, and more.

This was my first time using Slidev, but I was captivated by its rich feature set. You should give it a try too!

그나저나 Slidev는 소프트웨어 프로그래머를 爲(위)한 정말 잘 만든 發表(발표) 슬라이드 作成(작성) 소프트웨어 같다. 特(특)히, 슬라이드에 TypeScript 코드를 꽤 包含(포함)해야 하는 發表(발표) 資料(자료)를 만든다면 Slidev를 使用(사용)해 볼 것을 勸(권)한다. Twoslash가 支援(지원)된다…!

꼭 TypeScript 코드가 아니더라도 特定(특정) 줄들을 順序(순서)대로 強調(강조)하는 것도 되고, 라이브로 코드를 고칠 수도 있다. 비포 애프터로 두 코드를 比較(비교)할 때도 매직 무브로 괜찮은 演出(연출)이 可能(가능)하다.

아무튼 Slidev 最高(최고)…!

Optique 發表(발표) 資料(자료) 아직도 만드는 中(중)… 이걸 이렇게 며칠씩 붙잡고 있는 게 말이 되나…

By the way, both Elixir and Ruby are programming languages that are really not my cup of tea…

Setting up an Akkoma instance to test the LitePubRelay implementation of the @fedify/relay package (by @z9mb1)…

어려운 사람 테스트: 난 함께 지내기 매우 쉬운 사람입니다. https://www.idrlabs.com/kr/difficult-person/20-30-10-10-15-15-10/result.php

@kodingwarrior 쉬엄쉬엄 하세요…

#Hollo 0.7 brings a redesigned #notification system with much better performance. We've moved from generating #notifications on-demand to storing them as they happen, which makes the notifications endpoint about 60% faster. We've also added response compression (though if you're using a reverse proxy, you probably had this already).

More notably, Hollo 0.7 implements Mastodon's v2 grouped notifications API. Notifications like favorites, follows, and reblogs targeting the same post or account are now grouped together server-side, reducing clutter. Clients that support the new API (introduced in #Mastodon 4.3) will show cleaner, more organized notifications automatically.

Hollo 0.7 is still in development, but we're excited to share it with you when it's ready!

If I really end up buying a Steam Machine, I guess I'll have to get a Steam Controller too, right…? 🤔

Holloの通知取得APIが遅くなってから結構経つけど、ようやく今見てる。今日中に直すのが目標！

@jnkrtech That's a really interesting idea! The “greedy but respect defined handlers” approach would definitely be more user-friendly—no worrying about option order is a big win.

The challenge is that it would require a significant architectural change to how Optique currently works. Right now, parsing is a single-pass, left-to-right process where each parser consumes tokens as it encounters them. Your suggestion would need something like a two-pass system:

1. First pass: scan all tokens and match against explicitly defined parsers
2. Second pass: collect remaining unmatched tokens into passThrough()

This is doable, but it's a fairly fundamental shift from the current design. 🤔

I really like where you're going with this though. Let me spend some time thinking about whether there's a way to support this pattern without requiring a major redesign. Maybe there's a middle ground, or maybe the two-pass approach is worth it for the better DX.

And good luck convincing your team to switch! 🥰

Interesting design question for #Optique (a type-safe #CLI parser for #TypeScript): how should it handle unrecognized options in wrapper/proxy tools? Proposed three modes but wondering if the complexity is worth it. Thoughts?

https://github.com/dahlia/optique/issues/35