<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: fei mai</title>
    <description>The latest articles on DEV Community by fei mai (@mediadownloaderguides).</description>
    <link>https://dev.to/mediadownloaderguides</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4168281%2F94a4437c-a608-434d-830d-1ba393d1e994.png</url>
      <title>DEV Community: fei mai</title>
      <link>https://dev.to/mediadownloaderguides</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mediadownloaderguides"/>
    <language>en</language>
    <item>
      <title>I Pulled 100 Videos From Dailymotion's Trending API. Four Accounts Own Most of It.</title>
      <dc:creator>fei mai</dc:creator>
      <pubDate>Wed, 07 Oct 2026 11:52:26 +0000</pubDate>
      <link>https://dev.to/mediadownloaderguides/x-1n66</link>
      <guid>https://dev.to/mediadownloaderguides/x-1n66</guid>
      <description>&lt;p&gt;Dailymotion exposes a trending endpoint that requires no API key. I pulled 100 videos from it on October 7, 2026 — two pages of fifty — and then did the analysis that the endpoint itself does not do: I counted who was actually publishing.&lt;/p&gt;

&lt;p&gt;The result is uncomfortable for anyone who treats a "trending" feed as a proxy for platform-wide activity.&lt;/p&gt;

&lt;h2&gt;
  
  
  What the endpoint returns
&lt;/h2&gt;

&lt;p&gt;Two pages, fifty entries each. Every entry carries an id, a title, an owner, an owner id, a channel, a duration in seconds, a thumbnail, and a view count. No authentication, no rate limiting encountered at this volume.&lt;/p&gt;

&lt;p&gt;One thing worth knowing before you build on it: the &lt;code&gt;channel&lt;/code&gt; parameter does not work the way the documentation implies. Passing &lt;code&gt;channel=news&lt;/code&gt; or &lt;code&gt;channel=sport&lt;/code&gt; with a sort modifier returns a 400. The reliable path is to pull the feed whole and filter locally, which is what I did.&lt;/p&gt;

&lt;h2&gt;
  
  
  The concentration
&lt;/h2&gt;

&lt;p&gt;Twelve distinct accounts produced the hundred entries.&lt;/p&gt;

&lt;p&gt;43 videos, one account&lt;br&gt;
18 videos, a second&lt;br&gt;
9 videos, a third&lt;br&gt;
8 videos, a fourth&lt;br&gt;
6 videos, a fifth&lt;br&gt;
5 videos, a sixth&lt;br&gt;
2 videos, a seventh&lt;br&gt;
1 video each, five more accounts&lt;/p&gt;

&lt;p&gt;Four accounts account for 78 entries out of 100. Six accounts account for 89.&lt;/p&gt;

&lt;p&gt;If you had built a recommendation system on the assumption that this feed represents a broad sample of what the platform serves, the assumption fails here. This is closer to a syndication list than a ranking.&lt;/p&gt;

&lt;p&gt;The format those entries share is visible in any two of them. A 54-second micro-drama teaser, 77 views:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.dailymotion.com/video/xbhty7m" rel="noopener noreferrer"&gt;https://www.dailymotion.com/video/xbhty7m&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  A second teaser from the same cluster, same length, 33 views:
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.dailymotion.com/video/xbhrgti" rel="noopener noreferrer"&gt;https://www.dailymotion.com/video/xbhrgti&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;And the standout, from a different account entirely: a ten-minute news documentary that drew the highest view count in the hundred at just over 99 thousand plays, roughly 1,300 times the teasers above.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.dailymotion.com/video/x9o94sq" rel="noopener noreferrer"&gt;https://www.dailymotion.com/video/x9o94sq&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  The channel label tells you the same thing
&lt;/h2&gt;

&lt;p&gt;44 of the 100 entries sit in the &lt;code&gt;shortfilms&lt;/code&gt; channel. On Dailymotion that label is not a studio category, it is where user-uploaded micro-drama lands. Nearly half the feed carries it.&lt;/p&gt;

&lt;p&gt;Which means the feed's apparent diversity, sold as a ranking of videos from across the platform, is largely one format from one region of the catalogue, contributed by a small set of accounts.&lt;/p&gt;

&lt;p&gt;Two entries from outside that cluster make the contrast concrete. A seven-minute piece, 704 views:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.dailymotion.com/video/xbfge22" rel="noopener noreferrer"&gt;https://www.dailymotion.com/video/xbfge22&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  A five-and-a-half-minute motorsport recap, 7 views:
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://www.dailymotion.com/video/xbhp1j2" rel="noopener noreferrer"&gt;https://www.dailymotion.com/video/xbhp1j2&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Both sit in the same middle band the feed barely populates at all.&lt;/p&gt;

&lt;h2&gt;
  
  
  Freshness, and why it matters
&lt;/h2&gt;

&lt;p&gt;96 of the 100 entries were published within seven days of the pull. The oldest entry in the set was 2.8 days old.&lt;/p&gt;

&lt;p&gt;A trending feed that is 96 percent under a week old is not ranking accumulated interest. It is ranking what got traction this week, inside a very small set of publishers, in one format.&lt;/p&gt;

&lt;h2&gt;
  
  
  What this means if you consume the feed as a signal
&lt;/h2&gt;

&lt;p&gt;Two failure modes, both easy to fall into.&lt;/p&gt;

&lt;p&gt;Treating it as platform-wide: it is not. It is a rotating window, and this week the window is largely one account.&lt;/p&gt;

&lt;p&gt;Treating the ranking as a merit order: it is not that either. The single most-viewed entry in the hundred was a ten-minute news piece from a different account entirely, which beat every micro-drama entry by a wide margin. The feed listed it, but nothing about the ordering suggested it was the outlier it is.&lt;/p&gt;

&lt;p&gt;The useful move is to pull the feed, group by owner, and look at the distribution before you look at the list.&lt;/p&gt;

&lt;h2&gt;
  
  
  Method
&lt;/h2&gt;

&lt;p&gt;Collected from Dailymotion's public API on October 7, 2026, two pages of fifty, no key. Fields as returned. Account names shortened here for readability; the full grouped breakdown is below.&lt;/p&gt;

&lt;p&gt;Full dataset, group by owner, with every video linked: &lt;a href="https://vidmotionsave.com/" rel="noopener noreferrer"&gt;https://vidmotionsave.com/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>analysis</category>
      <category>api</category>
      <category>data</category>
      <category>webscraping</category>
    </item>
  </channel>
</rss>
