What is Hackers' Pub?

Baby chicks pass the bouba-kiki test, challenging a theory of language evolution

Link: https://www.scientificamerican.com/article/baby-chicks-pass-the-bouba-kiki-test-challenging-a-theory-of-language/
Discussion: https://news.ycombinator.com/item?id=47079208

Why does MainActor isolation prevent SendableMetatype conformance? A puzzling concurrency constraint explored through documentation practice and the Zettelkasten method.

🔗: https://christiantietze.de/posts/2026/01/zettelkasten-for-programmers-documenting-confusing-with-swift-sendablemetatype/ by Christian Tietze (@ctietzeChristian Tietze)

#Swift #Concurrency #iOSDev

이게 나오네

これは実物持ったりフォト​​見た瞬間に​​しそうな気がする

이준석은 뭐 소식 없나

RE: https://bsky.app/profile/did:plc:g23eq6mc3wh6nk5kmxbobm6i/post/3mflmnoj2v323

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 handling — setOutboxPermanentFailureHandler() 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

#Fedify #ActivityPub #fediverse #fedidev #TypeScript

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:

https://podcast.uberspace.de/folge-8-der-rechenzentrumsumzug/

#podcast

인생 어쩌라고다

하

저 평일마다 9시간동안 월급카페에서 작업메이트들이랑 정모하고 있어요 짱이죠

Hello @mastoblasterMastoBlaster - Official Account about the timeline, is it automatically refreshed or do I need to pull down to refresh it?

대구에, 그것도 2월 말에 함박눈이라니 ㄷㄷㄷ

운동 가고싶지 않아 설날주간 일주일 쉴때 좋았는데 ㅠ

지역코드 09-12가 부산이네요. 제가 부산 동래구 구포동에서 등록해서 111이거든요<

my Mastodon server is down :(

#merchtodon

Heheh, someone wants to optimise AI visibility in my blog post on stealing content by AI vendors https://hidde.blog/llm-theft-opt-out/

A couple days ago, I got a DM from a #Bonfire 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, #Fedify had no reason to send a second one.

I filed two issues on the Bonfire #ActivityPub 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.

#fedidev #fediverse #Hollo #HackersPub

Django's query string tag (from v5.1) is a good example of a maintenance slow-bleed.

It **seems** simple but, over the space of users, has so many possible (i.e. actual) applications that there's a long stream of requests and revisions needed.

When folks are like "Why can't we **just** add feature…?" it's because they simply don't see what **just** adding that feature entails.

https://forum.djangoproject.com/t/enhancement-proposal-for-querystring-template-tag-support-for-dynamic-context-based-keys/44281 #Django

mruby/cで車両データ取得するトークの資料が公開されてた #izumork01 https://speakerdeck.com/matsudai/ruby-x-che-ai-che-nodetawoqu-de-seyo

Finally! You can now use JS modules in service workers (i.e. use `import` and `export` to organize your code in modules).

Thank you, Firefox, for adding support and joining other browser engines.

https://web-platform-dx.github.io/web-features-explorer/features/js-modules-service-workers/

Outside.

#photography

みんな生成AI使ってる🤮ちゃうの僕だけ

ブ ロ ッ コ リ ー

一時間以上粘ってたら体が冷え切ってしまった
#misskey写真部

Show HN: Babyshark – Wireshark made easy (terminal UI for PCAPs)

Link: https://github.com/vignesh07/babyshark
Discussion: https://news.ycombinator.com/item?id=47128535

A couple days ago, I got a DM from a #Bonfire 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, #Fedify had no reason to send a second one.

I filed two issues on the Bonfire #ActivityPub 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.

#fedidev #fediverse #Hollo #HackersPub

A couple days ago, I got a DM from a #Bonfire 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, #Fedify had no reason to send a second one.

I filed two issues on the Bonfire #ActivityPub 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.

#fedidev #fediverse #Hollo #HackersPub

XKCD has become a valid coding for messages on the Internet.

That discussion looks like a typical 386

Then I did a successful 356 on him

Our core architecture is fully 2347 compliant

XKCD has become a valid coding for messages on the Internet.

That discussion looks like a typical 386

Then I did a successful 356 on him

Our core architecture is fully 2347 compliant

Kiro CLI無双。自身の利用ログ解析中に発見した異常値を調査、AWSサポート起票までやりきった話
https://dev.classmethod.jp/articles/kiro-cli-log-analysis-aws-support/

#dev_classmethod

@smallcircles🫧 socialcoding.. should PeerTube, Mastodon, Pixelfed, Loops, Bonfire and others merge in a single platform where a topic is more central, and not so much a file format?

The Chinese party-state's campaign to erase "minority languages" continues

"A years-long trend of replacing Mongolian-, Tibetan-, and Uyghur-medium instruction with Mandarin Chinese-medium instruction is now codified in law. Students in these communities will now only be taught their mother tongue as a single, standalone class; all other classes will be taught in Chinese."

https://www.nchrd.org/2026/02/chinas-erasure-of-ethnic-minority-languages/

#China #Tibet #Uyghur #linguistics #language #HumanRights

捕食者 #捕食者

https://x.com/DAIGATANA/status/2025888216277234093?t=mEYmJRBOTQqK_QiYjfnUmA&s=19

​​

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: https://berlin-werbefrei.de/

#BerlinWerbefrei #WerbemonitoreAbschalten #Berlin #Steglitz #Volksbegehren

Canva acquires startups working on animation and marketing
https://techcrunch.com/2026/02/23/canva-acquires-startups-working-on-animation-and-marketing/?utm_source=flipboard&utm_medium=activitypub

Posted into Startup News @startup-news-TechcrunchStartup News

manjaroアプデラッシュ

탐라의 자기소개 시간이 되엇으니 정식으로 소개합니다. 가끔 그림러, 가끔 게임러, 드물게 스트리머, 가끔 Live2D러 입니다. #러_트친소

동생이 베트남 선교 다녀오면서 사온 [족제비] 커피.. 이제 함 마셔보네요 ㅋㅋㅋㅋ 내리는 커피일줄 알았는데 인스턴트 스틱 커피였구.. 가루일땐 향이 정말 진하고 좋은데, 물에 타니 다 휘발되었는지 거의 향이 안 나..🥲

블루스카이 v1.117 업데이트 - Bandcamp 임베드 지원으로 게시물 내에서 음악을 재생할 수 있습니다 - 스타터 팩을 목록으로 변환할 수 있는 기능을 추가했습니다 - 뮤트한 단어가 만료되었을 때 “갱신” 버튼으로 기간을 조정할 수 있습니다 - 수많은 버그 수정 및 성능을 개선했습니다 caribouband.bandcamp.com/album/butter...

RE: https://bsky.app/profile/did:plc:z72i7hdynmk6r22z27h6tvur/post/3mfkhetnvdk2p

Butterfly, by Daphni

兄の息子…
兄Son(アニソン)…

Iowa farmers are leading the fight for repair

Link: https://www.ifixit.com/News/115722/iowa-farmers-are-leading-the-fight-for-repair
Discussion: https://news.ycombinator.com/item?id=47131506

The Chinese party-state's campaign to erase "minority languages" continues

"A years-long trend of replacing Mongolian-, Tibetan-, and Uyghur-medium instruction with Mandarin Chinese-medium instruction is now codified in law. Students in these communities will now only be taught their mother tongue as a single, standalone class; all other classes will be taught in Chinese."

https://www.nchrd.org/2026/02/chinas-erasure-of-ethnic-minority-languages/

#China #Tibet #Uyghur #linguistics #language #HumanRights

I sadly can‘t make it to #sotb26 and if anyone wants to attend the sold out event, here is your chance! Would be such a shame to leave this ticket unused.

FreeBSD에는 내 오래된 MacBook용 Wi-Fi 드라이버가 없었다, 그래서 AI가 만들어줬다
------------------------------
- 2016년형 MacBook Pro의 *Broadcom BCM4350 칩* 은 FreeBSD에서 기본 지원되지 않아, 기존에는 Linux VM을 통한 *wifibox 우회 방식* 이 일반적이었음
- 작성자는 Claude Code 를 이용해 Linux의 brcmfmac 드라이버를 FreeBSD로 포팅하려 했으나, 커널 패닉과 *LinuxKPI 호환성 문제* 로 실패함
- 이후 *Pi c…
------------------------------
https://news.hada.io/topic?id=26957&utm_source=googlechat&utm_medium=bot&utm_campaign=1834

なんかいま停電した！