You may have noticed me doing research about the technology stacks being used by #ActivityPub apps, this is because I'm involved in a couple federated projects (both of which are new use cases, and extending the #ActivityStreams format).
One of those (current dayjob) is #MoodleNet (for educators to curate educational resources together), and we now decided to use #Elixir for the back-end, which I explain in detail here:
https://docs.moodle.org/dev/MoodleNet/tech/stack
I'm open for feedback & collaboration requests!
@mayel
feel free to reach out if you are interested in incubating some of those things in upstream pleroma.
we definitely are interested in doing a lot of those same initiatives for pleroma 2.x series, especially cleaning up the AP code so that it is more modularized, as well as making it possible to run pleroma without OStatus transport and so on.
feel free to reach out if you are interested in incubating some of those things in upstream pleroma.
we definitely are interested in doing a lot of those same initiatives for pleroma 2.x series, especially cleaning up the AP code so that it is more modularized, as well as making it possible to run pleroma without OStatus transport and so on.
That's good to hear! Do you have any more details about your plans & timelines? I'll also look around the issue tracker in more detail.
i missed this somehow.
right now, we plan to release pleroma 1.0 very soon. the last few prerequisites for that are hopefully going in over the next week or two. after that, the tree is basically open for whatever.