洪 民憙 (Hong Minhee)'s avatar

洪 民憙 (Hong Minhee)

@[email protected] · 765 following · 868 followers

An intersectionalist, feminist, and socialist guy living in Seoul (UTC+09:00). Who's behind @fedify and @hollo. Write some free software in , , , & . They/them.

()

WebsiteGitHubBlogFedify

https://hongminhee.org/

https://github.com/dahlia

https://writings.hongminhee.org/

https://fedify.dev/

역보's avatar
역보

@[email protected]

윤석열 오늘 식사 메뉴

서울구치소 12월 식단표
서울구치소 12월 식단표
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected]

Misskeyプロジェクトはマージ権を持つ人がsyuiloさんしかいないのですか？

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

@[email protected]

Speak, 日本(일본) 市場(시장)에도 進出(진출)했구나. 몰랐다.

https://fedibird.com/@GabbingDog/113744920079525287

ガブ's avatar
ガブ

@[email protected]

話題のAI英会話アプリのSpeakを試してみた。

一応、レッスンとしては自己紹介とか趣味の話題とか決まっているようだが、こちらの返答については割と自由に回答しても、すぐに間違いを修正して正しい表現を教えてくれる。さすがChat-GPTという感じだ。何か表現を間違うと、その部分を取りだしてドリルみたいに何度も練習するようになっている。

Chat-GPTみたいなAIは何となく避けて使ってこなかったが、こういう用途には向いていて、適任だと思った。

そもそも日常会話の話題を考えるのが日本語でも下手なので、ある程度AI側が会話を主導してこっちの回答を引き出してくれるのは助かるし、日常会話の切り出し方も教わってるw

:rss: 全体 : hankyoreh japan's avatar
:rss: 全体 : hankyoreh japan

@[email protected]

【速報】裁判所、内乱容疑の尹錫悦大統領に逮捕状発付…韓国現職大統領で初
japan.hani.co.kr/arti/politics

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

Hollo 0.4.1及び0.4.2をリリースしました。このバージョンでは、幾つかの連合関連の問題を解決しましたので、Hollo 0.4.0をお使いの方は、早速0.4.2にアップデートすることをお勧めします。

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

Hollo 0.4.1 및 0.4.2를 릴리스했습니다. 두 버전에서는 몇 가지 연합 관련 이슈를 해결하였으니, Hollo 0.4.0을 쓰고 계신 분들께서는 조속히 0.4.2로 업데이트하실 것을 권합니다.

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Released Hollo 0.4.1 and 0.4.2. These versions fixed few federation issues. Recommend to update to 0.4.2 now if you're using Hollo 0.4.0!

pkg update's avatar
pkg update

@[email protected]

hollo 0.4.0으로 업그레이드. 메모리 사용량이 40% 수준으로 줄었다. 조금 더 테스트해보고 이 계정을 이동할 예정.

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

@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post

Okay, it seems to work when I configured Node.js's default DNS resolution order to "ipv6first"… 🤔

Welcome to Node.js v23.5.0. Type ".help" for more information. > const dns = await import("node:dns"); undefined > dns.setDefaultResultOrder("ipv6first"); undefined > await fetch("https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci"); Response { status: 200, statusText: 'OK', headers: Headers { 'alt-svc': 'h3=":443"; ma=2592000', 'cache-control': 'public, max-age=15', 'content-length': '10828', 'content-security-policy': "default-src 'self' 'unsafe-inline'; img-src *; media-src *; frame-ancestors *", 'content-type': 'text/html; charset=utf-8', date: 'Mon, 30 Dec 2024 16:32:22 GMT', server: 'Caddy', 'strict-transport-security': 'max-age=15552000; preload', vary: 'Origin, Accept', 'x-frame-options': 'DENY' }, body: ReadableStream { locked: false, state: 'readable', supportsBYOB: true }, bodyUsed: false, ok: true, redirected: false, type: 'basic', url: 'https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci' } >
Welcome to Node.js v23.5.0. Type ".help" for more information. > const dns = await import("node:dns"); undefined > dns.setDefaultResultOrder("ipv6first"); undefined > await fetch("https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci"); Response { status: 200, statusText: 'OK', headers: Headers { 'alt-svc': 'h3=":443"; ma=2592000', 'cache-control': 'public, max-age=15', 'content-length': '10828', 'content-security-policy': "default-src 'self' 'unsafe-inline'; img-src *; media-src *; frame-ancestors *", 'content-type': 'text/html; charset=utf-8', date: 'Mon, 30 Dec 2024 16:32:22 GMT', server: 'Caddy', 'strict-transport-security': 'max-age=15552000; preload', vary: 'Origin, Accept', 'x-frame-options': 'DENY' }, body: ReadableStream { locked: false, state: 'readable', supportsBYOB: true }, bodyUsed: false, ok: true, redirected: false, type: 'basic', url: 'https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci' } >
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected] · Reply to Chris​‌​‬ Hayes‌​​​'s post

@chris_hayes Hmm, interesting! I'm trying to configure User-Agent header!

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

@[email protected]

I'm troubleshooting a mysterious TypeError: fetch failed exception when using .js's built-in fetch() function. When I make the same request in or , it responds fine. Anyone know why this only happens in Node.js?

Deno 2.1.4 exit using ctrl+d, ctrl+c, or close() REPL is running with all permissions allowed. To specify permissions, run `deno repl` with allow flags. > await fetch("https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci"); Response { body: ReadableStream { locked: false }, bodyUsed: false, headers: Headers { "alt-svc": 'h3=":443"; ma=2592000', "cache-control": "public, max-age=15", "content-length": "10828", "content-security-policy": "default-src 'self' 'unsafe-inline'; img-src *; media-src *; frame-ancestors *", "content-type": "text/html; charset=utf-8", date: "Mon, 30 Dec 2024 15:59:09 GMT", server: "Caddy", "strict-transport-security": "max-age=15552000; preload", vary: "Origin, Accept", "x-frame-options": "DENY" }, ok: true, redirected: false, status: 200, statusText: "OK", url: "https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci" } >
Deno 2.1.4 exit using ctrl+d, ctrl+c, or close() REPL is running with all permissions allowed. To specify permissions, run `deno repl` with allow flags. > await fetch("https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci"); Response { body: ReadableStream { locked: false }, bodyUsed: false, headers: Headers { "alt-svc": 'h3=":443"; ma=2592000', "cache-control": "public, max-age=15", "content-length": "10828", "content-security-policy": "default-src 'self' 'unsafe-inline'; img-src *; media-src *; frame-ancestors *", "content-type": "text/html; charset=utf-8", date: "Mon, 30 Dec 2024 15:59:09 GMT", server: "Caddy", "strict-transport-security": "max-age=15552000; preload", vary: "Origin, Accept", "x-frame-options": "DENY" }, ok: true, redirected: false, status: 200, statusText: "OK", url: "https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci" } >
Welcome to Bun v1.1.42 Type ".help" for more information. [!] Please note that the REPL implementation is still experimental! Don't consider it to be representative of the stability or behavior of Bun overall. > await fetch("https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci"); Response {} >
Welcome to Bun v1.1.42 Type ".help" for more information. [!] Please note that the REPL implementation is still experimental! Don't consider it to be representative of the stability or behavior of Bun overall. > await fetch("https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci"); Response {} >
Welcome to Node.js v23.5.0. Type ".help" for more information. > await fetch("https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci"); Uncaught TypeError: fetch failed at node:internal/deps/undici/undici:13484:13 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async REPL1:1:33 { [cause]: AggregateError [ETIMEDOUT]: at internalConnectMultiple (node:net:1139:18) at internalConnectMultiple (node:net:1215:5) at Timeout.internalConnectMultipleTimeout (node:net:1739:5) at listOnTimeout (node:internal/timers:616:11) at process.processTimers (node:internal/timers:549:7) { code: 'ETIMEDOUT', [errors]: [ [Error], [Error] ] } } >
Welcome to Node.js v23.5.0. Type ".help" for more information. > await fetch("https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci"); Uncaught TypeError: fetch failed at node:internal/deps/undici/undici:13484:13 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async REPL1:1:33 { [cause]: AggregateError [ETIMEDOUT]: at internalConnectMultiple (node:net:1139:18) at internalConnectMultiple (node:net:1215:5) at Timeout.internalConnectMultipleTimeout (node:net:1739:5) at listOnTimeout (node:internal/timers:616:11) at process.processTimers (node:internal/timers:549:7) { code: 'ETIMEDOUT', [errors]: [ [Error], [Error] ] } } >
Esurio's avatar
Esurio

@[email protected]

来年配線がどうにかなったらPRIMARGYにHolloとMitraは移したさがある

Esurio's avatar
Esurio

@[email protected]

Hollo, 起動時のメモリ量は若干増えたかなって気はするけどBunの時ほどひどいメモリリークはなくなってる, 300MB程度で収まってるので

Esurio's avatar
Esurio

@[email protected]

Hollo 0.3.1→0.4.0

RE: https://c.koliosky.com/notes/a2eeiewnrafg01hd

Esurio's avatar
Esurio

@[email protected]

🎉

Esurio's avatar
Esurio

@[email protected]

とりあえず帰ったらHolloを0.4.0に上げてみるか

Esurio's avatar
Esurio

@[email protected]

いつの間にかHollo0.4.0がでてる

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

@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post

올 한 해를 마무리하며 〈聯合宇宙(연합우주)와 함께 한 一年(일년)〉이라는 主題(주제)로 블로그에 글을 올렸습니다. (페이지 구석의 링크를 눌러서 한글專用文(전용문)으로 바꿔서 보실 수 있습니다.)

https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.ko-kore.html

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

@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post

I wrote a blog post to wrap up the year 2024: A year with the fediverse.

https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.en.html

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

@[email protected]

Fediverse Advent Calendar 2024の24日目の記事を書きました。「フェディバースと共に過ごした一年」をテーマに書きました。

https://writings.hongminhee.org/2024/12/a-year-with-the-fediverse/index.ja.html

Fedify: an ActivityPub server framework's avatar
Fedify: an ActivityPub server framework

@[email protected]

Since 1.4.0, Object will have the emojiReactions property, which corresponds to the fedibird:emojiReactions property extended by .

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

@[email protected]

Fedifyにfedibird:emojiReactionsプロパティのサポートを追加中…

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

@[email protected] · Reply to KazukyAkayashi (Hollo)'s post

@KazukyAkayashi Don't know why, but Node.js (at least with v23.5.0) apparently fails to fetch your Iceshrimp server… 🤔

Welcome to Node.js v23.5.0. Type ".help" for more information. > await fetch("https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci"); Uncaught TypeError: fetch failed at node:internal/deps/undici/undici:13484:13 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async REPL1:1:33 { [cause]: AggregateError [ETIMEDOUT]: at internalConnectMultiple (node:net:1139:18) at internalConnectMultiple (node:net:1215:5) at Timeout.internalConnectMultipleTimeout (node:net:1739:5) at listOnTimeout (node:internal/timers:616:11) at process.processTimers (node:internal/timers:549:7) { code: 'ETIMEDOUT', [errors]: [ [Error], [Error] ] } } >
Welcome to Node.js v23.5.0. Type ".help" for more information. > await fetch("https://social.zarchbox.fr/notes/a2dn3k8kt5hm3gci"); Uncaught TypeError: fetch failed at node:internal/deps/undici/undici:13484:13 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async REPL1:1:33 { [cause]: AggregateError [ETIMEDOUT]: at internalConnectMultiple (node:net:1139:18) at internalConnectMultiple (node:net:1215:5) at Timeout.internalConnectMultipleTimeout (node:net:1739:5) at listOnTimeout (node:internal/timers:616:11) at process.processTimers (node:internal/timers:549:7) { code: 'ETIMEDOUT', [errors]: [ [Error], [Error] ] } } >
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected] · Reply to lamikennel's post

@lamikennel そうですね。ただ「辱説」という表現だけでは明白な差別発言かどうか分からないですね…

KazukyAkayashi (Hollo)'s avatar
KazukyAkayashi (Hollo)

@[email protected]

Update Hollo to v.0.4.0 🎉 But I will have to rewrite my hollo.service for systemd :pikathinknothappy:

http://hollo.social/@hollo/01941325-8d0e-71e4-ad49-daef861c01d0

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

The key changes of this release include:

  • Hollo is now powered by Node.js 23+ instead of Bun for more efficient memory usage.

  • Added an experimental feature flag TIMELINE_INBOXES to store all posts visible to your timeline in the database, rather than filtering them in real-time as they are displayed. This is useful for relatively larger instances with many incoming posts, but as of now it may have several bugs. It is expected to be the default behavior in the future after it is stabilized.

  • Now you can import and export your data from the administration dashboard in CSV format: follows, lists, accounts you muted, accounts you blocked, and bookmarks.

  • You can now make your profile discoverable.

  • The profile page now shows an account's cover image if it has one.

  • Many bug fixes.

For the details, see also the full changelog.

You can upgrade to Hollo 0.4.0 using the following ways:

NTSK's avatar
NTSK

@[email protected]

Hollo 0.4.0 :neocat_googly:

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

@[email protected] · Reply to lamikennel's post

@lamikennel 【辱說】ですね。単に悪口や罵詈雑言を意味します。

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

Hollo 0.4.0がリリースされました！HolloはActivityPubをサポートする御一人様向けのマイクロブログソフトウェアです。

今回のバージョンの主な変更点は以下の通りです。

  • HolloはBunの代わりにNode.js 23+を使う様になり、メモリ使用量を大幅に改善しました。

  • 実験的な機能フラグであるTIMELINE_INBOXESを追加しました。この機能フラグをオンにすると、タイムラインに表示する必要がある投稿をリアルタイムでフィルタリングして表示する代わりに、事前にデータベースに保存します。この方式は受け入れる投稿が多い比較的多くのインスタンスで有用ですが、現時点ではまだバグがある可能性が有ります。この動作は安定化された後、今後デフォルトになる予定です。

  • 管理ダッシュボードからアカウントのデータをCSVでインポートまたはエクスポートする事が出来ます。フォローしているアカウント、リスト、ミュートしたアカウント、ブロックしたアカウント、ブックマークをサポートします。

  • アカウントをdiscoverableに設定する事が出来ます。

  • アカウントにカバー画像が設定されている場合、プロフィールページに表示されます。

  • その他、様々なバグを修正しました。

詳細は完全な変更ログをご覧ください。

Hollo 0.4.0にアップグレードするには、以下の方法に従ってください：

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (In fact, the hollo.social server is already running on Node.js!) If this test is successful, starting with the next release, Hollo will be powered by Node.js instead of Bun.

The main reason for switching to Node.js is to optimize memory usage. As you can see in the graph image below, Node.js uses significantly less memory than Bun. With this switch, Hollo is expected to be even more lightweight than before!

Are you interested in trying out the Node.js version of Hollo early? Try to pull ghcr.io/dahlia/hollo:0.4.0-dev.290!

Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected] · Reply to Hollo :hollo:'s post

Hollo 0.4.0이 릴리스되었습니다! Hollo는 ActivityPub을 지원하는 일인 사용자용 마이크로블로그 소프트웨어입니다.

이번 버전의 주요 변경점은 다음과 같습니다.

  • Hollo는 이제 Bun 대신 Node.js 23+을 사용하여 메모리 사용량을 큰 폭으로 줄였습니다.

  • 실험적인 기능 플래그인 TIMELINE_INBOXES를 추가했습니다. 이 기능 플래그를 켜면 타임라인에 보여야 하는 게시물들을 실시간으로 필터링하여 표시하는 대신, 미리 데이터베이스에 저장하게 됩니다. 이 방식은 받아들이는 게시물이 많은 비교적 큰 인스턴스에서 유용하지만, 현재로서는 아직 버그가 있을 수 있습니다. 이 동작은 안정화된 뒤에는 앞으로 기본값이 될 예정입니다.

  • 관리 대시보드에서 계정의 데이터를 CSV로 가져오거나 내보낼 수 있습니다. 팔로하는 계정들, 리스트, 뮤트한 계정들, 차단한 계정들, 책갈피를 지원합니다.

  • 계정 설정에서 계정을 discoverable로 설정할 수 있습니다.

  • 계정에 커버 이미지가 설정되어 있을 경우 프로필 페이지에서 표시됩니다.

  • 그 외 여러 버그가 수정되었습니다.

자세한 내용은 전체 변경 내역을 확인하십시오.

Hollo 0.4.0으로 업그레이드하려면 아래 방법을 따르세요:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (In fact, the hollo.social server is already running on Node.js!) If this test is successful, starting with the next release, Hollo will be powered by Node.js instead of Bun.

The main reason for switching to Node.js is to optimize memory usage. As you can see in the graph image below, Node.js uses significantly less memory than Bun. With this switch, Hollo is expected to be even more lightweight than before!

Are you interested in trying out the Node.js version of Hollo early? Try to pull ghcr.io/dahlia/hollo:0.4.0-dev.290!

Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

Hollo 0.4.0 released! is a single-user federated microblogging software which is -enabled and powered by .

The key changes of this release include:

  • Hollo is now powered by Node.js 23+ instead of Bun for more efficient memory usage.

  • Added an experimental feature flag TIMELINE_INBOXES to store all posts visible to your timeline in the database, rather than filtering them in real-time as they are displayed. This is useful for relatively larger instances with many incoming posts, but as of now it may have several bugs. It is expected to be the default behavior in the future after it is stabilized.

  • Now you can import and export your data from the administration dashboard in CSV format: follows, lists, accounts you muted, accounts you blocked, and bookmarks.

  • You can now make your profile discoverable.

  • The profile page now shows an account's cover image if it has one.

  • Many bug fixes.

For the details, see also the full changelog.

You can upgrade to Hollo 0.4.0 using the following ways:

Hollo :hollo:'s avatar
Hollo :hollo:

@[email protected]

is currently testing .js instead of . (In fact, the hollo.social server is already running on Node.js!) If this test is successful, starting with the next release, Hollo will be powered by Node.js instead of Bun.

The main reason for switching to Node.js is to optimize memory usage. As you can see in the graph image below, Node.js uses significantly less memory than Bun. With this switch, Hollo is expected to be even more lightweight than before!

Are you interested in trying out the Node.js version of Hollo early? Try to pull ghcr.io/dahlia/hollo:0.4.0-dev.290!

Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Hollo's memory usage graph. When I was running on Bun, it used about 4GB of memory, but after switching to Node.js, it uses about 0.5GB of memory.
Older →