Your comments

So I'm seeing this as like a whitelist/blacklist type thing... like we have for the profanity filter? What are the properties we would like to add:


Byline contains ___


Caption contains ___


Keywords contain ___


Section is ___


Size maybe?


Has highres?


Then these would be added as DRM rules.

Thanks! I've added a feature request for this!

Hi Caleb!


I'm sorry you were having difficulty with the documentation. This was up there before, but I'm not sure if it was removed, or what. I will alert our documentation team. =)


But, I can give you some updates / instructions to try to help you out in the meantime.


For Google Newsstand, we do indeed have a special feed for that. It is essentially just an RSS feed with an additional altf=google_newsstand parameter. Like this:


https://www.flex-showcase.bloxcms.com/search/?t=article&f=rss&altf=google_newsstand


As for Apple News, we have been working with some beta customers on a test implementation of this, to try to learn about the format and all the caveats (there are many thus far). We are still planning on doing a native integration this year, but it got shuffled around a few times and we have been delayed. It is still on our roadmap though!


I hope this helps! Thanks!

Thanks for your request! This is scheduled to be released next week.

Hey Brendan... So are these local videos posted by reporters? Why not post them to BLOX first and then share to Facebook (that way you have preroll video which you can't get on Facebook). Or, are these Live videos?

Hi Brendan! Can you give me a use case for this? What specifically are you doing with Facebook Video? Who is posting the video and why? Is this Facebook Live?

So it looks like you're mostly using BLOX videos. Just a note that if you do provide them with the straight up link to the actual mp4, you won't be getting any pre-roll ads to monetize, but you would be counted for bandwidth. So, hopefully Whiz will run pre-roll ads, or at least let you run your own.


It looks like there is a ticket dealing with this already, so we can just address the details there. We may need to customize the feed for you if it isn't supported.