洪 民憙 (Hong Minhee)

My companion almost got pickpocketed twice in front of Brussels Central Station.

​​ Le dev de Hollo sera au FOSDEM
Depuis Seoul (Corée du sud) whooaa ça en fait du chemin.

RE: hollo.social/@hongminhee/019bfef9-c1d2-754b-900a-27359317798a

Just arrived at Brussels International Airport! It was long trip…

@django Great! I'm looking forward to your talk!

@zundan Yeah, maybe? This Coca-Cola had a bit more of a tangy taste.

@django Thanks! Are you attending this FOSDEM?

The Coca-Cola I bought at Abu Dhabi Airport tastes... slightly different from the ones I used to drink in Korea.

Just arrived in Abu Dhabi. First time in the Middle East.

Internet on the plane is… really… slow…

Internet on the plane is really… slow…

@root Hollo는 어떠세요?

Listen, if you're enjoying your time on Mastodon (or the fediverse at-large), it's time to talk to your friends who are still on Instagram, Threads, and Facebook (and ESPECIALLY Twitter/whatever-it's-called-now). The billionaire owners of these websites are not only NOT their friends, they are actively selling THEIR information.

Facebook knows all about them (and probably most of us, too) and will monetize that. They're also not going to let them see what THEY don't want THEM to see...

That shit doesn't happen here. It'll never happen here because the fediverse isn't algorithm-driven (and algorithm-manipulated). It's people-powered. You gotta be slinging good shit to show up in people's feed because either 1) people are reboosting you, or 2) they are following you.

https://www.wired.com/story/meta-is-blocking-links-to-ice-list-on-facebook-instagram-and-threads/

Prediction:

Pinterest, as people have known it, will be dead within five years. I honestly don't think the leadership there has any idea what their userbase actually wants. The End of UX continues…

(I wonder if it's time for a #Fediverse version of Pinterest. Scratch that, it is definitely time!)

https://www.theverge.com/news/868531/pinterest-layoffs-cuts-15-percent-ai-transformation

Cloudflare just published a vibe coded blog post claiming they implemented Matrix on cloudflare workers. They didn't, their post and README is AI generated and the code doesn't do any of the core parts of matrix that make it secure and interoperable. Instead it's littered with 'TODO: Check authorisation' and similar

https://blog.cloudflare.com/serverless-matrix-homeserver-workers/

@cryptix Thanks for the advice for a first-time traveller to Europe!

@catilac Are you attending FOSDEM too? We could hang out there then!

I just looked up what kind of plugs they use in Belgium and Germany. Luckily, it looks like they use Type F “Schuko” plugs, the same kind we use in South Korea!

I updated my "How to survive FOSDEM" article.

@fosdem organizers updated map so I updated it as well. The change was simple: there is no ATM at ULB (for quite a while).

So I added an info about it. And some minor edit.

https://marcin.juszkiewicz.com.pl/2019/10/15/how-to-survive-fosdem/

#FOSDEM #FOSDEM26

@ntek 該当機能の実装は完了しており、次のマイナーリリースであるHollo 0.8.0に含まれる予定です！機能のご提案ありがとうございました。

https://github.com/fedify-dev/hollo/issues/348#issuecomment-3804937820

This weekend I made a text generator bot trained on all 70+ issues of my newsletter :) It was really easy to make with @botkit , thanks @hongminhee !

RE: https://boo.nathanguilhot.deno.net/message/019bfe09-9738-7007-9a19-5e192cd75cad

When you necessarily need variable names for a single item of “data” vs. its collection, which naming convention do you prefer?

@laurenshof Thanks!

@kristoff Well, there's the simplest phrase which works for the most cases: “annyeonghaseyo.” For “thank you”: “gamsahamnida.” These spellings might look a little complicated, but the actual pronunciations aren't hard. Listen to the audio on the Wiktionary entries I linked.

By the way, I'm flying from Seoul to Brussels tomorrow to attend FOSDEM 2026. It's my first trip to Europe, so I'm both excited and nervous.

@ntek 良いアイデアですね。課題トラッカーにイシューとして作成していただけますか？

If people who speak a different native language than you make the effort to speak to you in yours, that's a privilege.

@hongminhee FWIW, I think EVE Online still uses its stackless Python fork (which supports goroutine-like tasks/fibers) for gameplay scripting.

This brings back memories. Before Python had async/await, before asyncio became standard, I was happily writing concurrent code with gevent. I actually preferred it.

The reason was simple: no function color problem. With async/await, you split the world into two kinds of functions—ones that block by default and ones that don't. You have to mark the latter with async and remember to await them. With gevent, everything just blocks by default, and you spawn when you need concurrency. It's the same mental model as multithreading, just lighter. Project Loom in Java does something similar, though the technical details differ.

I sometimes wonder what Python would look like if it had embraced gevent-style coroutines in CPython instead of adding async/await. Or if Stackless Python had been accepted upstream. Maybe async programming would be more approachable today.

The explicit await keyword gives you visibility into where context switches can happen, sure. But in practice, I/O points are obvious even without the keyword—you're reading from a socket, querying a database, making an HTTP request. The explicitness doesn't really prevent race conditions or timing bugs. Meanwhile, function colors infect everything. One async library forces your entire call stack to be async. You end up maintaining both sync and async versions of the same code, or the ecosystem just splits in two.

With gevent, there's no such problem. You just call functions. Spawn them if you want concurrency, call them normally if you don't. Go's goroutines and Project Loom are popular for good reasons—they make concurrency accessible without the cognitive overhead.

Python's choice is history now, and there's no going back. But looking at how things turned out, I can't help but think the more practical path was right there, and we walked past it.

사상(메시지)가 없는 작품은 없습니다. 어떤 작품이 아무런 사상이나 의도가 없어 보인다면 기존의 지배적인 질서에 너무나 완벽하게 순응하고 있기 때문입니다. 단지 사유를 멈추게 하는 그런 사상과. 사유를 시작하게 하는 사상이 있고 보통 후자를 메시지(사상)가 있다고 말할 뿐이죠. 작품에 사상이 없어야 한다 라는 주장은 사실 '지배적인 사상에 저항하지 마라' 라는 강력한 이데올로기(사상)적 명령입니다.

This brings back memories. Before Python had async/await, before asyncio became standard, I was happily writing concurrent code with gevent. I actually preferred it.

The reason was simple: no function color problem. With async/await, you split the world into two kinds of functions—ones that block by default and ones that don't. You have to mark the latter with async and remember to await them. With gevent, everything just blocks by default, and you spawn when you need concurrency. It's the same mental model as multithreading, just lighter. Project Loom in Java does something similar, though the technical details differ.

I sometimes wonder what Python would look like if it had embraced gevent-style coroutines in CPython instead of adding async/await. Or if Stackless Python had been accepted upstream. Maybe async programming would be more approachable today.

The explicit await keyword gives you visibility into where context switches can happen, sure. But in practice, I/O points are obvious even without the keyword—you're reading from a socket, querying a database, making an HTTP request. The explicitness doesn't really prevent race conditions or timing bugs. Meanwhile, function colors infect everything. One async library forces your entire call stack to be async. You end up maintaining both sync and async versions of the same code, or the ecosystem just splits in two.

With gevent, there's no such problem. You just call functions. Spawn them if you want concurrency, call them normally if you don't. Go's goroutines and Project Loom are popular for good reasons—they make concurrency accessible without the cognitive overhead.

Python's choice is history now, and there's no going back. But looking at how things turned out, I can't help but think the more practical path was right there, and we walked past it.