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

ICE shot a journalist in the leg. A journalist.

They’re shooting people who are there to cover the protests as an essential part of the freedom of the press and the right to free speech.

It was apparently a non-lethal round, yet emergency surgery is required.

This regime has already silenced so many journalists.

Kicked them out of the Oval Office and filled it with “friendlies” (ie propagandists).

These are dark times:

theguardian.com/us-news/2025/j

0
0
0

OK. Implementing share and like tracking in my tiny activity pub implementation went well: tap.resistant.tech/sarah/posts

Sitting at just under 1700 lines of code, I have now implemented all the features I wanted to for an mvp (managing multiple accounts, accepting followers, posting, liking, tracking likes/shares, rss, and a simple web interface)

Next steps:

- a little more functionality testing
- a round of review/refactor
- open source it
- setup an instance for some org accounts to migrate to

0
0
0
0
0
0
0
0
0
0
0
0

I’ve witnessed only a tiny number of noteworthy moments in , but as a summer intern in 1987 I attended MacWorld and was in the auditorium when Bill Atkinson introduced . Completely mind-blowing: graphics, simplicity, expressiveness.

I remember HyperTalk’s surprising use of `it` as an accumulator:

```
get the selection
put it into the message box
```

I can’t name a contemporary user-friendly environment that lets you create apps/sites as easily as HyperCard did. ☹️

0
0
0
0
0

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

I just got 6 more ready to go to new homes.

This is 6 more people who's lives will be positively changed by getting a great laptop for free, with solid FOSS software on it.

Think of how much this helps even the digital divide. I'm dedicated to make this my life's work at the moment. Imagine if companies could safely offload their "old" hardware, and it could end up like this, for the public good.

Again, huge thanks to and and all of for making this possible!

6 Dell latitudes lined up with printed nixbook guides on them
0
0
0
0
0
0

"재분배, 민주주의, 이주민과 여성에 대한 태도, 인간에 대한 이해 모든 측면에서 20대 남성이 일관되게 보수적이다." sovidence.tistory.com/1301 "또한 20대 남성은 어느 집단보다 노인에게 혜택을 주는것에 반대한다." "외국인에 대한 태도는 20대가 가장 부정적인데, 20대 여성은 범죄에 대한 우려, 20대 남성은 경제권을 뺏긴다고 생각한다."

여러 지표에서 일관되게 나타나는 20대 남성의 보수성

0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0

I’ve been playing for a few weeks. Today I finished Act 2. This is a thread of thoughts on the game. No spoilers. Just general thoughts.

First off, it is beautiful. Artists have made a style. It is coherent throughout and uniquely expressive. Colour, texture, light. It reminds me of Ghost of Tsushima in that you can turn an ordinary corner and find an extraordinary vista.

Second, it is LARGE. The outside world, plus the various dungeon-like settings are all huge.
1/n

0

Today's group bike club ride¹ took us from Victoria Park (& Danforth) out to Highland Creek via the Gatineau corridor and an interesting series of parks (and some residential hills), then back along a "straightforward" route. Naturally, it was cool and cloudy during the ride and the sun came out basically right afterward, but we had a good time anyway.

¹ ridewithgps.com/trips/293442937

0
0
0

Me, buying cool art for my wall at cons: Haha fuck yeah!! Yes!!

Me, trying to figure out later how to frame and mount these arbitrarily sized prints: Well this fucking sucks. What the fuck.

0
0
0
0
0
0
0

A class-action lawsuit, filed by the SPLC and the National Housing Law Project, challenges Louisiana’s unusual court system for evictions: some court officials can personally collect fees when they grant evictions. boltsmag.org/louisiana-justice

0

A class-action lawsuit, filed by the SPLC and the National Housing Law Project, challenges Louisiana’s unusual court system for evictions: some court officials can personally collect fees when they grant evictions. boltsmag.org/louisiana-justice

0
0
0
0
0