Recherche avancée

Sur d’autres sites (9337)

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

  
  
  

• ffmpeg h264 interesting bright video fail ?

  23 novembre 2019, par Max Paython

  I am trying streaming with ffmpeg using the information I found here.

  • Server

    ffmpeg -f dshow -i video="john":audio="doe" -vcodec libx264
    
    -preset ultrafast -tune zerolatency -acodec aac -f mpegts udp://localhost:1234

  • Client

    ffmpeg -i udp://localhost:1234?listen test.mp4

  The client will actually live stream the video, but for testing purposes I am writing the output to a file for now.

  Here comes the interesting part. I began the stream(video and audio) in a dark room, everything is fine. I turn on the room’s lights and the client cries with many errors. I later checked the output, it is very corrupted indeed on the light turned-on parts. What could be the reason behind this ? I am posting the errors here if it could be of assistance.

  Some of the errors :

  udp://localhost:1234?listen: corrupt decoded frame in stream 0trate= 845.6kbits/s dup=1250 drop=0 speed=1.08x
  
      Last message repeated 1 times
  
  [h264 @ 0000026c4af69400] Invalid NAL unit 1, skipping.7.61 bitrate= 864.7kbits/s dup=1441 drop=0 speed=1.07x
  
  [h264 @ 0000026c4af69400] Invalid level prefix
  
  [h264 @ 0000026c4af69400] error while decoding MB 18 8
  
  [h264 @ 0000026c4af69400] concealing 911 DC, 911 AC, 911 MV errors in P frame
  
  [h264 @ 0000026c4af4b780] Invalid NAL unit 1, skipping.
  
  [h264 @ 0000026c4af4b780] negative number of zero coeffs at 10 14
  
  [h264 @ 0000026c4af4b780] error while decoding MB 10 14
  
  [h264 @ 0000026c4af4b780] concealing 679 DC, 679 AC, 679 MV errors in P frame
  
  udp://localhost:1234?listen: corrupt decoded frame in stream 0
  
      Last message repeated 1 times
  
  [h264 @ 0000026c4ba1e1c0] Invalid NAL unit 1, skipping.8.21 bitrate= 858.0kbits/s dup=1460 drop=0 speed=1.07x
  
  [h264 @ 0000026c4ba1e1c0] out of range intra chroma pred mode
  
  [h264 @ 0000026c4ba1e1c0] error while decoding MB 34 18
  
  [h264 @ 0000026c4ba1e1c0] concealing 495 DC, 495 AC, 495 MV errors in P frame
  
  [h264 @ 0000026c4bb16840] top block unavailable for requested intra mode
  
  [h264 @ 0000026c4bb16840] error while decoding MB 10 0
  
  [h264 @ 0000026c4bb16840] concealing 160 DC, 160 AC, 160 MV errors in P frame
  
  udp://localhost:1234?listen: corrupt decoded frame in stream 0
  
  [h264 @ 0000026c4bb16cc0] Invalid NAL unit 0, skipping.8.58 bitrate= 853.9kbits/s dup=1463 drop=0 speed=1.06x
  
  [h264 @ 0000026c4bb16cc0] corrupted macroblock 16 28 (total_coeff=-1)
  
  [h264 @ 0000026c4bb16cc0] error while decoding MB 16 28
  
  [h264 @ 0000026c4bb16cc0] concealing 113 DC, 113 AC, 113 MV errors in P frame
  
  [h264 @ 0000026c4bb17140] cbp too large (84) at 12 0
  
  [h264 @ 0000026c4bb17140] error while decoding MB 12 0
  
  [h264 @ 0000026c4bb17140] concealing 160 DC, 160 AC, 160 MV errors in P frame
  
  [mpegts @ 0000026c4aeb8d80] PES packet size mismatch

  Edit : As suggestion, I added these parameters to the server.

  -b:v 1M -bufsize 2M

  Now the errors are mostly gone. Except one time where it seemed like it occured just as I was turning off the lights, although I could not reproduce it after trying 4-5 times.

  Errors :

  [h264 @ 000002646f0d2f80] cbp too large (118) at 23 1422.25 bitrate= 659.5kbits/s dup=368 drop=0 speed=1.33x
  
  [h264 @ 000002646f0d2f80] error while decoding MB 23 14
  
  [mpegts @ 000002646e578d80] PES packet size mismatch
  
  [h264 @ 000002646f0d2f80] concealing 666 DC, 666 AC, 666 MV errors in P frame
  
  [h264 @ 000002646f0d0f80] concealing 160 DC, 160 AC, 160 MV errors in P frame
  
  [aac @ 000002646e64d640] Number of bands (59) exceeds limit (43).
  
  Error while decoding stream #0:1: Invalid data found when processing input
  
  [aac @ 000002646e64d640] Multiple frames in a packet.
  
  [aac @ 000002646e64d640] Reserved bit set.
  
  [aac @ 000002646e64d640] Number of bands (31) exceeds limit (29).
  
  Error while decoding stream #0:1: Invalid data found when processing input
  
  [h264 @ 000002646e5e11c0] concealing 160 DC, 160 AC, 160 MV errors in P frame
  
  udp://localhost:1234?listen: corrupt decoded frame in stream 0trate= 633.1kbits/s dup=368 drop=0 speed=1.35x
  
      Last message repeated 2 times

  The errors decreased because I increased the bitrate ? (I don’t know the default bitrate by the way). Bright decoding fails because it carries more information, data ? (same in raw video, but maybe file is heavier encoded bright frames)

• Projects from behind-the-scenes

  28 septembre 2018, par Jake Thornton

  Kia ora from the marketing team !

  Marketing team ? That’s right ! You haven’t heard from us in the past, but we’ve been working in the background to create a better experience for you, our dedicated Matomo community.

  Kia ora ? Well, that just means “hello” in Maori, we’re based in New Zealand you see.

  The Matomo marketing team has some really exciting projects in the works we wanted to share with you, but first, there’s someone I want to introduce :

  Meet Joselyn from the Matomo Marketing team

  Meet Joselyn, one half of the Matomo marketing team and our Digital Marketing and Communications Specialist. Joselyn has come on board to help us communicate more frequently and effectively as we continue our mission to be the #1 free open source analytics platform in the world. Please take it away, Joselyn !

  “Hi everyone ! The team here at Matomo have been doing an incredible job passionately driving the cause for user privacy and data ownership and uniting that with a love for digital analytics. It’s exciting being a part of a team unafraid to push on with their hearts on their sleeves and their values at the forefront of everything they do. I hope to bring to light all the fantastic things happening in our world of web analytics as well as across the globe.

  

  Our online world is fascinating when we think about what we can achieve with analytics, but there’s room to improve. We see newer technologies, but old ways of working which don’t take into account a person’s safety online. So we hope to champion a new future which looks set to be much more meaningful. Ensuring you get the best experience, but also feel protected with the knowledge that we get it. Your data and privacy isn’t for sale.

  I also hear you guys, the community, have followed Matomo since the beginning, which is wonderful ! I hope you’ll be able to join us as we grow and learn. We’ve got so many thrilling things to share with you. The highs, the lows and everything in between. Cheers !”

  Thanks Joselyn ! On top of working to engage the community and new users, Joselyn will also be keeping the rest of the Matomo team on our toes getting the inside scoop on what’s happening within the Development and Support teams ; as well as giving you behind-the-scenes access to what’s going on here at Matomo. We have a big vision and with so many things happening right now, we want to get you involved as much as possible.

  It may sound a bit clichéd but I’m saying it anyway – without your help, Matomo wouldn’t be here today.

  Help us choose a logo

  So first of all, we want you to say thank you and second we’d be delighted if you could help choose our new logo ! As you may already know, we changed our name from Piwik to Matomo at the start of the year. Though it was fun using a cool font (Aileron Heavy btw) as a quick fix for our name change, it was a temporary solution. The Matomo team has been involved in the direction of creating a new logo, but now we’re stumped ! We have three different concepts to choose from so please help us out !

  Click here to logo poll

  A new website for Matomo.org !

  Other exciting marketing projects include a new website design (yay !) – to everyone gasping nervously…don’t worry, nothing in what we offer is changing. We are and always will be a freely accessible open source analytics platform, just wanted to quickly clear the air on that one !

  We also have some video projects in the works to make the Matomo experience better for everyone and there are even rumours a brand video that tells the Matomo story is on the way ;)

  What next ? With Joselyn on board and loads of exciting projects happening, it won’t be long until you hear from us again, so keep an eye out for our next update as we reveal the winning Matomo logo.

  Be sure to follow us on Facebook, Twitter and Github – we promise to be more active than what we have been !