Suggest a change

These fields are all optional and need only
be supplied if you would like a direct reply.

Subject
Your email address
Your real name

You must answer this!

If you don't, my spam filtering will
ensure that I never see your email.

What's 8 plus five (in digits only)?

Please make your changes here and then
Editing tips and layout rules.

File: AnatomyOfAHit

''' <link rel="alternate" type="application/rss+xml"
'''       href="/rss.xml" title="RSS Feed">

********> width="25%"
|>>
''' <a title="Subscribe to my feed"
'''    rel="alternate"
'''    href="https://www.solipsys.co.uk/rss.xml">
'''    <img style="border-width: 0px;"
'''         src="https://www.feedburner.com/fb/images/pub/feed-icon32x32.png"
'''         align="middle"
'''         alt="" />Subscribe!</a>
_
''' <a href="https://twitter.com/ColinTheMathmo">
''' <img src="https://www.solipsys.co.uk/new/images/TwitterButton.png"
'''      title="By: TwitterButtons.net"
'''      width="212" height="69"
'''      alt="@ColinTheMathmo"
'''     /></a>
<<|
----
My latest posts can be
found here:
  * ColinsBlog
----
Previous blog posts:
  * SellYourselfSellYourWork
  * AllTheLetters
  * BeingSlowToCriticise
  * StateMachineInRealLife
  * CoxeterOnceNerdSnipedConway
  * NotAlwaysYourFault
  * RememberingConway
  * PerceptionOfSpace
  * ParallelogramPuzzle
  * BackOfTheEnvelopeCOVID19
  * APointAgainstTheAxiomOfChoice
  * InDefenseOfTheAxiomOfChoice
  * JourneyingHomeThroughStormDennis
  * EarthRadiusRefined
  * VolumeOfASphere
  * BigOhAndRelations
  * MathematicalRelations
  * IntroducingBigOh
  * ConstantDifferences
  * AlgorithmsAndSizesOfInstances
  * IntroducingTimeComplexity
  * TheLinearFrog
  * SeventyVersusOneHundredRevisited
  * HowTheFarragoWorks
  * SeventyVersusOneHundred
  * PowersOfTwoInLexOrder
  * EmergingEExpanded
  * RageInducingSystemImplementation
  * TheBookIsNotAlwaysRight
  * EmergingE
  * ImpossibleToTranslate
  * WaitingInVain
  * NonRepeatingDecimals
  * RationalRepeats
  * WhyIsItLovely
  * CompilingCryptoConnections
  * ExploringConnectionsBetweenCryptoSystems
  * ElwynBerlekampHasLeftUs
  * RootCauseAnalysisAndThePhotocopierQuestion
  * TheUpDownTides
  * TheForeAftTide
  * TheSidewaysTide
  * WrappingUpWrappingUpTheEarth
  * TheOtherWrappingTheEarthProblem
  * WrappingTheEarth
  * TheRingOfSteel
  * RoundingUpTheRopes
  * OtherOtherOtherRopeAroundTheEarth
  * RopeAroundTheEarthRefined
  * TheOtherRopeAroundTheEarth
  * ElementaryEstimates
  * LatitudeCorrection
  * JustGiveMeTheAnswer
  * MoreMusingOnPollardRho
  * IdleThoughtsAboutPollardRho
  * WhenOptimisingCodeMeasure
  * ADogCalledMixture
  * AnotherPayPalScam
  * WhyTopPostingHasWon
  * UnexpectedInteractionOfFeatures
  * ArchimedesHatBoxTheorem
  * ConsideringASphere
  * ToLinkOrNotToLink
  * GenericAdviceForWritingAThesis
  * JustTeachMyChildTheMaths
  * NotASpectatorSport
  * LeftTruncatablePrime
  * TheDoctorAndTheLawyer
  * FourPointsTwoDistancesProof
  * MeetingRonGraham
  * NapkinRingVersusSphericalCap
  * TheFourPointsPuzzle
  * RadiusOfTheEarthPartTwo
  * GrepTimingAnomaly
  * TheRadiusOfTheEarth
  * ThisWorksToCureMyHiccoughs
  * PerhapsWeSavedOne
  * ThinkingAboutMastodon
  * DisappearingTrainsOnVirgin
  * TheIndependenceGame
  * OneOfMyFavouritePuzzles
  * ThinkingAboutRecursion
  * MemorisingTheTube
  * SpikeySpheres
  * SurprisinglyQuick
  * AnUnexpectedFraction
  * YouHaveToAdmireTheirOptimism
  * RepresentativesMatter
  * PythagorasByIncircle
  * APuzzleAboutPuzzles
  * HowNotToDoTwitter
  * Calculating52FactorialByHand
  * SmallThingsMightNotBeSoSmall
  * NotIfYouHurry
  * FactoringViaGraphThreeColouring
  * AnotherProofOfTheDoodleTheorem
  * WhenObviousIsNotObvious
  * GraphThreeColouring
  * TheDoodleTheorem
  * BeCarefulWhatYouSay
  * TheMutilatedChessboardRevisited
  * AMirrorCopied
  * TheOtherOtherRopeAroundTheEarth
  * PhotocopyAMirror
  * ThePointOfTheBanachTarskiTheorem
  * SieveOfEratosthenesInPython
  * FastPerrinTest
  * RussianPeasantMultiplication
  * FindingPerrinPseudoPrimes_Part2
  * FindingPerrinPseudoPrimes_Part1
  * TheUnwiseUpdate
  * MilesPerGallon
  * TrackingAnItemOnHackerNews
  * HackerNewsUserAges
  * PokingTheDustyCorners
  * ThereIsNoTimeForThis
  * PublicallySharingLinks
  * LearningTimesTables
  * GracefulDegradation
  * DiagrammingMathsTopics
  * OnTheRack
  * SquareRootByLongDivision
  * BeyondTheBoundary
  * FillInTheGaps
  * SoftwareChecklist
  * NASASpaceCrews
  * TheBirthdayParadox
  * TheTrapeziumConundrum
  * RevisitingTheAnt
  * TheAntAndTheRubberBand
  * IrrationalsExist
  * MultipleChoiceProbabilityPuzzle
  * RandomEratosthenes
  * WrappingUpSquareDissection
  * DissectingASquarePart2
  * DissectingACircle
  * DissectingASquare
  * AnOddityInTennis
  * DecisionTreeForTennis
  * DecisionTreesInGames
  * AMatterOfConvention
  * DoYouNourishOrTarnish
  * BinarySearchReconsidered
  * TwoEqualsFour
  * TheLostPropertyOffice
  * TheForgivingUserInterface
  * SettingUpRSS
  * WithdrawingFromHackerNews
----
Additionally, some earlier writings:
  * RandomWritings.
  * ColinsBlog2010
  * ColinsBlog2009
  * ColinsBlog2008
  * ColinsBlog2007
  * ColinsBlogBefore2007
********
Recently I found something I wrote a while ago, and with one or
two touches I thought it was worth recycling. So I refreshed it
a little and integrated it into my blog.  As is my wont I then
mentioned it in a couple of places, and went back to work.

[[[>50
Ironically, that item is about writing reports and otherwise
making public the work that you do.  Why is that ironic?  Because
this post is a report on some work I did that was caused by the
post about writing reports on work you do.
]]]
It's here: SellYourselfSellYourWork

Imagine my surprise when on
''' <a href="https://news.ycombinator.com/news" target="_blank">Hacker News</a>
(often known simply as "HN")
''' <a href="https://news.ycombinator.com/item?id=23250289" target="_blank">the item</a>
suddenly got a lot of attention. Indeed, I was *very* surprised,
and I set up some tracking to see what happened ... this is the
report.

It's worth noting that Hacker News can result in a "hug of death"
and a site going down from the traffic.  That's not very likely
in my case as the page is plain HTML, and in fact, very, /very/
elderly HTML that desperately needs bringing up to date.  But
ignoring that, I was expecting some traffic.  But the amount of
traffic depends on a few things.

Firstly, the currently ranking of the item on the Front Page.
When an item falls off the Front Page of HN the traffic plummets,
that's only to be expected. But there might be some relationship
between where the item is on the Front Page and the number of
click-throughs. Probably the data I collected probably isn't up
to that, but it might be interesting to see if we can see that.

Secondly, HN is sometimes very busy, and sometimes not so busy.
We can't measure that, but we do have a proxy.  We can look at
the age of the last item on the "Newest" page.  If that's very
young, then items are being submitted quickly, and we can assume
the site is busy.  If the $20^{th}$ item is over an hour old, we
can assume the site is /not/ very busy.

So let's start by looking at the age of the $20^{th}$ oldest
item on the "Newest" page:

''' <center><img src="https://www.solipsys.co.uk/images/HN_SYSYW_InverseActivity.png" width="80%" /></center>

We can see that over the 15 hours or so that the item was on the
Front Page HN was very busy, then not so busy, then getting busy
again.  This is measured in "Minutes Age of the $20^{th}$ Item",
and we can invert that to get "Items submitted per Hour":

''' <center><img src="https://www.solipsys.co.uk/images/HN_SYSYW_ActivityProxy.png" width="80%" /></center>

This is, as the title says, a proxy for the level of activity.

Next we can look at where the item ranks on the Front Page:

''' <center><img src="https://www.solipsys.co.uk/images/HN_SYSYW_Rank.png" width="80%" /></center>

This is a little misleading, as the rising line corresponds to
the falling item.  To that end, instead of the rank we can plot
"30 minus the rank":

''' <center><img src="https://www.solipsys.co.uk/images/HN_SYSYW_InverseRank.png" width="80%" /></center>

Interesting feature to note is that after 8 hours on the Front Page
the fall in ranking is almost linear:

''' <center><img src="https://www.solipsys.co.uk/images/HN_SYSYW_LinearFallInRanking.png" width="80%" /></center>

So what kind of traffic did this generate?  Looking at the logs
we have the following:

''' <center><img src="https://www.solipsys.co.uk/images/HN_SYSYW_Hits.png" width="80%" /></center>

We can see the huge initial spike, and the tail off at the end, but
through the range of 5 to 13 hours (or so) there is a constant
stream of 40 to 50 hits per minute.  That's consistent with the
final (so far!) tally or about 48k to 49k hits registered in the
logs.  Interestingly, the images in the page were only loaded
about half the time, so clearly there are people browsing with
"images off", which is perhaps worth knowing, but not surprising.

Also unsurprising is the drop off when the item falls from the
Front Page. That happens just after 16 hours, and you can clearly
see the drop in visits:

''' <center><img src="https://www.solipsys.co.uk/images/HN_SYSYW_Hits0.png" width="80%" /></center>

It might be an interesting exercise to plot Hits against Rank, and
try to draw out the effect of "Activity", remembering that as time
goes by, many of the visitors to the Front Page could be returning,
and hence already seen the submission.  If we assume that there's
an underlying hit rate and subtract that from the hits, then plot
the hits against the rank, perhaps there's something to be seen.
Not at all sure the existing data would warrant any conclusion on
that question, especially with the confounding factor of activity.

However, as a quick hack we can plot the different quantities on
the same chart, and scale everything to get things to match.  We
can also adjust the traces up and/or down, and see if we can get
things to line up, and then see if we can explain them. So here
we have the plots, arbitrarily scaled and vertically shifted:

''' <center><img src="https://www.solipsys.co.uk/images/HN_SYSYW_MatchedPlots.png" width="80%" /></center>

In area *A* we can see that the number of hits is following the
(proxy for the) Activity on the site, so perhaps it's simply the
number of visitors driving the hits, and we're getting some fixed
percentage of visitors clicking through.

Then in area *B* as the activity starts to pick up, the hits are
following the ranking, with a lower ranking producing fewer hits,
/etc./  That's perhaps understandable as well.

That continues through to area *C* where the uptick in activity
is producing more items submitted, and so more items that can be
ranked above this one.  As a consequence the ranking falls, and
the number of hits follows.

Finally, in area *D,* the item falls off the Front Page (probably
because it incurred the "Time Penalty") and the number of hits
falls off a cliff.

So there you are.  If you have any questions (other than "Why did
you bother?") then feel free to ping me via the comment form, or
by direct email if you have a working address for me.  If you do
contact me via the form and want an answer, don't forget to provide
a working return email address for youself!
----

|>>
| |>> <<<< Prev <<<< ---- SellYourselfSellYourWork <<| | : | |>> >>>> Next >>>> ---- AFactletForAll ... <<| |
----
********>
''' <a href="https://mathstodon.xyz/@ColinTheMathmo">
''' <img src="https://www.solipsys.co.uk/images/Mastodon_Mascot.png"
'''      width="256" height="280"
'''      alt="https://mathstodon.xyz/@ColinTheMathmo"
'''     /></a>
********
''' <a href="https://mathstodon.xyz/@ColinTheMathmo/">You can follow me on Mathstodon.</a>
_ _ _ _
[[[>
''' <a href="https://twitter.com/ColinTheMathmo">Of course, you can also<br>follow me on twitter:</a>

''' <a href="https://twitter.com/ColinTheMathmo">
''' <img src="https://www.solipsys.co.uk/new/images/TwitterButton.png"
'''      title="By: TwitterButtons.net"
'''      width="212" height="69"
'''      alt="@ColinTheMathmo"
'''     /></a>
''' <img src="/cgi-bin/CountHits.py?AnatomyOfAHit" alt="" />
]]]
********<

----

!! Send us a comment ...

''' <form action="https://www.solipsys.co.uk/cgi-bin/FormMail.pl" method=post>
''' <input type=hidden name="recipient"               value="colinsblogcomment@solipsys.co.uk" >
''' <input type=hidden name="subject"                 value="Blog comment : AnatomyOfAHit"         >
''' <input type=hidden name="redirect"                value="https://www.solipsys.co.uk/new/ThankYouForYourComment.html" >
''' <input type=hidden name="missing_fields_redirect" value="https://www.solipsys.co.uk/RequestError.html">
''' <input type=hidden name="env_report"              value="REMOTE_HOST, REMOTE_ADDR, HTTP_USER_AGENT"  >
''' <input type=hidden name="print_blank_fields"      value="1"                                          >

********> width="47%"
You can send us a message here. It doesn't get published,
it just sends us an email, and is an easy way to ask any
questions, or make any comments, without having to send a
separate email. So just fill in the boxes and then
''' <font size="+4"><INPUT TYPE="submit" VALUE="CLICK HERE TO SEND"></font>
******** width="53%"
********<

''' <table cellpadding="5">
'''   <tr>
'''     <td valign="top">Your name </td> <td valign="top">:</td>
'''     <td> <input type=text name="realname" size="48"> </td>
'''   <tr>
'''     <td valign="top">Email </td> <td valign="top">:</td>
'''     <td> <input type=text name="email" size="48"> </td>
'''     </tr>
'''   <tr>
'''     <td valign="top">Message </td> <td valign="top">:</td>
'''     <td> <TEXTAREA NAME="Message" ROWS=10 COLS=64></TEXTAREA> </td>
'''     </tr>
'''   </table>

''' <center>
'''   <font size="+4">
'''     <INPUT TYPE="submit" VALUE="CLICK HERE TO SEND">
'''     </font>
'''   </center>
''' </form>

********<