Arkodeon Technologies retweeted
Why DataSabi asks you to log out once after installing:
The app reads usage through a socket owned by the datasabi group. The installer adds you to that group, but group changes only apply in a new session.
Is there a cleaner way you'd handle it?
Arkodeon Technologies retweeted
Hotspot sharing is a blind spot in DataSabi right now.
If your laptop shares its connection with your phone, the traffic it forwards for the phone isn't counted. Only this computer's own apps are.
Should it be?
Arkodeon Technologies retweeted
Who can read your DataSabi usage data?
The collector's socket is /run/datasabi/collector.sock, mode 0660, group datasabi. Only members of that group can read it.
How do you usually lock down a local service's socket?
Arkodeon Technologies retweeted
Feedback from a DataSabi tester: he doesn't like watching his data go down. He wants a warning before it runs out.
Seeing usage and protecting a bundle are different jobs.
Which one would you want from a tool like this?
Arkodeon Technologies retweeted
DataSabi has a CLI too:
dsctl summary today: data per app
dsctl live: current rates
dsctl watch: rates and alerts as they happen
dsctl set-network 3 unlimited
Add --json for raw output.
Terminal or GUI for something like this?
Arkodeon Technologies retweeted
Known limitation: Docker and VM traffic usually shows as "Unknown / system" in DataSabi.
Those processes live in other network namespaces, so the collector sees the bytes on your real interface but can't name the app.
Would you want a per-container view?
Arkodeon Technologies retweeted
DataSabi's collector is now GPL-3.0.
Changes you share have to stay open, with source. The protocol crate stays Apache-2.0, so an app under any licence can talk to the collector. v0.1.6 and earlier stay Apache-2.0.
How do you pick a licence?
Arkodeon Technologies retweeted
btop shows you the network spike. It doesn't tell you which app caused it.
That gap is why I'm building DataSabi.
When your data suddenly drops, what's your first guess?
Arkodeon Technologies retweeted
A habit from building a school website: confirm it from the outside.
DNS said "success" but hadn't spread yet. Now I check from another network before I tell a client it's live.
What do you always double-check?
Arkodeon Technologies retweeted
Most MiFi routers don't tell your laptop the connection is metered.
So DataSabi treats any network NetworkManager reports as "unknown" as metered, and alerts there until you mark it unlimited.
The other default would miss the exact connections it's built for.
Agree?
Arkodeon Technologies retweeted
DataSabi's tester call on Earlynest closes Nov 19. 10 spots.
Ubuntu 22.04+ or Debian 12, a MiFi or hotspot, a few days of normal use, then a short report. Testers get credited in the release notes.
joinearlynest.com/calls/6aec…
Arkodeon Technologies retweeted
Some of your data goes to things you never opened.
DataSabi gives them plain names: "DNS lookups (systemd-resolved)", "Snap updates (snapd)", "System updates (apt)", "Firmware updates (fwupd)".
Which background service would surprise you most?
Arkodeon Technologies retweeted
Today's DataSabi commit changes nothing you can see. On purpose.
I moved the collector's shared parts into an engine: IDs, totals, alerts, saving every 5 s, hourly rollups. Linux code feeds it, and Windows will feed the same engine.
How do you plan for a second platform?
Arkodeon Technologies retweeted
A Python script using your data can show up as just "python3".
DataSabi names apps in this order: Flatpak ID, Snap name, AppImage path, interpreter + script, then the executable. So /opt/bot/sync.py gets its own line.
What would you want to see for your scripts?
Arkodeon Technologies retweeted
DataSabi is on Earlynest: 10 Linux tester spots open.
On Ubuntu 22.04+ or Debian 12 with a MiFi or hotspot? Use it for a few days, see which apps ate your data, and send a short report. Testers get credited in the release notes.
Join here: joinearlynest.com/calls/6aec…
Arkodeon Technologies retweeted
Linux folks on a MiFi or hotspot:
Do you track your data at all, or do you just wait for the "you have used up" text?
Arkodeon Technologies retweeted
What happens to a connection that lasts 50 ms?
DataSabi maps traffic to apps via /proc. Unmatched packets wait while the socket table is re-read, at most every 100 ms.
If the socket is gone by then, the bytes still count, as "Unknown / system".
How would you catch them?
I'd install git
Replying to @zieecodes
I'd start with Git. I want version history before I start “fixing” the config.
12
Arkodeon Technologies retweeted
DataSabi's collector reads at most the first 128 bytes of each packet. That's enough for the headers: addresses, ports and size.
It doesn't parse or store what's inside. Only per-app byte totals are kept.
How it works: arkodeon.com/datasabi/docs/h…
What would you want to check?


















