@pixelcode@martin MIT does not allow re-licensing unless you’re the copyright owner (or have the permission of all copyright owners). It allows sublicensing, which would not have the protections you desire.
What you can do is license all future changes and additions under AGPL, which would create not a dual license/sublicense but a hybrid license which, for all intents and purposes, would mean your codebase will enjoy the protections of AGPL. Think of it as a poison pill, if you will :)
Gregory's Server
@pixelcode @martin MIT does not allow re-licensing unless you’re the copyright owner (or have the permission of all copyright owners). It allows sublicensing, which would not have the protections you desire.
What you can do is license all future changes and additions under AGPL, which would create not a dual license/sublicense but a hybrid license which, for all intents and purposes, would mean your codebase will enjoy the protections of AGPL. Think of it as a poison pill, if you will :)