What is Hackers' Pub?

Hackers' Pub is a place for software engineers to share their knowledge and experience with each other. It's also an ActivityPub-enabled social network, so you can follow your favorite hackers in the fediverse and get their latest posts in your feed.

0
0
0
0
0
0
1
0
1
0
0
0
0
0
0
0
0
0
0
0
1
0
1
1
0

We're excited to announce the release of 1.6.1, which marks the beginning of the 1.6 series following the retraction of version 1.6.0. This release introduces significant new capabilities that expand Fedify's deployment options and enhance security compatibility across the .

🌐 Cloudflare Workers support

Fedify 1.6 introduces first-class support for Cloudflare Workers, enabling deployment of applications at the edge.

New components

Key features

  • Seamless integration with 's serverless runtime
  • Automatic handling of queue message processing through Workers' queue() method
  • Support for Node.js compatibility flag required for Fedify's cryptographic operations
  • Manual queue processing via Federation.processQueuedTask() method

For a complete working example, see the Cloudflare Workers example in the Fedify repository.

🏗️ Federation builder pattern

Fedify 1.6 introduces the FederationBuilder class and createFederationBuilder() function to support deferred federation instantiation. This pattern provides several benefits:

  • Deferred instantiation: Set up dispatchers and listeners before creating the federation object
  • Better code organization: Avoid circular dependencies and improve project structure
  • Cloudflare compatibility: Accommodates binding-based architectures where resources are passed as arguments rather than globals
  • Modular setup: Build complex federations piece by piece before instantiation

The builder pattern is particularly useful for large applications and environments like Cloudflare Workers where configuration data is only available at runtime.

🔐 HTTP Message Signatures (RFC 9421)

Fedify 1.6 implements the official HTTP Message Signatures standard (RFC 9421) specification, the final revision of the HTTP Signatures specification.

Double-knocking mechanism

To ensure maximum compatibility across the fediverse, Fedify 1.6 introduces an intelligent double-knocking mechanism:

  1. Primary attempt: RFC 9421 (HTTP Message Signatures) for modern implementations
  2. Fallback: Draft cavage version for legacy compatibility
  3. Adaptive caching: The system remembers which version each server supports to optimize future requests

This approach ensures seamless communication with both modern and legacy ActivityPub implementations while positioning Fedify at the forefront of security standards.

Interoperability testing

The RFC 9421 implementation has been thoroughly tested for interoperability with existing ActivityPub implementations that support RFC 9421 signature verification:

  • Mitra 4.4.0: Successfully verified Fedify-generated RFC 9421 signatures
  • Mastodon 4.4.0 development version: Tested RFC 9421 signature verification against Fedify's implementation (refer to Mastodon PR #34814, though Mastodon 4.4.0 has not yet been released)

These tests confirm that other ActivityPub implementations can successfully verify RFC 9421 signatures generated by Fedify, ensuring proper federation as the ecosystem gradually adopts the official specification. While these implementations currently support verification of RFC 9421 signatures, they do not yet generate RFC 9421 signatures themselves—making Fedify one of the first ActivityPub implementations to support both generation and verification of the modern standard.

🔍 WebFinger enhancements

Dedicated WebFinger lookup

The new Context.lookupWebFinger() method provides direct access to WebFinger data, offering developers more granular control over account discovery and resource resolution beyond the higher-level Context.lookupObject() method.

🛠 Context API improvements

Context data replacement

The new Context.clone() method enables dynamic context data replacement, providing greater flexibility in request processing and data flow management. This is particularly useful for middleware implementations and complex request routing scenarios.

🚀 Migration considerations

Backward compatibility

Fedify 1.6 maintains full backward compatibility with existing applications. The new HTTP Message Signatures and double-knocking mechanisms work transparently without requiring any code changes.

Node.js version requirement

Important: Fedify 1.6 requires Node.js 22.0.0 or later for Node.js environments. This change does not affect applications using Deno or Bun runtimes. If you're currently using Node.js, please ensure your environment meets this requirement before upgrading.

New deployment options

For new deployments, consider leveraging Cloudflare Workers support for:

  • Global edge deployment with low latency
  • Serverless scaling and automatic resource management
  • Integration with Cloudflare's ecosystem of services

🎯 Looking forward

Fedify 1.6 represents a significant expansion of deployment possibilities while maintaining the framework's commitment to broad compatibility across the fediverse. The addition of Cloudflare Workers support opens new architectural patterns for federated applications, while the RFC 9421 implementation ensures Fedify stays current with emerging ActivityPub security standards.


For detailed migration guides, API documentation, and examples, please visit the Fedify documentation. Join our community on Matrix or Discord for support and discussions.

2
0
2
0
0
0
0
0
1

wakest ⁂ shared the below article:

6.0.0 – New Kids on the Block

ActivityPub for WordPress @activitypub.blog@activitypub.blog

<p>Our latest release brings a lot of improvements — especially to our blocks! </p> <p>The Follow Me and Followers blocks now have a fresh design, better interactivity, and broader support for ActivityPub-enabled users.</p> <p>The Reactions block and “Reply on the Fediverse” feature also now take advantage of the latest Block Editor features and are built on the Interactivity API for a smoother experience.</p> <p>We’ll follow up soon with a deeper dive into the new block features — stay […]</p>

Read more →
0
3
0
0
0
0
0
1

この本面白そう。

基本的にPhotoshopを使うらしく、
「Figmaはワイヤーフレームならいいでしょう」
という感じなの、ゲーム業界はそうなのか……という感じ。

ゲームUI 作り方講座 Photoshop&After Effectsで学ぶ、UIデザインとアニメーションの基本 | 技術評論社
gihyo.jp/book/2025/978-4-297-1

ゲームUI 作り方講座 Photoshop&After Effectsで学ぶ、UIデザインとアニメーションの基本 | 技術評論社

UIデザイン + UIアニメーション &darr; ゲームUIの考え方と作り方がこれ1冊でわかる! ゲーム制作にあたって、UIのデザインはとても重要です。スマホの画面で操作しやすいUI、見やすいUI、魅力的なUIを制作する必要があります。本書は、ゲームUIをデザインしたい 新人ゲームデザイナー インディーゲームの制作者 ゲームの仕事につきたい学生 を対象に、ゲームUIをデザインするための基本的な考え方から、実際のUIパーツ、アニメーションの作り方までをやさしく解説した書籍です。前半のUIデザイン編では、Photoshopを使ってダイアログとホーム画面のUIパーツをデザイン。後半のUIアニメーション編では、デザイン編で制作したUIパーツに動きをつけます。本書の解説に使用しているサンプルファイルは、本書購入者のみダウンロード可能。UIアニメーションは、QRコードから動きを見ることができます。デザイン+アニメーションで、ゲームUIの知識と実践がよくわかる1冊です! 本書で作れるUI ボタン/アイコン/フレーム/ランク/ゲージ/ライフ/コイン/ジェム/ラベル/バッジ/バナー/ロゴ/メニュー

gihyo.jp · 技術評論社

0

Alan Turing died by suicide on 7 June 1954. Turing was convicted of gross indecency in 1952 and given a choice between imprisonment and probation. His probation would be conditional on his agreement to undergo hormonal physical changes designed to reduce his libido. Turing's conviction led to the removal of his security clearance and barred him from continuing with his consultancy for GCHQ. He was denied entry into the United States after his conviction.

Alan Turing in 1951.
0
0
0

오늘은 식민지역사박물관의 기획전시 "민주주의와 깃발"을 보고 왔습니다. 퇴진광장에 발끝만 걸친 시민이지만, 그 길면서 짧았던 시간에 대한 에필로그가 되는 느낌이었어요. 세월은 멈춤없이 흘러가도 누군가는 그 순간을 아카이빙하여 역사에 남기고 있다는 데서, 어떠한 큰 격려를 받은 느낌.

0
0
0
0
0
0
0
0
1
0

지난 5월 29일에 열렸던 #AIDotNetDay 모든 세션이 유튜브에 올라왔습니다.

https://www.youtube.com/playlist?list=PLDZRZwFT9WkvKxA62JsC060NYgxkWid1n

.NET이 AI 앱을 만드는데 가장 가성비 높은 언어라는 것을 다양한 세션을 통해 알아보세요.

#ai #dotnet #meai #aifoundry #foundrylocal #semantickernel #mcp #aitemplate #codewithoutbarriers #cwb
#AI DotNet Day

0
0
0
0
0
0