Recherche avancée

Sur d’autres sites (10646)

• 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 :
  
  

  
  
  

• Anomalie #4704 (En cours) : Par sinum tri le nombre par ordre alpha

  25 mars 2021, par Maïeul Rouquette

  Soit un site avec deux articles.

  - 20. Doublon
  - 3. Article 3

  Soit le squelette suivant

  <span class="CodeRay">par sinum titre
  
  <span class="tag">span><span class="error">(</span><span class="attribute-name">ARTICLES</span><span class="error">)</span> <span class="error">{</span><span class="attribute-name">par</span> <span class="attribute-name">sinum</span> <span class="attribute-name">titre</span><span class="error">,</span> <span class="attribute-name">titre</span><span class="error">}</span><span class="tag">></span>
  
  <span class="tag"></span>#TITRE*<span class="tag"></span>
  
  <span class="tag"></span>
  
  
  
  Par num titre
  
  <span class="tag">span><span class="error">(</span><span class="attribute-name">ARTICLES</span><span class="error">)</span> <span class="error">{</span><span class="attribute-name">par</span> <span class="attribute-name">num</span> <span class="attribute-name">titre</span><span class="error">}</span><span class="tag">></span>
  
  <span class="tag"></span>#TITRE*<span class="tag"></span>
  
  <span class="tag"></span>
  
  
  
  </span></span></span>

  Le resultat est le suivant

  par sinum titre
  20. Doublon
  3. Article 3
  Par num titre
  3. Article 3
  20. Doublon

  Visiblement, contrairement à par num, par sinum ne tient pas compte du fait que 20 > 3.

• ffmpeg upload transcoded video direct to gcs bucket using node child_process.spawn

  27 mai 2021, par Dev

  I'm trying to upload transcoded video directly to GCS, but when I used pipe with FFmpeg for GCS upload it exits with code 1.

  &#xA;

  const fp = `file_path/${video_name}`;
const bc = admin.storage().bucket("test");
const fu = bc.file(fp);
const ws = fu.createWriteStream({
    metadata: {
        contentType: 'video/mp4',
        metadata: {
            name: video_name,
        },
    },
});
const transcode = new Promise((resolve, reject) => {
    const ffmpeg = spawn('ffmpeg', ['-i', `${url}`, '-codec:v', 'libx264', '-profile:v', 'main', '-vf', `scale=-2:${quality}`, '-threads', '0', '-b:a', '128k', 'pipe:1']);
    ffmpeg.stderr.on('data', (data) => {
    });
    ffmpeg.stdout.pipe(ws);
    ffmpeg.on('close', async (code) => {
        console.log(code)
        resolve();
    });
});
return transcode;


  &#xA;