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.

The men's Paris-Roubaix just started, so I'm not able to do much else today.

I'm surprised so many of the cycling pundits give Wout Van Aert the chances to win, unlike last week when it was almost unanimous for Pogacar, or van der Poel.

0
0
0
0

Fetching remote objects or actors often involves handling lookups, content negotiation, and then parsing potentially untyped JSON.

With , it's much simpler: use Context.lookupObject(). Pass it a URI (e.g., https://instance.tld/users/alice) or a handle (e.g., @alice@instance.tld), and Fedify handles the lookup and content negotiation automatically.

The real power comes from the return value: a type-safe Activity Vocabulary object, not just raw JSON. This allows you to confidently access properties and methods directly. For example, you can safely traverse account moves using .getSuccessor() like this:

let actor = await ctx.lookupObject("@alice@instance.tld");
while (isActor(actor)) {
  const successor = await actor.getSuccessor();
  if (successor == null) break;
  actor = successor;
}
// actor now holds the latest account after moves

This is readily available in handlers where the Context object is provided (like actor dispatchers or inbox listeners).

Focus on your app's logic, not protocol boilerplate!

Learn more: https://fedify.dev/manual/context#looking-up-remote-objects

0

Fetching remote objects or actors often involves handling lookups, content negotiation, and then parsing potentially untyped JSON.

With , it's much simpler: use Context.lookupObject(). Pass it a URI (e.g., https://instance.tld/users/alice) or a handle (e.g., @alice@instance.tld), and Fedify handles the lookup and content negotiation automatically.

The real power comes from the return value: a type-safe Activity Vocabulary object, not just raw JSON. This allows you to confidently access properties and methods directly. For example, you can safely traverse account moves using .getSuccessor() like this:

let actor = await ctx.lookupObject("@alice@instance.tld");
while (isActor(actor)) {
  const successor = await actor.getSuccessor();
  if (successor == null) break;
  actor = successor;
}
// actor now holds the latest account after moves

This is readily available in handlers where the Context object is provided (like actor dispatchers or inbox listeners).

Focus on your app's logic, not protocol boilerplate!

Learn more: https://fedify.dev/manual/context#looking-up-remote-objects

0

Fetching remote objects or actors often involves handling lookups, content negotiation, and then parsing potentially untyped JSON.

With , it's much simpler: use Context.lookupObject(). Pass it a URI (e.g., https://instance.tld/users/alice) or a handle (e.g., @alice@instance.tld), and Fedify handles the lookup and content negotiation automatically.

The real power comes from the return value: a type-safe Activity Vocabulary object, not just raw JSON. This allows you to confidently access properties and methods directly. For example, you can safely traverse account moves using .getSuccessor() like this:

let actor = await ctx.lookupObject("@alice@instance.tld");
while (isActor(actor)) {
  const successor = await actor.getSuccessor();
  if (successor == null) break;
  actor = successor;
}
// actor now holds the latest account after moves

This is readily available in handlers where the Context object is provided (like actor dispatchers or inbox listeners).

Focus on your app's logic, not protocol boilerplate!

Learn more: https://fedify.dev/manual/context#looking-up-remote-objects

0
1
1
1
0
1
0
0
0

Recap of CloudFest hackathon

When you hear ‘CloudFest’, many people associate it with a business-to-business event, which it is, but the hackathon in the run-up to it still has a certain degree of community character. On the initiative of Andreas Heigl (@heiglandreas@andreas.heigl.org) and the support of Matthias Pfefferle (@pfefferleMatthias Pfefferle), this year’s hackathon provided the resources and space for an exchange of ideas around ‘federated events’.

Our group was one of the largest and very diverse. We used the first day primarily to exchange ideas about our goals and the status quo. Afterwards, we reviewed and improved existing features and developed prototypes and concepts for new ones.

For me as a developer of the WordPress plugin Event Bridge For ActivityPub, the best thing about these days was to finally get to know the entire WordPress/Automattic team involved with ActivityPub in person (greetings to @mattwiebe and @obenlandKonstantin Obenland’s :yikes:).

I would like to emphasise a few achievements in particular, without neglecting the achievements of all:

  • Matthias Heigl took the time to take an intensive look at the FEP-8a8e. His many years of experience with the development of calendar features and iCal provided important suggestions for making the specification even more far-sighted.
  • Laura (working-directory.com/) helped to reduce the barriers new developers face when experimenting with the interaction of Gancio/Mobilizon and WordPress and others.
  • Finally, many thanks to Cloudfest for the great organisation and hosting!

Links:

0
0

昔行ったベトナム料理屋、ベトナム人のシェフに「ノーパクチー」言ったら
「ノーパクチー!? おー、ノーノーノーノー! ノーパクチー、ノ~~~~。パクチー、ヘルシー、カラフル、OK?」
って倍量のパクチーぶち込まれたことある。

1
1
0
0
0
0
0
0
0
0
0

Born in 1914, Hedy Lamarr was a famous American actress who pioneered the technology that would lead to WiFi, GPS, cell phones & Bluetooth communication.

Lamarr was brilliant. Among many fascinating inventions, she developed a new communication system with composer George Antheil that used “frequency hopping” among radio waves.

Once called the “most beautiful woman in the world," Lamarr is now remembered as "the mother of Wi-Fi."

smithsonianmag.com/smithsonian

Hedy Lamarr publicity photo for the film The Heavenly Body, 1944
0
0
0
0
0
1
1
0
1
0
0
0
0

Misskey APIも全部`POST`の流儀だように記憶していたけど、`/api/server-info`のようにパラメタを取らないものは`GET`なのか。しかしその他のパラメタを取るAPIはついてはやはり、安全な操作だろうがパラメタをJSONとして`POST`する形になっている

0
0
1
1
1

Misskey APIも全部`POST`の流儀だように記憶していたけど、`/api/server-info`のようにパラメタを取らないものは`GET`なのか。しかしその他のパラメタを取るAPIはついてはやはり、安全な操作だろうがパラメタをJSONとして`POST`する形になっている

0
0
0
0
0
0
0

Was haben wir von der der Exklusivverträge für Werbung im öffentlichen Raum zu befürchten, die der Senat gerade hinter verschlossenenen Türen mit den Betreibern verhandelt?

Noch mehr digitale Werbung. Eine Bindung der Stadt für weitere 15 Jahre an Konzerne, die aus ihr eine Dauerwerbesendung machen.

Ein schwebender kann diese Pläne durchkreuzen. Darum ist es wichtig, jetzt für zu unterschreiben!

0
0
0