Replying to @luna@fedi.mldchan.dev

@luna
Likely unami can do more stuff than Goatcounter, but for me its enough to see general stuff :3
Also their tracker is like 1KiB of extra stuff to load which is basically nothing. The webserver itself uses only 66MiB which is also good considering I only have 4GiB on the VPS its running on alongside Masto, Uptime Kuma and an Etherpad server :3

Replying to @Wolkensteine@mastodon.wolkenheim.eu

@Wolkensteine yeah I built my server out of last gen components before memory skyrocketed in price so I have a beefy server where running something like umami doesn't really do anything alongside an MC server, Akkoma on fedi.mldchan.dev, Akkoma on the-wired.club, website, MC website, hedgedoc, XMPP, matrix, samba (local), mcaptcha, peertube, forgejo, 4 fedi bots, vaultwarden, ntfy, akabot.xyz website, immich

Replying to @luna@fedi.mldchan.dev

@luna
I am very happy about the VPS, it is one hosted by Hetzner and I only had good experiences with their support, although with new prices I'd not order another one, still on the old plan with 6€/mo instead of like a lot more.
Their webhosting plan is what got me there - 1,6€/mo with mail is great.
Would love to self host on own hardware but don't have static ips and don't want to use Cloudflare tunnels or similar.

Replying to @luna@fedi.mldchan.dev

@luna my old visitor counter broke when it was at ~500 about a year ago due to it being just a text file with a number in it, which was reset to 0 due to some bug that occured when the disk was full; i removed the counter since then and only fixed it 5 days ago, now its recording a timestamp of every visit in postgresql which allows me to visualize popularity of my site over time

see https://pleroma.laru.dsrv.x7q.eu/notice/B7zXTFnTRs3sVaAeUC
pleroma.laru.dsrv.x7q.euLaru (@laru@pleroma.laru.dsrv.x7q.eu)my new visitor counter is so cool

Replying to @luna@fedi.mldchan.dev

@luna oh i didnt wanna record peoples ips, i do deduplication too but by session rather than date, so someone visiting the site twice will only be counted twice if they close their browser between visits, this also ensures that only browsers get counted and curls/crawlers dont

basically it works like this:
1. is visitor cookie set ? proceed : set it to value a
2. send api request to get visitors
3. set cookie to value b

the api request will only count your visit if the cookie is set to value a, which only happens once per session unless you clear your cookies
basically only a client that evaluates javascript will trigger the counter (ofc this can be circumvented by sending the cookie on purpose but why would anyone do that)