5 ms·
This seems way more embarrassing to storytelling.io. The only take aways I have are how easy it is to switch to a free, open source alternative, and how loudly
by echelon 10y ago
This seems way more embarrassing to storytelling.io. The only take aways I have are how easy it is to switch to a free, open source alternative, and how loudly and publicly storytelling will complain about you. They should have handled this matter in private instead of blogging about it.
- AndyNemmity 10y agoAbsolutely. They handled it like they took joy in catching someone out publicly, and really tried to rub their nose in it. The end result is, I now know there is an open source alternative, and if the need were to arise would use it.
- danso 10y agoThis felt like a completely pyrrhic victory. Not only did they expose how unnecessary their own product was, but they exposed how unprofessional of a shop they were by leveling accusations over Twitter [0]. I'll take scrollytelling at their word that they were doing this to take a stand for software copyright. Sure, I can respect that. But if you're fighting for a world where SaaS/PaaS developers are properly paid and valued, the most convincing victories are when developers (particularly ones that depend on open-source) and such platforms attract loyal, deep-pocketed clients who show everyone else that such a business can be viable. This isn't like the case when The Oatmeal burned the HuffPo [1] for hotlinking. The Oatmeal presumably doesn't survive by syndicating to places like Huffpo. But clients who are somewhat unskilled at web production/hosting are the sole source of potential customers for ScrollyTelling, and ScrollyTelling demonstrated that it would rather burn them than mediate technical fuckups. [0] https://twitter.com/Scrollytellio/status/769971459263459328 https://twitter.com/Scrollytellio/status/769971459263459328 [1] https://www.theguardian.com/media/2015/oct/28/cartoonist-the-oatmeal-trolls-huffpo-over-images-published-sans-permission https://www.theguardian.com/media/2015/oct/28/cartoonist-the... edit: fixed typo in Oatmeal/Huffpo
- pyre 10y ago> ScrollyTelling demonstrated that it would rather burn them than mediate technical fuckups. From what I understand, they tried contacting them directly, but were given lots of promised callbacks / actions that never materialized. Is your opinion that the "professional" way to handle that just to ignore it and move on?
- mangeletti 10y ago> just to ignore it and move on? No. That's what courts are for. This notion that you (in the general sense) should publicly shame businesses and people over private concerns is absurd.
- pyre 10y agoOn the other hand, the idea that large entities should be able to get away with "small" transgressions just because it would be too costly than is worth it to pursue litigation isn't exactly the best situation either. I'm not saying that's the case here, but I can definitely see people at a large company working that sort of logic into their decision-making process. If all they had to do was ignore the "small guy" and he would eventually go away (due to the cost of long-protracted legal battle against an opponent with deep pockets), then they would.
- danso 10y agoI asked them on Twitter what the timeline was for the DMCA and they never replied. Their original post is vague on the timeline of when they attempted friendly contact and to whom: https://twitter.com/dancow/status/777702314475819009 https://twitter.com/dancow/status/777702314475819009 The earliest public Tweet I see about the issue is this, on Aug. 28, just a few weeks ago: https://twitter.com/Scrollytellio/status/769971299317911552 https://twitter.com/Scrollytellio/status/769971299317911552 So it looks like they've been emailing them at least before Aug. 28. But I disagree with the idea that there's nothing in between polite private emailing and then hostile subtweeting. Did Scrollytelling try the kind of gentle public shaming where they direct mention a few AJ editors about the matter? I don't see it. Don't get me wrong, no matter what their intentions, AJ was in the wrong to host copyrighted frontend code, and in an ideal world, the wronged party shouldn't have to Google for Twitter contacts to get them to comply. But we don't live in an ideal world of instant feedback and retribution. Scrollytelling has the right, of course, to blow it up as they did. I'm just pointing out that it was not just limited to surrender vs. going nuclear on the blogosphere. And in the media world, media people are very quick to act on Twitter, even when they don't respond to emails. I once complained on Twitter about WSJ's paywall and immediately got a response from the executive editor of the WSJ. It ended up with him blocking me for probably being snarky, but the point is that media people up the chain can be reachable without Herculean effort. And if you are a company whose customer base is completely reliant on media clients, it seems prudent to go for the constructive public outreach way rather than jumping right into "FUCK YOU PAY ME" discourse, especially when it seems that incompetence and not malice is the cause.
- h1d 10y agoWow, accusing the victim. I'm sure they're in business when they have something beyond other free alternatives or else they won't exist.
- ben_jones 10y agoArguments between people are best kept off Twitter, period. Once they get on Twitter not only are both sides forced to become defensive but the Twitter mob / cult of popular uninformed opinion gets involved and rocks start getting thrown. Adults should know better. If Al Jazeera did not respond to private inquiry THEN perhaps it would be justified to use a public medium (as that would be the only medium available) but that did not happen.
- h1d 10y agoThe initial article says they contacted AJ over multiple channels but got no resolving replies and then went public.
- Twirrim 10y agoAl Jazeera didn't respond to private inquiry. They kept brushing them off, promising to return calls and not actually returning the call.
- res0nat0r 10y agoOver what period of time? It seems like many of these Twitter shamings happen after someone doesn't respond within 48 hours or some silly arbitrary small timeline and then said company likes to rush to Twitter to try and get the mob to sort it out for them.
- dismantlethesun 10y agoAbout 15 days. They started contact on August 28th. It's not that long in the business world, I'd personally wait about 90 days before making a public stink about anything except something that'd terminate my company before then.
- SCdF 10y agoTheir name is apparently "scrollytelling", not storytelling. FWIW I misread it as that the first time this issue aired, I only just noticed it this time around.
- eatbitseveryday 10y agoPerhaps people typing on their mobile devices have auto-correct change the spelling.
- mrgoldenbrown 10y agoThey tried to handle it privately and were rebuffed: "we exhaustively tried to resolve the situation amicably, but our friendly requests over multiple channels were ignored. The DMCA request was our last resort." (from the first article)
- AndyNemmity 10y agoThey contacted Hidde who was the person who did this, and he said he would take care of it. They then moved on to AJ whom they have no relationship with. They got a response back, but not to the speed they wanted. No idea how long this was from the article.
- mariuolo 10y agoHow? Do you think the infringing code would have been removed without public shaming? Not necessarily out of malice, but in large organisations these matters tend to be forgotten or idle for a long time. Anyway they did try to settle things amicably, to no avail.
- danso 10y agoI agree that it seems to be a case of miscommunication and It's-not-my-job syndrome at AJ and its partners. But unless there's a huge burden in hosting costs -- and the fact that scrollytelling didn't break the hotlinks (nevermind that the story didn't seem widely shared in the first place) seems to suggest that they weren't huge -- it doesn't seem necessary to escalate this in the way that it was. Maybe I'm missing something, but the first public tweet regarding this matter is this: https://twitter.com/Scrollytellio/status/769971299317911552 https://twitter.com/Scrollytellio/status/769971299317911552 > @Hiddemhigh poor form to actively link to a stolen ripoff of our code. cc @martijnvtol I've had luck communicating with media folks by prodding them on Twitter, e.g. "Hey @editor, who is the best person to talk about etc etc". Did ScrollyTelling do that? Was it necessary to jump from private prodding to hostile accusation via subtweet?
- ben_jones 10y agoI took an ethics course a few years ago and we had many discussions on what were the pragmatic options for improving ethics around the world. One of the most popular was "public shaming" both for governments and corporations. My problem with this was the fact that governments and corporations are always made by people and a public shaming campaign would always end up as a witch hunt of a particular person. When an individual witch hunt is combined with a relatively misinformed mass of people the outcome is often unjust and can lead to violence, that because it was 'approved' by the masses, is deemed ok. I don't think it is. Now in this case the public shaming seems tame and does not seem to have devolved to individual witch hunts. But look no further then 'dongle gate' where a single twitter post led to two relatively innocent people being fired (neither intended the consequences of their actions IMO) and you can see where public shaming in general gets us.
- lima 10y agoProps to them for mentioning Pageflow though. They could have said "an open source alternative" instead.
- ralfd 10y ago> They should have handled this matter in private instead of blogging about it. But they tried that first? From the first blog post: > Hidde promised to resolve the situation. In addition we contacted you directly too. After waiting patiently we received no response. After many tries through your editorial office we got hold of an editor who promised to return our call. This never happened either. As a final measure we sent you a DMCA takedown request and waited patiently. No response.
- tilsammans 10y agoThe value we add is not in the software we use. Far from it. RedHat does just fine too, even if you can download the distribution for free. There's room for both models. Besides, it's far from a secret that we're standing on the shoulders of Pageflow. It's on our homepage, and we have a good relationship with them. We are overall #5 contributor to Pageflow: https://github.com/codevise/pageflow/graphs/contributors https://github.com/codevise/pageflow/graphs/contributors Al-Jazeera had been using Pageflow for a long time and it's great that they continue doing so. This outcome is perfect as far as we are concerned!
- ultramancool 10y agoYeah, honestly I wouldn't be surprised if Al-Jazeera thought they were using the open source version and were in the clear legally and thought the whole DMCA was a bogus attempt to extort them.
- DjangoReinhardt 10y agoI feel like I should point out that their name isn't storytelling but I also feel like I shouldn'tdo that... :/