Comment on A bit of my selfhost journey [that no one asked about]

WhatAmLemmy@lemmy.world ⁨4⁩ ⁨days⁩ ago

• InternetCitizen2@lemmy.world ⁨4⁩ ⁨days⁩ ago

  I did try that, but the mobile app is more strict about an ssl cert and I am only doing local stuff right now. Tho I am planing to hook my server to a domain eventually.

  source

  • WhatAmLemmy@lemmy.world ⁨4⁩ ⁨days⁩ ago

    Try the web app (PWA). I don’t remember it complaining about http localhost.

    I’d also raise that as an issue with the developer. No self host-able app should enforce https. Only warn/notify. There are numerous situations where http is a perfectly fine, permanent solution (LAN/VPN).

    source

    • tripflag@lemmy.world ⁨3⁩ ⁨days⁩ ago

      So I realize the following does not directly apply in this specific case, since we are talking about a full android app. But in general, there are strictly technical limitations which absolutely requires you to use https. This for example applies to PWA’s, and it also applies to apps which are WebView-based.

      Basically the w3c is disagreeing with you; there are several important javascript features which are forcefully disabled if you are not connecting over https. This is a decision made by the webbrowser itself, and not something you or the dev can disable or otherwise avoid.

      For example, it is impossible to use the browser’s built-in api for getting the sha512 hash of a file, which is why i had to go through great pains to do that in other suboptimal ways in one selfhosted service i made. Most devs rightfully wouldn’t bother, since those restrictions are arbitrary and effectively pointless, as there are (usually painful) workarounds.

      List of features which require https: …mozilla.org/…/features_restricted_to_secure_cont…

      source
    • InternetCitizen2@lemmy.world ⁨3⁩ ⁨days⁩ ago

      Other people were talking about it with the dev on github.

      source