Hi. Thanks for the article! We faced the same problem with our product, but used some coding+twitter to get around it. I wrote a post about it, so you’re invited to read and comment!