Well, I was trying to expand the socket-io-plugin since it is no longer actively maintained and it is lacking features that I need. It’s an issue for which there already is an active open issue on Github. So in order to do this (amon other things) I’ll need a deeper understanding of the mechanics behind the whole request flow of Strapi. This is un-obtainable via the existing docs.
Given the lack of responses on these topics implies to me that either this kind of knowledge is lacking in the Strapi community. To me, these questions have risen to the surface, a few days in after me last Strapi project a year ago. So I don’t perceive them as very advanced use cases. Maybe it is because the more advanced users are currently more focused/interested in version 5, I dunno. Either way, all of this combined. It seems to me that not enough energy is being put in the constructing of a foundation that is required for a well-supported, community-based, open-source project, which is a pity.
Obviously I am a nobody in relation to this software, so my opinion is just that. So I am not expecting that the roadmap will take a 30 degree turn based on my experience. But nonetheless I wanted to expres the disappointment I experienced with Strapi, so the team would be aware at least that of problems that some people are running into. Then it’d be up to them what to do with it ![]()