While you hosting your own reverse proxy might be too on-the-nose, it's not inconceivable that you construct the offer in such a way that it is filtered out for

While you hosting your own reverse proxy might be too on-the-nose, it's not inconceivable that you construct the offer in such a way that it is filtered out for you by an unwitting 3rd party. For example, if you make it look like an advert (which is what it is) then it would be filtered by ad blockers. There may be other "accidental" techniques for say Cloudflare. (I don't know, I don't use Cloudflare.) You're asking a judge to judge intent, when that intent could be hidden with minimal effort. On the other hand it's easier to just not use AGPL in the first place. Blanket bans on AGPL are common because at some point it's just more work than it's worth. Personally I see AGPL as a signal, "don't Saasify my code" and I'm happy to comply with that signal. Ditto GPL being "don't use in closed source". Personally I release under MIT not GPL or AGPL, because it is freeer (for some definition of free) but again that's a personal choice not a character judgement.