![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://beehaw.org/pictrs/image/c0e83ceb-b7e5-41b4-9b76-bfd152dd8d00.png)
2·
1 year agoI’m also interested in this for using stremio from phones and PCs. Chromecast in particular also kinda sucks due to limited codec support.
I’m also interested in this for using stremio from phones and PCs. Chromecast in particular also kinda sucks due to limited codec support.
Just wanted to add that event digitizing older records these days is better. Some hospitals do make old scanned notes indexed and searchable through OCR now.
This still just feels like a muddying of technical language. If you were to write an article about autopilot killing somebody and use object to refer to them, that’s certainly dehumanization, but saying that an object detection algorithm performs poorly on humans doesn’t feel like it is.
Part of the problem is that in general we aren’t talking about specialized human detection models that incorporate things like pose estimation. Instead it is almost always a general object detection alg, and referring to the same models differently based on the subject just adds muddiness.
I’m mostly familiar with AI within healthcare, and in my workplace, any released model is going to have a number of conversations and evaluations about the technical performance, practical impact on patients, and general ethics of the model. Those conversations blend, but it’s harmful to make the language less clear in any one of those contexts.