Search (7 results, page 1 of 1)

0.021547427 = product of:
  0.043094855 = sum of:
    0.043094855 = product of:
      0.08618971 = sum of:
        0.08618971 = weight(_text_:22 in 6021) [ClassicSimilarity], result of:
          0.08618971 = score(doc=6021,freq=2.0), product of:
            0.15912095 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045439374 = queryNorm
            0.5416616 = fieldWeight in 6021, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=6021)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Ariadne. 1999, no.22

0.017854942 = product of:
  0.035709884 = sum of:
    0.035709884 = product of:
      0.07141977 = sum of:
        0.07141977 = weight(_text_:i in 2548) [ClassicSimilarity], result of:
          0.07141977 = score(doc=2548,freq=8.0), product of:
            0.17138503 = queryWeight, product of:
              3.7717297 = idf(docFreq=2765, maxDocs=44218)
              0.045439374 = queryNorm
            0.41672117 = fieldWeight in 2548, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              3.7717297 = idf(docFreq=2765, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2548)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Page Rank is a topic much discussed by Search Engine Optimisation (SEO) experts. At the heart of PageRank is a mathematical formula that seems scary to look at but is actually fairly simple to understand. Despite this many people seem to get it wrong! In particular "Chris Ridings of www.searchenginesystems.net" has written a paper entitled "PageRank Explained: Everything you've always wanted to know about PageRank", pointed to by many people, that contains a fundamental mistake early on in the explanation! Unfortunately this means some of the recommendations in the paper are not quite accurate. By showing code to correctly calculate real PageRank I hope to achieve several things in this response: - Clearly explain how PageRank is calculated. - Go through every example in Chris' paper, and add some more of my own, showing the correct PageRank for each diagram. By showing the code used to calculate each diagram I've opened myself up to peer review - mostly in an effort to make sure the examples are correct, but also because the code can help explain the PageRank calculations. - Describe some principles and observations on website design based on these correctly calculated examples. Any good web designer should take the time to fully understand how PageRank really works - if you don't then your site's layout could be seriously hurting your Google listings! [Note: I have nothing in particular against Chris. If I find any other papers on the subject I'll try to comment evenly]

0.015307425 = product of:
  0.03061485 = sum of:
    0.03061485 = product of:
      0.0612297 = sum of:
        0.0612297 = weight(_text_:i in 3891) [ClassicSimilarity], result of:
          0.0612297 = score(doc=3891,freq=12.0), product of:
            0.17138503 = queryWeight, product of:
              3.7717297 = idf(docFreq=2765, maxDocs=44218)
              0.045439374 = queryNorm
            0.35726398 = fieldWeight in 3891, product of:
              3.4641016 = tf(freq=12.0), with freq of:
                12.0 = termFreq=12.0
              3.7717297 = idf(docFreq=2765, maxDocs=44218)
              0.02734375 = fieldNorm(doc=3891)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Content

"Let us start with your positive experiences with Google. I have known Google longer than most. At Opera, we were the first to add their search into the browser interface, enabling it directly from the search box and the address field. At that time, Google was an up-and-coming geeky company. I remember vividly meeting with Google's co-founder Larry Page, his relaxed dress code and his love for the Danger device, which he played with throughout our meeting. Later, I met with the other co-founder of Google, Sergey Brin, and got positive vibes. My first impression of Google was that it was a likeable company. Our cooperation with Google was a good one. Integrating their search into Opera helped us deliver a better service to our users and generated revenue that paid the bills. We helped Google grow, along with others that followed in our footsteps and integrated Google search into their browsers. Then the picture for you and for opera darkened. Yes, then things changed. Google increased their proximity with the Mozilla foundation. They also introduced new services such as Google Docs. These services were great, gained quick popularity, but also exposed the darker side of Google. Not only were these services made to be incompatible with Opera, but also encouraged users to switch their browsers. I brought this up with Sergey Brin, in vain. For millions of Opera users to be able to access these services, we had to hide our browser's identity. The browser sniffing situation only worsened after Google started building their own browser, Chrome. ...
How should Google be regulated? We should limit the amount of information that is being collected. In particular we should look at information that is being collected across sites. It should not be legal to combine data from multiple sites and services. The fact that these sites and services are using the same underlying technology does not change the fact that the user's dealings is with a site at a time and each site should not have the right to share the data with others. I believe this the cornerstone of laws in many countries today, but these laws need to be enforced. Data about us is ours alone and it should not be possible to sell it. We should also limit the ability to target users individually. In the past, ads on sites were ads on sites. You might know what kind of users visited a site and you would place tech ads on tech sites and fashion ads on fashion sites. Now the ads follow you individually. That should be made illegal as it uses data collected from multiple sources and invades our privacy. I also believe there should be regulation as to how location data is used and any information related to our mobile devices. In addition, regulators need to be vigilant as to how companies that have monopoly power use their power. That kind of goes without saying. Companies with monopoly powers should not be able to use those powers when competing in an open market or using their monopoly services to limit competition."

0.0123128155 = product of:
  0.024625631 = sum of:
    0.024625631 = product of:
      0.049251262 = sum of:
        0.049251262 = weight(_text_:22 in 1149) [ClassicSimilarity], result of:
          0.049251262 = score(doc=1149,freq=2.0), product of:
            0.15912095 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045439374 = queryNorm
            0.30952093 = fieldWeight in 1149, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=1149)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

17.12.2013 11:02:22

0.0123128155 = product of:
  0.024625631 = sum of:
    0.024625631 = product of:
      0.049251262 = sum of:
        0.049251262 = weight(_text_:22 in 4996) [ClassicSimilarity], result of:
          0.049251262 = score(doc=4996,freq=2.0), product of:
            0.15912095 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045439374 = queryNorm
            0.30952093 = fieldWeight in 4996, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=4996)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

19. 2.2019 17:22:00

0.00769551 = product of:
  0.01539102 = sum of:
    0.01539102 = product of:
      0.03078204 = sum of:
        0.03078204 = weight(_text_:22 in 2564) [ClassicSimilarity], result of:
          0.03078204 = score(doc=2564,freq=2.0), product of:
            0.15912095 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045439374 = queryNorm
            0.19345059 = fieldWeight in 2564, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2564)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

16. 1.2016 10:22:28

0.00769551 = product of:
  0.01539102 = sum of:
    0.01539102 = product of:
      0.03078204 = sum of:
        0.03078204 = weight(_text_:22 in 2565) [ClassicSimilarity], result of:
          0.03078204 = score(doc=2565,freq=2.0), product of:
            0.15912095 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.045439374 = queryNorm
            0.19345059 = fieldWeight in 2565, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2565)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

16. 1.2016 10:22:28