• 1 Post
  • 592 Comments
Joined 2 years ago
cake
Cake day: September 27th, 2023

help-circle
  • So you’re just reimplementing the current model but with the extra layer of a browser in between.

    No, I’m removing the layer of the native code that launches whatever flavor of Electron they’re running under the hood in favor of the browser and webview that’s already installed on your device (or whatever other one you’re interested in switching to).

    Installing a PWA is the same as installing a native app, except instead of running it directly you also have to have a browser installed to run it.

    …which literally every single mobile device already has. Seriously, you can’t uninstall webview if you wanted to.

    Plus, you only have to install one browser for the entire system, Come on. You can’t honestly believe that the dozens of reproduced copies of the same codebases that live on your phone right now are a good use of your phone’s storage or memory.

    It’s adding a significant amount of complexity […]

    I don’t know what complexity you think it’s adding. It’s removing a bunch of native code, and replacing it with web-standard code that (in the case of most apps) was already written for the native app anyway, or at least was written for the web app.

    […] for no good reason.

    Ever wanted to mod an app? If it was a web app running in a browser, you could. Would you like to use ad blockers on the YouTube app? Or use a userscript to hide stories about a particular person? Or automate the function of one of your apps? With native code you can’t. With web apps you can. Web apps are more accessible, they adhere to published standards, they’re not as heavy on your operating system, they’re more resistant to privacy-siphoning attacks and surveillance, they’re more easily able to share code…and, to be honest, they’re also easier to develop. The only reason for corpos not to do this is because it gives the user power that they would rather be able to sell to the user instead.

    Browsers are huge attack targets.

    Security is not improved by forcing users to switch to native apps. For one thing, most companies’ apps already are web apps; if they’re not already hardened, wrapping them in native code and putting them in the Play Store or App Store won’t magically make them more secure, because decompiling native apps and sniffing API endpoints is still a thing. Also, it could be argued that browsers are more resistant to security issues, since you can patch them once and mitigate certain vulnerabilities in every app without waiting for developers to ship a fix.

















  • I have a wifi-enabled garage door opener whose manufacturer discontinued the Google Home connection for so that you have to use their app and see their Amazon or Walmart ads. I also have a wifi-enabled alarm system whose manufacturer apparently doesn’t care about Matter integration or whatever. So leaving the house in my car requires the use of two different apps (three if I also need to turn off lights).

    In actuality I just use the physical buttons. But there was a time that I had a beautiful dream of getting a smart lock and setting my house up to lock the doors, close the garage door, and arm the alarm when I pushed a button in the car–and, more importantly, undo all of those things in reverse when I got home.


  • Toilets can appear to have flushed fully, but still have…material…stuck in the U-bend that hasn’t completely evacuated the toilet. A subsequent flush won’t work, even though the water in the bowl is clean.

    Ask me how I know.

    That said, this could almost certainly be better-solved in other ways. Maybe by preventing the tank from refilling if there’s still something in the u-bend (then you’d know it needed attention because there’d be no water in it)?