Recherche avancée

Sur d’autres sites (7526)

• Cloaked Archive Wiki

  16 mai 2011, par Multimedia Mike — General

  Google’s Chrome browser has made me phenomenally lazy. I don’t even attempt to type proper, complete URLs into the address bar anymore. I just type something vaguely related to the address and let the search engine take over. I saw something weird when I used this method to visit Archive Team’s site :

  
  
  

  There’s greater detail when you elect to view more results from the site :

  
  
  

  As the administrator of a MediaWiki installation like the one that archiveteam.org runs on, I was a little worried that they might have a spam problem. However, clicking through to any of those out-of-place pages does not indicate anything related to pharmaceuticals. Viewing source also reveals nothing amiss.

  I quickly deduced that this is a textbook example of website cloaking. This is when a website reports different content to a search engine than it reports to normal web browsers (humans, presumably). General pseudocode :

  PLAIN TEXT

  C :

  1. if (web_request.user_agent_string == CRAWLER_USER_AGENT)
  2.  return cloaked_data ;
  3. else
  4.  return real_data ;

  You can verify this for yourself using the wget command line utility :

  <br />
$ wget --quiet --user-agent="<strong>Mozilla/5.0</strong>" \<br />
 http://www.archiveteam.org/index.php?title=Geocities -O - | grep \&lt;title\&gt;<br />
&lt;title&gt;GeoCities - Archiveteam&lt;/title&gt;

  $ wget —quiet —user-agent="Googlebot/2.1"
  http://www.archiveteam.org/index.php?title=Geocities -O - | grep \<title\>
  <title>Cheap xanax | Online Drug Store, Big Discounts</title>
  

  I guess the little web prank worked because the phaux-pharma stuff got indexed. It makes we wonder if there’s a MediaWiki plugin that does this automatically.

  For extra fun, here’s a site called the CloakingDetector which purports to be able to detect whether a page employs cloaking. This is just one humble observer’s opinion, but I don’t think the site works too well :
  
  

  
  
  

• Separate stereo audio file into 3 files containing Left, Center, and Right with FFMPEG

  11 mai 2022, par user319249

  I'm not looking to separate a stereo track into L/R. Most rock is mixed LCR and some applications have the ability to isolate vocals this way since vocals tend to be mixed in the Center.

  &#xA;

  Can FFMPEG separate a stereo audio file into three files containing hard right, hard left, and center ?

  &#xA;

• avformat/movenc : don't use mono layout when a front center label is expected

  28 mars 2022, par James Almer

  avformat/movenc : don't use mono layout when a front center label is expected
  On output streams where a multichannel stream needs to be stored as one track
  
  per channel, each track will have a channel layout describing the position of
  
  the channel they contain. For the track with front center, the mov muxer was
  
  using the mov layout "mono" instead of the label for the front center position.
  Since our channel layout API considers front center == mono, we need to do some
  
  heuristics. To achieve this, we make sure all audio tracks contain streams with
  
  a single channel, and only one of them is front center. In that case, we write
  
  the front center label instead of signaling mono layout.
  Fixes the last part of ticket #2865
  Signed-off-by : James Almer <jamrial@gmail.com>
  

  • [DH] libavformat/movenc.c
  • [DH] libavformat/movenc.h