Introduction
Introduction Statistics Contact Development Disclaimer Help
____ __ __ _ ___ __ …
/ __/ / /_ ___ ___ / / ___ _ ___ ( ) ___ / _ ) / / ___ ___ …
_\ \ / __// -_) / _ \ / _ \/ _ `/ / _ \|/ (_-< / _ | / / / _ \ / _ `…
/___/ \__/ \__/ / __//_//_/\_,_/ /_//_/ /___/ /____/ /_/ \___/ \_, /…
/_/ /___/ …
PDATE ON TILDE ANALYTICS
Anyway, for this week I have some updates for the tilde amalytics!
Updated session tracking
In order to count unique pageviews the pixel stored the SHA1 hash of the
request IP address. This is not really secure since a) I am sure rainbow
tables for IPv4-SHA1 exist and b) the ip doesn't change, so you can
track an user between session.
I changed this to something new: a session cookie!
Now before you start worrying about me tracking users between websites,
I can tell tou that the session cookie does not have a max age set, so
it will expire after the browser is closed. Also it doesn't reveal the
request's ip address so this is the better option!
New dashboard for viewing analytics
The current analytics "dashboard" is everything but user friendly. In
order to help the maybe one person that is using this I crafted this
mess of javascript code:
Find it on my ~town
How to use this:
1. Open the left menu
2. Create a new site
3. Add pages to the site with the floating + button
4. ???
5. Profit!
Here is a screenshot:
[Screenshot showing analytics data, two bar graphs and a table]
Anyway, that's all I have for this week. Maybe I'll have some time this
week to start programming some sort of comments system.
Check me out on the fediverse: [@[email protected]](https://mas.to/@steph)
COMMENTS:
Add a comment by mailing to [email protected] and putting [ceb1b] in the subject
ther blog posts by ~steph
Going off the grid - part 2
020-03-08 - 20:03
Going off the grid
020-02-14 - 11:11
You are viewing proxied material from tilde.club. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.