Remember people, if newpipe give error when try to play a video, just turn your phone horizontally and vertically until the error leave. Is really easy

      • Forbo@lemmy.ml
        2·
        1 day ago

        Even with that repo it doesn’t come up. Not sure how long it takes for it to appear, GitHub is showing the release was tagged about three hours ago as of this writing.

          • tetris11@lemmy.ml
            2·
            1 day ago

            Not OP, but can also confirm it’s not there.

            My current version is
            Version 0.27.4 org.schabi.newpipe

            Rotating does nothing

            • merde alors@sh.itjust.works
              2·
              1 day ago

              i’m on droidify, started using obtainium for newpipe after the last “google breaks newpipe” (because it takes repositories some time to add the new updates)

              than what i see in there is my obtainium update (?)

              • tetris11@lemmy.ml
                2·
                1 day ago

                I stay well clear of obtanium. Github releases are not the source-reproducible binaries they sometimes pretend to be. There’s no QC whatsoever.

                I’ll stick with the F-droid vetting. It’s not perfect, but it’s enough

                • N0x0n@lemmy.ml
                  2·
                  6 hours ago

                  Care to elaborate? I do not fully understand the meaning of your claim :/. I use Obtainium for everything and haven’t had any issues until now.

                  Still curious from your perspective the meaning of what you said.

                  • tetris11@lemmy.ml
                    2·
                    6 hours ago

                    not the best resource, but:

                    we don’t audit every single app that makes it into the store. But we do make sure that everything is free software, and do test/investigate to a certain degree.

                    From what I understand, F-droid regularly audits a few new apps for malicious code, and always makes sure that the source built the binary.

                    With Github releases, maybe some of these binaries are generated by CI, but I’m betting more that they’re generated locally in dev and then uploaded to Github as direct releases. That is, the source you see on a repo on Github is not neccesarily the same source used to generate their binaries.

                    To me that’s a wide angle of attack, and that’s why I stick with F-droid, even if it’s minimal checking.