3 ms·
I think going in with the DMCA was understandable. Not sure what had been done before you decide to call the reporter and Al-Jazeera out as thieves on Aug. 28:
by danso 10y ago
I think going in with the DMCA was understandable. Not sure what had been done before you decide to call the reporter and Al-Jazeera out as thieves on Aug. 28: https://twitter.com/Hiddemhigh/status/769636034749558784 https://twitter.com/Hiddemhigh/status/769636034749558784
Was that necessary? I mean, at that point, how much resistance had they been giving you? They are in the wrong no matter what you call them on Twitter, but I can see them being even more recalcitrant after that. Having worked for and with media orgs, this feels like a classic case of crossed wires and ineptitude; the vast majority of editors and reporters at Al-Jazeera and elsewhere have no clue about what copying CSS/assets mean. That is, they think of webpages as being some immutable discrete package, as if someone had sold them a video.
Being a big news org makes them move a bit slower than is ideal. Throw in the factor of this being freelance work, and then the tech component, and yeah, I could see incompetency being the reason rather than malice. I agree with the original commenter that this was a possible sales opportunity with one of the few online media orgs with actual money and runway to try out different story-telling forms and vendors. This was a needless way to antagonize them.
More importantly, you've dampened the possibilities for other relationships to news orgs. Web devs/techies at media companies, having had to deal with a decade of Web incompetency by media cos, are likely to side with the possibility that this was an honest mistake. And these web devs are already reluctant to outsource content-production/delivery to a third-party. If they're ever asked about using scrollytelling.io vs. any of the other possible vendors, this incident is not going to weigh in your favor.