So to truly custom mod mastadon or similar agpl things that could hide some of the secret added sauce.. you could modify the core project to call another code c

So to truly custom mod mastadon or similar agpl things that could hide some of the secret added sauce.. you could modify the core project to call another code chunk / like a wordpress plugin.. then you'd be required to release copies of your modified source which would just have a new line of code calling for 'other thing'.. it wouldn't have to include the whole 'other thing' like if you added a line bringing in recaptcha so essentially you could create right in mastadon, or similar project, but you could also break out separate things, like wordpress themes, wordpress plugins, third party addins.. Is this all right? I'm trying to remember some of the debate back in the day with licensing and WP themes and plugins and such, although I'm thinking that was a different license. It certainly seems to me like this is going to end up being a situation where there is a publicly available github thing that has nothing of interest other than a few lines calling for a few extra js calls or something for spam / moderation and not the actual code that is hidden in those addins. If this is not the case with this type of licensing I'd like to know - I've been itching to deploy a mastadon for a while now and would like to know more about restrictions. abuse vectors, all that.