• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: July 20th, 2023

help-circle
  • This affects me a lot day to day. I have a phone, but it runs postmarketOS, not iOS or Android. It really shows me the importance of open standards. I feel that every business should be required to support open standards for each of the services they offer.

    For me, buying train tickets used to be ok, but is getting harder now. Some train operators are really pushing you to use their app now, and getting rid of the option to download a PDF. It really frustrates me: it’s not like it costs them more to offer PDF download - if anything, it’s much cheaper to offer that functionality than to build and maintain an app for iOS and Android.

    Back when I had an Android phone, I used Monzo, and it was so easy to send money to friends, set up standing orders etc. I wish they offered a proper web interface. Now, I use Natwest’s online banking, and it’s a real pain - I use the card reader to authenticate, then the website logs me out seemingly every 2 mins of inactivity. Some features, like pre-notifying that you’ll be travelling abroad, are only available on the app. I only see this trend continuing.

    The concert tickets example in the article is insane to me. I can’t think of a use case that is better suited for PDFs, and that’s what we’ve been doing for the last 10+ years without any issues. It really is user hostile and excludes people on the edges of society who don’t fit, for whatever reason, with what the 80-90% do.





  • Just as a warning, this is licensed under the AGPL, with a CLA that requires copyright assignment. So, they could pull the rug at any time:

    2.3 Outbound License. Based on the grant of rights in Sections 2.1 and 2.2, if We include Your Contribution in a Material, We may license the Contribution under any license, including copyleft, permissive, commercial, or proprietary licenses.


  • It’s not perfect yet, but it’s much, much better than the old days.

    OMEMO is supported by every major client, and they interoperate successfully. Unfortunately, most clients are stuck with an older version of the OMEMO spec. It’s not ideal, but it doesn’t cause any practical issue, unless you use Kaidan or UWPX, which only support the latest version.

    All popular clients and servers support retrieving chat history now too.

    In practice, I’ve been using it for several months to chat with friends and family, and haven’t had any issues.






  • I really wish there was a GPL-licensed rendering engine and browser, accepting community funding, with some momentum behind it.

    I feel Ladybird have correctly identified the problem - that all major browsers and engines (including Firefox) get their primary source of funding from Google, and thus ads. And the donations and attention they’ve received show that there is real demand for an alternative.

    But I think the permissive license they have chosen means history will repeat itself. KHTML being licensed under the LGPL made it easy for Google to co-opt, since it was so much easier to incorporate into a proprietary (or more permissively licensed) codebase.

    There is Netsurf, but the rendering engine understandably and unfortunately lags behind the major ones. I just wish it was possible to gather support and momentum behind it to the same extent that Ladybird has achieved.