e dot dot dot
a mostly about the Internet blog by

April 2021
Sun Mon Tue Wed Thu Fri Sat
       
 


Content Moderation Case Study: Dealing With Podcast Copycats (2020)

Furnished content.


Summary: Since the term was first coined in 2004, podcasts have obviously taken off, with reports saying that around 55% of Americans have listened to a podcast as of early 2021. Estimates on a total number of podcasts vary, but some sites estimate the total at 1.75 million podcasts, with about 850,000 of them described as active. Still, for many years, actually hosting a podcast remained somewhat complicated.A few services have been created to try to make it easier, and one of the biggest names was Anchor.fm, which tried to make it extremely easy to create and host a podcast -- including the ability to add in an advertising-based monetization component. In early 2019, as part of its aggressive expansion into podcasts, Spotify purchased Anchor for $150 million.However, in the summer of 2020, podcasters began calling out Anchor for allowing others to re-upload copies of someone else's podcasts, claim them as their own, and monetize those other podcasts. Erika Nardini from Barstool Sports called this out on Twitter, after seeing a variety of Barstool podcasts show up on Anchor, despite not being uploaded there by Barstool.

The issue got a lot more attention a month later when podcaster Aaron Mahnke wrote a thread detailing how a variety of popular podcasts were being reuploaded to Anchor and monetized by whoever was uploading them.After that thread started to go viral, Anchor promised to crackdown on copied/re-uploaded podcasts. The company claimed that it had an existing system in place to detect duplicates, but that those doing the uploading had figured out some sort of workaround, by manually uploading the podcasts, rather than automating the effort:
The copycats, Mignano says, found a workaround in Anchor's detection system. This is definitely a new type of attack for Anchor, he says. The people who uploaded these copycat shows downloaded the audio from another source, manually reuploaded it to Anchor, and filled in the metadata, essentially making it appear to be a new podcast.This manual process, he says, makes uploading copycat shows more time-intensive and therefore less appealing and only achievable on a small scale. He says the company found a few dozen examples out of the more than 650,000 shows uploaded to Anchor this year. (In contrast, people can also upload shows more automatically by pasting an RSS feed link into Anchor, but the company would seemingly detect if someone tried to upload a popular show's feed and pass it off as their own.)The good news is that so many creators are using Anchor, and that growth has been far more than I think we projected, which is great, but I think the downside in this case is that, with any rapidly growing platform, that has brought on some growing pains and we need to do a better job of anticipating things like this, he says. We're working right now to ensure that our copycat detection and creator outreach continues to improve to keep pace.
Decisions to be made by Anchor/Spotify:
  • How do you detect which podcasts are copies from elsewhere, especially when the original versions may not have originated on Anchor?
  • People can always work around attempts to block copycats, so what kind of review process can be put in place to prevent abuse?
  • Will being too aggressive at preventing abuse potentially lead to taking down too much? For example, what if one podcast uses clips from another for the purpose of commentary?
  • Should there be extra validation or other hurdles to turn on monetization?
Questions and policy implications to consider:
  • What are the trade-offs in making it especially easy to host, distribute and monetize podcasts? Is it worth making it so easy when that process will likely be abused?
  • Is there a middle ground that allows for the easy creation, distribution and monetization of audio content that won't be as subject to abuse?
  • Is there a risk that cracking down on copycat content itself could go too far and silence commentary and criticism?
While Anchor/Spotify continue to update their practices, in the midst of all of this, another story came out (with less attention) showing how being too aggressive in stopping copycats can also backfire. This story actually came out a month before Anchor said it would beef up its process for stopping copycats, and involved a podcaster who wanted to test out Anchor to see if he should recommend it on his own podcast. That podcaster, Jonathan Mendonsa, posted a test episode to Anchor to see how it works, only to have his entire account shut down with no explanation or notice.Mendonsa was surprised to find out that Anchor was comparing audio he uploaded to Anchor to audio uploaded elsewhere, and felt that the decision to completely shut down his account immediately was perhaps a step too far. From the story at PodNews:
Jonathan told Podnews: I was testing Anchor to see if I would recommend it to my podcast course students. This duplicate content" caused them to not only take down the episode but to actually shut down my account entirely without no recourse or notice. What does that mean when a podcaster wants to republish an old episode? Or use a clip from another episode?"For this show to have been pulled within two hours of posting must mean that Anchor is automatically comparing audio uploaded to their platform with all audio already available on Spotify - since this audio was identical to an episode already there.Anchor needs to clarify the tech they are using, and what triggers this, Jonathan told us. I never considered that any podcast platform would be looking for duplicate content, so I just used the same trailer. I wouldn't be mad if it got flagged or the episode got unpublished - but to delete the entire account?
It's interesting to note the challenges on both sides of this issue, with some being upset that Anchor makes it too easy to distribute duplicate content, and others being upset at how quickly and aggressively it responds to duplicate content.Originally posted to the Trust & Safety Foundation website.

Read more here

posted at: 12:00am on 10-Apr-2021
path: /Policy | permalink | edit (requires password)

0 comments, click here to add the first



Khloe Kardashian Streisands A Photo She Wanted Taken Down By Issuing Takedowns

Furnished content.


The Kardashians are no strangers to Techdirt's pages. Being comprised of family members who are by and large famous for being famous, the Kardashians have been notorious for a heavy-handed approach to policing their own images, often times through spurious claims on intellectual property or publicity rights. So, heading into this story, it should be noted that the default posture of this particular family tends to be the use of IP claims to police anything to do with the family's image on the internet.But, as readers of this site will recognize, often times these policing attempts have the opposite of the intended effect. This certainly seems to be the case with Khloe Kardashian's recent attempts to rid the internet world of a un-touched photo of her poolside.

The alleged leaked photo pictured Kardashian smiling in a swimsuit. Many previously criticized Kardashian on social media for her attempts to remove it online after it was leaked, suggesting she was contributing to body image issues by hiding the unfiltered photo. In her post, Kardashian said she thought the leaked photo of herself was "beautiful" but she is entitled to want it removed."When someone takes a photo of you that isn’t flattering in bad lighting or doesn’t capture your body the way it is after working so hard to get it to this point, you should have every right to ask for it to not be shared - regardless of who you are," she wrote.
That... isn't how copyright law actually works, though. And it was copyright Khloe's team used to issue takedown requests to all kinds of sites, including Reddit and Twitter. According to her team, the photo was shot at a Kardashian residence and was "accidentally uploaded" to the internet by "an assistant." Left unsaid are some important details when it comes to the copyright question. Some reports indicate that the takedown notices were issued by Khloe's grandmother, who reportedly took the photo. When the family assistant uploaded it on accident, it was done so without authorization. A mistake. But once that was done, it's unclear how sharing the post via retweets and social media somehow is a copyright violation subject to a DMCA notice.But that isn't really the point of this post. Instead, this is a story of a classic Streisand Effect in action. Due in large part to the efforts to disappear the photo, it's now in much wider circulation on the internet, including in posts from news organizations where any takedown request made by the Kardashians would run straight into the First Amendment. And so now the photo Khloe wanted disappeared is all over the place.
After circulating for about two days, the image is likely experiencing the Streisand Effect, where the effort to suppress information — a story, a video or a picture — only amplifies it further.
Now, I am not including the photo in question here for multiple reasons. First, I don't need it to get the point of the post across. Second, in recent comments, Khloe has indicated that part of the reason for her wanting the photo gone is that she has struggled with body image issues in her life and I have enough respect for that to not want to add to it.But that's kind of the point, right? Other media sources are showing the photo as part of the news coverage of all of this, which is the exact opposite reality that Khloe was attempting to achieve with the aggressive takedowns of the photo elsewhere. Sometimes, it seems, it's a better strategy to simply let a story die rather than amplify it by trying to kill it.

Read more here

posted at: 12:00am on 10-Apr-2021
path: /Policy | permalink | edit (requires password)

0 comments, click here to add the first



April 2021
Sun Mon Tue Wed Thu Fri Sat
       
 







RSS (site)  RSS (path)

ATOM (site)  ATOM (path)

Categories
 - blog home

 - Announcements  (0)
 - Annoyances  (0)
 - Career_Advice  (0)
 - Domains  (0)
 - Downloads  (3)
 - Ecommerce  (0)
 - Fitness  (0)
 - Home_and_Garden  (0)
     - Cooking  (0)
     - Tools  (0)
 - Humor  (0)
 - Notices  (0)
 - Observations  (1)
 - Oddities  (2)
 - Online_Marketing  (0)
     - Affiliates  (1)
     - Merchants  (1)
 - Policy  (3743)
 - Programming  (0)
     - Bookmarklets  (1)
     - Browsers  (1)
     - DHTML  (0)
     - Javascript  (3)
     - PHP  (0)
     - PayPal  (1)
     - Perl  (37)
          - blosxom  (0)
     - Unidata_Universe  (22)
 - Random_Advice  (1)
 - Reading  (0)
     - Books  (0)
     - Ebooks  (0)
     - Magazines  (0)
     - Online_Articles  (5)
 - Resume_or_CV  (1)
 - Reviews  (2)
 - Rhode_Island_USA  (0)
     - Providence  (1)
 - Shop  (0)
 - Sports  (0)
     - Football  (0)
          - Cowboys  (0)
          - Patriots  (0)
     - Futbol  (0)
          - The_Rest  (0)
          - USA  (0)
 - Technology  (1049)
 - Windows  (1)
 - Woodworking  (0)


Archives
 -2024  March  (164)
 -2024  February  (168)
 -2024  January  (146)
 -2023  December  (140)
 -2023  November  (174)
 -2023  October  (156)
 -2023  September  (161)
 -2023  August  (49)
 -2023  July  (40)
 -2023  June  (44)
 -2023  May  (45)
 -2023  April  (45)
 -2023  March  (53)
 -2023  February  (40)


My Sites

 - Millennium3Publishing.com

 - SponsorWorks.net

 - ListBug.com

 - TextEx.net

 - FindAdsHere.com

 - VisitLater.com