洪 民憙 (Hong Minhee)

Hackers' Pub Android Client v1.1.1 Released!

I didn't add any features but, Refined Compose Screen's UX flow. Also for home timeline.

You can download here : https://github.com/hackers-pub/android/releases/tag/v1.1.1

RE: https://hackers.pub/@kodingwarrior/019d2de5-b9a6-7b58-9f91-38c84ff9f381

Next release of Hackers' Pub Android client will have some UI improvements...

I Can't See Apple's Vision https://matduggan.com/i-cant-see-apples-vision/ #apple #mac

@zanzi @jnkrtech Your point about abstraction ladders is something I've been turning over since I read it. The Terence Tao/Lean combination feels like a glimpse of exactly what you're describing: Lean's type system carries so much semantic weight that the LLM doesn't need to compensate with volume. The proof is short because the language is expressive enough to make it short. That's very different from what happens when you point an LLM at TypeScript.

I'm skeptical of vibe coding, and have been from the start. Generating an entire project from prompts feels to me like a path to maintainability disaster, and I think most of the people currently excited about it haven't yet had to clean up what they made. The enthusiasm reads a lot like the dynamic typing boom of the 2000s: Ruby, Python, JavaScript, the whole wave. “We can build so fast.” True, and then ten years passed, the codebases grew, the teams changed, and people started hitting walls they hadn't anticipated. Python grew type hints. Flow and TypeScript appeared. Ruby quietly declined. The reckoning came, it just took a while.

I expect vibe coding to follow the same curve. One difference worries me though. With dynamic typing, the code was at least written by humans who understood it at the time. The technical debt was “hard to read.” With LLM-generated code that nobody reviewed deeply, the debt is something else: code that exists for reasons nobody can reconstruct. That's a harder problem.

There's a related problem I don't think more training data will fix. LLMs converge toward the average of what they've seen, and the average code on the internet is not concise. Verbose code is the norm; terse, well-factored code is rare, and usually underdocumented, so it contributes a weak training signal at best. The result is that LLMs have internalized the habits of the median developer: defensive, repetitive, over-specified. Conciseness requires knowing what not to write, and that judgment depends on domain context and something like aesthetic sense—neither of which transfers easily through pretraining. I don't see a scaling path out of that.

My own workflow tries to avoid this. Even when I use an LLM for Fedify, I steer constantly: small outputs, immediate review, corrections before moving on. The LLM is closer to a fast typist than an autonomous collaborator. It still helps, but the judgment about what to write, what to cut, where to stop, stays with me.

Which brings me to your actual question, what should the metric be. I don't have a clean answer, but I think it has something to do with how much of the codebase a human can hold in their head and feel responsible for. LOC never measured that. Neither does “prompt to working demo.” Whatever comes next probably needs to.

And on the higher-level languages point: I think you're right, and I'd add that this might be where the more interesting craft ends up living. Not writing the implementation, but designing the abstractions well enough that the implementation, whoever or whatever produces it, stays within bounds a human can oversee. That's a different skill from what most developers have trained, but it doesn't feel like a lesser one.

Where are the nuanced left-wing takes on modern AI and LLMs?

So much of the discourse around this tech is centered on rejecting it because of who currently owns it. But like all tech, it can be used for both oppression and liberation.

Who is focusing on the latter?

@jnkrtech @zanzi Thanks, here are my pieces about the topic:

• 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
• Why craft-lovers are losing their craft

I hope you enjoy them!

Our Fediverse & Social Web track has been accepted for @COSCUP 2026 (Taipei, Aug 8–9)! We'll have a full day—six hours—to fill with talks on the #fediverse, #ActivityPub, and the open social web.

The CFP for speakers isn't open yet, but we'll announce it here when it is. Stay tuned!

#SocialWeb #COSCUP #fedidev

@julian Haha, I will attend to both!

何が始まるんです？

草
https://blog.coscup.org/2026/03/coscup-x-ubucon-asia-2026-first-wave-of.html?m=1

@liaizon there are some good FLOSS LLMs like Haidra: https://haidra.net

federated Urban Dictionary when?

Friendly reminder: last year I built FediMod FIRES, a protocol and reference server implementation for sharing moderation data.

I haven't yet been able to get anyone to adopt it or even signal intent to adopt. But regularly I see people complaining about the lack of data sharing when it comes to moderation, especially for combating spam, scams, and harassment. The tool is there, please use it!

Whilst I'm not actively working on FediMod FIRES this quarter, I did apply in November for a grant to continue that work, and last I heard a few weeks ago is that the grant made it to the next stage, so I may have some money again to fund development.

It's not 1.0.0 yet, because I decided it needed more work for me to be happy to call it that, but it is usable!

Installation is also super simple for data producers, literally two commands on debian or ubuntu boxes.

Learn more: https://fires.fedimod.org/manuals/reference-server/

#moderation #fediblock #administration

@smallcircles Yeah, Unicode and modern web capabilities are literally a blessing for East Asians!

@smallcircles It's basically called Korean mixed script, which is no longer used in modern Korean (both in the South and the North). Writing Korean this way is my own habit and leaves younger generations unable to read it well, so I annotated those Sino-Korean words with hangul, the Korean alphabet. Annotations are technically implemented using HTML <ruby> tags.

「Mastodon でモンゴル文字の縦書きを実装」のスライドを公開しました。参照URLなどを少し修正しています。 https://postfixnotation.org/slide/mastodon-vertical-1.pdf #FediLUG

@Yohei_Zuho 美味しそう‼️

@dansup Haha, that's fine. Would you attend to FediCon this year? We could hang out there!

@dansup Thanks! Do you want to come to Taipei this summer? 🤣

@COSCUP 2026（台北、8月8–9日）にて、Fediverse & Social Webトラックが採択されました！#フェディバース、#ActivityPub、オープンなソーシャルウェブをテーマに、丸一日・計6時間のトラックを予定しています。

発表者向けのCFPはまだ始まっていませんが、公開され次第お知らせします。お楽しみに！

#Fediverse #SocialWeb #COSCUP #ActivityPub #fedidev

@COSCUP 2026(臺北(타이베이), 8月(월) 8–9日(일))에서 저희 Fediverse & Social Web 트랙이 承認(승인)되었습니다! #聯合宇宙(연합우주), #ActivityPub, 오픈 소셜 웹을 主題(주제)로 하루 終日(종일), 總(총) 6時間(시간)을 進行(진행)할 豫定(예정)입니다.

發表者(발표자) 募集(모집) CFP는 아직 열리지 않았지만, 始作(시작)되는 대로 바로 公知(공지)하겠습니다. 期待(기대)해 주세요!

#페디버스 #연합우주 #SocialWeb #COSCUP #fedidev

Our Fediverse & Social Web track has been accepted for @COSCUP 2026 (Taipei, Aug 8–9)! We'll have a full day—six hours—to fill with talks on the #fediverse, #ActivityPub, and the open social web.

The CFP for speakers isn't open yet, but we'll announce it here when it is. Stay tuned!

#SocialWeb #COSCUP #fedidev

@Yozumina 그래서 요즘에는 리니어, 택타일, 클릭, 넌클릭 같이 나누더라고요…

Magic Link Pitfalls https://lobste.rs/s/lzxb0m #browsers #email
https://etodd.io/2026/03/22/magic-link-pitfalls/

Hackers' Pub Android Client v1.1.0 Released!

• Added Notification polling (both for background/foreground)
• Added on-device translation using ML-kit (thanks to @nove_b)

You can download here : https://github.com/hackers-pub/android/releases/tag/v1.1.0

A new fediverse server software (which runs on Cloudflare Workers) made by @siliconsjang!

https://hackers.pub/@siliconsjang/019d2090-d19d-7aa4-a1bb-0c93cafdb127

페디버스 소프트웨어를 만들고 있습니다. 정신이 되는 만큼 최대한 유지보수 관리 해 볼 예정.. 현재 일부 마스토돈 API 호환도 되고.. 근데 아직 대부분의 타 서비스에 로그인 등은 못해요! - 마스토돈으로 로그인 등 작동하는 경우도 있고 안하는 경우도 있는. 발견시마다 조금씩 마스토돈 표준(?)에 맞추는 중

목표는 마스토돈 30: 미스키 30: 자체 10: AP표준 30 으로 개발하고싶네요(?)

그래서 뭐냐고요? 서버리스 Wildebeest에서 유래한 SiliconBeest라는 소프트웨어고 역시클라우드플레어 서버리스 위에서 돌아가게 만들고 있어요!

https://github.com/SJang1/siliconbeest https://siliconbeest.sjang.dev