home.social

Search

343 results for “hongminhee”

  1. A friend of mine, @siliconsjang, released SiliconBeest v1.0.0 today. It's a #fediverse server built on #Cloudflare Workers, D1, R2, and Queues, using Fedify.

    I like the starting point: after watching fediverse servers go down together during Cloudflare outages, they thought, why not just run on Cloudflare directly?

    They're aiming for something cheap enough that a small instance can stay on Cloudflare's free plan, and a somewhat bigger one can fit in the $5/month tier. It's still early; a lot is missing, and Mastodon/Misskey API compatibility is more of a long-term goal.

    I'm glad to see Fedify put to use for something like this. Worth checking out.

    The source code is on GitHub under AGPL 3.0.

    #ActivityPub #fedidev

    RE: https://hackers.pub/@siliconsjang/2026/siliconbeest-v1.0.0

  2. I'm using on @hollo, but it frequently dies due to . Am I doing something wrong, or is this a bug in Meilisearch?

  3. keeps dying because of out of memory… Why is this happening?

  4. , the migration tool for , supports not only schema upgrades but also downgrades and branch merges, so I didn't have much trouble moving between different branches with slightly different schemas in my local development environment, which is something I don't think many database migration tools offer.

    alembic.sqlalchemy.org/en/late

  5. @hongminhee I still write JS because it has a specification. When I adventure into implementation-defined languages for the browser, I use #PureScript

    I had great hopes for TypeScript when they were still maintaining the specification, but I dropped it once their solution to implementation drifting from specification was to retire the specification.

    ---

    Also, I come from the camp that the only real type system is a static type system, like Pierce in "Types and Programming Languages".

  6. Found this helpful resource by Ben Boyter (@boyter): a collection of sequence diagrams explaining how #ActivityPub/#WebFinger works in practice—covering post creation, follows, boosts, deletions, and user migration.

    If you're trying to implement ActivityPub, the spec can be frustratingly vague, and different servers do things differently. This aims to be a “clean room” reference for getting federation right.

    https://github.com/boyter/activitypub

    #fediverse #fedidev

  7. In #WebFinger, are there any relations that use the template property instead of the href property, excluding the http://ostatus.org/schema/1.0/subscribe relation?

    #fedidev

  8. Has anyone tried integrating with Deploy? Locally, error reports and traces are sent to Sentry just fine, but after deploying to Deno Deploy, nothing is sent to Sentry. Has anyone experienced this?

  9. Today I discovered an interesting inconsistency in Activity Streams specs while investigating a Fedify issue.

    The question: How should we interpret URLs like "icon": "https://example.com/avatar.png"?

    JSON-LD context (https://www.w3.org/ns/activitystreams): @type: "@id" → “This is an IRI reference, dereference it to fetch an ActivityStreams object.”

    Activity Streams Primer: “assume that a bare string is the href of a Link object, not an id” (no dereferencing)

    Result: JSON-LD processor-based implementations try to parse PNG files as JSON and fail.

    Turns out w3c/activitystreams#595 already discusses the same issue for href properties. I added a note that icon, image, etc. have the same problem.

    Once again reminded of how tricky spec work can be…

    #ActivityPub #Fedify #ActivityStreams #fedidev #specifications

  10. Well, I vote for Han unification of , and I rather think that more Chinese characters should have been unified (e.g., 高 & 髙, 產 & 産, 內 & 内). 🤷

  11. Every time I try to publish a package to #JSR (JavaScript Registry), it frequently gets stuck in the “processing” state, so I'm seriously considering whether I should stop publishing my TypeScript packages there altogether. 🤔

  12. Why is publishing packages to #JSR so slow? A lot of the CI time for the Fedify project is spent waiting for the JSR server to process the packages we've uploaded.

  13. I want to use #JSX for developing :botkit: #BotKit, but I can't because #JSR doesn't support JSX yet.

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

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

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

  15. 東(동)아시아에도 FediCon 같은 行事(행사)가 있으면 좋겠다는 말을 여러 番(번) 해왔는데요. 獨立的(독립적)인 컨퍼런스는 아직 어렵더라도, 작은 첫걸음으로 생각해보고 있는 게 있습니다.

    @COSCUP 2026(臺北(타이베이), 8月(월) 8日(일)–9日(일))이 커뮤니티 트랙 提案(제안)을 받고 있어요. FOSDEM의 Social Web devroom 같은 느낌으로, 거기서 Social Web 트랙을 열 수 있지 않을까 하고 構想(구상) 중입니다.

    아직 確定(확정)된 건 아무것도 없지만, #ActivityPub, #聯合宇宙(연합우주), 或(혹)은 소셜 웹 全般(전반)을 다루고 있고 發表(발표)나 共同(공동) 오거나이징에 關心(관심)이 있으신 분이 있다면 이야기 걸어주세요.

    https://floss.social/@COSCUP/116152356550445285

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

  16. 이番(번)에 @lqez 님의 《우리의 코드를 찾아서》에 出演(출연)하여 #페디버스, #ActivityPub, #Fedify, #Hollo 等(등)에 關(관)해 이야기를 나눴습니다. Fedify와 Hollo의 開發(개발) 祕話(비화) 같은 게 궁금하시다면 한 番(번) 보셔도 재밌을지도 모르겠습니다. ㅎㅎㅎ

    https://www.youtube.com/watch?v=sqxR8zscSDo

    #연합우주 #fediverse #fedidev

  17. 大部分(대부분)의 #ActivityPub 具顯(구현)들이 NoteArticle의 內容(내용) (content) 안에서 누군가 다른 액터를 멘션할 境遇(경우) tag 屬性(속성)으로 該當(해당)하는 Mention 客體(객체)들을 包含(포함)시킵니다. 그러면 Person, Group 等(등) 액터 客體(객체)들도 略歷(약력) (summary) 안에서 누군가 다른 액터를 멘션할 境遇(경우) tag 屬性(속성)으로 該當(해당)하는 Mention 客體(객체)들을 包含(포함)해야 할까요? 或是(혹시) 이미 그렇게 動作(동작)하는 具顯(구현)이 있을까요? (Mastodon은 確認(확인)해 본 結果(결과) 包含(포함)시키지 않는 것 같습니다만.) 어떻게 보시나요?

    #연합우주 #聯合宇宙(연합우주) #fedidev

  18. 제가 開發(개발)하고 있는 프로젝트 Hackers' Pub의 베타 테스터를 모십니다!

    이 프로젝트는 #聯合宇宙(연합우주)(fediverse)板(판) velog 같은 것으로, 소프트웨어 開發者(개발자)를 爲(위)한 #ActivityPub 基盤(기반)의 SNS 兼(겸) 블로그 플랫폼입니다. AGPL-3.0 라이선스로 소스 코드가 公開(공개)되어 있을 뿐 아니라, GitHub에서 프로젝트를 公開的(공개적)으로 進行(진행)하고 있습니다.

    職業(직업)으로든 趣味(취미)로든 소프트웨어를 開發(개발)하시는 분들, 聯合宇宙(연합우주)를 좋아하시는 분들, 새로운 플랫폼을 써 보고 싶으신 분들은 부디 參與(참여)해 주시기 바랍니다! 關心(관심) 있으신 분들은 答(답)글이나 DM으로 이메일 住所(주소)를 보내주시면 됩니다.

    #HackersPub #페디버스 #연합우주

  19. 安寧하세요, 저는 서울에 살고 있는 30代 後半 오픈 소스 소프트웨어 엔지니어이며, 自由·오픈 소스 소프트웨어와 聯合宇宙의 熱烈한 支持者입니다.

    저는 TypeScript用 ActivityPub 서버 프레임워크인 @fedify 프로젝트와 싱글 유저用 聯合宇宙 마이크로블로그인 @hollo 프로젝트의 製作者이기도 합니다.

    저는 東아시아 언어(이른바 )와 유니코드에도 關心이 많습니다. Mastodon에서는 國漢文混用體를 쓰고 있어요! 제게 韓國語나 英語, 日本語로 말을 걸어주세요. (아니면, 漢文으로도!)

  20. 이달 末에 페디버스의 여러 오픈 소스 소프트웨어에 컨트리뷰트 해 보는 스프린트를 서울에서 열려고 합니다. 먼저, 컨트리뷰터 또는 메인테이너 분들부터 모으고 있어요! 저는 제가 만든 ActivityPub 서버 프로젝트인 Hollo를 들고 갑니다.

    forms.gle/Y5yeiqPhgnW89xXt7

  21. Hi @hongminhee,
    #asbestos wasn't banned from the beginning, nor was #Xray. Time told. So it may with #LLMs.
    As to how productive they are - the data basis so far is too narrow to tell IMO. Some say so, some other. Recently a study claimed devs feel +20% but in fact are -20%.
    I have the notion the L im LLM fits the B in Big IT quite well.

    We have to re-focus from the means to the ends. What goals do we accomplish, not how much software do we engage.

  22. Hi @hongminhee,
    maybe #LLMs are the X-ray of IT.
    In the early days used like candy. (Kids got their feet x-rayed in stores on open appliances, so the parents could see if the shoes fit. No kidding)
    As experience grew, use was regulated and cut down increasingly. But it's still used to this day. For narrow usecases. Applied carefully.

    Admittedly I doubt LLMs are as useful as #Xray. I think it's rather the #asbestos (which made wonderful things of concrete possible but mostly wasn't worth the downsides).

  23. The #CFP for the Fediverse & Social Web track at COSCUP 2026 (Taipei, Aug 8–9) is now open! If you're working on #ActivityPub, the #fediverse, or anything in the open social web space, we'd love to hear from you. The deadline is May 9. #COSCUP is free to attend.

    👉 https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp

    (Boosts appreciated!)

    #SocialWeb #fedidev

  24. The #CFP for the Fediverse & Social Web track at COSCUP 2026 (Taipei, Aug 8–9) is now open! If you're working on #ActivityPub, the #fediverse, or anything in the open social web space, we'd love to hear from you. The deadline is May 9. #COSCUP is free to attend.

    👉 https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp

    (Boosts appreciated!)

    #SocialWeb #fedidev

  25. The #CFP for the Fediverse & Social Web track at COSCUP 2026 (Taipei, Aug 8–9) is now open! If you're working on #ActivityPub, the #fediverse, or anything in the open social web space, we'd love to hear from you. The deadline is May 9. #COSCUP is free to attend.

    👉 https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp

    (Boosts appreciated!)

    #SocialWeb #fedidev

  26. The #CFP for the Fediverse & Social Web track at COSCUP 2026 (Taipei, Aug 8–9) is now open! If you're working on #ActivityPub, the #fediverse, or anything in the open social web space, we'd love to hear from you. The deadline is May 9. #COSCUP is free to attend.

    👉 https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp

    (Boosts appreciated!)

    #SocialWeb #fedidev

  27. The #CFP for the Fediverse & Social Web track at COSCUP 2026 (Taipei, Aug 8–9) is now open! If you're working on #ActivityPub, the #fediverse, or anything in the open social web space, we'd love to hear from you. The deadline is May 9. #COSCUP is free to attend.

    👉 https://hackers.pub/@fedidevkr/2026/fediverse-social-web-track-at-coscup-2026-cfp

    (Boosts appreciated!)

    #SocialWeb #fedidev