Ariadne Conill
Ariadne Conill
yes, but you'll need to change the regex for inspircd.
you should probably verify the HOPM regex actually works. at any rate, there's some reasons why it's in .py: i don't know what damage the configparser will do to it.
i should probably add some sort of github issue template explaining that, yes. some people seem to not realize they are being duped.
pleroma.site (as well as any other Pleroma install) has ActivityPub C2S available through OAuth. You will need to use the Mastodon API to obtain client secrets for OAuth.
the correct location to make AP C2S calls is at /users/:username/inbox
@yvolk my current Pleroma tree has /api/ap/whoami for this purpose. I will deploy it on pleroma.site in a few hours. will this work for you?
I deployed that endpoint on pleroma.site.
The AP C2S whoami endpoint which allows for mapping OAuth credentials to an actor endpoint is now in Pleroma upstream. `oauthAuthorizationEndpoint` and `oauthTokenEndpoint` will be added to actors too.
Only the 3.2 _core_ protocol should be RFCized, the extensions evolve too quickly to bother with RFC workflow. So this is basically, the relevant parts of `RFC1459` plus the core...
Where we wind up then, is 3.1 with some of the corrections from 3.2, and the 3.2 wire format, as well as `ISUPPORT` and `MONITOR`. Although CTCP/DCC is an informal...