Recent searches
Search options
@mo8it@fosstodon.org#OxiTraffic, a self-hosted, simple and privacy respecting website traffic tracker 
Demo: https://oxitraffic.mo8it.com
I just published version 0.6 with a #Docker image! 
️
(You don't have to use Docker though)
Do you have a #blog?
I can host it for you if you want to test it with your website 
Of course, it is written in #Rust 
Check out the README, I spent a lot of time on it 
https://codeberg.org/mo8it/oxitraffic
Boost? 
I have to thank @mre for his valuable feedback to the last versions
He uses OxiTraffic on his blog:
https://oxitraffic-corrode-dev.mo8it.com/
I can host it for your blog too! 
@mo8it really like that service. What sets it apart is the simple interface and the 20-second-on-page rule for counting visits.
@mo8it can you check unique visitos?
@ssebastianoo No, because OxiTraffic doesn't track the IP address. It also doesn't use cookies. The user agent is also untouched. All of this is for privacy reasons.
This doesn't mean that bots would be counted though. A visit is only counted if the visitor stays on the page for more than 20 seconds. This should filter bots out.
@mo8it awesome, I'll definitely try this
@mo8it This looks super neat!
@mo8it is it possible to use an image instead of a js script ?
@panigrc Using an image was actually the first strategy that I tried. But it produced garbage calls from bots. Some bots load images!
Some bots even run JS! Therefore, my strategy is to only count a visit if the user stays on the page for at least 20 seconds. After testing this strategy for some months, it turns out to be very effective against bots.
@panigrc I get your concerns, I hate JS myself and try to avoid it whenever possible! Therefore, I made the JS script that is executed on the visitor's machine very tiny and well documented:
https://codeberg.org/mo8it/oxitraffic/src/branch/main/templates/count.js
I also explain how it works in the README:
https://codeberg.org/mo8it/oxitraffic#how-it-works
Don't hesitate to ask further questions if you have any concerns
@mo8it the following scenario would work, only if lazy loading images wouldn't require the use of a js library:
1. Have an image load on top of the page
2. Have an image on the bottom
Count the difference between the load times and if i.e. <5s don't count it.
@panigrc Good idea! But bots don't scroll. They just load the link pointing to the image.
Also, without JS, this strategy would require storing the IP or something similar which OxiTraffic doesn't do to preserve the privacy of visitors :)
@mo8it This looks like a nice thing to have but I'm currently not inclined to self-host something that's open to the internet. :-/
@thedoctor I can quickly host it for you to test it, at least for a couple of months :)
@mo8it That's nice of you but I'm afraid I might end up liking it and then after a few months facing the same problem...
@mo8it I highly suggest you share this on /r/selfhosted I'm sure some of the community would love to try it out!
@JzJad Thanks for your suggestion!
I will share it on Reddit after the next release :D
@mo8it This is cool! :). Does this support an API to upload data? This way I can setup a cron job to parse webserver logs and send to oxiTraffic.This is useful for seeing stats for apps where it is not possible to inject the javascript. I think except for 'Average time spent' (also filtering out bots), other metrics should be available.
@balki All endpoints are documented here:
https://codeberg.org/mo8it/oxitraffic#endpoints
But there is no API to manually upload such data. Sorry, OxiTraffic isn't designed for that use case 
I am pretty sure that it won't be useful anyway. I tried such telemetry without bot filtering and the results were just trash :/
@mo8it I see. Thanks!