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

📣 🎊 PyOhio Registration is Now Open! Make sure you secure your space and register now! 🎊 📣

ti.to/pyohio/2025

is always a Free to attend . This year it will take place on Saturday & Sunday July 26 & 27, 2025 at the Cleveland State University Student Center in Cleveland, Ohio

You can donate to help support this free Python Conference even if you're unable to attend! We've got a lot upcoming, make sure you watch for more info!

pyohio.org/2025/

0
1

Happy 30th birthday to . I wrote a history of it several years ago: “If CGI scripts were the start of interactive programming on the web, then PHP was the natural next step — at least on the server-side. Just a month after Brendan Eich created the JavaScript scripting language at Netscape, an independent developer from Canada named Rasmus Lerdorf released the first version of a toolset he called Personal Home Page Tools (PHP Tools).” cybercultural.com/p/1995-php-q

0
0
0
0

Last week the W3C Advisory Committee elected 7 people to the W3C Advisory Board: Daniel Appelquist, Theresa O'Connor, Hiroshi Ota, Avneesh Singh, Hidde de Vries, Song Xu, and Brent Zundel. They join continuing AB participants Wei Ding, Max Gendler, Tatsuya Igarashi, and Elena Lape.

We extend grateful thanks to departing participants, Tantek Çelik, Elika J Etemad, Wendy Reid, and Chris Wilson, whose terms end at the end of June 2025.
w3.org/news/2025/w3c-advisory-

W3C AB icon
0
0
0
0
0
0
0
0
0
0
0

@reiver ⊼ (Charles) :batman: shared the below article:

Backfilling Conversations: Two Major Approaches

julian @julian@community.nodebb.org

<p>In February 2025, I presented a topic at FOSDEM in Brussels entitled <a href="https://spectra.video/w/xwCSYfZh1mJY64zJ9GngbE" rel="nofollow ugc">The Fediverse is Quiet — Let's Fix That!</a> In it, I outlined several "hard problems" endemic to the fediverse, focusing on one particular complaint that is often voiced by newcomers and oldtimers alike; that the fediverse is quiet because you don't ever see the full conversation due to some design considerations made at the protocol level.</p> <p>Since then there have been a number of approaches toward solving this problem, and it is worth spending the time to review the two main approaches and their pros and cons.</p> <p><em>N.B. I have a conflict of interest in this subject as I am a proponent of one of the approaches (FEP 7888/f228) outlined below. <strong>This article should be considered an opinion piece.</strong></em></p> <hr /> <h2>Crawling of the reply tree</h2> <p>First discussed 15 April 2024 and merged into Mastodon core on 12 Mar 2025, <a href="https://neuromatch.social/@jonny">@<bdi>jonny@neuromatch.social</bdi></a> pioneered this approach to "fetch all replies" by crawling the entirety of the reply tree. When presented with an object, the Mastodon service would make a call to the <code>context</code> endpoint, and if supported(?) would start to crawl the reply tree via the <code>replies</code> collection, generating a list of statuses to ingest.</p> <p>This approach is advantageous for a number of reasons, most notably that <code>inReplyTo</code> and <code>replies</code> are <strong>properties that are ubiquitous</strong> among nearly all implementations and their usage tends not to differ markedly from one another.</p> <p><em>N.B. I am not certain whether the service would crawl <em>up</em> the <code>inReplyTo</code> chain first, before expanding downwards, or whether <code>context</code> is set in intermediate and leaf nodes that point to the root-level object.</em></p> <p>One disadvantage is this approach's <strong>susceptibility to network fragility</strong>. If a single node in the reply tree is temporarily or permanently inaccessible, then every branch of the reply tree emanating from that node is inaccessible as well.</p> <p>Another disadvantage is the reliance on intermediate nodes for indexing the reply tree. The amount of work (CPU time, network requests, etc.) scales linearly with the size of the reply tree, and more importantly <strong>discoverability of new branches of the reply tree necessitate a re-crawl of the entire reply tree</strong>. For fast-growing trees, this may not net you a complete tree depending on when you begin crawling.</p> <p>Lastly, in the ideal case, a full tree crawl would net you a complete tree with all branches and leaves. Great!</p> <p>Mastodon is the sole implementor of this approach, although it is not proprietary or special to Mastodon by any means.</p> <h2>FEP 7888/f228, or FEP 171b/f228</h2> <p>Summarized by <a href="https://mitra.social/users/silverpill">@<bdi>silverpill@mitra.social</bdi></a> in <a href="https://w3id.org/fep/f228" rel="nofollow ugc">FEP f228</a> (as an extension of FEPs <a href="https://w3id.org/fep/7888" rel="nofollow ugc">7888</a> by <a href="https://mastodon.social/@trwnh">@<bdi>trwnh@mastodon.social</bdi></a> and <a href="https://w3id.org/fep/171b" rel="nofollow ugc">171b</a> by <a href="https://fediversity.site/channel/mikedev">@<bdi>mikedev@fediversity.site</bdi></a>), this conversational backfill approach defines the concept of a "context owner" as referenced by compatible nodes in the tree. This context owner returns an <code>OrderedCollection</code> containing all members of the context.</p> <p>A major advantage of this approach centers around the pseudo-centralization provided by the context owner. This "single source of truth" maintains the index of objects (or activities) and supplies their IDs (or signed full activities) on request. Individual implementations then retrieve the objects (or activities). It is important to note that <strong>should the context owner become inaccessible, then backfill is no longer possible to achieve</strong>. On the other hand, a dead or unresponsive intermediate node will not affect the ability of the downstream nodes to be processed.</p> <p>The context owner is only able to respond with a list of objects/activities that it knows about. This does mean that downstream branches that do not propagate upwards back to the root will not be known to the context owner.</p> <p>Additionally, consumers are also able to query the context owner for an index without needing to crawl the entire reply tree. The ability to de-duplicate objects at this level reduces the overall number of network requests (and CPU time from parsing retrieved objects) required, <strong>making this approach relatively more efficient</strong>.</p> <p>Additional synchronization methods (via id hashsums) could be leveraged to reduce the number of network calls further.</p> <p>A number of implementors follow this approach to backfill, including NodeBB, Discourse, WordPress, Frequency, Mitra, and Streams. Additional implementors like Lemmy and Piefed have expressed interest.</p> <p>One technical hurdle with this approach is technical buy-in from implementors themselves. Unlike crawling a reply tree, this approach only works when the context owner supports it, and thus should be combined with various other backfill strategies as part of an overall conversational backfill solution.</p> <h2>Conclusion</h2> <p>2025 is shaping up to be an exciting year for resolving some of the harder technical and social problems endemic to the open social web/fediverse. It is this author's opinion that we may be able to make good headway towards resolving the "quiet fedi" problem with these two approaches.</p> <p>It is important to note that <strong>neither approach conflicts with the other</strong>. Implementations are free to utilise multiple approaches to backfill a conversation. Both methods presented here have pros and cons, and a combination of both (or more) could be key.</p> <p>Feel free to use this as a starting point for discussions regarding either approach. Does one speak to you more than the other? Are the cons of either approach significant enough for you to disregard it? What other approaches or changes could you recommend?</p>

Read more →
0

惟恐版面變得太厭世,趕快用美食(?)洗版😂。

週末自炊咖喱飯,內容物都是自己喜歡吃的蔬菜。
玉米筍+雪白菇,吃起來很有口感,美中不足的是馬鈴薯,不知道是煮的不夠透還是品種不對,味道和咖喱完全分開,有點可惜、下次換種🥔試試看。

0
0

The article is about something else, but I belatedly realized that all I wanted to do is write an article about infinity.

Maybe I still should, but I don't know if the remaining five subscribers can handle it

0

So... I've been thinking a LOT about how to get our word out. There's a TON of us here. If we all created accounts on a big tech platform and all took turns posting a thing and every single one of us retweeted that one thing all at once (which we can organize when the best time to do it would be of Fedi) we break through the noise.

We use our collective voices to shake fucking Twitter. Idk if it'll work like this or not. But it's a thought. For example, go make a Twitter. Follow a bunch of random folks. Make idle interaction. Then a week from now @elenaElena Rossini on GoToSocial ⁂ for instance posts her video and we all retweet it. Will it catch the algorithms attention and bubble it to the top of the page.

Bots have been used on reddit like this. Just a thought how to use what they consider their greatest advantage against them. Our greatest advantage is we have people with amazing intellect and passion. There has to be a way so our message gets out over there.

0
0
2
0

Thank you @codethink for being a Bronze sponsor of ! 🧡

Codethink specializes in system-level software engineering to enable advanced technical applications, working across a range of industries including automotive, medical, telecoms and finance.

Visit their website to know more: codethink.co.uk/

0
0
0
0

グレタ・トゥーンベリさんと一緒にマドリーン号に乗っている欧州議会議員のリマ・ハッサンさん、勉強不足でいままで知らなかった。シリアのパレスチナ人民キャンプ生まれで、いまはフランス国籍。

0
0
0
0
0
4
0

"Werewolves are weak to silver"
Pah. This is BS. They are strong to everything else. There's a difference.

Take say faeries, who are properly weak to iron. You ask them to handle a cast-iron pan or a steel chef's knife, they can't do it.

But werewolves? Ask them to eat with your silverware, they might look at you odd, but they're fine.

Granted, stab them in the eye with your silver steak knife (you weirdo. who has those?), they'll have a bad time. As would a normal human. Or faerie.

0

Unserer Lehrer hatten übrigens (mutmaßlich) Gastgeschenke mitgenommen. Zumindest gehe ich davon aus. Zur Selbstversorgung kommen mir 18 Flaschen Wein und eine unbestimmte Menge Bier zu viel vor.
Wir haben eine tolle Kaffeerösterei und einen super Teeladen in der Stadt. Aber man muss Alkohol mitnehmen. Wein können die Franzosen ja nämlich selbst gar nicht und Bier ist unsere Kultur. ☝️
🙄
Ich hätte von Lehrkörpern heutzutage etwas mehr erwartet...

0
0
24
0
0
0
0
0
0
0
0
0
0
0

Bridgy Fed and Bounce matter bc it's not just ActivityPub, ATProto, or any other protocol. It's about leveling the playing field for what comes next and not losing our relationships when we want to try the next innovation.

These aren't just bridges between standards, they're bridges for the future.

0