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

Who should I send Delete activities to?

SorteKanin @SorteKanin@socialhub.activitypub.rocks

How to handle incoming Delete activities is already well-discussed elsewhere [1][2].

However, I have a hard time finding material on how to handle outgoing Delete activities. Specifically around this question: Who do I send such an activity to?

Naively, you might send the activity to the actor's followers. But imagine this simple scenario:

  1. Alice follows Bob.
  2. Bob posts a Note that Alice receives.
  3. Alice stops following Bob.
  4. Bob deletes the Note.

If we only send Delete activities to the followers of the actor, Alice will never receive the Delete activity and the Note will not be deleted, which is clearly not what Bob intended.

Another strategy might be to keep a record of all historical followers of an actor, and then send Delete activities to current and past followers. However, I am worried that this is not good enough either:

  1. Alice follows Bob and Bob follows Charlie.
  2. Charlie posts a Note that Bob receives.
  3. Bob shares (Announces) the Note, and Alice receives the Note too because she follows Bob.
  4. Alice stops following Bob and Bob stops following Charlie.
  5. Charlie deletes the Note.

I am a bit dumbfounded at what to do in this scenario. I might be missing something, but it seems impossible for Charlie to know that Alice has the Note. The only way I could possibly see this working is that Bob receives the Delete activity (as he is a past follower) and then graciously re-Announces the Delete activity to his followers, since he previously announced the deleted Note. Then Alice would also receive the Delete, as the re-Announce of the Delete would also need to be sent to all past followers.

However this seems complicated and relies on the good behaviour of Bob to re-Announce to his past followers, and I see no way to discover if Bob never re-Announced the deletion.

Another option is to send Delete activities to all known servers, but this doesn't necessarily include Alice either I would think.

How is this done in existing implementations? This is making me think reliable deletions are impossible and I'd love to be proved wrong.

Read more →
0
0
0

Hi everyone, it’s that time of the year again, when the air smells fresh, the flowers are blooming and systems researchers are locked in a windowless room because it’s the SOSP deadline! I wrote these hints on how to write an SOSP paper quite some time ago but I think it’s still a great reference for new and old students. irenezhang.net/blog/2021/06/05

0
0
0
0
0

Man @tut@fosstodon.org and do NOT like each other.
Tut doesn't seem to get the post size limit, sees (almost?) every post/toot as a pinned toot, and doesn't load notifications until I jump into the notifications pane and start scrolling around.

Bummer it's not being developed anymore. Wish I could find more time to learn Go. XD
0
0
0
0
0

Here is my #bio / #introduction just for the bsd.cafe community:

Hi, I'm R.L. I've dabbled in the fediverse since 2018 (originally mastodon.host (sadly defunct), then librem.one around 2019, then fosstodon starting in April 2022, then alpha.polymaths.social in fall 2023, and finally polymaths.social last October).

Last week, I migrated my main fediverse account from the excellent fosstodon.org to polymaths.social to take advantage of the camaraderie there, and of course the generous post character count limits. XD

I've dabbled in Linux since 1997, used it at home since 2000, and used it full time uninterrupted as my daily driver since 2019.

I've dabbled in the BSDs since 2022 or so, and currently have an #OpenBSD #Thinkpad which I use as a dedicated writing machine.

I love the power (hardware compatibility, feature set) and ease-of-use of Linux, and the "purity" and "unixyness" of the BSDs.

I was an infosec analyst and sysadmin in a previous life, but have left that behind, for my own sanity's sake. ;)

This will be my backup account, so please definitely follow me at @rl_dane@polymaths.social, but I look forward to having enjoyable chats on here as well from time to time.

Many thanks to @stefano@bsd.cafe for adding me!

P.S., Thanks for all the boost/retoot love! ❤️ ❤️ ❤️
0

Wish there was more open data in Australia?

libre.net.au is a new online community that aims to provide a space for Australians to collect, analyse and publish free and open datasets.

We're still getting started, but if you'd be interested in helping out with an open source price tracker for Australia, come join our Matrix chat!

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

Happy Tuesday!

Today we've updated the NodeBB community forum onto the remote-categories testing branch, which means that users on the open social web that identify themselves as "Groups" will be rendered in NodeBB as categories. Prior to this, they looked like users.

Here are some examples of remote categories:

ActivityPub "groups" and forum categories have quite a few things in common — they don't usually post topic themselves, they "contain" topics, and they are usually administered by a separate group of users (moderators!) In many ways, these groups lend themselves to categories much more easily than they do as users.

Notes:

  • We will likely be releasing this as v4.3.0-alpha this Wednesday. Probably this means you don't want this on a live forum just yet.
  • A lot of the backend logic is complete, but a lot of the frontend UX will be worked on.
  • You can "search" for categories (via "in categories" in the search page), paste the full handle in order to instruct NodeBB to pull a new category in.
  • You can now no longer mention a remote category. Instead, create your topic right in that category itself. As it should be :smirk_cat: .
  • Remote content coming in that is slotted into a remote category will still show up in your "world" feed. That is still intended to be where discovery of content outside the local NodeBB instance will take place.
  • Report any bugs or confusing behaviours (and there will be some) here.

Screenshots

4872fc8c-a679-4968-9daf-84bedb8bf237-image.png

08c3972a-6c7e-4cef-937c-0c4830770a8a-image.png

0
0
0
0
0
0
0
0
0
0
0

そんなこんなでおっさんまだまだ歯を悪くするので今日は

神経を抜く治療をしてもらってきました。歯医者さんが使うZeissの実体顕微鏡は対物レンズから物面までの距離がたぶん15cmくらい取れてすごいんだよねえ!!

歯茎の麻酔が取れていないのでモンエナが漏洩します←

0
0
0
0
0
0
0
0

Bei , Thema "MehrHärte beim Bürgergeld" behauptet 'Promi-Unternehmerin' Grupp-Kofler (deren Lobbyismus nie offengelegt wird) sekundiert von T. Kuban (CDU), dass "bei den meisten" Bürgergeld-Beziehenden "auch noch Schwarzarbeit" dazukomme.

Als nach 1/2 Sendung der Moderator doch mal nach Belegen für die mehrfache Lüge fragt, antwortet Kuban, es gebe da ja "solche&solche Statistiken", er wolle sich "nicht festlegen". Wahrheit, Lüge, Bauchgefühl - egal. Ein Hohn für Armutsbetroffene.

Webseite der CDU:  Werbekachel der PR-Kampagne "Meine Stimme für Merz" mit Foto von Grupp-Kofler.
0
0
0
0
0

> セクション230が失われれば、ビッグテックは議論を醸すオンライン言論(...)を問答無用で削除するようになるだろう。社会的権力を持たないマイノリティのユーザ(...)は、未来永劫、ビッグテックによってその声を奪われることになる。なぜなら、ビッグテックにはその言論にホストする価値があるかどうかを判断するインセンティブがないからだ。

セクション230:「プラットフォームの免責」はなぜ必要なのか » p2ptk[.]org

p2ptk.org/monopoly/4764

0
0

> セクション230が失われれば、ビッグテックは議論を醸すオンライン言論(...)を問答無用で削除するようになるだろう。社会的権力を持たないマイノリティのユーザ(...)は、未来永劫、ビッグテックによってその声を奪われることになる。なぜなら、ビッグテックにはその言論にホストする価値があるかどうかを判断するインセンティブがないからだ。

セクション230:「プラットフォームの免責」はなぜ必要なのか » p2ptk[.]org

p2ptk.org/monopoly/4764

0

얼굴인식 사진공유 카메라앱 슈티를 함께 만들 분을 찾습니다. 앱은 출시되어 있어 써보실수 있습니다. 이번달 내로 페디버스 연동을 끝내면 제가 생각한 MVP는 완성입니다. 앞으로도 개발해야할 부분들이 많고, 개중에 기술적으로 흥미로운 문제들도 다수 있습니다.

지금 2025년 상반기 투자유치를 목표로 팀 빌딩을 하고 있습니다. 관심 있으신 분, 또는 잘 모르겠지만 이야기를 나눠보고 싶은 분도 bgl@gwyng.com으로 편하게 연락주세요.

0