J@antheas @bsherman @M2 Hey so there's a lot of coreos in this upstream chart:
J
Jthat's the pink line, it's more than fedora server and us. I think we should get ucore sorted out on countme if we can.
Bthis is the issue https://github.com/ublue-os/ucore/issues/202
GitHub
Our machines are pushing metrics to Fedora's servers. Bluefin, Aurora and Bazzite are being recorded as separate distros, however I believe UCore is counted under CoreOS. It would be awesome to...
J@Lorbus your skillset would be useful here. 
Bi think we have examples in bluefin/bazzite... per the issue... i just never dove into it
Jwho was the other person doing charts, 4 digit number as a nick
4Maybe me?
4I really do have a talent for bad and/or non memorable nicknames
J@Niko
Jhaha yes!
Jwe just need to figure out what os-release changes to make, but we have to account for announcing because apparently people use sysexts?
Byeah, i have added announcements to the repo README
but that's usually not until something is actually done, not ahead of time
but that's usually not until something is actually done, not ahead of time
Band i can probably pick it up this weekend... i just haven't spent the time to follow what bluefin/bazzite do
JI think we'll just be setting the os-release, wait a few weeks for it to start showing up in the stats
Lyeah that seems like the right path forward. Not sure about the sysext stuff, haven't used any of that yet. If they are id-specific, they'll likely break. Maybe they can be changed to allow for multiple IDs?
MTravier used to have them be any. But he changed it to be fedora.
LYeah I think that's to distinguish between sysexts for servers and desktops, maybe it can just be
CoreOS || uCore for the server ones?MIt's the ID that we need to change for countme and that's coded to fedora for travier.
MActually could probably just change variant or something else
BI think we have an “ID_LIKE” key in os-release on universal blue desktops, we could suggest support for that in travier’s repo, or does that need to be upstream change?
MActually, I'm thinking we may be able to do this without changing ID. Keeping compat with sysexts
BOk? But it would still allow uCore to differentiate in countme?
BThings get even trickier if we start thinking about a CentOS based uCore too LOL
Mso I believe fedora normally differentiates with variant_id
Msince everything uses ID=fedora
Bso... are aurora/bluefin/bazzite changing countme incorrectly?
I thought it was intentional to avoid using their trademark perhaps?
I thought it was intentional to avoid using their trademark perhaps?
Mthat might be....
LI don't think shipping ID=fedora infringes on their TM tbh
Lfedora references are literally everywhere in Bluefin
Lbecause that's where most of the packages come from
Lbut IANAL
Lso far, neither Red Hat nor Fedora have sued anyone for fair use of their stuff
Myeah there is a ton of stuff that is fundamentally fedora that we would never be able to move away from if using fedora as a base
AIt was intentional to get other counting services to differentiate us
BI was correct it was intentional, incorrect about why 
Lmakes sense so we need to figure out how to have our own ID and still be able to use @Timothée Ravier 's sysexts with uBlue OSes
so we need to figure out how to have our own ID and still be able to use @Timothée Ravier 's sysexts with uBlue OSes
Nif the only goal is to be able to count in countme, variant would be fine
Nwe get both columns -
so it's
so it's
Nand more columns that i left out for brevity
Nhmm so if we were to switch coreOS to uCore it'd be from:
to
to
Nah so travier must have linked it to the os_variant, because core os's os_name is Fedora Linux still FYI
Nwe could switch it to:
so as to not break anything, but we're kinda getting into hack territory here. (keep the
so as to not break anything, but we're kinda getting into hack territory here. (keep the
os_variant: coreos, which sysexts are looking for, but change the os_name from Fedora Linux to uCore...)NSuggested here for prosperity https://github.com/ublue-os/ucore/issues/261
GitHub
Hi! Goal is to know how many ucore nodes are running with countme. The first few columns of countme data look like this: week_start,week_end,hits,os_name,os_version,os_variant so for bazzite: 2025-...
Ni can probably figure out how to do that if we're down. it's a bit of a workaround though.
NGitHub
Hi! Goal is to know how many ucore nodes are running with countme. The first few columns of countme data look like this: week_start,week_end,hits,os_name,os_version,os_variant so for bazzite: 2025-...
NGitHub
Suggestion to close #261 and #202.
Nimplements the learnings from above ticket thread
LLGTM
Bi left a review requesting a few small changes, but I very much appreciate your PR and everyone chiming in to help make a good change here
