@pfaffman
Thank you for the quick response. I would like to highlight some points regarding this:
Developer resources, time, and money: Converting our logic into a plugin for Discourse undoubtedly requires developer resources, time, and financial investment. This process involves understanding the Discourse platform, adapting our logic to its structure, and implementation, all of which entail significant effort.
Maintenance and Updates: Having our own plugin means that we are responsible for long-term maintenance and regular updates. This requires additional resources and attention to ensure that the plugin functions smoothly, remains compatible with future Discourse versions, and addresses any potential security vulnerabilities. It binds resources as well.
Considering these factors, it seems to me that in the initial step, it would be more sensible to look for a simpler solution. Are there perhaps existing plugins that reload 3rd party scripts on every page change/route change?
@merefield
Do I understand you correctly that the publisher who wants to integrate an adnetwork opens a post in the marketplace threat and asks for support with the integration?