Target Audience

I don’t write simply to find things out, although curiosity is my primary motivator, as I find I want to read something which hasn’t been written—“…I realised that I wanted to read about them what I myself knew. More than this—what only I knew. Deprived of this possibility, I decided to write about them. Hence this book.”¹ There are many benefits to keeping notes as they allow one to accumulate confirming and especially contradictory evidence², and even drafts can be useful so you Don’t Repeat Yourself or simply decently respect the opinions of mankind.

The goal of these pages is not to be a model of concision, maximizing entertainment value per word, or to preach to a choir by elegantly repeating a conclusion. Rather, I am attempting to explain things to my future self, who is intelligent and interested, but has forgotten. What I am doing is explaining why I decided what I did to myself and noting down everything I found interesting about it for future reference. I hope my other readers, whomever they may be, might find the topic as interesting as I found it, and the essay useful or at least entertaining–but the intended audience is my future self.

Development

It is everything I felt worth writing that didn’t fit somewhere like Wikipedia or was already written. I never expected to write so much; but I discovered that once I had a hammer, nails were everywhere, and that supply creates its own demand³.

Long Site

One of my personal interests is applying the idea of the Long Now. What and how do you write a personal site with the long-term in mind? We live most of our lives in the future, and the actuarial tables give me until the 2070^–₁₀2080s, excluding any benefits from caloric restriction/intermittent fasting or projects like SENS. It is a common-place in science fiction⁴ that longevity would cause widespread risk aversion. But on the other hand, it could do the opposite: the longer you live, the more long-shots you can afford to invest in. Someone with a timespan of 70 years has reason to protect against black swans—but also time to look for them.⁵ It’s worth noting that old people make many short-term choices, as reflected in increased suicide rates and reduced investment in education or new hobbies, and this is not due solely to the ravages of age but the proximity of death—the HIV-infected (but otherwise in perfect health) act similarly short-term.⁶

What sort of writing could you create if you worked on it (be it ever so rarely) for the next 60 years? What could you do if you started now?⁷

Keeping the site running that long is a challenge, and leads to the recommendations for Resilient Haskell Software: 100% FLOSS software⁸, open standards for data, textual human-readability, avoiding external dependencies⁹¹⁰, and staticness¹¹.

Preserving the content is another challenge. Keeping the content in a DVCS like git protects against file corruption and makes it easier to mirror the content; regular backups¹² help. I have taken additional measures: WebCitation has archived most pages and almost all external links; the Internet Archive is also archiving pages & external links¹³. (For details, read Archiving URLs.)

One could continue in this vein, devising ever more powerful & robust storage methods (perhaps combine the DVCS with forward error correction through PAR2, a la bup), but what is one to fill the storage with?

Long Content

‘Blog posts’ might be the answer. But I have read blogs for many years and most blog posts are the triumph of the hare over the tortoise. They are meant to be read by a few people on a weekday in 2004_20ya and never again, and are quickly abandoned—and perhaps as Assange says, not a moment too soon. (But isn’t that sad? Isn’t it a terrible ROI for one’s time?) On the other hand, the best blogs always seem to be building something: they are rough drafts—works in progress¹⁵. So I did not wish to write a blog. Then what? More than just “evergreen content”, what would constitute Long Content as opposed to the existing culture of Short Content? How does one live in a Long Now sort of way?¹⁶

It’s shocking to find how many people do not believe they can learn, and how many more believe learning to be difficult. Muad’Dib knew that every experience carries its lesson.¹⁷

My answer is that one uses such a framework to work on projects that are too big to work on normally or too tedious. (Conscientiousness is often lacking online or in volunteer communities¹⁸ and many useful things go undone.) Knowing your site will survive for decades to come gives you the mental wherewithal to tackle long-term tasks like gathering information for years, and such persistence can be useful¹⁹—if one holds onto every glimmer of genius for years, then even the dullest person may look a bit like a genius himself²⁰. (Even experienced professionals can only write at their peak for a few hours a day—usually first thing in the morning, it seems.) Half the challenge of fighting procrastination is the pain of starting—I find when I actually get into the swing of working on even dull tasks, it’s not so bad. So this suggests a solution: never start. Merely have perpetual drafts, which one tweaks from time to time. And the rest takes care of itself. I have a few examples of this:

1. DNB FAQ:

   When I read in Wired in 2008_16ya that the obscure working memory exercise called dual n-back (DNB) had been found to increase IQ substantially, I was shocked. IQ is one of the most stubborn properties of one’s mind, one of the most fragile²¹, the hardest to affect positively, but also one of the most valuable traits one could have²²; if the technique panned out, it would be huge. Unfortunately, DNB requires a major time investment (as in, half an hour daily); which would be a bargain—if it delivers. So, to do DNB or not?

   Questions of great import like this are worth studying carefully. The wheels of academia grind exceeding slow, and only a fool expects unanimous answers from fields like psychology. Any attempt to answer the question ‘is DNB worthwhile?’ will require years and cover a breadth of material. This FAQ on DNB is my attempt to cover that breadth over those years.

2. Neon Genesis Evangelion notes:

   I have been discussing NGE since 2004_20ya. The task of interpreting Eva is very difficult; the source works themselves are a major time-sink²³, and there are thousands of primary, secondary, and tertiary works to consider—personal essays, interviews, reviews, etc. The net effect is that many Eva fans ‘know’ certain things about Eva, such as End of Evangelion not being a grand ‘screw you’ statement by Hideaki Anno or that the TV series was censored, but they no longer have proof. Because each fan remembers a different subset, they have irreconcilable interpretations. (Half the value of the page for me is having a place to store things I’ve said in countless fora which I can eventually turn into something more systematic.)

   To compile claims from all those works, to dig up forgotten references, to scroll through microfilms, buy issues of defunct magazines—all this is enough work to shatter the heart of the stoutest salaryman. Which is why I began years ago and expect not to finish for years to come. (Finishing by 2020 seems like a good prediction.)

3. Cloud Nine: Years ago I was reading the papers of the economist Robin Hanson. I recommend his work highly; even if they are wrong, they are imaginative and some of the finest speculative fiction I have read. (Except they were non-fiction.) One night I had a dream in which I saw in a flash a medieval city run in part on Hansonian grounds; a steampunk version of his futarchy. A city must have another city as a rival, and soon I had remembered the strange ’90s idea of assassination markets, which was easily tweaked to work in a medieval setting. Finally, between them, was one of my favorite proposals, Buckminster Fuller’s cloud nine megastructure.

   I wrote several drafts but always lost them. Sad²⁴ and discouraged, I abandoned it for years. This fear leads straight into the next example.

4. A Book reading list:

   Once, I didn’t have to keep reading lists. I simply went to the school library shelf where I left off and grabbed the next book. But then I began reading harder books, and they would cite other books, and sometimes would even have horrifying lists of hundreds of other books I ought to read (‘bibliographies’). I tried remembering the most important ones but quickly forgot. So I began keeping a book list on paper. I thought I would throw it away in a few months when I read them all, but somehow it kept growing and growing. I didn’t trust computers to store it before²⁵, but now I do, and it lives on in digital form (currently on Goodreads—because they have export functionality). With it, I can track how my interests evolved over time²⁶, and what I was reading at the time. I sometimes wonder if I will read them all even by 2070.

What is next? So far the pages will persist through time, and they will gradually improve over time. But a truly Long Now approach would be to make them be improved by time—make them more valuable the more time passes. (Stewart Brand remarks in The Clock of the Long Now that a group of monks carved thousands of scriptures into stone, hoping to preserve them for posterity—but posterity would value far more a carefully preserved collection of monk feces, which would tell us countless valuable things about important phenomenon like global warming.)

One idea I am exploring is adding long-term predictions like the ones I make on PredictionBook.com. Many²⁷ pages explicitly or implicitly make predictions about the future. As time passes, predictions would be validated or falsified, providing feedback on the ideas.²⁸

For example, the Evangelion essay’s paradigm implies many things about the future movies in Rebuild of Evangelion²⁹; The Melancholy of Kyon is an extended prediction³⁰ of future plot developments in The Melancholy of Haruhi Suzumiya series; Haskell Summer of Code has suggestions about what makes good projects, which could be turned into predictions by applying them to predict success or failure when the next Summer of Code choices are announced. And so on.

I don’t think “Long Content” is simply for working on things which are equivalent to a “monograph” (a work which attempts to be an exhaustive exposition of all that is known—and what has been recently discovered—on a single topic), although monographs clearly would benefit from such an approach. If I write a short essay cynically remarking on, say, Al Gore and predicting he’d sell out and registered some predictions and came back 20 years later to see how it worked out, I would consider this “Long Content” (it gets more interesting with time, as the predictions reach maturation); but one couldn’t consider this a “monograph” in any ordinary sense of the word.

One of the ironies of this approach is that as a transhumanist, I assign non-trivial probability to the world undergoing massive change during the 21^st century due to any of a number of technologies such as artificial intelligence (such as mind uploading³¹) or nanotechnology; yet here I am, planning as if I and the world were immortal.

I personally believe that one should “think Less Wrong and act Long Now”, if you follow me. I diligently do my daily spaced-repetition review and n-backing; I carefully design my website and writings to last decades, actively think about how to write material that improves with time, and work on writings that will not be finished for years (if ever). It’s a bit schizophrenic since both are totalized worldviews with drastically conflicting recommendations about where to invest my time. It’s a case of high discount rates versus low discount rates; and one could fairly accuse me of committing the sunk cost fallacy, but then, I’m not sure that sunk cost fallacy is a fallacy (certainly, I have more to show for my wasted time than most people).

The Long Now views its proposals like the Clock and the Long Library and seedbanks as insurance—in case the future turns out to be surprisingly unsurprising. I view these writings similarly. If Ray Kurzweil’s most ambitious predictions turn out right and the Singularity happens by 2050 or so, then much of my writings will be moot, but I will have all the benefits of said Singularity; if the Singularity never happens or ultimately pays off in a very disappointing way, then my writings will be valuable to me. By working on them, I hedge my bets.

Finding My Ideas

To the extent I personally have any method for ‘getting started’ on writing something, it’s to pay attention to anytime you find yourself thinking, “how irritating that there’s no good webpage/Wikipedia article on X” or “I wonder if Y” or “has anyone done Z” or “huh, I just realized that A!” or “this is the third time I’ve had to explain this, jeez.”

The DNB FAQ started because I was irritated people were repeating themselves on the dual n-back mailing list; the modafinil article started because it was a pain to figure out where one could order modafinil; the trio of Death Note articles (Anonymity, Ending, Script) all started because I had an amusing thought about information theory; the Silk Road 1 page was commissioned after I groused about how deeply sensationalist & shallow & ill-informed all the mainstream media articles on the Silk Road drug marketplace were (similarly for Bitcoin is Worse is Better); my Google survival analysis was based on thinking it was a pity that Arthur’s Guardian analysis was trivially & fatally flawed; and so on and so forth.

None of these seems special to me. Anyone could’ve compiled the DNB FAQ; anyone could’ve kept a list of online pharmacies where one could buy modafinil; someone tried something similar to my Google shutdown analysis before me (and the fancier statistics were all standard tools). If I have done anything meritorious with them, it was perhaps simply putting more work into them than someone else would have; to quote Teller:

“I think you’ll see what I mean if I teach you a few principles magicians employ when they want to alter your perceptions…Make the secret a lot more trouble than the trick seems worth. You will be fooled by a trick if it involves more time, money and practice than you (or any other sane onlooker) would be willing to invest.”

“My partner, Penn, and I once produced 500 live cockroaches from a top hat on the desk of talk-show host David Letterman. To prepare this took weeks. We hired an entomologist who provided slow-moving, camera-friendly cockroaches (the kind from under your stove don’t hang around for close-ups) and taught us to pick the bugs up without screaming like preadolescent girls. Then we built a secret compartment out of foam-core (one of the few materials cockroaches can’t cling to) and worked out a devious routine for sneaking the compartment into the hat. More trouble than the trick was worth? To you, probably. But not to magicians.”

Besides that, I think after a while writing/research can be a virtuous circle or autocatalytic. If one were to look at my repo statistics, you see that I haven’t always been writing as much. What seems to happen is that as I write more:

• I learn more tools

  eg. I learned basic meta-analysis in R to answer what all the positive & negative n-back studies summed to, but then I was able to use it for iodine; I learned linear models for analyzing MoR reviews but now I can use them anywhere I want to, like in my Touhou draft material.

  The “Feynman method” has been facetiously described as “find a problem; think very hard; write down the answer”, but Gian-Carlo Rota gives the real one:

  Richard Feynman was fond of giving the following advice on how to be a genius. You have to keep a dozen of your favorite problems constantly present in your mind, although by and large they will lay in a dormant state. Every time you hear or read a new trick or a new result, test it against each of your twelve problems to see whether it helps. Every once in a while there will be a hit, and people will say: “How did he do it? He must be a genius!”

• I internalize a habit of noticing interesting questions that flit across my brain

  eg. in March 2013_11ya while meditating: “I wonder if more doujin music gets released when unemployment goes up and people may have more spare time or fail to find jobs? Hey! That giant Touhou music torrent I downloaded, with its 45000 songs all tagged with release year, could probably answer that!” (One could argue that these questions probably should be ignored and not investigated in depth—Teller again—nevertheless, this is how things work for me.)

• if you aren’t writing, you’ll ignore useful links or quotes; but if you stick them in small asides or footnotes as you notice them, eventually you’ll have something bigger.

  I grab things I see on Google Alerts & Scholar, Pubmed, Reddit, Hacker News, my RSS feeds, books I read, and note them somewhere until they amount to something. (An example would be my slowly accreting citations on IQ and economics.)

• people leave comments, ping me on IRC, send me emails, or leave anonymous messages, all of which help

  Some examples of this come from my most popular page, on Silk Road 1:

  1. an anonymous message led me to investigate a vendor in depth and ponder the accusation leveled against them; I wrote it up and gave my opinions and thus I got another short essay to add to my SR page which I would not have had otherwise (and I think there’s a <20% chance that in a few years this will pay off and become a very interesting essay).

  2. CMU’s Nicholas Christin, who wrote a paper by scraping SR for many months and giving all sorts of overall statistics, emailed me to point out I was citing inaccurate figures from the first version of his paper. I thanked him for the correction and while I was replying, mentioned I had a hard time believing his paper’s claims about the extreme rarity of scams on SR as estimated through buyer feedback. After some back and forth and suggesting specific mechanisms how the estimates could be positively biased, he was able to check his database and confirmed that there was at least one very large omission of scams in the scraped data and there was probably a general undersampling; so now I have a more accurate feedback estimate for my SR page (important for estimating risk of ordering) and he said he’ll acknowledge me in the/a paper, which is nice.

Information Organizing

Occasionally people ask how I manage information and read things.

1. For quotes or facts which are very important, I employ spaced repetition by adding them to my Mnemosyne

2. I keep web clippings in Evernotes; I also excerpt from research papers & books, and miscellaneous sources. This is useful for targeted searches when I remember a fact but not where I learned it, and for storing things which I don’t want to memorize but which have no logical home in my website or LW or elsewhere. It is also helpful for writing my book reviews and the monthly newsletter, as I can read through my book excerpts to remind myself of the highlights and at the end of the month review clippings from papers/webpages to find good things to reshare which I was too busy at the time to do so or was unsure of its importance. I don’t make any use of more complex Evernote features.

   I periodically back up my Evernote using the Linux client Nixnote’s export feature. (I made sure there was a working export method before I began using Evernote, and use it only as long as Nixnote continues to work.)

   My workflow for dealing with PDFs, as of late 2014, is:

   1. if necessary, jailbreak the paper using Libgen or an university proxy, then upload a copy to Dropbox, named year-author.pdf

   2. read the paper, making excerpts as I go

   3. store the metadata & excerpts in Evernote

   4. if useful, integrate into Gwern.net with its title/year/author metadata, adding a local fulltext copy if the paper had to be jailbroken, otherwise rely on my custom archiving setup to preserve the remote URL

   5. hence, any future searches for the filename / title / key contents should result in hits either in my Evernote or Gwern.net

3. Web pages are archived & backed up by my custom archiving setup. This is intended mostly for fixing dead links (eg. to recover the fulltext of the original URL of an Evernote clipping).

4. I don’t have any special book reading techniques. For really good books I excerpt from each chapter and stick the quotes into Evernote.

5. I store insights and thoughts in various pages as parenthetical comments, footnotes, and appendices. If they don’t fit anywhere, I dump them in Notes.

6. Larger masses of citations and quotes typically get turned into pages.

7. I make heavy use of RSS subscriptions for news. For that, I am currently using Liferea. (Not that I’m hugely thrilled about it. Google Reader was much better.)

8. For projects and followups, I use reminders in Google Calendar.

9. For recording personal data, I automate as much as possible (eg. Zeo and arbtt) and I make a habit of the rest—getting up in the morning is a great time to build a habit of recording data because it’s a time of habits like eating breakfast and getting dressed.

Hence, to refind information, I use a combination of Google, Evernote, grep (on the Gwern.net files), occasionally Mnemosyne, and a good visual memory.

As far as writing goes, I do not use note-taking software or things like FreeMind or org-mode—not that I think they are useless but I am worried about whether they would ever repay the large upfront investments of learning/tweaking or interfere with other things. Instead, I occasionally compile outlines of articles from comments on LW/Reddit/IRC, keep editing them with stuff as I remember them, search for relevant parts, allow little thoughts to bubble up while meditating, and pay attention to when I am irritated at people being wrong or annoyed that a particular topic hasn’t been written down yet.

My Experience of Writing

What is it like to write, for me?

I would divide my writing into two types: ‘incremental’/occasional, and ‘big bang’. Incremental writing is the ordinary kind of writing where I might add a quote or reference, or copyedit something, or write a small forgettable response to someone; ‘big bang’ writing is the more valuable sort where I sit down and bang out an entire essay like “Why Not To Write A Book” in a single session.

Why don’t you write? Since I find it easy to write, I’ve been puzzled by the many people I know who have worthwhile things they could write, and are fully capable of ‘writing’ them in the sense of explaining them to me (often in text-based chat!) in sufficient detail that it could be turned into a serviceable blog post—but who won’t.

Typical mind. Asking them about their experience of writing, and what bars them from taking that critical step even when they agree the topic is worthwhile & they would like to have the writeup, I’ve come to realize my experience of writing is completely different from theirs.

Blank-page tyranny. For them, the problem with longform writing is not a lack of material (my default assumption), but the writing being a school-like exercise in pain & tedium, as they struggle to fill up the blank page and assemble their atomic details into a coherent output: they struggle to take their pile of individual playing cards, and build a house of cards (which could topple at the first mistake).

Text earworms. For me, this is almost never problem because my experience of writing is radically different. I rarely struggle with assembling my fragments into a whole, because the whole instead inflicts itself on me. Much of my writing is like a musical earworm or intrusive thought: I experience the rumination as a mental voice reciting a paragraph, looping indefinitely, until I suppress it or get distracted (but then it may return, of its own volition). The paragraph might be a dialogue³², a comment in reply to someone specific, or on a general topic, a tweet, an email, or it might be the key paragraph for an essay I’ve been musing for a while—anything, really. The paragraph usually starts as a tangled rat’s-nest of fragments, allusions, citations, and parenthetical digressions, and gradually cleans itself up into something more readable. (One can always tell when I wrote something in a rush, without the benefit of revision to flatten it out, because of the nested parentheticals and tangents.)

Transcription. The voice is clearly myself, and does not feel like any kind of muse or external force, any more than a musical earworm or phrase feels “alien” to you; but it is effortless and involuntary³³, and hard to make it go away, which can be annoying. So I put down my writings into my website in order to forget the writings in my head. Thus, ‘big bang’ writing is easy—I am simply an amanuensis for the voice in my head. The key text has repeated itself so often that I can write it in a sitting. Indeed, these paragraphs have repeated themselves so many times that I am barely even thinking about this as I write it. (Instead I am thinking about a different topic: the value of writing a book vs blog posts.) I don’t experience the ‘tyranny of the blank page’, so much as the ‘tyranny of transcription’.

90% done. The real pain comes in the editing process afterwards, where I must laboriously stitch together the fragments and copyedit and add references and markup. (The voice is no help there, having gone silent once the loop has been written down.) The ‘incremental’ phase of writing is frustrating enough that I generally avoid writing as long as I can, in the hopes that the voice will give up and go away.³⁴ If I cannot outwait the recitation, if it keeps returning over enough periods, or some specific reason comes up (like an interested reader), then I may bother to write it down (rather than do something more fun, like read new research papers).

No free lunch. But that is only my experience of writing. Even if it does not feel like effortful thinking, and often like simply writing down something ‘obvious’, the voice comes from somewhere, and is not divine inspiration. The underlying reality must be the usual one: writing is like gardening. One patiently tends one’s garden, seeding and watering and pruning, and green shoots come up, and one day, one may behold a sudden blossoming, which one may cut and put in a vase to be seen by all. Or not, and let it wither and fall.

Confidence Tags

Most of the metadata in each page is self-explanatory: the date is the last time the page was meaningfully modified³⁵, the tags are categorization, etc. The “status” tag describes the state of completion: whether it’s a pile of links & snippets & “notes”, or whether it is a “draft” which at least has some structure and conveys a coherent thesis, or it’s a well-developed draft which could be described as “in progress”, and finally when a page is done—in lieu of additional material turning up—it is simply “finished”.

The “confidence” tag is a little more unusual. I stole the idea from Muflax’s “epistemic state” tags; I use the same meaning for “log” for collections of data or links (“log entries that simply describe what happened without any judgment or reflection”) personal or reflective writing can be tagged “emotional” (“some cluster of ideas that got itself entangled with a complex emotional state, and I needed to externalize it to even look at it; in no way endorsed, but occasionally necessary (similar to fiction)”), and “fiction” needs no explanation (every author has some reason for writing the story or poem they do, but not even they always know whether it is an expression of their deepest fears, desires, history, or simply random thoughts). I drop his other tags in favor of giving my subjective probability using the “Kesselman List of Estimative Words”:

1. “certain”

2. “highly likely”

3. “likely”

4. “possible” (my preference over Kesselman’s “Chances a Little Better [or Less]”)

5. “unlikely”

6. “highly unlikely”

7. “remote”

8. “impossible”

These are used to express my feeling about how well-supported the essay is, or how likely it is the overall ideas are right. (Of course, an interesting idea may be worth writing about even if very wrong, and even a long shot may be profitable to examine if the potential payoff is large enough.)

Importance Tags

An additional useful bit of metadata would be distinction between things which are trivial and those which are about more important topics which might change your life. Using my interactive sorting tool Resorter, I’ve ranked pages in deciles from 0–10 on how important the topic is to myself, the intended reader, or the world. For example, topics like embryo selection for traits such as intelligence or evolutionary pressures towards autonomous AI are vastly more important, and be ranked 10, than some poems or a dream or someone’s small nootropics self-experiment, which would be ranked 0–1.

Writing Checklist

It turns out that writing essays (technical or philosophical) is a lot like writing code—there are so many ways to err that you need a process with as much automation as possible. My current checklist for finishing an essay:

• syntax:

  • balanced brackets & quotes check

  • do a Pandoc/Firefox preview for visible major formatting problems

  • Markdown lint-checker

  • linkchecker for

    1. dead links

    2. inserting into archive queue

• references:

  • for academic hyperlinks, include a tooltip with the title & author metadata

  • for any papers cited: either link full text, provide a local full text, or submit a request on /r/Scholar or LessWrong; for books, insert an Amazon link if a copy can’t be hosted

• language:

  • spellcheck

  • check readability level (eg. Flesch-Kincaid)

  • probability word checklist

  • check for use of the word “significant”/“significance” and insert “[statistically]” as appropriate (to disambiguate between effect sizes and statistical-significance; this common confusion is one reason for “statistical-significance considered harmful”)

  • convert English units to metric

  • proselint checks

• content:

  • mention any use of PredictionBook in my essay on forecasting & prediction markets

  • mention any use of Fermi estimates in Fermi calculations

  • arrange for notifications of future results (when deciding to do long-term followups, eg. dual n-back research):

    1. Google Alerts

    2. Google Scholar Alerts

    3. PubMed alerts

  • if using statistics:

    • rerun all code to verify reproducibility

    • use reporting/quality checklists:

      • cross-sectional & other non-randomized analyses: STROBE

      • randomized experiments: CONSORT (statement)

      • meta-analyses: PRISMA

• after publication, publicize; currently:

  1. Hacker News

  2. Reddit

  3. LessWrong (and further sites as appropriate)

  4. Twitter

feedback <- read.csv("https://gwern.net/doc/traffic/2013-gwern-gwernnet-anonymousfeedback.csv",
                     colClasses=c("Date","logical","integer"))
plot(Visits ~ Day, data=feedback)
feedback$Time <- 1:nrow(feedback)
summary(step(glm(Feedback ~ log(Visits) + Visits + Time, family=binomial, data=feedback)))
# ...
# Coefficients:
#              Estimate Std. Error z value Pr(>|z|)
# (Intercept) -7.363507   1.311703   -5.61  2.0e-08
# log(Visits)  0.749730   0.173846    4.31  1.6e-05
# Time        -0.000881   0.000569   -1.55     0.12
#
# (Dispersion parameter for binomial family taken to be 1)
#
#     Null deviance: 578.78  on 753  degrees of freedom
# Residual deviance: 559.94  on 751  degrees of freedom
# AIC: 565.9

Popularity

On a semi-annual basis, since 2011_13ya, I review Gwern.net website traffic using Google Analytics; although what most readers value is not what I value, I find it motivating to see total traffic statistics reminding me of readers (writing can be a lonely and abstract endeavour), and useful to see what are major referrers.

Gwern.net typically enjoys steady traffic in the 50–100k range per month, with occasional spikes from social media, particularly Hacker News; over the first decade (2010^–₁₀2020), there were 7.98m pageviews by 3.8m unique users.

See Gwern.net Website Traffic

Colophon