Feb 112011
 Posted by on UTC 2011.02.11Fri at 00:21 LGFYME, Uncategorized No Responses »
  • LGFEDJ: Implementation LGYUMY (of most universal solution LGUNIV to fix (Google Trends))

    1. LGFEDY: Tries to accomplish Strategy LGFEDY
    2. LGFKV8: Term, Unit, & Conversion table
      LGFL0E: Term Unit Example 1, in 2011,the search popularity of: To convert to the prior unit,multiply by To convert to
      (fingers=LGFings), multiply by
      Example 1 converted to (fingers=LGFings) to convert to LGMarms,
      multiply by
      Example 1 converted to LGMarms
      LGFPS8: I can[……]MORE
  • Feb 112011

    LGFAYS: : ,

    1. LGFB60: Overview
      1. LGFB17: An outstanding service where Google shares & graphs a lot of the trends can can be seen from the search queries they get.
      2. LGFB3D: Comprehensive, covers most any search term of any commonality.
      3. LGFB4I: Something I’ve seen other smart people use, such as searching for “jQuery” by its maker perhaps in this video.
      4. LGFB55: Something designers & leaders & anyone making a choice should likely check out.
    2. LGF3C4: Worth note, unobvious:
      1. LGF3DB: only lets[……]MORE
    Feb 102011
  • LGFBBV: To kind of universally say “how popular” something is, really need a fixed scale, as raw # of searches or other absolute scale, but how do you do that in (Google Trends)?
    1. LGFBUP: For instance, currently compared to the term “Facebook”, many/most terms score at/near 0, but of course they really aren’t 0.
    2. LGFBL7: but the tool doesn’t seem to give fixed values even with “CSV with fixed scaling” output:
      1. LGFBLI: in multi-term comparison output
        1. LGFBER: My guess is this is intentional to make it difficult to get the raw underlying data, even if[……]MORE