ActivityPub client development is coming along!
-
ActivityPub client development is coming along!
AP platform developers be warned, I be opening issues in your repo soon.
-
ActivityPub client development is coming along!
AP platform developers be warned, I be opening issues in your repo soon.
sorry Pleroma devs, I just opened up a 2nd #c2s issue in barely a week, and I have no idea what the project capacity is.
-
sorry Pleroma devs, I just opened up a 2nd #c2s issue in barely a week, and I have no idea what the project capacity is.
@django if there are any updates to make to this issue on #ActivityPub #C2S .. do not hesitate to comment :)
https://codeberg.org/fediverse/delightful-fediverse-apps/issues/130
-
undefined hongminhee@hollo.social shared this topic on
-
@django if there are any updates to make to this issue on #ActivityPub #C2S .. do not hesitate to comment :)
https://codeberg.org/fediverse/delightful-fediverse-apps/issues/130
@smallcircles will do!
-
undefined evan@cosocial.ca shared this topic on
-
ActivityPub client development is coming along!
AP platform developers be warned, I be opening issues in your repo soon.
@django Have you tried Oni? https://git.sr.ht/~mariusor/oni
It supports ActivityPub client API and is actively developed
-
@django Have you tried Oni? https://git.sr.ht/~mariusor/oni
It supports ActivityPub client API and is actively developed
@silverpill I did try back in september, I need to try it again! thx
-
@silverpill I did try back in september, I need to try it again! thx
-
sorry Pleroma devs, I just opened up a 2nd #c2s issue in barely a week, and I have no idea what the project capacity is.
@django
>c2s
But why though? Basically nothing uses that besides an android app that probably hasn't been update in 5+ years. -
@django
>c2s
But why though? Basically nothing uses that besides an android app that probably hasn't been update in 5+ years.@django Apparently AndStatus is still developed, so it is still used by something. That said the c2s interface in Pleroma was to be turned off by default I think due to lack of maintenance and recent security issues discovered in it. -
@django Apparently AndStatus is still developed, so it is still used by something. That said the c2s interface in Pleroma was to be turned off by default I think due to lack of maintenance and recent security issues discovered in it.
@phnt I saw the issue. Do you know if it has been confirmed? (The timing is unfortunate)
-
@phnt I saw the issue. Do you know if it has been confirmed? (The timing is unfortunate)
@django There has been some talk about it around the 2.9.1 release months ago iirc, but nothing since. One of the Akkoma maintainers also disclosed recently some information disclosure issues that might affect c2s, so the subject might come up again. But if someone is willing to maintain it and fix issues, it will probably likely stay.
Not sure if Akkoma still has support for it enabled since they have a habit of removing features and options from BE. -
@django There has been some talk about it around the 2.9.1 release months ago iirc, but nothing since. One of the Akkoma maintainers also disclosed recently some information disclosure issues that might affect c2s, so the subject might come up again. But if someone is willing to maintain it and fix issues, it will probably likely stay.
Not sure if Akkoma still has support for it enabled since they have a habit of removing features and options from BE.@phnt I asked about C2S support in their issue queue, and they said they had more or less ripped everything C2S out of the codebase. The vulnerability was reported to Pleroma a few days later 🫤
-
@django
>c2s
But why though? Basically nothing uses that besides an android app that probably hasn't been update in 5+ years.phnt@fluffytail.org fwiw some of us AP devs have identified that end user applications may not be the ideal (or even the only) use case for C2S.
A more interesting approach would be to pair it with OAuth2 authentication and use the C2S API as a transport layer in a server to server context. Performing actions on behalf of another user.
A more traditional API (e.g. Mastodon API) would be used to communicate with end user apps/sessions etc.
-
Yeah a few of us had a good chat about that approach at the last #fediforum and we're now prototyping that in Bonfire at the moment, as a way to easily add federation capability to non-federated webapps (eg. for an events/calendar app to publish events by just POSTing a JSON with the event info via C2S to a bonfire server).