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

イ・米によるイラン急襲で死者が出ている施設の中に「女子小学校」が… 👿 (見出しに書け)

(そもそも国際法違反の攻撃であり、非軍事施設それも学校を爆撃するなど言語道断なのは勿論のこと、為念)

小学校に攻撃…児童57人が死亡 イラン国営通信(2026年2月28日掲載)|日テレNEWS NNN

news.ntv.co.jp/category/intern

>> イラン国営通信によりますと28日、イラン南部ミナーブにある女子小学校がアメリカとイスラエルの攻撃を受け、少なくとも57人の児童が死亡、60人がケガをしたということです。また53人の児童が、ガレキの下に取り残されていて、救助活動が続いていると…

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

Before going to bed last night, a friend told me they were already hearing bombs dropping (in the Middle East, but not in Iran or Israel). Their flights back to the US got cancelled.

Millions of people who don't want a war dragged into it anyways. I'm praying for the living and mourning the dead.

0
0
2
0
0
2
0
0
0
0
0
0

🕐 2026-02-28 18:00 UTC

📰 「全エンジニアが Claude Code を 100% 活用する」を目指してダッシュボードを作った (👍 121)

🇬🇧 Team dashboard created to track Claude Code adoption. Survey revealed engineers don't know about custom skills/sub-agents others built.
🇰🇷 Claude Code 활용도 추적을 위한 팀 대시보드 제작. 설문 결과 다른 사람이 만든 스킬/서브에이전트를 모르는 경우가 많았음.

🔗 zenn.dev/dinii/articles/28c8fc

0
0
0
9
0
0
2
0
0
0
0

Heading to the event or only able to join us in spirit? If you see something that evokes "toot", "tŵt", "dwti" or anything Welsh, send something to today's FediWall with the hashtag

And follow along with this self-updating wall of toots: fediwall.social/?servers=masto

toot wales fedi wall
0
2
0

Ultimately I try to be grateful for the duality that I can see and feel because I think that navigating this requires having compassion for all these sides of ourselves. Being an ambitious person, with many years of skills, who gets joy out of creating, but also being a person in a world that is very happy to take advantage of creative and ambitious people past their limits. Knowing it is true that collectively my beautiful queer household starts further back always, this is just reality.

You have to find ways to fight that aren't grinding. You have to find paths to work hard that feel meaningful, like the rewards flow back to you and not to everyone else. You have to take the world as it is yet continually and always expect it to be far better than you have experienced. It is a lifelong challenge.

0
0

I don’t know what the hell ICE / CBP / FBI?? / other feds are up to, but we’ve had several •huge• swarms of federal vehicles rolling out these last few days.

They aren’t doing the kinds of chaotic off-the-street kidnappings there were doing all through Dec and Jan. But they sure are up to •something•.

1/

0
0
2
0
0
0
0
0
2
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.

1
0