• 0 Posts
  • 12 Comments
Joined 7 months ago
cake
Cake day: March 10th, 2025

help-circle




  • The answer:

    The device local name string is specified to be encoded in UTF-8. However, the Microsoft Wireless Notebook Presenter Mouse 8000 reports its name as Microsoft⟪AE⟫ Wireless Notebook Presenter Mouse 8000, encoding the registered trademark symbol ® not as UTF-8 as required by the specification but in code page 1252. What’s even worse is that a bare ⟪AE⟫ is not a legal UTF-8 sequence, so the string wouldn’t even show up as corrupted; it would get rejected as invalid.

    Thanks, Legal Department, for sticking a ® in the descriptor and messing up the whole thing.

    There is a special table inside the Bluetooth drivers of “Devices that report their names wrong (and the correct name to use)”. If the Bluetooth stack sees one of these devices, and it presents the wrong name, then the correct name is substituted.

    That table currently has only one entry.

    I mean, I don’t get how it’s legal’s fault when they’re not the one’s creating the firmware/programming, but sure let’s blame them. It’s the dev who verbatim copied and pasted the name from legal for whatever reason (even though a normal person wasn’t going to check the firmware to see it).



  • They don’t care about whether they live with you or not. It’s about providing less service than what you’re paying for. Like how mobile carriers say, “unlimited data*” – *after 25GB, we [may] slow your connection speed to 256kbps. So this way, it’s “5 accounts*” – *they must physically live with you. So now you’re paying for 5 accounts, where 3 or 4 of them technically are unusable.

    Why? Money. Those other people who you would have shared with now need to get their own account(s). Suddenly, “profits are through the roof!” – until the next big squeeze. At this point, Google is squeezing its customers like a dry tube of toothpaste.