If this were true, it proves nothing other than Apple is by far the most popular company to have adopted this standard. But it isn't even true, in the top 10 results for "HEIF" there are results related to Windows, Android, and Canon cameras.

This isn't proprietary tech. It's a industry-developed, documented standard that Apple pays royalties for using, just like anyone else would. There's a mature library with an open source LGPL license with language bindings to C++, Swift, Python, JavaScript, Go, and Rust for anyone to incorporate in their software. Apple isn't locking anyone out from reading, writing, or otherwise interoperating with HEIF files created and distributed by Apple devices. This is a completely different situation compared to the terrible shite Apple does around controlling iMessage. This is just being mad because there's a new format out there and Apple adopted it before your preferred software vendor did (or did well).

0 ...

Report Post

Posted by LemmyLives

Texas

Member since Mar 2019

10013 posts

Posted on 9/15/23 at 11:23 pm to AlxTgr

quote:
I have never had issues with text groups, even if I am the only one.

You don't know there are problems if you don't see them, because you're on Android. I'm not dumb enough to think this is a carrier problem (too many layers underneath messages in the OSI layer), where 15 guys are fine, but the one Android dude can't see messages. Even 1:1, I can't send pictures to a different droid user.

MKV over MP4, fight!

1 ...

Report Post

Posted by Korkstand

Member since Nov 2003

28997 posts

Posted on 9/16/23 at 11:08 am to LemmyLives

quote:
I'm not dumb enough to think this is a carrier problem

Shot fired?

quote:
(too many layers underneath messages in the OSI layer)

How are you shoehorning iMessage/SMS into this model? iMessage is not an Open System, nor do they want it to Interconnect. iMessage sits atop the whole stack, correct? And SMS/MMS make up essentially the whole OSI stack, right? And a completely different stack than the one iMessage sits atop.

The glaringly obvious "problem" is that not everyone is using the same chat app in this scenario. That is Apple's problem to fix if they want to.

Assuming that won't happen, the only way to fix it is to rebuild/replace enough of the stack below it to support the features needed for intercommunication. That is on the carriers.

Page 1 2 3 4