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

Instead of defending the use of LLMs for polishing up your writing, we could be advocating for unpolished writing. Blog posts with spelling errors and awkwardly repeated words. Emails that sound a bit less warm and professional because you forgot the preamble of "Apologies for the late reply, hope you're well! Thanks for the thing last week".

If there's no budget for a human editor, why should the text meet a "professional" (middle class, formally educated) standard? Dyslexic people can just write how they write and people can deal with it. Autistic people can just say what they mean to say and not waste energy on the double empathy gap.

We can learn to read for a more inclusive world, instead of wasting the planet's diminishing resources masking our differences.

0

Since 1999, February 21 is UNESCO's International Mother Language Day, promoting multilingualism! en.wikipedia.org/wiki/Internat

As a global community, and thanks to the efforts of more than 200 translators, CoMaps is already available in more than 50 languages. Why not celebrate Mother Language Day by adding some translations and grow that number? translate.codeberg.org/project

a sharepic saying "help us translate"
0
1
0
2

@julian @evanEvan Prodromou

No need to, I didn't call you out :)

I think the fediverse-we-have has become a very different one than the fediverse-promised based on the initial specs when there weren't implementations and an installed base making numerous design decisions in a very ad-hoc pragmatic fashion. Which is in itself fine, and a very good approach to get an ecosystem off the ground. But having the app-centric, app-first evolution be the primary evolution process, brought us to a different space than the ubiquitous, heterogeneous social networking environment we might all be working in, focused on exciting solution designs and less in all the plumbing and impl details.

No one is really to blame I guess. This is where laissez-faire in grassroots environments leads us, following the social dynamics that exist.

We can do better, but it is very hard in our individualist, FOSS-project-oriented herding of cats chaotic environment. The challenges are social in nature..

discuss.coding.social/t/major-

@julian @evanEvan Prodromou

Btw, some time ago in a matrix discussion I sketched how I'd like to conceptually 'see' the social network. Not Mastodon-compliant per se (though it might be via a Profile or Bridge) but back to "promised land". Where the protocol is expressed in familiar architecture patterns and borrows concepts from message queuing, actor model, event-driven architecture, etc.

Then as a "Solution designer" I am a stakeholder that wants to be completely shielded from all that jazz. That should all be encapsulated by the protocol libraries and SDK's that are offered in language variants across the ecosystem. et al is a black box. I can directly start modeling what should be exchanged on the bus, and I can apply domain driven design here. And if I have a semantic web part of my app I'd use linked data modeling best-practices.

I would have power tools like and methods like .

eventcatalog.dev/features/visu

eventmodeling.org/

Diagram showing the concept of an actor communicating to a remote actor, where there is a schema-based closed-world communication bus, and an open-world semantic web interface.
0
0
0
0
1
0
1

@eyeintheskyThe Eye

I am a former facilitator of SocialHub and part of the FEP team.

The whole idea of the FEP process is that it is accessible to all fedizens, and anyone can take the initiative and write, submit, and guide their own FEP document towards a FINAL status.

It is recommended practice to introduce a new FEP to the SocialHub developer forum for discussion, which the FEP forum category federates out. The forum thus also serves as an archive of past discussions around ActivityPub / fediverse evolution.

However, it is not *required* to discuss on SocialHub should you not want to do so for some reason. I'd say it has the disadvantage that it fragments discussion and it becomes harder to parse the 'body' of FEP's created over time. People would have to use the tracking issue accompanying a FEP to figure out where to discuss things.

But the freedom to choose is the important part. It helps lower the barrier to write FEP's.

0
0
1
1
2
2
0
0
4
0
2

Eure Wünsche wurden gehört und es gibt jetzt das Fediverse-weit erste Franzbrötchen-Emoji :franzbroetchen:

Es werden nach und nach weitere norddeutsche kulinarische Schöpfungen hinzukommen.

(Edit: Es ist nicht das erste Franzbrötchen im Fediverse. Aber von uns selbst gebacken!)

0
0
1
0
0

A Palestinian woman, who was denied entry to Jerusalem, walks next to members of Israeli troop, as people make their way to Al-Aqsa compound, also known to Jews as the Temple Mount, in Jerusalem's Old City, to attend the first Friday prayers during the Muslim holy fasting month of Ramadan, near the Qalandia checkpoint in the Israeli-occupied West Bank. REUTERS/Mohammed Torokman




An old Palestinian woman with a walking stick, who was refused entry to the al-Aqsa, is surrounded by four Israeli soldiers.
0
0
0
3
0
0

@voidbotbest practices for dev+test Code needs to be self-descriptive, but code comments—docstrings in particular—are essential.

I have worked with anti-docstring people, and frankly, I've found that reality always proves them wrong in the end.

---

Good documentation does not describe the code in detail. Instead:

1. You have a single-line docstring that summarizes what the function does (unless the function name is blatantly obvious).
2. You have a longer section of documentation that describes caveats and philosophy, if needed. Preferably, you don't need this.

You need the summary (point 1) to reduce cognitive overload by avoiding the need to interpret code every time you look something up.

You need the author's notes (point 2) to provide context for special cases. These are facts that you cannot infer from the code itself.

---

Anything you do not write down will be forgotten.

The argument that people should not write documentation because it gets outdated annoys the hell out of me.

It is an arrogant way of disregarding part of one's due diligence as a programmer, the one where you ensure that code remains maintainable for years to come.

---

To summarize:

1. Documentation that compensates for poorly written code is bad.
2. Documentation as additional context to code is good.

0
0
1
2
0

Was mache ich falsch mit @activitypub.blog auf meinem Blog Biblionik? Mein letzter Beitrag erscheint nicht in voller Länge hier im Fediverse, sondern nur abgeschnitten auf die ersten soundsoviel hundert Zeichen? 🧐 Diesen Beitrag hier meine ich: biblionik.org/2026/02/21/mein-

0
2
0
1
0
16
0
0

1차/2차 만화/소설 작가님 중에 여기 저랑 같이 나가실 분 계실까요! ​:pndslime_rainbow:
https://witchform.com/payform/?uuid=87ASXITSO8
5월 23일(토) ~ 24일(일)에 서울 양재 aT센터에서 열리는 행사에요!

저는 소설로 참가하려고 하는데, 같이 하실 분께서 원하시면 굿즈도 판매 가능한 부스로 신청할 수도 있어요!
저도 굿즈 판매 위주였어서
:pndslime_hot:

0
0
1
1
0
1

I really don't know why it is I've lost motivation this badly to nerd on my own projects due to AI.

All the things I like coding on for my own purposes are things nobody would want to pay me for. Economically, all of it has been quite worthless. Likewise, I never even *wanted* to become a professional artist or musician, I just enjoyed creating things.

So it seems completely bizarre to me that I still strongly feel like AI has made it all pointless.

0
0