Evan Genest's Learning Log

Web developer notes emphasizing LAMP, Symfony, PHP, Javascript, Drupal, and Node.

This is an Eleventy project created from the eleventy-base-blog repo.

My Matomo Instances

web analytics


I have installed Matomo on some of my hobby sites:

  1. Little Furnace is my resume and portfolio
  2. Pikl.us is my URL shortener with the tricky Are-you-a-human question
  3. Tattl.me is this blog

Matomo Cloud

Tattl.me is on Matomo Cloud. That means when you send an http request to this site it calls the Matomo server in Germany or New Zealand (backed up in Ireland) to get the matomo.js file which contains my settings. Once that file is received, the visitor's browser runs Matomo in the browser. Various actions now have Javascript listeners. When you scroll, mouseover, navigate through links, or leave the page, the matomo.js program sends JS objects to my Matomo Cloud server.

For a fee, Matomo keeps the database and API of my instance updated, maintained, and backed up.

Matomo On Premise

Little Furnace and Pikl.us are installed onto the same computer as my page, behind the same server. This requires more vigilence and attention. Permissions of files, updating of versions, backing up: all are my responsiblity.

The up side of On Premise is that it's free. Also, if I was trying to be super secret about sensitive information, I am in control of the computer. I could even run this without an internet connection, using localhost on an intranet. I guess that could be a fun way to track what goes on inside my house. (Parents! Get detailed reports about your youngsters http traffic! There's a use case I haven't seen promoted enough.)

Matomo Server Log Analytics

I have not tried this yet. Sounds like it would be a fun project to fork and play with. The repository is here.

This is one of several articles for people wishing to try out different aspects of the devtools in Firefox.


When you use web pages and web applications what is stored in the Firefox or Chrome browser? Read some of the descriptions here:

Browse things stored in the client

Many objects (objects in a JS sense) are stored in the browser when you use a web page. These are not hidden or mysterious. They are easy to browse in the devtools. In Firefox:
Will reveal several types of stored things:

Local Storage vs Cookies


Local Storage Methods

Here is homework .

  1. Go to your browser's cookies list: Settings->Privacy&Security->Cookies->ManageCookies (in Firefox)
  2. (optional) If you don't have many cookies, get some. Go to commercial sites: Amazon, OfficeSupply.com. Go to some high content story sites: vox.com, scoutingmagazine.org/ your local newspaper, yahoo.com. Do some browsing to accumulate some cookies
  3. Look at pairs of sites. For their cookies, describe what is the same and what is different (do this in any way that makes sense for you, think of your audience, get your ideas across any way you prefer). Choose sites with 2 or more cookies.
    a. two sites that sell things
    b. a high traffic site and a less high traffic site
    c. two sites with URLs ending in .edu domain (If stumped you can find these by putting "site:.edu into Duck Duck Go or Google")
    d. two sites with a URL ending in the .gov domain

Local Storage exercise to try

  1. Store a property. Get the browser console
 (Firefox: Ctl+Shift+I) -> Console  

Store your own silly property

localStorage.setItem('froggy', 42);  

Is the item still there? Check!


Remove your made up proper property using any method listed above in the Methods section.
Confirm it is gone, using something similar to localStorage.getItem() again.

Combined Exercise to try

  1. Use everything from above to look at some interesting large websites and see which properties that are typically stored in cookies versus which properties are typically stored in local storage. This is open-ended; there is no right answer.