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
0
0
0
1
0
0
0

매체의 성향을 막론하고 이런 기사가 나온다는 것은 뭔가 잘못되어도 아주 크게 잘못되었다는 걸 반증한다. 집은 살 수 있는 좋은 때를 잡아야 하는 그런게 아니다. 언제나 들어가서 살 수 있어야 한다.

RE: https://bsky.app/profile/did:plc:4sujqnbd47ey26qcvajqoxa2/post/3mfjm4bv2it2n

0
0
0
0
0
0

Wir werden immer wieder gefragt, ob wir unsere Server eigentlich auch selber nur mieten. Die Antwort ist ein klares Nein. Wir machen das tatsächlich alles selbst.

Das heißt auch, dass wir dann doch mal umziehen müssen. Mehr dazu und wie es in unseren Racks so aussieht erfahrt ihr in der aktuellen Folge Uberspace: Lower Decks:

podcast.uberspace.de/folge-8-d

0
2
0
0
0
50
0

이 분보다 더 심한 분 계시는데 정전기가 원래 악!!!!하고 끝난다면 그 분은 지속임 걍 전류가 흘러서 그분이랑 손 닿으면 그 분이 손 뗄 때까지 전기가 흐름 직장동료가 그분은 여기서 이럴게 아니라 친환경 대체에너지 뭐시기로 인체실험 받으러 가야한다고 함

RE: https://bsky.app/profile/did:plc:l4woljooiwedcgowo7u3fbdt/post/3mfldqfzedk2x

0
0
0
0
1
0

In Steglitz steppt der Bär - Wir sagen Werbemonitoren den Kampf an!

Du willst mit uns Werbung gegen Werbung machen?

Komm in deine Berlin Werbefrei - Kiezgruppe und mach mit bei unseren Plakat-Aktionen!
Oder lass eine Unterschrift da.

👉 Unterstütze das Volksbegehren „Berlin Werbefrei“ für weniger Werbung im öffentlichen Raum Berlins.
➡️ Alle Infos & Unterschriften: berlin-werbefrei.de/

0
0
0
0
0
0
0
0
0
0
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

4
6
0

Wir werden immer wieder gefragt, ob wir unsere Server eigentlich auch selber nur mieten. Die Antwort ist ein klares Nein. Wir machen das tatsächlich alles selbst.

Das heißt auch, dass wir dann doch mal umziehen müssen. Mehr dazu und wie es in unseren Racks so aussieht erfahrt ihr in der aktuellen Folge Uberspace: Lower Decks:

podcast.uberspace.de/folge-8-d

0
2
0
0
0
0
0
0
0
0
0
0

A couple days ago, I got a DM from a user. I happily replied and sent a follow request—but the Accept never came back, even though they hadn't enabled manuallyApprovesFollowers. My DM reply probably never arrived either. Classic interop bug.

I checked out the Bonfire source and dug in. Turns out Bonfire hasn't implemented RFC 9421 yet, so it was silently discarding any activity signed with it. That alone would be workable, except for one more issue: Bonfire was responding 200 OK even when signature verification failed, instead of 401 Unauthorized.

This matters because Fedify implements a double-knocking mechanism—if a request signed with RFC 9421 fails, it retries with the older draft cavage signature. But since Bonfire returned 200 OK on the failed first knock, had no reason to send a second one.

I filed two issues on the Bonfire repo—one requesting RFC 9421 support, and one about returning 401 on invalid signatures. For the latter, I also sent a PR, which got merged pretty quickly: bonfire-networks/activity_pub#9.

That said, individual Bonfire instances won't pick up the fix until they actually deploy it. So in the meantime, I patched Hollo and Hackers' Pub to use draft-cavage-http-signatures-12 as the firstKnock, so Bonfire instances can at least understand the first request.

One last thing: Fedify caches whether a given server supports RFC 9421, and the Bonfire servers I'd already talked to were cached as “supports RFC 9421”—because they'd been returning 200 OK. I had to manually clear that cache on both hollo.social and hackers.pub before everything finally worked.

After all that, the mutual follow went through and my DM reply landed. Worth it.

0
3
0
0
0