New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request - Please support ActivityPub for updates to threads #9527
Comments
Hi Derek, Could you explain how the feature would be useful to you? Do you know anyone interested in doing the development work? |
It would be similar to an RSS feed, but possible to follow from Mastodon etc. Discourse is indeed working on such limited ActivityPub support. For now as a work-around I would suggest you just use a RSS feed to Mastodon bot that should already work with Loomio. Edit: Although I can't figure out how to get the RSS/ATOM feed for the thread listing. For individual threads it seems to work by adding a |
Indeed, with regards to pace-layering an organisations activity, it is useful for groups to bridge conversations across platforms. An ActivityPub integration of Loomio would render it an equal participant in conversations that already today span multiple channels, as we see with the aforementioned Mastodon and Discourse, but also with WordPress, Pixelfed, Peertube, Owncast, WriteFreely and the likes. Offering an integration with ActivityPub allows to collect various dispersed conversation streams into more linear narratives and helps to structure web-wide conversation. Currently, I'm seeing these stories present in this thread:
If you are unsure what else ActivityPub support could be good for, please find inspiration in the replies to this recent toot: https://cosocial.ca/@evan/112185826897209052 |
My co-op uses Loomio for governance and a Mastodon server for communication. It would be great if we could see the results of polls, updates on discussions, etc, showing up our feeds. Supporting ActivityPub in the way that Discourse is now doing would be very valuable for our community.
The text was updated successfully, but these errors were encountered: