bretg

@muuki88 - I have some reservations about some details in your suggestion, but in the end I think we're close to saying the same thing: `it should be possible to...

Here's another, perhaps quicker solution to the specific use case brought up by FreeStar: ``` if s2sConfig.bidders is non-existent or empty AND a global ortb2.ext.prebid.storedrequest exists, then pbsBidAdapter will ignore...

Spoke with @nicgallardo -- seems like perhaps the 'explicit signal add PBS as a bidder' might work for them. One question is going to be about validations... should pbsBidAdapter allow...

Reviewed this thread and trying to summarize the various use cases. This is an upgrade of was done before to support the harder scenarios. Here are the assumptions: - we...

FYI - I added getUserSyncs to the list of spec entries needed by server-side adapters. client-side user syncs are still a thing for another 9 months even for server-side bidders.

@snapwich - I'm not following how dead code elimination helps here > propose a regular prebid.js and a s2s version of prebid.js A "PBJS lite" might happen eventually, but for...

> do you think it makes sense which of the modules could be moved to server side and which have to live on the client? I would say that Prebid...

I think our goal here should be to get rid of the client-side footprint altogether. Did an analysis of how transformBidParams is used - Rubicon: there was an old mismatch...

If we want to keep the javascript at a minimum, shouldn't we get rid of client-side enforcement altogether? Here are the modules that would **not** be needed in a prebid.less...

Right Muki - I was thinking of the prebid.less scenario, but we're a ways off from that. Baby steps. All of these modules are needed as long as there's client-side...