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.

1
0
2
0
0
0
0
0
5
0

Correspondance Howard-Lovecraft :

⚠️ Avis pour les retardataires ! ⚠️

Je republie ici un post de Mnémos (l’éditeur) sur le forum de la correspondance :

“Nous organiserons un "late Pledge" d'ici quelques semaines, soit la possibilité d'acquérir la Correspondance durant une période de temps limitée. Pour ne pas la manquer, surveillez nos réseaux sociaux :)”

fr.ulule.com/la-correspondance

A bon entendeur, salut !

0

Y'know what? As an and enthusiast, it's genuinely awesome to see increased mainstream coverage of and . Unfortunately, a lot of these articles are riddled with mistakes, misinformation, clickbait, and overall low quality. A few minutes ago, while catching up on tech news I came across one author's frequent posts on Linux and FreeBSD.

To emphasize my point, I am only going to focus on one article titled, "After decades on Linux, FreeBSD finally gave me a reason to switch operating systems."

The following passages stuck out like sore thumb:

1.) "FreeBSD is more challenging than Linux."

-But is it really? Subjective, particularly if coming from a GUI-driven Linux distribution. Frankly I find FreeBSD easier because of the excellent documentation and coherent design.

2.) "FreeBSD is Unix-like" but further down he states, "Essentially, FreeBSD is Unix, where Linux is based on Unix."

-Contradictory, incorrect, and confusing for newcomers. FreeBSD is Unix. Linux (neither the kernel nor OS) is based on Unix.

3.) "Think of FreeBSD as a more challenging version of Linux. This operating system doesn't hold your hand, so you might learn a thing or two as you install it and the software you require. Even for a seasoned Linux veteran like me, FreeBSD can often be a head-scratcher."

-Challenging because it's *different than Linux*? FreeBSD doesn't hold your hand? What about , , , heck even ? Since the author didn't mention it, I'm going to assume he did not check the FreeBSD Handbook and his "seasoned Linux" experience has been using a Linux desktop for a couple years. Also, head-scratcher?! Being an experienced Debian user, I'd be scratching my head too if I just decided to use Gentoo on a whim. The trauma of hand-configuring the xorg.conf file was real.

Finally, contrary to the article's title, the author ended up not switching to FreeBSD.

-Clickbait.

I am all for more people exploring FreeBSD and Linux. They are great OSes but it is critical the information being reported is both accurate and consistent. For reference the article is linked below.

zdnet.com/article/freebsd-linu

0

Échec complet de la manif d'extrême droite organisée à Bruxelles, en face du Consulat général de France, appelant à la "Justice pour Quentin* et dénonçant les "antifas assassins". Moins de 20 personnes. Durée 8 minutes.

0
3
0
0
5
0
0

Crafted this nice ActivityPub profile page for my Fedify/indiekit AP implementation, this is obviously for browsers, AP server receive an AP representation of my profile
Screenshot below is Fedify 2.0 built in debugger

🔗 https://rmendes.net/notes/2026/02/22/e0491

0
0
1

Überschrift: "US Präsident fährt mit herunter gelassenen Hosen nach China".

Ich finde es bedenklich, dass wir in Zeiten leben, in denen ich nicht sicher sagen kann, ob das wörtlich gemeint oder sinnbildlich gesprochen ist.

0
0
0
0
0
0
0
0
0
11
0
0
2
0

Crafted this nice ActivityPub profile page for my Fedify/indiekit AP implementation, this is obviously for browsers, AP server receive an AP representation of my profile
Screenshot below is Fedify 2.0 built in debugger

🔗 https://rmendes.net/notes/2026/02/22/e0491

0

Ich denke, auf im Recht blicken wir derzeit falsch und, dass sie sich extrem schnell durchsetzen wird, aber nicht in Spruchkörpern.

Die zahlenmäßig allermeisten Rechtsnutzenden haben kein (bzw. nur 1) Staatsexamen. Es sind
- Rechtspfleger:innen
- Kostenbeamte
- Verwaltungsleute
- Servicepools

Meine Einschätzung wäre, dass aktuell 30% dieser Jobs und in ~2 Jahren 90% -im Durchschnitt (!)- von KI nicht mehr schlechter erledigt werden, als derzeit von Menschen (aber zu 20% der Lohnkosten).

0

Before creating and publishing FEDERATION.md for I wanted to understand what existing practice looked like across the Fediverse.

FEP-67ff describes the requirements of the FEDERATION.md file in loose terms and provides a non-normative template. I scraped the URLs of FEDERATION.md files from FEP-67ff itself and confirmed I could fetch them. The FEP listed 30 accessible projects (31 total, but one project—FIRM—does not appear to exist).

If a file had a section with the heading "Supported FEPs" per the non-normative template, I only looked there for supported FEPs. Otherwise I scanned the entire document.

Implemented FEPs, ranked by the number of implementations that attest support, are:

FEP   Name                                                        #
----  ---------------------------------------------------------  --
67ff  FEDERATION.md                                              18
f1d5  NodeInfo in Fediverse Software                             16
8b32  Object Integrity Proofs                                     7
044f  Consent-respecting quote posts                              7
2677  Identifying the Application Actor                           7
e232  Object Links                                                6
1b12  Group federation                                            6
3b86  Activity Intents                                            6
521a  Representing actor's public keys                            5
2c59  Discovery of a Webfinger address from an ActivityPub actor  5
7888  Demystifying the context property                           5
5feb  Search indexing consent for actors                          5
4adb  Dereferencing identifiers with webfinger                    4
d556  Server-Level Actor Discovery Using WebFinger                4
fb2a  Actor metadata                                              4
ef61  Portable Objects                                            4
8fcf  Followers collection synchronization across servers         4
844e  Capability discovery                                        4
7628  Move actor                                                  3
61cf  The OpenWebAuth Protocol                                    3
c390  Identity Proofs                                             3
400e  Publicly-appendable ActivityPub collections                 3
c0e0  Emoji reactions                                             3
0151  NodeInfo in Fediverse Software (2025 edition)               3
fffd  Proxy Objects                                               2
f228  Backfilling conversations                                   2
fe34  Origin-based security model                                 2
eb48  Hashtags                                                    2
171b  Conversation Containers                                     2
a5c5  Web Syndication Methods                                     2

There are obvious flaws in the methodology. Or maybe in the data. Only 18 out of the 30 projects I could access had a FEDERATION.md that attested FEDERATION.md support. Only 19 mentioned "FEDERATION.md". Only 21 mentioned "67ff". The remaining projects clearly did support FEP-67ff—the file itself was evidence. (FEDERATION.md is not meant to be machine readable—there's an issue about that).

It was more difficult to rank implemented federation protocols. I extracted keywords from documents with a  "Supported federation protocols and standards" section and created a dictionary of terms. If a file had a section with the heading "Supported federation protocols and standards", I only looked there. Otherwise I scanned the entire document.

Feature            #
----------------  --
activitypub       26
webfinger         24
http_signatures   21
nodeinfo          19
json_ld            2
ld_signatures      2
ostatus            2
authorized_fetch   1
atproto            1

If time allows, I'm going to try to rank these documents by "utility", though I haven't yet determined the exact metric. These documents clearly provide valuable information, but their lack of standardization makes them harder to analyze systematically.

0
0
1
0
0

Fedify 2.0.0 is here!

This is the biggest release in Fedify's history. Here are the highlights:

  • Modular architecture — The monolithic @fedify/fedify package has been broken up into focused, independent packages: @fedify/vocab, @fedify/vocab-runtime, @fedify/vocab-tools, @fedify/webfinger, and more. Smaller bundles, cleaner imports, and the ability to extend ActivityPub with custom vocabulary types.
  • Real-time debug dashboard — The new @fedify/debugger package gives you a live dashboard at /__debug__/ showing all your federation traffic: traces, activity details, signature verification, and correlated logs. Just wrap your Federation object and you're done.
  • ActivityPub relay support — First-class relay support via @fedify/relay and the fedify relay CLI command. Supports both Mastodon-style and LitePub-style relay protocols (FEP-ae0c).
  • Ordered message delivery — The new orderingKey option solves the “zombie post” problem where a Delete arrives before its Create. Activities sharing the same key are guaranteed to be delivered in FIFO order.
  • Permanent failure handlingsetOutboxPermanentFailureHandler() lets you react when a remote inbox returns 404 or 410, so you can clean up unreachable followers instead of retrying forever.

Other changes include content negotiation at the middleware level, @fedify/lint for shared linting rules, @fedify/create for quick project scaffolding, CLI config files, native Node.js/Bun CLI support, and many bug fixes.

This release includes significant contributions from Korea's OSSCA participants. Huge thanks to everyone involved!

This is a major release with breaking changes—please check the migration guide before upgrading.

Full release notes: https://github.com/fedify-dev/fedify/discussions/580

Fedify 2.0.0을 릴리스했습니다!

Fedify 역사상 가장 큰 릴리스입니다. 주요 변경 사항을 소개합니다:

  • 모듈형 아키텍처 — 기존의 단일 @fedify/fedify 패키지를 @fedify/vocab, @fedify/vocab-runtime, @fedify/vocab-tools, @fedify/webfinger 등 독립적인 패키지들로 분리했습니다. 번들 크기가 줄어들고, 임포트가 깔끔해지며, 커스텀 어휘 타입으로 ActivityPub을 확장할 수도 있습니다.
  • 실시간 디버그 대시보드 — 새로운 @fedify/debugger 패키지로 /__debug__/ 경로에 라이브 대시보드를 띄울 수 있습니다. 연합 트래픽의 트레이스, 액티비티 상세, 서명 검증, 로그까지 한눈에 확인할 수 있습니다. 기존 Federation 객체를 감싸기만 하면 됩니다.
  • ActivityPub 릴레이 지원@fedify/relay 패키지와 fedify relay CLI 명령어로 릴레이 서버를 바로 띄울 수 있습니다. Mastodon 방식과 LitePub 방식 모두 지원합니다(FEP-ae0c).
  • 순서 보장 메시지 전달 — 새로운 orderingKey 옵션으로 “좀비 포스트” 문제를 해결합니다. DeleteCreate보다 먼저 도착하는 문제가 더 이상 발생하지 않습니다. 같은 키를 공유하는 액티비티는 FIFO 순서가 보장됩니다.
  • 영구 전달 실패 처리setOutboxPermanentFailureHandler()로 원격 인박스가 404나 410을 반환할 때 대응할 수 있습니다. 도달 불가능한 팔로워를 정리하는 등의 처리가 가능합니다.

이 외에도 미들웨어 수준의 콘텐츠 협상, @fedify/lint, @fedify/create, CLI 설정 파일, 네이티브 Node.js/Bun CLI 지원, 다수의 버그 수정 등이 포함되어 있습니다.

이번 릴리스에는 한국 OSSCA (오픈소스 컨트리뷰션 아카데미) 참가자분들의 큰 기여가 담겨 있습니다. 참여해 주신 모든 분께 감사드립니다!

브레이킹 체인지가 포함된 메이저 릴리스입니다. 업그레이드 전에 마이그레이션 가이드를 꼭 확인해 주세요.

전체 릴리스 노트: https://github.com/fedify-dev/fedify/discussions/580

3
1
0

i often ask people to only reply to my posts in certain ways (like “please only reply if you find man hard to use”)

It’s because sometimes I get hundreds of replies a day and if folks don’t stay on topic then the replies get so repetitive that it’s hard for me to learn new information.

Really appreciate when people follow the prompts (which most of you do!). I’m posting a reminder because it’s been going a little less well recently than usual

0
0
1
0
0
1
1
1

Fedify 2.0.0 is here!

This is the biggest release in Fedify's history. Here are the highlights:

  • Modular architecture — The monolithic @fedify/fedify package has been broken up into focused, independent packages: @fedify/vocab, @fedify/vocab-runtime, @fedify/vocab-tools, @fedify/webfinger, and more. Smaller bundles, cleaner imports, and the ability to extend ActivityPub with custom vocabulary types.
  • Real-time debug dashboard — The new @fedify/debugger package gives you a live dashboard at /__debug__/ showing all your federation traffic: traces, activity details, signature verification, and correlated logs. Just wrap your Federation object and you're done.
  • ActivityPub relay support — First-class relay support via @fedify/relay and the fedify relay CLI command. Supports both Mastodon-style and LitePub-style relay protocols (FEP-ae0c).
  • Ordered message delivery — The new orderingKey option solves the “zombie post” problem where a Delete arrives before its Create. Activities sharing the same key are guaranteed to be delivered in FIFO order.
  • Permanent failure handlingsetOutboxPermanentFailureHandler() lets you react when a remote inbox returns 404 or 410, so you can clean up unreachable followers instead of retrying forever.

Other changes include content negotiation at the middleware level, @fedify/lint for shared linting rules, @fedify/create for quick project scaffolding, CLI config files, native Node.js/Bun CLI support, and many bug fixes.

This release includes significant contributions from Korea's OSSCA participants. Huge thanks to everyone involved!

This is a major release with breaking changes—please check the migration guide before upgrading.

Full release notes: https://github.com/fedify-dev/fedify/discussions/580

3
5
0

Ich denke, auf im Recht blicken wir derzeit falsch und, dass sie sich extrem schnell durchsetzen wird, aber nicht in Spruchkörpern.

Die zahlenmäßig allermeisten Rechtsnutzenden haben kein (bzw. nur 1) Staatsexamen. Es sind
- Rechtspfleger:innen
- Kostenbeamte
- Verwaltungsleute
- Servicepools

Meine Einschätzung wäre, dass aktuell 30% dieser Jobs und in ~2 Jahren 90% -im Durchschnitt (!)- von KI nicht mehr schlechter erledigt werden, als derzeit von Menschen (aber zu 20% der Lohnkosten).

0
0
1
1

Before creating and publishing FEDERATION.md for I wanted to understand what existing practice looked like across the Fediverse.

FEP-67ff describes the requirements of the FEDERATION.md file in loose terms and provides a non-normative template. I scraped the URLs of FEDERATION.md files from FEP-67ff itself and confirmed I could fetch them. The FEP listed 30 accessible projects (31 total, but one project—FIRM—does not appear to exist).

If a file had a section with the heading "Supported FEPs" per the non-normative template, I only looked there for supported FEPs. Otherwise I scanned the entire document.

Implemented FEPs, ranked by the number of implementations that attest support, are:

FEP   Name                                                        #
----  ---------------------------------------------------------  --
67ff  FEDERATION.md                                              18
f1d5  NodeInfo in Fediverse Software                             16
8b32  Object Integrity Proofs                                     7
044f  Consent-respecting quote posts                              7
2677  Identifying the Application Actor                           7
e232  Object Links                                                6
1b12  Group federation                                            6
3b86  Activity Intents                                            6
521a  Representing actor's public keys                            5
2c59  Discovery of a Webfinger address from an ActivityPub actor  5
7888  Demystifying the context property                           5
5feb  Search indexing consent for actors                          5
4adb  Dereferencing identifiers with webfinger                    4
d556  Server-Level Actor Discovery Using WebFinger                4
fb2a  Actor metadata                                              4
ef61  Portable Objects                                            4
8fcf  Followers collection synchronization across servers         4
844e  Capability discovery                                        4
7628  Move actor                                                  3
61cf  The OpenWebAuth Protocol                                    3
c390  Identity Proofs                                             3
400e  Publicly-appendable ActivityPub collections                 3
c0e0  Emoji reactions                                             3
0151  NodeInfo in Fediverse Software (2025 edition)               3
fffd  Proxy Objects                                               2
f228  Backfilling conversations                                   2
fe34  Origin-based security model                                 2
eb48  Hashtags                                                    2
171b  Conversation Containers                                     2
a5c5  Web Syndication Methods                                     2

There are obvious flaws in the methodology. Or maybe in the data. Only 18 out of the 30 projects I could access had a FEDERATION.md that attested FEDERATION.md support. Only 19 mentioned "FEDERATION.md". Only 21 mentioned "67ff". The remaining projects clearly did support FEP-67ff—the file itself was evidence. (FEDERATION.md is not meant to be machine readable—there's an issue about that).

It was more difficult to rank implemented federation protocols. I extracted keywords from documents with a  "Supported federation protocols and standards" section and created a dictionary of terms. If a file had a section with the heading "Supported federation protocols and standards", I only looked there. Otherwise I scanned the entire document.

Feature            #
----------------  --
activitypub       26
webfinger         24
http_signatures   21
nodeinfo          19
json_ld            2
ld_signatures      2
ostatus            2
authorized_fetch   1
atproto            1

If time allows, I'm going to try to rank these documents by "utility", though I haven't yet determined the exact metric. These documents clearly provide valuable information, but their lack of standardization makes them harder to analyze systematically.

0
1
0
1

Überschrift: "US Präsident fährt mit herunter gelassenen Hosen nach China".

Ich finde es bedenklich, dass wir in Zeiten leben, in denen ich nicht sicher sagen kann, ob das wörtlich gemeint oder sinnbildlich gesprochen ist.

0