SocialHub admins can federate categories, making categories accessible in the fediverse. This is an overview of current ActivityPub actors that you can follow and participate in from the Fediverse.
This might be related, but we should probably reset all the client credentials for Mastodon servers, since they may have been revoked (like with Hachyderm) which causes an error connecting your SocialHub and Mastodon accounts. v4.3.0 and v4.2.9 removed the code that was causing OAuth Applications to be deleted (which left client applications in a broken state)
I think itâs because the previous attempts to send the posts to federation failed, and your post probably came after an upgrade that fixed the federation. My post should then federate cleanly as well.
Will you please consider changing the table here to have easy-to-copy-paste strings for the followable actors? Itâs too much work to manually build what I need to enter into my clientâŠ
(aside: I am so sad people use these completely nonstandard and non-URI ways of referring to activitypub actors when the whole spec was meant to make âhttps://â uris followableâŠ)
on the other hand, I am very excited socialhub is now followable on the fediverse. This is what we talked about at ActivityPub Conf Prague 5 years ago and itâs finally real! thanks to all who made it happen
I made the handles complete. Note that the category links are the URLs (or are there specific URLs for the actors themselves @angus, that do not appear in the UI?). You can also go there and click the button on each category to show options, such as following, etc.
Apologies for being absent here, Iâve had to focus on other work.
Thereâs a few two many messages and issues for me to parse all in one go. @how could you help me focus on the most pressing issues on this community wrt to the ActivityPub plugin? What is at the top of the list do you think?
I would say @bengoâs complaint about copy-pasting the actorâs URL might come first, since it would allow people outside Discourse connecting from a usable URL. Right now the URL is simply the one of the federated category (or else), but when pasted within Mastodon, for example, it does not show up anything useful.
Another minor annoyance I found is that remote likes are not âdocumentedâ: missing icon, no useful name nor link.
Those are from the top of my head. Iâm sure others may have stronger opinions on the interop level that I did not take the time to observe properly. Howâs the group interop going?
@angus What has been said about actor URLs also applies to post URLs.
For example the top-level post here has ID https://socialhub.activitypub.rocks/ap/object/7db3a82e730dac6957cfca7da9ac5f0b, but if you open it in the browser (with Accept: text/html) the server responds with âBad Requestâ. The expected response is a HTML representation of the post.
And the reverse: when requesting https://socialhub.activitypub.rocks/t/federated-socialhub-categories/4648/1 with Accept: <ap media type>, the server responds with 406 Not Acceptable instead of returning an AP representation of the post.
This is something Iâll be looking to work on after this big PR is merged.
Albeit, I would note that this kind of behaviour, i.e. automatic AP-to-Platform URI conversion, is (as far as Iâm aware) not part of the ActivityPub spec. In my head itâs more of a nice-to-have feature that ActivityPub power-users have gotten used to. In general Iâm a little wary of focusing on things that fit into that category. The overall sustainability of the Discourse AP plugin will, in the end, be determined by broader adoption. But, nevertheless, I am going to implement this soon.
@how +1 this I am creating a browser extension to easier interact with websites that support AP with Mastodon and rely on the Masto search API for it. Because of that it doesn't work for Discourse rn
thanks to all who made it happen
button on each category to show options, such as following, etc.