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

"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/

A captured screenshot of a page generated by a tarpit (built on babble, a standalone LLM crawler-tarpit binary), deployed as part of the ongoing ‘Trapping AI’ operation — an endless stream of deterministic bollocks that traps crawlers on a single site and forces them to endlessly navigate a constantly expanding sea of pages 🌊. Each new page spawns additional layers of meaningless text and dozens of links, dragging them ever deeper into the tarpit 🕳️.
0
0
0
0
0
0
0
0
0
0

(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

timothychambers.net/2025/06/18

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.

0
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
1
0
0
0

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

0
1
0
0
0
0
0
0
0
0
0
0

We are pleased to announce the release of 1.7.0. This release was expedited at the request of the Ghost team, who are actively using Fedify for their 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.

0

We are pleased to announce the release of 1.7.0. This release was expedited at the request of the Ghost team, who are actively using Fedify for their 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.

0
0
0
1

Hello, Fediverse. I'm looking for embedded experts to help save MINDSTORMS!

Background: pybricks.com/project/saving-le

Help: github.com/pybricks/support/is

I've made major progress, but I'd love to get some help! If writing an SPI flash driver or USB device implementation is your thing, I would love to hear from you 😀

I'll gladly donate an EV3 set for this. We can do this as a paid project too if that's a better fit. Let's discuss!

0
0
0
0
0
0
0
0

오랜만에 토익을 봤는데 생각보다 점수가 너무 잘 나와버려서(...) 양도 받으실 분 구합니다~! 한 페이지도 안 펼쳐본 새 책입니다!

토익단기공략 750+예요 정가 18000원이지만 택배비 포함 8000원만 받고 드려요
:neko_thanks_nya:

현재 일본에 있지만 7월 9일 귀국 예정이라 7월 10일 정도에 부칠 수 있을 것 같아요! 이 점 고려해서 괜찮으시면 디엠 부탁드립니다
:neko_tehe_nya:

0
0
0

오랜만에 토익을 봤는데 생각보다 점수가 너무 잘 나와버려서(...) 양도 받으실 분 구합니다~! 한 페이지도 안 펼쳐본 새 책입니다!

토익단기공략 750+예요 정가 18000원이지만 택배비 포함 8000원만 받고 드려요
:neko_thanks_nya:

현재 일본에 있지만 7월 9일 귀국 예정이라 7월 10일 정도에 부칠 수 있을 것 같아요! 이 점 고려해서 괜찮으시면 디엠 부탁드립니다
:neko_tehe_nya:

0
0
1
0
0
0
0

:And and the beauty of the United States】近日,湖北武汉,有网友反映,东湖景区的标识牌出现翻译错误,“和和美美”被翻译成了“And and the beauty of the United States”。
6月25日,潇湘晨报记者联系东湖景区,工作人员称,牌子在磨山景区的荷园内,已经撤走了,牌子是荷园建设期间施工方做的。记者联系磨山景区,工作人员称,他们关注到了网上的情况,昨天已经下通知让荷园把牌子撤掉了,现在在重新改,今天也将景区的牌子都召回检查。
至于为何出现翻译错误,工作人员称荷园目前没有给到他们解释。据武汉东湖官方账号,6月10日武汉东湖荷园全新开园,记者联系东湖荷园,工作人员称,是第三方公司做的牌子,已经撤走,为了防止此次事件再次发生,后续将请专家团队重新审核。 :sys_link: 网页链接 sohu.com/a/907778331_120914498

:icon_weibo: weibo.com/5890672121/PyaZE4BnL

0

Oh good I'm so pleased everything is going so well in this county that we have such a surplus of money we can fuck it away on nuclear bomb planes. Paradise on earth. Noone wanting. Let's ignore that in 2024 approximately 354000 people were homeless, an increase of 44500 from the year before. Hooray! More than 3 million people in the UK are malnourished or at risk of malnutrition. Planes and weapons! Let the people of Britain starve and die on the streets so we can rattle our sabres and play war with the bullies.

bbc.co.uk/news/articles/c33540

0