That smells right, I see it was labeled "high priority" 3 months ago...
dango
joined 1 year ago
RCS is supported by /carriers/, and many do support it. It is open in that sense.
I don't think Google is "disallowing" others from implementing RCS, it's just others choose not to? Like, RCS/SMS is a core feature of the phone/os, so it doesn't really make sense for anyone other than the OEM (or Android) to care about it. Samsung is an OEM, and Google is Android.
Telegram e.g. isn't going to implement RCS becuase why would they? Just use telegram's protocol. Etc.
And carriers don't implement any apps today? When was the last time you had to install a carrier specific SMS app? It's always down to the OEM.
RCS is an open standard, anyone can implement it. Google just implements one such app. (Google also implements, uh... android... so bad news if you're trying to avoid Google and use an android)
If you're still using SMS or MMS, it's all unencrypted, always.
Sync for kbin when
Yeah, it'd be pretty nice for similar communities to opt in to co-federating (I imagine on the backend a submission to one mag would submit to all mags, and the UI just has to be smart enough to dedup)
Whoever wrote this fundamentally does not understand how Youtube works.
These "videos" are songs uploaded to "Youtube Music" (similar to spotify), the "auto generated video" just plays the song that the record label provided to youtube.
This is like claiming Spotify "auto generated" song entries after a record label uploaded music there.