• Treedrake@kbin.social
    0·
    1 year ago

    But to be fair, the CloudFlare DDoS protection needs to be dropped so kbin.social, where most users and content are, is able to federate properly. This is a huge obstacle, especially when some are complaining that we need to register on other instances and not crash this one (e.g. fedia.io). Fedia has pretty much no content.

      • Scio@kbin.social
        1·
        1 year ago

        @BiggestBulb

        From what I can tell, Kbin recently got PWA support and some people have already installed it. But with the Cloudflare setup alongside federation this too broke, and now the manifest does not work correctly.

        Waiting out a few weeks before badgering anyone about it myself 🌝

        Edit: the PWA is working again!

        Next stop: collapsible comments, and the app to find system screen orientation support 🙏

        • parrot-party@kbin.social
          0·
          1 year ago

          I doubt it’s a PWA. A PWA is still active even when you aren’t using it. Allows for notifications and picking up where you left off. What you probably have is a web link on your home page, which can be done in Android as well.

          • abff08f4813c@kbin.social
            1·
            1 year ago

            Confirmed. On my Android (Samsung) it’s just a link. When I did it on an iPhone (iPhone 6 in fact), it was a proper PWA. Not sure why it works as a PWA only on iPhone but not on Android.

            I tried to run Lighthouse through Chrome dev tools on kbin.social but it seems like CloudFlare is throwing that off.
            Lighthouse reports that fedia.io isn’t PWA compliant due to a single issue in the manifest file (probably forgot to update a url from kbin to fedia or something trivial like that).

            Edit: and a day later, with CloudFlare off, I get the install option and the true PWA.