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.

洪 民憙 (Hong Minhee) @hongminhee@hackers.pub
Public

Cloudflare Workers 배포와 RFC 9421 (HTTP Message Signatures) 서명 및 검증을 지원하는 Fedify 1.6이 릴리스되었습니다!

1
0
0
The CEO of waifuism @waifu@mai.waifuism.life
Public

Devlog #11:
After I forgot to pay for the VPS expenses, my setup broke, so i had to migrate from gitea to forgejo, which took a few days but was not as painful as I expected...
At least now we can use ssh (i was using docker in the previous setup for some reason) and I just solved another issue ​:capybara_sit:​
So we're a little bit closer now ​:watamelon_pet:​
I'm taking some time between programming sessions to also make cards so we don't start the game and just have no cards to play with, so I may make a post asking for recommended characters people would like to have in the game as cards even if they won't be in the sourcecode.

RE: https://mai.waifuism.life/notes/a8kwic8ejmf007dt

0
0
1
0
0
0
0
0
0
0
0
0
해담 :_ku::_mo::_ri: :blobcatgooglyverified: @cmrbada@k.lapy.link
Public
Shared by zero

고이즈미 신지로 신 농림수산부 장관, 한국에서 불리는 별명은 "펀쿨섹좌" : 일본 마이니치 신문

아니 이게 일본 공식 뉴스에 수출됌 ​:kirby_lmao:​

https://mainichi.jp/articles/20250522/k00/00m/030/270000c

小泉新農相、韓国でのあだ名は「ファンクルセク座」　由来はあの発言 | 毎日新聞

　韓国メディアは、自民党の小泉進次郎氏が21日に農相に就任したことについて、一斉に報じた。小泉氏はその独特な発言などから、韓国でも広く知られ、不思議なニックネームまでついている。

mainichi.jp · 毎日新聞

0
0
0
0
0
0
0
0
0
1
0
0
Fedify: ActivityPub server framework @fedify@hollo.social
Public
Shared by 洪 民憙 (Hong Minhee)

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.

Cloudflare Workers©

Build your next application with Cloudflare Workers

workers.cloudflare.com

2
0
2
Fedify: ActivityPub server framework @fedify@hollo.social
Public
Shared by ここあにゃん :surprised_karin_chibi:

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.

Cloudflare Workers©

Build your next application with Cloudflare Workers

workers.cloudflare.com

2
0
2
1
0
0
Fedify: ActivityPub server framework @fedify@hollo.social
Public

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.

Cloudflare Workers©

Build your next application with Cloudflare Workers

workers.cloudflare.com

2
0
2
0
0
0
0
0
0
해담 :_ku::_mo::_ri: :blobcatgooglyverified: @cmrbada@k.lapy.link
Public

고이즈미 신지로 신 농림수산부 장관, 한국에서 불리는 별명은 "펀쿨섹좌" : 일본 마이니치 신문

아니 이게 일본 공식 뉴스에 수출됌 ​:kirby_lmao:​

https://mainichi.jp/articles/20250522/k00/00m/030/270000c

小泉新農相、韓国でのあだ名は「ファンクルセク座」　由来はあの発言 | 毎日新聞

　韓国メディアは、自民党の小泉進次郎氏が21日に農相に就任したことについて、一斉に報じた。小泉氏はその独特な発言などから、韓国でも広く知られ、不思議なニックネームまでついている。

mainichi.jp · 毎日新聞

0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
4
1
0
tagesschau @tagesschau@ard.social
Public

Union sieht "Inszenierung" von Pro Asyl bei Urteil zu Zurückweisungen

Zurückweisungen von Asylsuchenden an der Grenze sind rechtswidrig - so sieht es zumindest ein Berliner Gericht. Die Union wirft nun Pro Asyl vor, das Urteil provoziert zu haben. Die Hilfsorganisation weist die Vorwürfe zurück.

➡️ tagesschau.de/inland/innenpoli

Union sieht "Inszenierung" von Pro Asyl bei Urteil zu Zurückweisungen

Zurückweisungen von Asylsuchenden an der Grenze sind rechtswidrig - so das Urteil eines Berliner Gerichts. Die Union wirft nun Pro Asyl vor, die Entscheidung provoziert zu haben. Die Hilfsorganisation weist die Vorwürfe zurück.

www.tagesschau.de · tagesschau.de

0
0
0
0
1
0
0
0
0
0
0
0
kazuhito @kazuhito@vivaldi.net
Public

Favorite Photo: natural beauty in the morning with mountains, rice fields and rivers by rahmadhimawan_photography flic.kr/p/2r9bbku

natural beauty in the morning with mountains, rice fields and rivers

The natural beauty of the morning in North Bengkulu, displays a harmonious blend of majestic mountains, lush green rice fields, and clear river flows. Fresh air and a calm atmosphere present a natural tranquility that pampers the eyes and soul.

www.flickr.com · Flickr

0
0
0
0
0
0
ふるふる @frfr@mk.f72u.net
Public

しゅい回復モード入れたならこれやってみ
https://www.pasoble.jp/windows/10/088123.html#c4

Windows 10 復旧 コマンドプロンプトでシステムファイルとイメージを修復

Windows10 の挙動や動作がおかしい、または起動しないなど、コマンドプロンプトによりディスクチェックやトラブルシューティングで解決できない問題が修復ができる可能性があります。

www.pasoble.jp · パソブル

1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
4
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
✧✦Catherine✦✧ @whitequark@mastodon.social
Public

i've upgraded the Ethernet controller applet for

this is the main loop of the applet working in bridge mode (acting as a network card for your PC). no weird optimizations, no hacks, just a loop that forwards packets in normal boring Python

on a 100BASE-T link, i get ~95.5 Mbps [saturated link] of upload bandwidth and ~70 Mbps of download bandwidth before packet loss starts

how cool is this?

async def run(self, args): if args.operation == "bridge": os_iface = OSNetworkInterface(args.interface) async def forward_rx(): async for packet in self.eth_iface.iter_recv(): if len(packet) >= 14: # must be at least ETH_HLEN, or we'll get EINVAL on Linux await os_iface.send([packet]) async def forward_tx(): while True: for packet in await os_iface.recv(): if not await self.eth_iface.send(packet): break async with asyncio.TaskGroup() as group: group.create_task(forward_rx()) group.create_task(forward_tx())
0
0
0
1
0
0
0
0
0
0
0
0