<![CDATA[Following a thread is now available in the latest version of #HolosSocial.]]>Following a thread is now available in the latest version of . already lets you follow an object, not only an account, so a Follow can target a post. You then receive new replies, even from accounts you do not follow. A thread is short-lived, so the Follow uses the standard endTime property to expire on its own. It works best when other servers support it, that's why I want to turn it into a .

For people curious about the idea: https://tom79.dev/posts/follow-a-note/

]]>https://bb.devnull.land/topic/52f2fb66-ce4f-49a6-af78-023c911badf4/following-a-thread-is-now-available-in-the-latest-version-of-holossocial.RSS for NodeSat, 13 Jun 2026 01:18:07 GMTFri, 12 Jun 2026 19:43:58 GMT60<![CDATA[Reply to Following a thread is now available in the latest version of #HolosSocial. on Fri, 12 Jun 2026 22:14:28 GMT]]>@silverpill
The Activity Vocabulary defines Follow on an object, while AP describes delivery and assumes an actor. Both are true at their level. My idea is not to make the Note an actor, but to let the author's actor handle the Follow for its own thread, since it already has an inbox and a key. Your observer creates a new actor per object. Mine reuses the one that already exists. Both need support on each side for real time. Polling is just my fallback when a server does not.

]]>https://bb.devnull.land/post/https://toot.fedilab.app/users/apps/statuses/116739438563831664https://bb.devnull.land/post/https://toot.fedilab.app/users/apps/statuses/116739438563831664Fri, 12 Jun 2026 22:14:28 GMT<![CDATA[Reply to Following a thread is now available in the latest version of #HolosSocial. on Fri, 12 Jun 2026 21:52:13 GMT]]>@apps ActivityPub's Follow activity is intended to be used on actors: https://www.w3.org/TR/activitypub/#follow-activity-outbox.

This is one of the reasons I proposed that "observer" actor. Another option is to use a custom activity (e.g. Watch).

]]>https://bb.devnull.land/post/https://mitra.social/objects/019ebdd2-40df-7c93-b62d-0dd05736d43dhttps://bb.devnull.land/post/https://mitra.social/objects/019ebdd2-40df-7c93-b62d-0dd05736d43dFri, 12 Jun 2026 21:52:13 GMT<![CDATA[Reply to Following a thread is now available in the latest version of #HolosSocial. on Fri, 12 Jun 2026 21:36:14 GMT]]>@silverpill
Thanks, I read your FEP. The main difference is that the Follow targets the Note directly, with no observer actor in between. It also adds two conditions: the author must be indexable, so consent is explicit, and the Follow uses endTime because a thread is short-lived. On my side, Holos falls back to polling the replies collection when a server ignores the Follow, so it keeps working everywhere.

]]>https://bb.devnull.land/post/https://toot.fedilab.app/users/apps/statuses/116739288243939151https://bb.devnull.land/post/https://toot.fedilab.app/users/apps/statuses/116739288243939151Fri, 12 Jun 2026 21:36:14 GMT<![CDATA[Reply to Following a thread is now available in the latest version of #HolosSocial. on Fri, 12 Jun 2026 21:18:57 GMT]]>@apps I wrote this FEP: https://codeberg.org/fediverse/fep/src/branch/main/fep/f06f/fep-f06f.md

Object observer is an ActivityPub actor that can be followed to receive object updates.

However, I never implemented it. Pulling context and replies is often enough.

]]>https://bb.devnull.land/post/https://mitra.social/objects/019ebdb3-ccbd-7e93-8eab-df451b51a9echttps://bb.devnull.land/post/https://mitra.social/objects/019ebdb3-ccbd-7e93-8eab-df451b51a9ecFri, 12 Jun 2026 21:18:57 GMT