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

any TU Berlin students here? there's a brand new Open Source Hardware seminar this semester (MNT will also make an appearance if it happens) and so far only 3 students registered! they need at least 5 to make it work, so if you're interested or know potential candidates at TU, spread the word: tu.berlin/qw/studium-lehre/leh

0
0
0
0

As we approach the release of Bonfire 1.0, this isn’t your typical launch announcement. Instead, it’s a moment to reflect on how we’ve built Bonfire, a roadmap of values, methods, and intentions – and an invitation to define what comes next.

In a world of “move fast and break things,” we’ve chosen a different tempo — one rooted in care, deep listening, and collective stewardship...

📣 Read our latest blog post: bonfirenetworks.org/posts/slow

0
0
0

비퀴어 청년 남성분들 제일 신기한점 억울한 건 되게 많은데 그럼 님을 글케 힘들게 하는 이 사회의 문제점을 진지하게 말해 보라고 하면 갑자기 억울징징은 어디가고 기득권 팬보이 모드가 돼서 AI 쓰는 게 기업 입장에선 좋긴 하다 한국 남자면 군대 가는 게 당연한 거다 복지한다고 무조건 좋은 게 아니다 이럼 하지만 넌 기업가도 아니고 장교도 아니고 나랏님도 아니잖아...

0

We're excited to announce that we've implemented RFC 9421 (HTTP Message Signatures) in , complete with our double-knocking mechanism to maintain backward compatibility with the draft cavage version.

This implementation includes both signature generation and verification, meaning is used when both sending and receiving activities. While we haven't merged the RFC 9421 implementation branch yet, we're currently conducting interoperability tests with development versions of Mastodon and other implementations. Once these tests confirm compatibility, we'll proceed with the merge.

As noted in the attached docs, although RFC 9421 is the final and official standard for HTTP Signatures, the draft cavage version remains widely used across the . Our double-knocking mechanism ensures maximum compatibility by trying the RFC 9421 version first, then falling back to draft cavage if needed.

Currently, we support RSA-PKCS-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

HTTP Message Signatures

This API is available since Fedify 1.6.0.

RFC 9421, also known as HTTP Message Signatures, is the final revision of the HTTP Signatures specification. Although it is the official standard, it is not widely used in the fediverse yet. As of May 2025, major ActivityPub implementations, such as Mastodon, et al., still rely on the draft cavage version of HTTP Signatures for signing portable activities.

Fedify automatically signs activities with the sender's private key if the actor keys dispatcher is set and the actor has any RSA-PKCS#1-v1.5 key pair. If there are multiple key pairs, Fedify selects the first RSA-PKCS#1-v1.5 key pair among them.

NOTE

Although HTTP Message Signatures support other than RSA-PKCS#1-v1.5, Fedify currently supports only RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures. This limitation will be lifted in the future releases.Double-knocking HTTP Signatures

This API is available since Fedify 1.6.0.

As you read above, there are two revisions of HTTP Signatures: the draft cavage version and the RFC 9421 version. The draft cavage version is declared as obsolete, but it is still widely used in the fediverse, and many ActivityPub implementations still rely on it. On the other hand, the RFC 9421 version is the official standard, but it is not widely used yet.

To support both versions of HTTP Signatures, Fedify uses the double-knocking mechanism: trying one version, then falling back to another if rejected. If it's the first encounter with the recipient server, Fedify tries the RFC 9421 version first, and if it fails, it falls back to the draft cavage version. If the recipient server accepts the RFC 9421 version, Fedify remembers it and uses the RFC 9421 version for the next time. If the recipient server rejects the RFC 9421 version, Fedify falls back to the draft cavage version and remembers it for the next time.
1
0
1
1
0
1
0
0
0
1
0
0
0
1
0
0
0
0
1
0
0
0
0

引用 < x.com/tkatsumi06j/status/19206 >
----
🇮🇳❌🇵🇰印パ間の戦闘が本格化するなか、🇮🇳インド人記者がムスリムの🇮🇳インド人少年にインタビューするも、“期待通りの答え“を得られず苛立ちを隠せなくなってつい「誰がそんな考え方を教えた?」と訊いてしまった時の少年の返し。プライスレス。
x.com/GozukaraFurkan/status/19

記者「パキスタンよ永遠なれ?」
少年「永遠なれ」
記者「恥ずかしくないのか?」
少年「なぜ恥ずかしがる必要が?」
記者「パキスタンは滅ぼされるべきではない?」
少年「は?もちろん滅ぼされるべきではないよ」
記者「インドよ永遠なれ。イエスかノーか?」
少年「イエス」
記者「パキスタンよ永遠なれ。イエスかノーか?」
少年「イエス。どの国もその国のスペースで永遠なればいい。あなたも自分のスペースで暮らしているんだろう?」
記者「名前は?」
少年「ケイフだ」
記者「フルネームは?」
少年「ムハマド・ケイフだ」
記者「出身は?」
少年「ビハールから」
記者「インドに住みながらも、パキスタンを支持しているってことを少しも恥ずかしいとは思わないのか?…

なぜパキスタンを滅ぼしてはいけない?」

少年「あなたはそんなことを大事として報じていて、恥ずかしくないのか?そんなことをニュースにしていて、恥ずかしくないのか?ヒンズーとムスリムの問題にして、そこらじゅうに言いふらして。なぜインドを支持するかって?その前にまず答えて。あちらにも人びとがいる。こちらにも。向こうにもムスリムがいる。ヒンズーがいる。みな人間だ。なぜ“皆殺し“にする必要がある?教えてくれよ?なぜ皆滅ぼす必要がある?教えてくれよ?誰にも生きる権利がある。誰にでもだ。ならなぜ彼らを滅ぼす必要が?」

記者「君はパキスタンを支持するのか?」
少年「向こうに行ってあなたが誰かに殺されたとする。それで全ておしまいか?」
記者「君はパキスタンを支持するのか?」
少年「支持するよ」
記者「君はインド人ではないのか?」
少年「インド人だよ。あなたはあの国を滅ぼせという。滅ぼせと。けど、どこも人が住んでいるんだよ。」
記者「これだけ訊かせてくれ。誰がそんな考え方を教えた?」
少年「自分の頭だよ。決まってるだろ!」

0

My 25 years of palaeoart chronology...

Here's my 2023 Western Interior Seaway illustration, from DINOSAUR BEHAVIOUR, by Prof Benton (Princeton University Press). It features an Edmontosaurus carcass attracting attention from birds, pterosaurs, bony fish, sharks, marine reptiles, and ammonites.

0

引用 < x.com/tkatsumi06j/status/19206 >
----
🇮🇳❌🇵🇰印パ間の戦闘が本格化するなか、🇮🇳インド人記者がムスリムの🇮🇳インド人少年にインタビューするも、“期待通りの答え“を得られず苛立ちを隠せなくなってつい「誰がそんな考え方を教えた?」と訊いてしまった時の少年の返し。プライスレス。
x.com/GozukaraFurkan/status/19

記者「パキスタンよ永遠なれ?」
少年「永遠なれ」
記者「恥ずかしくないのか?」
少年「なぜ恥ずかしがる必要が?」
記者「パキスタンは滅ぼされるべきではない?」
少年「は?もちろん滅ぼされるべきではないよ」
記者「インドよ永遠なれ。イエスかノーか?」
少年「イエス」
記者「パキスタンよ永遠なれ。イエスかノーか?」
少年「イエス。どの国もその国のスペースで永遠なればいい。あなたも自分のスペースで暮らしているんだろう?」
記者「名前は?」
少年「ケイフだ」
記者「フルネームは?」
少年「ムハマド・ケイフだ」
記者「出身は?」
少年「ビハールから」
記者「インドに住みながらも、パキスタンを支持しているってことを少しも恥ずかしいとは思わないのか?…

0
0
0
0

@nogajunnogajun🍉

の 「 」。午後繰り返し聴いてます。イヤーワームになってきました。KPOPという範疇に留まらず、質のいいポップソング。長く待たされたけど、満足できる出来です。

単純なコード進行で覚えやいメロディ。ウクレレでやりやすそう。あとで挑戦してみます。

MVでなく、映像なしで音だけで聴くとラップ部分がなくてもいい感じ。Fifty Fiftyの「Cupid」では英語版はラップ部分は演奏だけになっていたはず。英語圏の市場を狙うなら、ラップはなしがいいのかな。本家のラッパーには届かないから。

New Jeansの新作が期待できない今年の夏、これが夏のランニングのパワーソングになりそう。

昨夏は、土岐麻子さんゲストのこの曲、GOOD BYE APRIL「ふたりのBGM feat. 土岐麻子」
youtube.com/watch?v=uSHIGejNnxg

0
1

Looking for implementations with support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

  • has implemented RFC 9421 (even in a development branch)
  • is currently implementing it
  • has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into 's main branch.

Any leads or connections would be greatly appreciated! 🙏

1
5
1

引用 < x.com/tkatsumi06j/status/19206 >
----
🇮🇳❌🇵🇰印パ間の戦闘が本格化するなか、🇮🇳インド人記者がムスリムの🇮🇳インド人少年にインタビューするも、“期待通りの答え“を得られず苛立ちを隠せなくなってつい「誰がそんな考え方を教えた?」と訊いてしまった時の少年の返し。プライスレス。
x.com/GozukaraFurkan/status/19

記者「パキスタンよ永遠なれ?」
少年「永遠なれ」
記者「恥ずかしくないのか?」
少年「なぜ恥ずかしがる必要が?」
記者「パキスタンは滅ぼされるべきではない?」
少年「は?もちろん滅ぼされるべきではないよ」
記者「インドよ永遠なれ。イエスかノーか?」
少年「イエス」
記者「パキスタンよ永遠なれ。イエスかノーか?」
少年「イエス。どの国もその国のスペースで永遠なればいい。あなたも自分のスペースで暮らしているんだろう?」
記者「名前は?」
少年「ケイフだ」
記者「フルネームは?」
少年「ムハマド・ケイフだ」
記者「出身は?」
少年「ビハールから」
記者「インドに住みながらも、パキスタンを支持しているってことを少しも恥ずかしいとは思わないのか?…

0
0
0
0
1
1
0

예전부터 생각하던 건데, git reset --hard를 인자 없이 쓰면 git stash로 동작하거나, 아니면 적어도 인자 없이 썼을 때 오류가 나게끔 설정할 수 있었으면 좋겠다. 별 생각 없이 날려도 괜찮겠지 싶어서 git reset --hard 쳤다가 몇 분 뒤에 후회하는 경우가 종종 있다.

2

We're excited to announce that we've implemented RFC 9421 (HTTP Message Signatures) in , complete with our double-knocking mechanism to maintain backward compatibility with the draft cavage version.

This implementation includes both signature generation and verification, meaning is used when both sending and receiving activities. While we haven't merged the RFC 9421 implementation branch yet, we're currently conducting interoperability tests with development versions of Mastodon and other implementations. Once these tests confirm compatibility, we'll proceed with the merge.

As noted in the attached docs, although RFC 9421 is the final and official standard for HTTP Signatures, the draft cavage version remains widely used across the . Our double-knocking mechanism ensures maximum compatibility by trying the RFC 9421 version first, then falling back to draft cavage if needed.

Currently, we support RSA-PKCS-v1.5 key pairs for generating HTTP Message Signatures, with plans to expand to other signature types in future releases.

We look forward to contributing to a more standardized and secure fediverse!

HTTP Message Signatures

This API is available since Fedify 1.6.0.

RFC 9421, also known as HTTP Message Signatures, is the final revision of the HTTP Signatures specification. Although it is the official standard, it is not widely used in the fediverse yet. As of May 2025, major ActivityPub implementations, such as Mastodon, et al., still rely on the draft cavage version of HTTP Signatures for signing portable activities.

Fedify automatically signs activities with the sender's private key if the actor keys dispatcher is set and the actor has any RSA-PKCS#1-v1.5 key pair. If there are multiple key pairs, Fedify selects the first RSA-PKCS#1-v1.5 key pair among them.

NOTE

Although HTTP Message Signatures support other than RSA-PKCS#1-v1.5, Fedify currently supports only RSA-PKCS#1-v1.5 key pairs for generating HTTP Message Signatures. This limitation will be lifted in the future releases.Double-knocking HTTP Signatures

This API is available since Fedify 1.6.0.

As you read above, there are two revisions of HTTP Signatures: the draft cavage version and the RFC 9421 version. The draft cavage version is declared as obsolete, but it is still widely used in the fediverse, and many ActivityPub implementations still rely on it. On the other hand, the RFC 9421 version is the official standard, but it is not widely used yet.

To support both versions of HTTP Signatures, Fedify uses the double-knocking mechanism: trying one version, then falling back to another if rejected. If it's the first encounter with the recipient server, Fedify tries the RFC 9421 version first, and if it fails, it falls back to the draft cavage version. If the recipient server accepts the RFC 9421 version, Fedify remembers it and uses the RFC 9421 version for the next time. If the recipient server rejects the RFC 9421 version, Fedify falls back to the draft cavage version and remembers it for the next time.
1
0
1

Looking for implementations with support! 🔍

As mentioned in the Fedify announcement below, I've implemented RFC 9421 (HTTP Message Signatures) and need to verify its interoperability with other ActivityPub implementations.

The challenge is that most major ActivityPub projects don't seem to have full RFC 9421 implementations in production yet. If you're working on an ActivityPub project that:

  • has implemented RFC 9421 (even in a development branch)
  • is currently implementing it
  • has plans to implement it soon

Please reach out! I'd love to collaborate on interoperability testing to ensure our implementations work properly with each other before merging this into 's main branch.

Any leads or connections would be greatly appreciated! 🙏

1
5
1
0
1

Das Silicon Valley hat sich mit Donald Trump verbündet. Für Europa ist das die Gelegenheit, die Abhängigkeit von der US-Tech-Branche zu beenden und digital souverän zu werden.

Auf der zeigt der Tech-Kritiker und Podcast-Moderator Paris Marx (@parismarx), wie eine europäische Tech-Entwicklung aussehen könnte, bei der die Öffentlichkeit Vorrang vor Investor*innen hat.

➡️ re-publica.com/de/news/rp25-sp

Foto von Paris Marx. Marx steht auf der re:publica Bühne und trägt ein Mikrophon sowie kurze Haare.Das Visual zeigt den Titel der Session "Reject US Tech. Embrace Digital Sovereignty." An den Seiten sind grafische Elemente aus dem diesjährigen Logo GenXYZ zu sehen. Darunter ist das Datum sowie die Location der republica 25 platziert.
0
0
0
0