🔧 A small update to AG Analytics

While troubleshooting an issue where the analytics script was being blocked, I decided to tweak the tracker's name.
tracker.js has been renamed to widget.js.

The old /tracker.js hasn't gone anywhere—it keeps working, so sites where it’s already installed shouldn't break. However, new installations will now use /widget.js right from the start.

I also updated the snippet generation, the README, and the documentation regarding custom domains (subdomain.domain.com).

In short, there’s no urgent need to migrate existing sites; you can switch them over gradually at your own pace.
It’s a minor change, but these are the kinds of things you have to do when a project moves beyond just "internal testing" 🙂

🧩 Found the culprit behind the broken statistics collection

It looks like I initially headed down the wrong path.

Renaming /collect to /event and tracker.js to widget.js, or setting up a custom domain, didn't solve the issue. It turned out the names had nothing to do with it.

The browser classifies both event and ping requests as ping requests. This happens because navigator.sendBeacon() is used.

Some blockers—including Brave Shields and specific uBlock Origin lists—can block these requests entirely, regardless of the domain or filename.

In the end, I replaced sendBeacon() with a standard:

fetch(..., { keepalive: true })

Now the browser classifies the requests as fetch/XHR rather than ping.

Long story short, the problem wasn't what the analytics were named, but how they sent the data 😅

It also explains why my previous attempts didn't make any difference.

🪙 Now, a bit about CoinLumaBot

One of the projects that has been part of AGTEAM for a long time is @CoinLumaBot.

Its purpose is incredibly simple: to quickly check the current cryptocurrency rate without opening an exchange, a website, or a separate app.

You select the coin you need, and you get the up-to-date price. It supports BTC, ETH, and other cryptocurrencies.

No trading, wallets, or unnecessary features. Just open Telegram → check the rate → carry on with your day.

These are exactly the kind of small tools I enjoy creating: a single, specific task that the bot handles quickly and without any fuss.

👉 @CoinLumaBot — for those times when you just need to know what your crypto is worth right now.

Proxy Checker v2.6.0 — Virtualized Results Table

This release fixes the remaining slowdown with large result sets: the results table no longer creates a live widget for every single proxy.

✨ What's new:

🚀 Virtualized results table — previously, each result row was built from ~9 real Tk widgets, so 1000+ live proxies meant 9000+ widgets on screen at once, and rendering got visibly slower the more was found. The table now keeps a small fixed pool of row widgets (just enough to cover the visible area) and reuses/repositions them while scrolling instead of creating a new set per row. Rendering cost now depends on the size of the window, not on how many proxies were found.

⚡️ Off-screen rows are free — while a scan is running and you're looking at the top of the list, rows appended further down (out of view) no longer touch any widgets at all; they only show up once you actually scroll to them.

🧵 Raised how many queued results are processed per UI tick back up, since rendering is cheap now regardless of batch size.

📥 Download: v2.6.0

🪙 CoinLumaBot — v3.1.0

A small but logical change to @CoinLumaBot.
I’ve removed the daily automatic report—now the stats don’t come on their own and don’t create unnecessary noise.

What’s changed:

📊 /stats has been replaced with /status;
🔐 /status is available only to the administrator;
⏱️ Stats are now retrieved on demand;
🧹 The daily Cron job has been completely removed;
📄 The documentation has been updated.

The bot’s regular commands haven’t changed. The database also doesn’t require migration.

⚙️ v3.1.0

"It works on my machine!" 📦
Discover how Docker & containers package code and dependencies into portable, isolated environments that run anywhere.

alexgor.com/blog/how-containers-work-docker-explained