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

イギリスの規制法でWikipediaが「破壊される」としてウィキメディア財団が法的措置に踏み切る - GIGAZINE
gigazine.net/news/20250509-wik

『Wikipediaが最も規制が厳しい「カテゴリー1」に分類される可能性が濃厚に』

『「カテゴリー1」は、公共への影響が広範に及ぶ大規模な商用プラットフォームやソーシャルメディアを念頭に置いた分類で、該当する企業はユーザーの身元確認や、匿名ユーザーによる記事の投稿のブロックなど、負担の大きいコンプライアンス規定が義務付けられます。

もし、これらが…適用された場合、Wikipediaのボランティア編集者の安全やプライバシーが損なわれ、本来はコンテンツの保護や改善に充てられるべき資源が対応に費やされることにより、記事が改ざんされたり破壊されたりするおそれがあると、ウィキメディア財団は主張』

『Wikipediaのトップページにある「今日の一枚」をユーザーが選ぶことさえ、カテゴリー1の分類要件のひとつである「コンテンツ推奨システム」に該当するおそれがある』

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

【5/11 文学フリマ東京40 出店!】ブース: O-13

『令和6年令和めぐり』
まだ始まって間もない新元号「令和」ですが、すでに街には「令和」と名の付く地名やスポットが生まれています。そんな「令和」な場所5か所を訪問した記録です。

『令和6年令和めぐり』表紙
0
0

【5/11 文学フリマ東京40 出店!】ブース: O-13

『令和6年令和めぐり』
まだ始まって間もない新元号「令和」ですが、すでに街には「令和」と名の付く地名やスポットが生まれています。そんな「令和」な場所5か所を訪問した記録です。

『令和6年令和めぐり』表紙
0
0
0
0
1
0

Fedify에 드디어 RFC 9421을 얼추 구현했고, 이제 상호운용성 테스트를 위해 Mastodon의 특정 브랜치를 실제로 인스턴스로 띄워서 액티비티를 송수신해봐야 한다. 그런데 Mastodon 띄우기가 너무나 귀찮다… (Mastodon 띄우기 귀찮아서 ActivityPub 개발 시작한 사람.)

3
0

Fedify에 드디어 RFC 9421을 얼추 구현했고, 이제 상호운용성 테스트를 위해 Mastodon의 특정 브랜치를 실제로 인스턴스로 띄워서 액티비티를 송수신해봐야 한다. 그런데 Mastodon 띄우기가 너무나 귀찮다… (Mastodon 띄우기 귀찮아서 ActivityPub 개발 시작한 사람.)

3

駅で面白そうって思うアニメの広告見たけど名前忘れたのでその為に再度出かける必要がある。

Twitterとかで時系列検索したけど最近設置された広告なのかTweetしている人を確認できていない・・

どうしようかな~。

0

Hi friends! It's Thursday and it is that time: I'm putting together this week's Installer and want to know everything you're into. What are you playing / watching / reading / listening to / poking with a stick this week? Tell me so I can tell everyone! (And subscribe to Installer!)

0
0
0
0
0

Wrote up an to get feedback on adding support to https://apply.coop soon after we launch. If anyone else has feedback it is certainly welcome! It does require a Codeberg account to comment, but we're open to email feedback as well.

I am not an ActivityPub expert so a lot of this was learning while planning this out.

https://codeberg.org/limeleaf/apply.coop/issues/213


0
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

After I published a recent article where I showed how to mitigate an accidental DDoS after enabling ActivityPub for WordPress with the Surge plugin, I found an optimization for improved cache handling. Out of the box, there’s a problem with the default configuration since Surge ignores the Accept header.

[…]

epiph.yt/en/blog/2025/optimize

0
1

Fedify에 드디어 RFC 9421을 얼추 구현했고, 이제 상호운용성 테스트를 위해 Mastodon의 특정 브랜치를 실제로 인스턴스로 띄워서 액티비티를 송수신해봐야 한다. 그런데 Mastodon 띄우기가 너무나 귀찮다… (Mastodon 띄우기 귀찮아서 ActivityPub 개발 시작한 사람.)

3
0
38
0
0

【5/11 文学フリマ東京40 出店!】ブース: O-13

『紅白看板マルわかり図鑑DX』
かつて存在した金融業者「マルフク」の看板を追いかけている著者が、看板の細かすぎるバリエーションや珍しいタイプの看板を解説。46ページの大ボリューム!

『紅白看板マルわかり図鑑DX』表紙 モナコ広告
0
0
0
0

【5/11 文学フリマ東京40 出店!】ブース: O-13

『紅白看板マルわかり図鑑DX』
かつて存在した金融業者「マルフク」の看板を追いかけている著者が、看板の細かすぎるバリエーションや珍しいタイプの看板を解説。46ページの大ボリューム!

『紅白看板マルわかり図鑑DX』表紙 モナコ広告
0
1

세계화 시대에는 먼 나라 전쟁도 가까운 삶에 영향을 준다. 유럽이 점점 우리에게서 멀어지고 있다. 러시아 영공 통과가 가능하던 시절 서울에서 파리까지 편도로 약 11시간이 걸렸다. 러시아를 통과하지 못해 노선이 남쪽으로 우회하기 시작했는데 그 남쪽으로도 아프간, 시리아, 레바논, 이스라엘을 피해야 한다. 결국 13~14시간까지 늘어났다. 인도-파키스탄 경계를 지나칠 수 없게 되면 또 한참 남쪽으로 돌게 된다. 이러다간 두바이 환승이 필수가 되거나 소련 시절의 앵커리지 북극항로가 되돌아오는 수가 있다.

RE: https://bsky.app/profile/did:plc:vxgwb2wg74hcpmfjcmwm7dkt/post/3loqb6o55b222

0
1
1

In Moscow, Chinese president Xi is celebrating the “Victory Day” sitting right next to Putin and looking at the deadly drones Putin is using to kill civilians in Ukraine.

Every citizen of the free world: Chose something better than “made in China”.

Xi next to Putin.The Russian version of the Shahed-136 drone displayed on a number of trucks.
0
0
0
1

세계화 시대에는 먼 나라 전쟁도 가까운 삶에 영향을 준다. 유럽이 점점 우리에게서 멀어지고 있다. 러시아 영공 통과가 가능하던 시절 서울에서 파리까지 편도로 약 11시간이 걸렸다. 러시아를 통과하지 못해 노선이 남쪽으로 우회하기 시작했는데 그 남쪽으로도 아프간, 시리아, 레바논, 이스라엘을 피해야 한다. 결국 13~14시간까지 늘어났다. 인도-파키스탄 경계를 지나칠 수 없게 되면 또 한참 남쪽으로 돌게 된다. 이러다간 두바이 환승이 필수가 되거나 소련 시절의 앵커리지 북극항로가 되돌아오는 수가 있다.

RE: https://bsky.app/profile/did:plc:vxgwb2wg74hcpmfjcmwm7dkt/post/3loqb6o55b222

0
1
1
1

정치얘기를 뭐라고 하든 욕먹을 것 같긴 한데 현재진행형으로 광장을 배신하고 있는 민주당도 싫지만 "윤석열이 되면 왜 안되는데요"의 정의당(새 정당명이 뭐더라)도 별로다 그래도 내란의힘에 표를 줄 수는 없으니까 어쨌든 둘 중 하나를 골라야 되는데..... 마음을 정하기가 힘들다

0

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

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

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

引用 < x.com/tkatsumi06j/status/19207 >
----
この動画、反応してるのは日本人やムスリムだけではありません。インスタでIndian boy mediaで検索するといくつもの投稿に物凄い反響があります。ほとんどがポジティブなコメントで誘導的なメディアに批判的です。全世界がこの14歳のインド人のムスリム少年の毅然とした姿勢に感銘を受けているのです。

パキスタンもインドも皆殺しにされるべきではないとメディアのインタビューに答える少年を "indian boy media" で検索した結果表示された多数の動画へのリンク画像
0
0