개인프로젝트 어딘가에 https://posthog.com/ 붙이고 싶은데 뭔가 서빙하고 있는게 하나도 없음....... 플러터앱 출시하면 좀 넣어볼까

Is alt text useful? Should you describe colors in images? Find answers to these questions, and more, with these polls and insights.

https://stefanbohacek.com/blog/polls-about-alt-text-on-social-media/

#AltText #accessibility #ImageDescription

Towards fearless SIMD, 7 years later https://lobste.rs/s/g1z2pu #rust
https://linebender.org/blog/towards-fearless-simd/

いろいろしてた。

Yesterday I had the great pleasure of meeting @cwebberChristine Lemmer-Webber AFK for the first time. I have been following her work since early MediaGoblins, thru to ActivityPub standardiziation & on to her work with @spritelyThe Spritely Institute. That people can exist in this digital and mental realm for so many years & then suddenly exist in front of you as real humans with flesh & bones never ceases to amaze me. I also got to meet Pooja, who's one of the people responsible for the initial industrial design for the MNT Pocket Reform!

もう以前のようには飲めなくなっちゃんたんだよなあ

해커스 펍이 왕성한 이 때, 혼자 조용히 저는 @holloHollo 가 좋아요 ㅎㅎ

これもすごい！労働者がんばれ^_^

港の産業別労働組合・全国港湾が、24時間ストライキを決行し、日本のすべての港の荷役を停止させました。横浜港では山下埠頭のゲートをストの横断幕で封鎖。全国港湾は春闘で10%・3万円以上の賃上げを求め、港湾事業者に対して利益を上げている船社に港湾料金の価格転嫁をすべきだと主張しています。

https://x.com/akahatakokumin/status/1906141338279797077

AI가 생성한 내용을 내 지식관리시스템(위키 등)에 복붙하면 그건 내 지식일까 아닐까?

2008년 경에 The extended mind (1998, Andy Clark and David Chalmers)라는 짧은 에세이를 읽었는데 여기서 본 내용이 참고할만 하다.

저자들은 장기기억 상실을 앓고 있는 사람이 수첩에 모든 걸 기록하고 항상 이를 참고한다면 그 수첩에 담긴 글들은 "확장된 기억"이라고 주장한다. 더 나아가서, 수첩의 내용이 단순히 "기억"이 아니라 "믿음extended dispositional belief"이기 위해서 필요한 기준을 추가로 제시한다.

1. 해당 정보가 그 사람의 삶에 항상 함께하며 참고해야하는 상황이 오면 거의 반드시 참고하여 행동한다.
2. 참고하고 싶을 때 어려움 없이 참고할 수 있어야 한다.
3. 일단 그 정보를 참고하면 이를 의심없이 수용한다.
4. 그 정보가 거기에 담긴 이유는 과거 언젠가 내가 내용을 신뢰했기 때문이다.

AI가 생성한 내용을 검토 없이 복붙했다면 이는 4번을 만족하지 못하고, 이에 따라 3번에도 문제가 생긴다. 따라서 검토 없는 복붙은 좋은 전략이 아닐 뿐 아니라 내 지식관리시스템을 망칠 가능성이 크다.

참고로 에세이의 저자들은 이 중 마지막 기준에 논쟁의 여지가 있다고 말하긴 한다. 무의식적으로 믿음이 형성되는 경우, 기억 조작이 일어난 경우 등이 있기 때문. 그런데 KMS 맥락에선 4번이 중요하다고 봐도 되겠다.

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

#Fedify now implements a smart fan-out mechanism for delivering activities to large audiences. This change is particularly valuable for accounts with many followers. When sending activities to many recipients, Fedify now creates a single consolidated message containing the activity payload and recipient list, which a background worker then processes to re-enqueue individual delivery tasks.

This architectural improvement delivers several benefits: Context.sendActivity() returns almost instantly even with thousands of recipients, memory consumption is dramatically reduced by avoiding payload duplication, UI responsiveness improves since web requests complete quickly, and the system maintains reliability with independent retry logic for each delivery.

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

You can now explicitly configure a canonical origin for your server, which is especially useful for multi-domain setups. This feature allows you to set different domains for WebFinger handles and #ActivityPub URIs, configured through the new origin option in createFederation(). This enhancement prevents unexpected URL construction when requests bypass proxies and improves security by ensuring consistent domain usage.

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

Followers collection synchronization (FEP-8fcf) is now opt-in rather than automatic. This feature must now be explicitly enabled through the syncCollection option, giving developers more control over when to include followers collection digests. This change improves network efficiency by reducing unnecessary synchronization traffic.

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Key format support has been expanded for better interoperability. Fedify now accepts PEM-PKCS#1 format in addition to PEM-SPKI for RSA public keys. We've added importPkcs1() and importPem() functions for additional flexibility, which improves compatibility with a wider range of ActivityPub implementations.

Improved Key Selection Logic

The key selection process is now more intelligent. The fetchKey() function can now select the public key of an actor if keyId has no fragment and the actor has only one public key. This enhancement simplifies key handling in common scenarios and provides better compatibility with implementations that don't specify fragment identifiers.

New Authorization Options

Authorization handling has been enhanced with new options for the RequestContext.getSignedKey() and getSignedKeyOwner() methods. This provides more flexible control over authentication and authorization flows. We've deprecated older parameter-based approaches in favor of the more flexible method-based approach.

Efficient Bulk Message Queueing

Message queue performance is improved with bulk operations. We've added an optional enqueueMany() method to the MessageQueue interface, enabling efficient queueing of multiple messages in a single operation. This reduces overhead when processing batches of activities. All our message queue implementations have been updated to support this new operation:

• @fedify/redis 0.4.0
• @fedify/postgres 0.3.0
• @fedify/amqp 0.2.0

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

The Fedify command-line tools have been enhanced with an improved web interface for the fedify inbox command. We've added the Fedify logo with the cute dinosaur at the top of the page and made it easier to copy the fediverse handle of the ephemeral actor. We've also fixed issues with the web interface when installed via deno install from JSR.

Additional Improvements and Bug Fixes

• Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
• Fixed bundler errors with uri-template-router on Rollup
• Improved error handling and logging for document loader when KV store operations fail
• Added more log messages using the LogTape library
• Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

#fedidev #fediverse

アルパカおいしい！！
アルパカやすい！！

AI가 생성한 내용을 내 지식관리시스템(위키 등)에 복붙하면 그건 내 지식일까 아닐까?

2008년 경에 The extended mind (1998, Andy Clark and David Chalmers)라는 짧은 에세이를 읽었는데 여기서 본 내용이 참고할만 하다.

저자들은 장기기억 상실을 앓고 있는 사람이 수첩에 모든 걸 기록하고 항상 이를 참고한다면 그 수첩에 담긴 글들은 "확장된 기억"이라고 주장한다. 더 나아가서, 수첩의 내용이 단순히 "기억"이 아니라 "믿음extended dispositional belief"이기 위해서 필요한 기준을 추가로 제시한다.

1. 해당 정보가 그 사람의 삶에 항상 함께하며 참고해야하는 상황이 오면 거의 반드시 참고하여 행동한다.
2. 참고하고 싶을 때 어려움 없이 참고할 수 있어야 한다.
3. 일단 그 정보를 참고하면 이를 의심없이 수용한다.
4. 그 정보가 거기에 담긴 이유는 과거 언젠가 내가 내용을 신뢰했기 때문이다.

AI가 생성한 내용을 검토 없이 복붙했다면 이는 4번을 만족하지 못하고, 이에 따라 3번에도 문제가 생긴다. 따라서 검토 없는 복붙은 좋은 전략이 아닐 뿐 아니라 내 지식관리시스템을 망칠 가능성이 크다.

참고로 에세이의 저자들은 이 중 마지막 기준에 논쟁의 여지가 있다고 말하긴 한다. 무의식적으로 믿음이 형성되는 경우, 기억 조작이 일어난 경우 등이 있기 때문. 그런데 KMS 맥락에선 4번이 중요하다고 봐도 되겠다.

ぺいー

ぺいー

We're excited to announce the release of Fedify 1.5.0! This version brings several significant improvements to performance, configurability, and developer experience. Let's dive into what's new:

Two-Stage Fan-out Architecture for Efficient Activity Delivery

#Fedify now implements a smart fan-out mechanism for delivering activities to large audiences. This change is particularly valuable for accounts with many followers. When sending activities to many recipients, Fedify now creates a single consolidated message containing the activity payload and recipient list, which a background worker then processes to re-enqueue individual delivery tasks.

This architectural improvement delivers several benefits: Context.sendActivity() returns almost instantly even with thousands of recipients, memory consumption is dramatically reduced by avoiding payload duplication, UI responsiveness improves since web requests complete quickly, and the system maintains reliability with independent retry logic for each delivery.

For specific requirements, we've added a new fanout option with three settings:

// Configuring fan-out behavior
await ctx.sendActivity(
  { identifier: "alice" },
  recipients,
  activity,
  { fanout: "auto" }  // Default: automatic based on recipient count
  // Other options: "skip" (never use fan-out) or "force" (always use fan-out)
);

Canonical Origin Support for Multi-Domain Setups

You can now explicitly configure a canonical origin for your server, which is especially useful for multi-domain setups. This feature allows you to set different domains for WebFinger handles and #ActivityPub URIs, configured through the new origin option in createFederation(). This enhancement prevents unexpected URL construction when requests bypass proxies and improves security by ensuring consistent domain usage.

const federation = createFederation({
  // Use example.com for handles but ap.example.com for ActivityPub URIs
  origin: {
    handleHost: "example.com",
    webOrigin: "https://ap.example.com",
  },
  // Other options...
});

Optional Followers Collection Synchronization

Followers collection synchronization (FEP-8fcf) is now opt-in rather than automatic. This feature must now be explicitly enabled through the syncCollection option, giving developers more control over when to include followers collection digests. This change improves network efficiency by reducing unnecessary synchronization traffic.

await ctx.sendActivity(
  { identifier: sender },
  "followers",
  activity,
  { 
    preferSharedInbox: true,
    syncCollection: true,  // Explicitly enable collection synchronization
  }
);

Enhanced Key Format Compatibility

Key format support has been expanded for better interoperability. Fedify now accepts PEM-PKCS#1 format in addition to PEM-SPKI for RSA public keys. We've added importPkcs1() and importPem() functions for additional flexibility, which improves compatibility with a wider range of ActivityPub implementations.

Improved Key Selection Logic

The key selection process is now more intelligent. The fetchKey() function can now select the public key of an actor if keyId has no fragment and the actor has only one public key. This enhancement simplifies key handling in common scenarios and provides better compatibility with implementations that don't specify fragment identifiers.

New Authorization Options

Authorization handling has been enhanced with new options for the RequestContext.getSignedKey() and getSignedKeyOwner() methods. This provides more flexible control over authentication and authorization flows. We've deprecated older parameter-based approaches in favor of the more flexible method-based approach.

Efficient Bulk Message Queueing

Message queue performance is improved with bulk operations. We've added an optional enqueueMany() method to the MessageQueue interface, enabling efficient queueing of multiple messages in a single operation. This reduces overhead when processing batches of activities. All our message queue implementations have been updated to support this new operation:

• @fedify/redis 0.4.0
• @fedify/postgres 0.3.0
• @fedify/amqp 0.2.0

If you're using any of these packages, make sure to update them alongside Fedify to take advantage of the more efficient bulk message queueing.

CLI Improvements

The Fedify command-line tools have been enhanced with an improved web interface for the fedify inbox command. We've added the Fedify logo with the cute dinosaur at the top of the page and made it easier to copy the fediverse handle of the ephemeral actor. We've also fixed issues with the web interface when installed via deno install from JSR.

Additional Improvements and Bug Fixes

• Updated dependencies, including @js-temporal/polyfill to 0.5.0 for Node.js and Bun
• Fixed bundler errors with uri-template-router on Rollup
• Improved error handling and logging for document loader when KV store operations fail
• Added more log messages using the LogTape library
• Internalized the multibase package for better maintenance and compatibility

For the complete list of changes, please refer to the changelog.

To update to Fedify 1.5.0, run:

# For Deno
deno add jsr:@fedify/fedify@1.5.0

# For npm
npm  add     @fedify/fedify@1.5.0

# For Bun
bun  add     @fedify/fedify@1.5.0

Thank you to all contributors who helped make this release possible!

#fedidev #fediverse

꺼무위키 광고 싹 짜르기 이거 쓰면 광고 수입이 꺼무에게 안 갈 겁니다. 이 페이지에 리스트 되어 있는 광고 차단 확장 기능 중 하나(저는 uBlock Origin 추천)를 설치한 뒤에 링크에 있는 스크립트를 설치하도록 합시다. 가장 좋은 건 꺼무를 안 쓰는 거겠지만 아무래도 저기 자료가 제일 많이 모여있고 간단하게 찾기에 편한 것도 있어서... 정 써야 하는 게 불가피하다면 광고 수입이라도 저 더러운 것들에게 가는 건 최소화 해야겠지요.

NamuLink | List-KR Community

@stefanoStefano Marinelli thank you :)

企画考えるのはGeminiよりChatGPTの方がよさそう、無料の範囲では。

해커스 펍이 왕성한 이 때, 혼자 조용히 저는 @holloHollo 가 좋아요 ㅎㅎ

해커스 펍이 왕성한 이 때, 혼자 조용히 저는 @holloHollo 가 좋아요 ㅎㅎ

我發現在嘟文前打一個「RT」的用法好像是類似推特的引用推文？而推特那邊的用法好像是指轉貼不能轉推的推文（或者不想打擾到原推）。不知道我理解的有沒有錯🤔

Convert Linux to Windows https://lobste.rs/s/tobrqw #unix #windows
https://philipbohun.com/blog/0007.html

해커스 펍이 왕성한 이 때, 혼자 조용히 저는 @holloHollo 가 좋아요 ㅎㅎ

Slides have been released on this wonderful piece of balancing software for your proxmox clusters proxyLB
Now you can learn even more about this piece of wonderful software

Courtesy of @gyptazy

🖋️ #bash #proxyLB #freeBSD #boxyBSD #sh #zsh #ksh #csh  #netBSD #openBSD #POSIX #proxmox #loadbalancer

https://github.com/gyptazy/ProxLB

🍋

#藍アート #藍art

망할 놈의
IPv6

#ProxLB - an opensource & advanced VM loadbalancer for #Proxmox clusters. Including affinity & anti-affinity rules, maintenance mode (evacuating nodes) and more. I just published my slides about it.

Project: https://github.com/gyptazy/ProxLB
Slides: https://cdn.gyptazy.com/files/talks/ProxLB-Intelligent-Workload-Balancing-for-Proxmox-Clusters.pdf

#homelab #vmware #alternatives #opensource #python #coding #devops #virtualization #proxmoxve

今日一日韓国制作のバラエティ見て芸人いなくて無理な笑わせ演出が無いとこんなに楽しく品が良い番組が作れるんだな、と感動してたら日本のバラエティが終わってる話が流れてきたので何も言えない

Malware is harder to find when written in obscure languages like Delphi and Haskell

https://www.theregister.com/2025/03/29/malware_obscure_languages/

Discussions: https://discu.eu/q/https://www.theregister.com/2025/03/29/malware_obscure_languages/

#haskell #programming

IPv6 두통

AI가 생성한 내용을 내 지식관리시스템(위키 등)에 복붙하면 그건 내 지식일까 아닐까?

2008년 경에 The extended mind (1998, Andy Clark and David Chalmers)라는 짧은 에세이를 읽었는데 여기서 본 내용이 참고할만 하다.

저자들은 장기기억 상실을 앓고 있는 사람이 수첩에 모든 걸 기록하고 항상 이를 참고한다면 그 수첩에 담긴 글들은 "확장된 기억"이라고 주장한다. 더 나아가서, 수첩의 내용이 단순히 "기억"이 아니라 "믿음extended dispositional belief"이기 위해서 필요한 기준을 추가로 제시한다.

1. 해당 정보가 그 사람의 삶에 항상 함께하며 참고해야하는 상황이 오면 거의 반드시 참고하여 행동한다.
2. 참고하고 싶을 때 어려움 없이 참고할 수 있어야 한다.
3. 일단 그 정보를 참고하면 이를 의심없이 수용한다.
4. 그 정보가 거기에 담긴 이유는 과거 언젠가 내가 내용을 신뢰했기 때문이다.

AI가 생성한 내용을 검토 없이 복붙했다면 이는 4번을 만족하지 못하고, 이에 따라 3번에도 문제가 생긴다. 따라서 검토 없는 복붙은 좋은 전략이 아닐 뿐 아니라 내 지식관리시스템을 망칠 가능성이 크다.

참고로 에세이의 저자들은 이 중 마지막 기준에 논쟁의 여지가 있다고 말하긴 한다. 무의식적으로 믿음이 형성되는 경우, 기억 조작이 일어난 경우 등이 있기 때문. 그런데 KMS 맥락에선 4번이 중요하다고 봐도 되겠다.

A reminder, the Fediverse cost money.

Yes, it is free for YOU to use, but your local administrator pays for domain registration, web hosting, storage space, CDN, and of course, bandwidth.

The busier and more active your Fedi site, the most it cost.

If you are able, consider reaching out to your admin, and asking how you can help. Even small contributions add up and make a difference.

#Fediverse #Fedi #ActivityPub #Mastodon #Misskey

@hongminhee洪 民憙 (Hong Minhee) ㅋㅋㅋ 맞아요! 추억이 방울방울. 당시에 <Supersizing the Mind>를 요약해서 공유했더랬죠. 오랜 시간 영향을 준 (지금도 주고 있는) 좋은 책이었어요.

#블스지식인: 중앙대학교 주변에 괜찮은 ~3km짜리 산책로가 있나요?

this is why we can't have nice things

https://github.com/marrink-lab/bentopy/commit/12681b4c641afffb4dddcf882c9784bfba94d71c

諸位，一個壞消息一個好消息，壞消息是明天是星期一，好消息是星期四就放假了

Rust finally has upcast 🎉

This is huge!

https://lucumr.pocoo.org/2025/3/27/any-upcast/

Koto Programming Language https://lobste.rs/s/dqezic #rust
https://koto.dev/

@hongminhee洪 民憙 (Hong Minhee) ㅋㅋㅋ 맞아요! 추억이 방울방울. 당시에 <Supersizing the Mind>를 요약해서 공유했더랬죠. 오랜 시간 영향을 준 (지금도 주고 있는) 좋은 책이었어요.

anyways windows was defeated in the air, so I may get to cut a releza

买个二手的 M1 Mac Studio 吧

people call me madam here, so fancy

GAY WOMEN YURI WOMEN WOMEN WOMEN WOMEN

nuintari's rules of networking 0x1f:

Standardize on single mode fiber. There is no significant cost savings for using multimode, no technical advantage to doing so, and the asset management team will thank you.

我发现我对联邦宇宙的贡献还没有某位现在在 X 上活跃的兽对 Atmosphere 的贡献高，现在开始锁嘟

#사진 #사진토돈 #photography #마스토돈사진부

FOURB

카메라: 보이그랜더 BESSA R
렌즈: 보이그랜더 COLOR-SKOPAR 35mm F2.5 MC
🎞️: Kodak Eastman Double-X 5222 200

@bglbgl gwyng 파이어베이스랑은 결이 좀 다른 것 같구요. 그나마 비교를 할만하다면, 구글 애널리틱스랑 그나마 비교가 가능할 것 같은데, posthog는 퍼널 분석은 깔고 가는거고 메트릭별로 쿼리를 날려보고 그걸로 차트도 뽑아볼 수 있어욥.