雖然是在明天
但今天先貼好了

Definition. an invariant is a property that is satisfied at all times, regardless of… oh, you don’t want to? oh, sorry, sorry, i didn’t mean to impose, yeah no it’s fine, you can violate the property if you’d like, it’s just… ah don’t worry about it, i shouldn’t have asked

エンジニアの人やたらZennというのに記事投稿するけど、ダークモード非対応で目が潰れてしまう​​

Have news headlines changed the way we phrase toots? Local woman weighs in

I'm currently looking for PhD students in theoretical computer science, and we have a funding opportunity for a student in Inria Lille in France to work with myself and my collaborator Mikaël Monet. The proposed topic (quite flexible): https://a3nm.net/work/research/offers/phd_enumeration_changes.pdf. Applications are until April 23, to start in fall 2025.

I think the LINKS team in Inria Lille is a great place to do this kind of research -- in fact I recently joined it myself. :) Please apply or to forward to potential candidates!

Canadians booking trips to the U.S. has dropped by over 70% according to OAG. This is a COVID-level drop in travel which will have downstream economic impact on hotels, restaurants and more in the coming months.

I still think the market hasn’t priced in how disastrous the current government will be for American businesses.

Shocked scientists say this is a pretty good sandwich, vow to order it again

電波ちゃん @denpasabu電波 かいた！
色んな服を着せようねって言ってたから、赤いロリータにしてみたよ！〜こむぎちゃんを添えて〜
問題あれば下げます…！
#電波ちゃんアート

Canadians booking trips to the U.S. has dropped by over 70% according to OAG. This is a COVID-level drop in travel which will have downstream economic impact on hotels, restaurants and more in the coming months.

I still think the market hasn’t priced in how disastrous the current government will be for American businesses.

@stefanoStefano Marinelli Years ago we actually had a client calling us after a go-live just to tell us that everything runs finde and they wanted to thank us. But the ringing made everyones pulse spike. 🤣😂

You'd think with how hard it is to transition now, eggs would be cheaper

めっちゃくちゃいいものもろた Anthony Fuしか勝たん

俺たちのSignals道はこれからだ

In case this is useful to somebody:

Because of corporate collusion with law enforcement dating back to the 80s, all colour printers put tracking information on their printouts, whether you're printing a colour document or not, encoding information that ties printouts back to the specific printer used.

https://en.wikipedia.org/wiki/Printer_tracking_dots

In 2018, scholars at TU Dresden created a tool to re-anonymize color-printed documents by obscuring that data:

https://dl.acm.org/doi/10.1145/3206004.3206019

The tool: https://github.com/dfd-tud/deda

勉強会楽しかったけどVueのリアクティブについてまだまだ何もわからんなという気付きがあった

7.7 magnitude earthquake hits Southeast Asia, affecting Myanmar and Thailand

Link: https://twitter.com/TaraBull808/status/1905534938558157139
Discussion: https://news.ycombinator.com/item?id=43503265

Oversleptが全くできなくなっている。。。

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

窮人機之爭 (X

if you use consumer AI to "make art" or as a searching, writing, or reasoning engine, you're not welcome in my orbit and won't have fun here. you've never needed to use these things, and they're standing in a junkyard of other people's proprietary work.

if you use AI tools for accessibility etc. that's a different situation, not talking about you in this disclaimer!

すごい久々にビートマニアやったら全然指が動かん。

Please note, even Vivaldi with the newly built-in Proton VPN can't keep your secrets safe if you invite random journalists into your chats.
https://vivaldi.com/blog/privacy-without-compromise-proton-vpn-is-now-built-into-vivaldi/

#FediDonutFriday 🍩🍩🍩 Happy Friday everyone!

Nextjs를 처음 도입하고 계속 서버가 터져서 일단 롤백하고, 안정화&튜닝을 하다가 결국 Nextjs 소스를 깠다.

“Vercel에서만 제공되는 공개되지 않은 부분이 있는 것 같다”고 했을때 개발자들의 반응은 우리 CTO가 미쳤어요“였지만…

지금도 Vercel과 Nextjs는 쳐다보지도 않는다.

https://news.hada.io/topic?id=19999

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

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

ハマったらこれ楽しい

​​ ​​​​

RE: https://k.lapy.link/notes/a5w4te2cbb

"이때다"…식품업계, '권력 공백'에 줄줄이 가격 인상 n.news.naver.com/mnews/articl... 식품 대기업들이 가격을 마구 올리고 있는게 "이 시국" 정부가 물가 관리에 관심이 덜하기 때문이라는 것.

"이때다"…식품업계, '권력 공백'에 줄줄이 가격 인상

드디어 파괴된 이케아 의자와 똑같은 의자를 조립했다. 지난번 의자의 파괴된 부분을 미리 보강했는데 사실 보강 안해도 10년 이상 힘을 받기 위해 설계된 방향의 수직 방향으로 받는 힘을 버텨냈다. ......... 왜 설계 방향에 수직으로 힘을 받았느냐 하면 ......... 내가 삐딱한 자세로 앉아서 .......

多項式なのがポイントなのね
納得

통합 절차가 계획대로 진행되면 내년 6월 치러지는 지방선거 때 통합자치단체인 '대전충남특별시'가 출범한다. 이렇게 되면 대전시와 충남도는 1989년 분가한 지 37년 만에 다시 하나로 합쳐진다. 입력 : 2025-03-27 15:58:01 www.mk.co.kr/news/special...

대한민국 2위 경제거점 '대전충남특별시'… 내년 7월 ...

미얀마에서 28일 규모 7.7 강진이 일어나 많은 사상자가 발생한 것으로 추정됩니다. 이번 강진은 진원에서 1300㎞ 떨어진 타이 수도 방콕에서 건설 중이던 건물이 무너질 만큼 강력했습니다.

미얀마 7.7 강진…1300㎞ 떨어진 방콕 30층 건물...

Debugging other people's code, the diary.

So I made code change to this open source project, but don't know how to write the test.

Surely there's already an existing test that touched this code?
Where are those tests?

I know, just use the measurement context from coverage py. Popular open source project like this, surely they use coverage, right?

Looks at codebase.
No coverage.py dependency.

😐

ok... just add 1/0 here then and see which tests break.

3 new failed tests.

Aah, there you are.

정혜경 의원, “경찰 폭행에 전치 2주…서울경찰청장 고소하겠다” 입력2025.03.28. 오후 5:30 “국회의원 신분 확인하고도 자행 된 경찰 폭력에 심각성 느껴” www.womennews.co.kr/news/article...

정혜경 의원, “경찰 폭행에 전치 2주…서울경찰청장 고...

[단독] '전역' 임성근에 830만원 성과금…'복직' 박정훈은 올해도 0원 입력 2025.03.28 20:42 news.jtbc.co.kr/article/NB12...

[단독] '전역' 임성근에 830만원 성과금…'복직' ...

RS符号の仕組みちょっと理解した

The ActivityPub specification does not have an example of the "sharedInbox" field in use.

Although it does say "An optional endpoint..." — I suspect a lot of people won't know (with confidence) that it can go under the "endpoints" field. For example:

"endpoints": {
"sharedInbox": "https://social.example/inbox"
},

Especially if the person is still trying to understand ActivityPub, and isn't aware of the "endpoints" field yet.

#ActivityPub #DeSo #FediDev #FediDevs #Fediverse #SharedInbox

한전없이 전기 사는 '전력직접구매' 허용...대형 전기 소비처 '직구' 시작 www.etnews.com/20250328000327 일본에서 전기 민영화를 돌려말할 떄 쓰는 표현이라고. 진짜 나쁘다.

[단독] 한전없이 전기 사는 '전력직접구매' 허용......

여전히 줄이면 대충특별시...

RE: https://bsky.brid.gy/convert/ap/at://did:plc:uabkr6tn7ru4b4e5e6udleuf/app.bsky.feed.post/3llgtlpipec2m

[단독] '전역' 임성근에 830만원 성과금…'복직' 박정훈은 올해도 0원 입력 2025.03.28 20:42 news.jtbc.co.kr/article/NB12...

[단독] '전역' 임성근에 830만원 성과금…'복직' ...

It's considered uncool to kneel in front of your mutuals and ask them to marry you. This type of behavior is widely referred to as engagement bait

iPad 第11世代（A16）のことを「iPad 11st」と書いているサイトがあった（日本のサイト）