this post was submitted on 13 Dec 2023
543 points (98.9% liked)

Technology

59311 readers
5302 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] originalucifer@moist.catsweat.com 98 points 11 months ago (2 children)

this prolly wasnt a bad decision early on... why push something to a population who cant utilize it... but shit changes fast, google.

[–] ozymandias117@lemmy.world 48 points 11 months ago (1 children)

It seems somewhat damning that Google’s own browser had a workaround for this, though

[–] originalucifer@moist.catsweat.com 12 points 11 months ago (1 children)

was it ignorance or malicious intent?

if it was a person, i would try and assume ignorance.. im not sure google the company deserves such respect

[–] villainy@lemmy.world 25 points 11 months ago (1 children)

Or it's a company so fuckoff huge that one department (Chrome on Android) couldn't get a bug report escalated in another department (YouTube). Eventually they just put in a UA workaround while the bug rots in a backlog somewhere. Common enterprise bullshit.

Or the Chrome on Android team didn't even bother reporting the issue to YouTube and just threw in a cheap workaround. Also common enterprise bullshit.

[–] lolcatnip@reddthat.com 6 points 11 months ago* (last edited 11 months ago)

Bingo. When I was a Chrome developer working on video stuff, we mostly treated YouTube like a separate company. Getting our stuff to work with theirs was a priority, but no more than, say, Netflix. We pretty much treated them as a black box that consumed the same API we provided for everyone.

[–] Flaky@iusearchlinux.fyi 36 points 11 months ago (1 children)

The weirder thing is Firefox on ARM being detected as a HiSense TV. I did a cursory search to see if HiSense ever used Firefox OS on the TV and it doesn't seem like it. Panasonic seemed to be the only manufacturer using it.

[–] ericswpark@lemmy.ml 10 points 11 months ago* (last edited 11 months ago)

Could be that the developers for the HiSense TV just copy-pasted whatever UA into their browser codebase and called it a day.