Chronotope’s avatarChronotope’s Twitter Archive—№ 92,599

  1. …in reply to @Chronotope
    I kid, I kid. I agree with nwquah - we do need to be serious and careful about our deployment of more complex ad technology to the podcast marketplace, one which I would also argue has grown in part because of the lack of 3rd party ad tech and measurement.
    1. …in reply to @Chronotope
      Hell, doubts and concerns about programmatic and IAB-qualified 'measurement' companies entering the podcast space are not only something I share, but have documented over the years: Chronotope/958828651990126592 Chronotope/773929117012094976 Chronotope/690238490647367680
      1. …in reply to @Chronotope
        But one thing has become absolutely clear to me the longer I've spent in editorial technology and slowly shifted into the biz side: these technologies *will* be developed. The money, the push, the desire, and the willingness of publishers & brands to adopt is all there.
        1. …in reply to @Chronotope
          And we already have seen what happens to journalism in a space if publishers don't lead the process of figuring out how ads and monetization works. Rampant fraud, bullshit measurement, creepy rebates, and a race to the bottom in quality - both for advertisers and publishers!
          1. …in reply to @Chronotope
            To be clear Rhapsochord isn't a podcast CMS, it approaches podcast monetization as a service, and considers itself neutral about what handles CMS-style tasks. This comes out of how we do things in the RED team and as a publisher-based ad tech shop.
            1. …in reply to @Chronotope
              We understand that publishers need and want flexibility and we built the service to provide that. We understand the paper wall and built a system that acknowledges those very important concerns.
              1. …in reply to @Chronotope
                Our team's experience from the publisher side, and our partnership with internal product & engineering teams who live and breathe audio mean we have both sides - editorial and ad operations.
                1. …in reply to @Chronotope
                  DAI is *the future* not just with audio, but with video & more. We need to step up and into this space as publishers. Not just my team. Everyone does. Which is why we opened our API standard up to discussion, starting at SRCCON schedule.srccon.org/#_session-rebuilding-ad-tech
                  OpenGraph image for schedule.srccon.org/#_session-rebuilding-ad-tech
                  1. …in reply to @Chronotope
                    We've lived through over a decade of bad technology and failed businesses that resulted from publishers allowing fear, ignorance, and distrust of the biz side to prevent us from being leaders in the ad tech space. We live in a world literally deformed by that lack of involvement.
                    1. …in reply to @Chronotope
                      But this is *why* I joined RED at WashPost to begin with. Because I believe it's not too late to save the future, by bringing our ideas, principles and ethics as publishers to the table to build the next gen of ad tech for publishers, by publishers. That includes for podcasts.
                      1. …in reply to @Chronotope
                        I suspect that nwquah and I have the exact same thoughts and concerns here, but I'm always interested in taking input and talking over ideas. I don't want to just be Twitter threading at ya. Would love to talk it over, perhaps... in a podcast? :P
                        1. …in reply to @Chronotope
                          To finish this: all the love for Nieman Lab and Hot Pod, long time reader and subscriber here. We build a better future for publishers by having these conversations and working together.


Search tweets' text