What is Hackers' Pub?

おはぎ

Human history:

1. We invented gods to explain complexity
2. We invented markets to manage complexity
3. We invented algorithms to outsource complexity

And now no one knows who’s in charge.

こっちは近所のスーパーに並んでたOhagiとPeanut Butter Mochi

こっちは近所のスーパーに並んでたOhagiとPeanut Butter Mochi

And here it is! 🌍☀️

Already available at https://murena.com

@angyeong_love@kurry.social오너님 @hillside@kurry.social힐씨 님!
리퀘스트가 도착했어요!

https://soundcloud.com/ivadenibel/shine

We are pleased to announce the release of #Fedify 1.7.0. This release was expedited at the request of the Ghost team, who are actively using Fedify for their #ActivityPub implementation. As a result, several features originally planned for this version have been moved to Fedify 1.8.0 to ensure timely delivery of the most critical improvements.

This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.

Native retry mechanism support

This release introduces support for native retry mechanisms in message queue backends. The new MessageQueue.nativeRetrial property allows queue implementations to indicate whether they provide built-in retry functionality, enabling Fedify to optimize its retry behavior accordingly.

When nativeRetrial is set to true, Fedify will delegate retry handling to the queue backend rather than implementing its own retry logic. This approach reduces overhead and leverages the proven retry mechanisms of established queue systems.

Current implementations with native retry support include:

• DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
• WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
• AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Alongside Fedify 1.7.0, we have also released @fedify/amqp 0.3.0. This release adds the nativeRetrial option to AmqpMessageQueueOptions, enabling you to leverage your AMQP broker's built-in retry mechanisms. When enabled, this option allows the AMQP broker to handle message retries according to its configured policies, rather than relying on Fedify's internal retry logic.

Configurable double-knocking

The new FederationOptions.firstKnock option provides control over the HTTP Signatures specification used for the initial signature attempt when communicating with previously unknown servers.

Previously, the first knock for newly encountered servers always used RFC 9421 (HTTP Message Signatures), falling back to draft-cavage-http-signatures-12 if needed. With this release, you can now configure which specification to use for the first knock when communicating with unknown servers, with RFC 9421 remaining the default.

Summary

This release maintains Fedify's commitment to reliability and compatibility while laying the groundwork for more efficient message processing. The native retry mechanism support will particularly benefit applications using queue backends with sophisticated retry capabilities, while the double-knocking mechanism addresses real-world compatibility challenges in the ActivityPub ecosystem.

For detailed technical information about these changes, please refer to the changelog in the repository.

#fedidev #fediverse

わたし自身が当事者です
自分が過去に楽しく遊ばせてもらってたサーバーを離れるきっかけの一因が、HDML診断という診断メーカーです
旧Twitterで「俺、HDMLかもしれん……」というものにこじつけた診断ですね
もちろん、正しくはADHDです

この診断で遊ぶのは良くないとLTLで発言して「自分は当事者だが、楽しく遊んでいる(だから水を差すな)」とかなりつよめの、また多数のバッシングを受けました

違うんだ、と言いたくても、その時は言葉が出ませんでした

우리 탈출 후 꿀창고 턴 곰 두마리 ㅋㅋ

​​←もしかして​​だけでなく藍紫色(シアン ​​とほぼ補色)の​​も掛けてるの？

💬 Did you know we support over 60 languages in our vector map labels?

📝 Customizing how each element is displayed couldn't be simpler.

👇 Learn how.

https://docs.stadiamaps.com/tutorials/changing-the-map-label-language/?utm_campaign=tutorial_customize_language&utm_source=mastodon&utm_medium=social

#maps #mapping
https://docs.stadiamaps.com/tutorials/changing-the-map-label-language/?utm_campaign=tutorial_customize_language&utm_source=mastodon&utm_medium=social

우리 탈출 후 꿀창고 턴 곰 두마리 ㅋㅋ

分別して捨てる仕組みは必要だと思うけど、燃えるゴミとして捨てる人は一定数出そうな気がする

リチウムイオン電池 発火事故や火災相次ぎ自治体に適切な処分推進を通知 総務省 | NHK | 総務省 : 👀
---
https://www3.nhk.or.jp/news/html/20250625/k10014844131000.html

カラオケいいなカラオケ

ささげちゃんのしっぽながー！

Accessibility in Design Systems https://www.voorhoede.nl/en/blog/accessibility-in-design-systems/

Selfish reasons for building accessible UIs https://nolanlawson.com/2025/06/16/selfish-reasons-for-building-accessible-uis/

CSS Cascade Layers Vs. BEM Vs. Utility Classes: Specificity Control — Smashing Magazine https://www.smashingmagazine.com/2025/06/css-cascade-layers-bem-utility-classes-specificity-control/

A guide to Scroll-driven Animations with just CSS https://webkit.org/blog/17101/a-guide-to-scroll-driven-animations-with-just-css/

Color Everything in CSS | CSS-Tricks https://css-tricks.com/color-everything-in-css/

CSS Color Functions | CSS-Tricks https://css-tricks.com/css-color-functions/

!?

#こじまささげ #cat #特に意味をなさない猫の計測 #measure_the_cat

오늘 6.25구나

"Trapping AI" – Slight Update! 🌀

Activity in the "Trapping AI" project is accelerating: in just under a month, over 26 million requests have hit our tarpit URLs 🕳️. Vast volumes of meaningless content were devoured by AI crawlers — ruthless digital leeches that relentlessly scour and pillage the web, leaving no data untouched.

In the coming days, we’ll roll out a new layer of complexity — amplifying both the intensity and offensiveness of our approach. This escalation builds on fakejpeg, a tool developed by @pengfoldAlun Jones.

🖼️ fakejpeg generates fake JPEGs on the fly. You "train" it with a collection of existing JPEGs, and once trained, it can produce an arbitrary number of things that look like real JPEGs — perfect for feeding aggressive web crawlers junk 🗑️.

Explore fakejpeg: https://github.com/gw1urf/fakejpeg

Learn more about "Trapping AI": https://algorithmic-sabotage.github.io/asrg/trapping-ai/#expanding-the-offensiveness

See the tarpit in action: https://content.asrg.site/

Just a simple #Fact for #Today and, in fact, any other day. 🤣

#Memes #Microsoft #MicrosoftTeams #Windows

서울시가 침수 피해에 취약한 반지하 주택을 없애나가기로 했으나 지난 3년간 1만8천 가구를 줄이는 데 그쳤습니다. 여전히 21만9천여 가구는 반지하에 살고 있습니다.

또 장마철인데…서울엔 여전히 21만여 가구가 반지하에 ...

(1/2)

"And even our terms 'Server' Or 'Instance' make sense in an engineering flowchart but why in all that is holy would we foist those onto users to pretend to understand? At the very least we should talk about new folks joining a 'server community' of fellow users."

@tchambersTim Chambers, 2025

https://www.timothychambers.net/2025/06/18/113327.html

So much for "server" making more sense to newbies than "instance". I followed the herd on this usage, even though I questioned the wisdom, given how overloaded the term "server" is.

てすと
ですと

#こじまささげ #cat #特に意味をなさない猫の計測 #measure_the_cat

서울시가 침수 피해에 취약한 반지하 주택을 없애나가기로 했으나 지난 3년간 1만8천 가구를 줄이는 데 그쳤습니다. 여전히 21만9천여 가구는 반지하에 살고 있습니다.

또 장마철인데…서울엔 여전히 21만여 가구가 반지하에 ...

​​

On this day in 1978, the rainbow flag first flew as a symbol of pride. It was raised at San Francisco Gay Freedom Day.

current status ❯ git commit -am 'wip' --no-verify

With a name like "Bunker Buster" you had to know it's not. Any parent should know this. Looking at you "Huggies."

으어...

동거인 시점

부트캠프의 함정, 오버엔지니어링 https://subokim.wordpress.com/2025/06/20/overengineering/

串焼き10本
活きあじ x2
バリバリキャベツ
ぶったたききゅうり
ハムカツ
若鶏の唐揚げ
ニンニクの芽と砂肝ガーリック炒め

👋 Everyone: see what you think:

The Seven Deadly #Fediverse UX Sins Part 2: The Road To Redemption: https://www.timothychambers.net/2025/06/24/the-seven-deadly-fediverse-ux.html

Don't claim that these are final answers - but hope they help continue constructive motion to final answers!

cc: @renchapRenaud Chaput @dansup
@cheeaunChee Aun 🤔 @scottjenson @newsmastNewsmast Foundation @andypiper @ricmacRichard MacManus @evanEvan Prodromou @laurenshof @pfefferle @fediversenews #fedidev #mastodev @timbray

베스트샵에서 산 진공청소기 씽큐 앱으로 언제 오는지 배송추적이 되는 것 같았는데 갑자기 조회가 안되고 베스트샵 직원한테서 전화가 오더니 배송이 많이 밀렸대… 이것참큰일이군~

お狐様 #illustration #oc

Been horrifying teammates by referring to undocumented information that's held only in people's heads as "locked in meat storage".

Please use this with your teams/projects and report back on how they like it?

Die Regierung plant gerade ein erstes Rettungspaket für Gasheizer.

Einen Heizrabatt. Nur heißt er nicht so.

Wie er finanziert wird, ist perfide 🧵

就目前的就业形势来看，毕业典礼属于是丧事喜办了。#抄

We are pleased to announce the release of #Fedify 1.7.0. This release was expedited at the request of the Ghost team, who are actively using Fedify for their #ActivityPub implementation. As a result, several features originally planned for this version have been moved to Fedify 1.8.0 to ensure timely delivery of the most critical improvements.

This release focuses on enhancing message queue functionality and improving compatibility with ActivityPub servers through refined HTTP signature handling.

Native retry mechanism support

This release introduces support for native retry mechanisms in message queue backends. The new MessageQueue.nativeRetrial property allows queue implementations to indicate whether they provide built-in retry functionality, enabling Fedify to optimize its retry behavior accordingly.

When nativeRetrial is set to true, Fedify will delegate retry handling to the queue backend rather than implementing its own retry logic. This approach reduces overhead and leverages the proven retry mechanisms of established queue systems.

Current implementations with native retry support include:

• DenoKvMessageQueue — utilizes Deno KV's automatic retry with exponential backoff
• WorkersMessageQueue — leverages Cloudflare Queues' automatic retry and dead-letter queue features
• AmqpMessageQueue — can now be configured to use AMQP broker's native retry mechanisms

The InProcessMessageQueue continues to use Fedify's internal retry mechanism, while ParallelMessageQueue inherits the retry behavior from its wrapped queue.

AMQP message queue improvements

Alongside Fedify 1.7.0, we have also released @fedify/amqp 0.3.0. This release adds the nativeRetrial option to AmqpMessageQueueOptions, enabling you to leverage your AMQP broker's built-in retry mechanisms. When enabled, this option allows the AMQP broker to handle message retries according to its configured policies, rather than relying on Fedify's internal retry logic.

Configurable double-knocking

The new FederationOptions.firstKnock option provides control over the HTTP Signatures specification used for the initial signature attempt when communicating with previously unknown servers.

Previously, the first knock for newly encountered servers always used RFC 9421 (HTTP Message Signatures), falling back to draft-cavage-http-signatures-12 if needed. With this release, you can now configure which specification to use for the first knock when communicating with unknown servers, with RFC 9421 remaining the default.

Summary

This release maintains Fedify's commitment to reliability and compatibility while laying the groundwork for more efficient message processing. The native retry mechanism support will particularly benefit applications using queue backends with sophisticated retry capabilities, while the double-knocking mechanism addresses real-world compatibility challenges in the ActivityPub ecosystem.

For detailed technical information about these changes, please refer to the changelog in the repository.

#fedidev #fediverse