• 0 Posts
  • 14 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • Mountaineer@aussie.zonetoMemes@lemmy.mlDear iPhone users:
    link
    fedilink
    English
    arrow-up
    12
    arrow-down
    2
    ·
    2 days ago

    Funnily enough, I’ve got a few friends who are long time iPhone users, who actually point this stuff out themselves:

    “OMG! Have you seen the eye watering price of the new one?”
    “Yay, I finally get stuff you’ve had for years.”

    Neither party would ever consider anything else, and they both buy the new model every year. 🤷

    At this point I admit that my reasons for choosing Android all those years ago no longer exist or matter, but I can’t imagine changing ecosystem either.








  • You can interoperate with googles RCS.
    If you are willing and able to enter a partnership like Samsung, you can do it fully (including encryption support etc).

    Google are determined to not make it easy, and I agree with you, it appears to be yet another messaging land grab.

    Trying to put myself in their headspace for a moment, one justification for making it hard is to stop thousands of apps coming out declaring “full RCS support!” through the APIs, then screwing the pooch (through poor security or deliberate back doors or or or).
    Right now Google are desperately attempting to make RCS happen, after almost a decade of trying and failing to make various carriers play ball.
    They do not want any bad press about how feature poor/insecure/slow/buggy it is right now.


  • Mountaineer@aussie.zonetoAndroid@lemdro.idIs RCS an open standard?
    link
    fedilink
    English
    arrow-up
    14
    arrow-down
    1
    ·
    7 months ago

    Only Google can make an RCS app

    Yes and no.
    You don’t need to make your own OS, but you do need to implement support for the RCS protocol within your app, rather than piggyback on Googles APIs.

    I don’t like it, but there’s no legal requirement for google to provide those APIs, like they did with SMS etc.



  • I don’t think it’s strictly compliant, although they claim to have based it’s syntax on Korn shell, which is the strictest definition of POSIX shells.

    You can do pretty much everything in powershell that you can do in something like bash BUT, it will be done slightly differently, so trying to make a script cross compatible is pointless (you might as well just write it natively in powershell etc).

    Powershell isn’t inherently bad, unlike bash for instance which just allows piping out text output, Powershell can pass around true .net objects.
    But if what you’re looking for is cross OS compatability, you’re pushing shit uphill.

    99.9% of the time, I open powershell and just ssh into a “real” linux box.


  • FOSS is enshitification-hardened, not proof.

    VLC remains awesome because the guy (maybe Jean-Baptiste Kempf?) that controls the project has refused to be bought, has in fact refused HUGE sums of money.

    The original author of any project has to right to sell it with the corresponding licence changes at any time.
    There’s some legal grey area on something like Linux or VLC which have MANY MANY developer hands in the pie, and existing users could certainly fork off the existing releases, but VLC could pivot tomorrow to a for profit company and make future releases of the official VLC a paid product, if they choose too.