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

RE: mastodon.social/@arstechnica/1

...in which Amazon tell us that outages were caused by unreviewed AI code...

oh yeah somebody said something about there being no doubt about productivity gains because 'they see them everyday'?

Well ok I'll accept your still anecdotal evidence but I would like to debit hours from those x1 engineers productivity gains and raise a credit for hours lost by every person affected by these outages.

0
0
0
0
0
2
0
0
1
1
1
0
1
0
0
0
0

The February 2026 Trunk & Tidbits is posted. Our monthly engineering update, including progress on 4.6, our AI contribution policy, upcoming end-of-life for version 4.3, some posts about the Share button, and more.

blog.joinmastodon.org/2026/03/

0
2
2
0
0
0
0

ARTE.tv featured our project in a recent documentary on European digital dependencies:

openwebsearch.eu/wo-bleibt-das

🥳 A big shoutout goes to @djoerd from our team at @Radboud_uniRadboud University whom you can see in the interview!

University Passau, @Radboud_uniRadboud University, CERN, German Aerospace Center, Leipzig University, Technische Universität Graz, IT4Innovations National Supercomputing Center, CSC-IT Center for Science, A1 Slovenija d.d., Bauhaus-Universität Weimar, @osfOpen Search Foundation, @LRZ_DELeibniz Supercomputing Centre , SUMA-EV, @nlnet

Our project was featured on arte.tv (German version)
0
0
0
0
0

Today @kopperkopper :colon_three: shared a post on the fediverse titled how to not regret c2s, and I found it genuinely interesting to read, even if I'm not sure its proposed architecture actually solves what it sets out to solve.

The author's frustration with naïve implementations is well-founded. Slapping an facade onto an existing Mastodon-like server and calling it C2S doesn't buy you much—you end up with the rigidity of a bespoke API without any of the interoperability C2S is supposed to offer. The “JSON-LD flavored Mastodon API” framing is apt.

The proposed solution is to split responsibility more aggressively: the C2S server should be nearly stateless and dumb, storing ActivityPub objects without interpreting them, while a separate “client” layer handles indexing, timelines, moderation, and exposes its own API to the frontend running on the user's device. It's a clean separation of concerns on paper.

But here's what bothers me. When you map this architecture onto familiar terms, it looks roughly like this:

  • C2S server ≈ a database (PostgreSQL, say)
  • “Client” ≈ an application server (Mastodon, Misskey)
  • “Frontend” ≈ the actual client app on your phone

That's not a new architecture. That's just the current architecture with the labels shifted. The interesting question is which interface gets standardized, and the author's answer is the one between the C2S server and the “client” layer—the bottom boundary.

The problem is that what people actually want from C2S is to connect any frontend to any server. The portability they're after lives at the top boundary, between the frontend and whatever is behind it. But the author explicitly argues against standardizing that layer: “we don't really need a standardized api,” they write, leaving each client free to expose whatever API it likes.

Which means frontends remain locked to specific clients, just as Mastodon apps are locked to the Mastodon API today. The interoperability promise of C2S—log in to any server with any app—isn't actually delivered. It's been pushed one layer down, out of reach of the end user.

There's real value in the post's thinking about data hosting vs. interpretation, and about the security implications of servers that understand too much. But as an answer to the question C2S is supposed to answer, I'm not convinced.

2
0
0
0
0
0
0
0
0
0
1
0
0
0

틴케이스 좋아하시나요?

smartstore.naver.com/dami2

작은 스티커나 간단한 마스킹 테이프등을 넣어서 보관하기 좋은 사이즈로 제작한 백합 틴케이스에요.🥰

정말 정말 간만에 틴케이스를 제작해 봤는데, 색도 선명하고 사이즈도 딱 마음에 들게 나와서 무척 기뻤답니다.

1월 오프라인에서는 실물도 보여드렸는데, 예쁘다는 칭찬을 정말 많이 받아서 어깨가 으쓱해졌었어요. 😘❤️

0

RE: mastodon.social/@arstechnica/1

...in which Amazon tell us that outages were caused by unreviewed AI code...

oh yeah somebody said something about there being no doubt about productivity gains because 'they see them everyday'?

Well ok I'll accept your still anecdotal evidence but I would like to debit hours from those x1 engineers productivity gains and raise a credit for hours lost by every person affected by these outages.

0
1
1