Christine,

I'll chime in on this one & extend the wishes a bit further. It would be MOST awesome if we could simply have a block that could have a form assigned to it. Block could then be place on any page. Handle all form submits via ajax so you don't have to have dedicated urls for each form, instead allow them to post to a generic behind the scene form handler that grabs the form id and then process that form accordingly. This would then allow us to embed forms everywhere, in article pages, in modals, and have much nicer design than trying to smash all kinds of html into the description area of a form.

Been wanting this for a long time :)

We've had the same issue with a number of our sites in eastern Idaho. We utilize DFP Premium to serve our ads and our partner, OS4, says that they have seen an update in these kinds of ads and are working to develop additional malware detection steps to try to block them, but they are basically remnant ads. Do you use any remnant?

@Nick, yes, you can do that by having the first block use the top story flag, and the second block require articles without the top story flag. My use case is more for "breaking news" style items that "decay" over time to no longer be breaking news. If I use flags, then its a manual operation to remove the flag.

Hiya Christine :)

Most examples are going to be tied to Flags. Another scenario might be a top story block on a page with a set of new stories below. Perhaps your rule is set up so that the top story block shows articles flagged as top story in the past day. Your story list below excludes top story so it doesn't duplicate, but it also shows the past weeks' articles. So ideally after 24 hours you'd want your top story to appear in the story list below. Currently you'd have to go in and edit the asset, remove the flag, then it would work as you wanted.

Over zealous tagging:

Good examples is one of my sports departments that tags every article with "sports", "sports/{sport}" and maybe another section tag as well for some niche version. This is obviously a management issue, but with constant turnover, one that's an ongoing challenge.

Your idea would be interesting as well. Always though the idea of a "decaying" flag would be interesting. (i.e. flag gets auto-removed after a specified number of hours).