I know some folks simply don't like that the handshake for https takes a little longer and for page performance reasons, prefer http.

Ideally, it would inherit whatever protocol I have on my overall library- so if I leave it "//", they are all that way, whereas if I specify "https://", they'd all be https.... though as a developer I know that's not a simple option.Alternatively, if I could specify in the Launch interface for my ad...

Something that was a potential security concern in DTM is become a breaking defect in Launch. If I have a page that doesn't load on the typical "http" or "https" protocol, I would need to specify a protocol in my embed code, so this:<script src="//assets.adobedtm.com/9310dd7d04eb33be499693ff5cc9558f...

Currently, when you upgrade an extension, you get this notice:This has scared quite a few clients off of upgrading, because there really is NO going back. Especially for Adobe extensions, there is a strong need to be able to revert in case of issues (not to be snarky, but appMeasurement/VisitorID co...

Yes, this has come up for a client of mine as well- for instance, if most of their site can be akamai-hosted, but a portion HAS to be self-hosted (for security concerns)- ideally they could reference one production environment through multiple methods.

It'd be wonderful to have a console code snippet (similar to DTM's "localStorage.setItem('sdsat_stagingLibrary', true)") or even have it added to the Launch Switcher plugin (which currently requires the user navigate to Launch's Environments page).Use case: if we want a third party to be able to tes...

I suspect Adobe is going to leave this open for someone else to develop- the joy of an open source system is everyone can wait for someone else to build it. In truth, 33 Sticks was working on making such a thing (similar to our existing pixel loader extension) when we realized it'd probably be bette...

even if I move all s.tl beacons to rules, this is still an issue.... my global variables don't fire on my s.tl rule-based beacons either.

I can see this working and is a good solution in the current set up, but I still definitely would like a way to do it without having to make sure my "global" rule gets triggered for ALL rules/beacons.

I'd imagine a potential issue with this is that your pageload/top/bottom rules won't fire on the new library... by the time you set this in the console, those triggers have already run.