I think you missed the point, that I was making, albeit poorly (little endian still requires leading zeros when not transmitting in a byte format, otherwise you don't know if the first on signal is for 1, 256, 1024, etc.) it's all good though
ITGuyLevi
I'm not seeing any trailing zeros if that is in little endian, you start little end first and it isn't limited to a silly 8-bits, it can be used to represent numbers far larger than 255 if continued (though then it wouldn't be representative of a byte and half the joke would be lost).
Little-endian for the win!
I usually just gather a nibble by picking up a couple crumbs... I'll see myself out.
Napping. Not everyone understands the fun that can be had.
I'm sure a successor will come around when room forms for them, I don't know of a reason any of the core *arr stack should need one. If you know of one don't hesitate to share, I'm just not really aware of any, they are awesome to me.
Odd way to phrase it, but I totally agree.
I would have been a bit more specific, but it applies to all of them (they aren't the reason I don't trust Google either).
Sadly I'm not completely switched away yet, I'm doing the best I can with the sacrifices I'm willing to make and accepting what I can't. I run GOS on a pixel, it has GPS but severely locked down, most apps get denied the network permission and pretty much nothing has access to any data outside of limited storage scopes or the minimum contacts (i.e. Android Auto can only see two contacts in my phone and can't see any SMS/messaging).
Beyond that I do the usual Google replacements (Nextcloud for files/seedvault backups, immich for photo backups, CoMaps instead of Google Maps, etc).
I yern for the day I can have an old flip phone with a hotspot built in for a few apps on other devices (or bt tethering).
America isn't the reason I don't use Google Play Services... Google is the reason for that specific choice for me.
Personally when I need something and have seen an ad for a product that fits the need, I'll buy it. If I've seen the ad so much that it's seared into my brain, I search for the product and buy the ripoff version of it (when possible), or I DIY it.
Edit: corrected autocorrect
When I realized they paywalled OIDC I had to look elsewhere.
In a normal byte format it wouldn't help, the byte standard breaks off bits into 8 bit chunks and calls them bytes (I'm not trying to explain basics, just putting it there for background), little-endian excels at using the least number of bits to express larger numbers in a stream. If you wanted to send any number from 0-255 you only need 1 byte, for 256-512 you need two bytes (or 16 bits), in little-endian it can be represented in just 9 bits, or up to 1024 in 10 bits, etc.
Doesn't matter for much to many people, but when the number gets big enough you can save a lot of bandwidth.