<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Disable Explicit Songs? in Desktop (Windows)</title>
    <link>https://community.spotify.com/t5/Desktop-Windows/Disable-Explicit-Songs/m-p/1640201#M688</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.spotify.com/t5/user/viewprofilepage/user-id/3365130"&gt;@innocuous_name&lt;/a&gt; wrote:&lt;BR /&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Spotify knows that their explicit flag markers are incomplete and don't want to field the complaints. &amp;nbsp;&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;I should point out that the "Explicit" tag that is not shown in the search results in the iOS app is actually present when I view the album. So, at least for my example (and most any other test I have found), their tag exists and is correctly placed.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So while I acknowledge a "complete" solution would require community flagging as you suggest, to not offer making use of the existing metadata seems a bit... intentional. And I would not be surprised if an external service is already providing that "Explicit" tag. I doubt each music service is manually identifying tracks with adult language.&lt;/P&gt;</description>
    <pubDate>Mon, 10 Apr 2017 19:57:10 GMT</pubDate>
    <dc:creator>dmpace</dc:creator>
    <dc:date>2017-04-10T19:57:10Z</dc:date>
  </channel>
</rss>

