You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 30, 2023. It is now read-only.
A common complaint about the FediVerse are missing replies. Here is how to implement a "reply fetcher" in an ActivityPub Client. Usage will require a server supporting ActivityPub Client 2 Server.
Implementation Strategy
Here's how to implement this:
from bovine.activitypub import actor_from_file
actor = actor_from_file('you.toml', aiohttp.ClientSession())
# the following is awkward and should be fixed
response = await actor.proxy_element(original_url)
element = json.loads(await response.text)
The element then has a replies collection. Fetch it ... getting it with actor.get_ordered_collection might be currently possible. As the credentials used to connect to the Bovine ActivityPub Server are the same as used to other hosts. However, it would be cleaner to also proxy the elements.
A common complaint about the FediVerse are missing replies. Here is how to implement a "reply fetcher" in an ActivityPub Client. Usage will require a server supporting ActivityPub Client 2 Server.
Implementation Strategy
Here's how to implement this:
The element then has a replies collection. Fetch it ... getting it with
actor.get_ordered_collection
might be currently possible. As the credentials used to connect to the Bovine ActivityPub Server are the same as used to other hosts. However, it would be cleaner to also proxy the elements.Then repeat this for all the replies.
Once this is done build a display. It might be possible to reuse Buffalo in particular:
https://codeberg.org/helge/Buffalo/src/branch/main/src/components/timeline/DisplayConversation.js
The text was updated successfully, but these errors were encountered: