Lucky for me I accidentally double tapped when trying to move the zoomed in image only to see this waiting for me
Lucky for me I accidentally double tapped when trying to move the zoomed in image only to see this waiting for me
Not sure what you’re referring to, but I’m using it on a Pixel 7 without issue.
I should have thought to mention it. I’ll update my comment 👍
All you should need to do is set the App Source URL to https://codeberg.org/Bazsalanszky/Infinity-For-Lemmy/releases/ and then toggle on Include prereleases. Once they get a full release out you can toggle it off
I’ve been using Obtainium instead and loaded Infinity through it this morning. You can also have it pull from f-droid repos instead of GitHub if you want when that hits
Edit: Currently the app is in prerelease so you’ll need to toggle that option. Once they have a full release you can toggle it back off.
Butthole problems
You can also throw the releases page URL into obtainium and toggle to include pre-releases and it’ll notify you of any updates/install them.
Yep, this is why I run forgejo internally and have zero intention of exposing it to the public.
Thanks for this. I’ve been using it for almost 2 weeks and aside from having to manually tell Lasts/AntennaPod to sync it’s been a seamless replacement for pocket casts. Well, once I figure out how to get the f-droid version of AntennaPod to play nice with Android auto (a problem I only came across yesterday)
That’s again for the recommendation.
Any chance you also listen to them on PC? I’m looking to move away from Pocket Casts to Antennapod but haven’t looked into desktop players yet (web/win&lin)
I’ve been with Fastmail for about a year and a half now. The number of complaints in their subreddit about outages had me a little worried but I’ve never once missed out on an important email or anything like that.
My literal only complaint is lack of offline viewing for messages but I just run K-9 and shit’s solid.
This is what I do on ipt, my ratio is insane because the 24/7 seeding + redeeming points. Def the way to go if you can swing it.
That’s a very narrow definition of self hosting. Do you also not consider it self hosting if you use a cloud provider VPS? It relies on a 3rd party so I’d love to see the gymnastics that keep stuff on a VPS as self hosted but not Plex. If you don’t consider things on a VPS as self hosted then I’m not sure what to say other than I disagree.
Also Plex is a staple of the self hosted community (though I prefer Jellyfin.) I’m wondering if they’ve confused self hosting and FOSS somehow
The apk isn’t always what f-droid compiles. There’s two scenarios where they publish the apk signed by the developer.
https://f-droid.org/docs/Reproducible_Builds/
It’s one added layer of security to you, but to others it’s a man in the middle that could be an extra attack vector.
If you don’t trust the dev to put out an apk that’s compiled from their public source why are you trusting any of your data with them?
How does f-droid solve this problem? From my understanding they confirm that the .apk
provided by the dev matches what compiles from source and run it through Virus Total. Those are trivial steps for a malicious dev to take to slip in something nefarious.
At that point you’re relying on the community to check every commit for nefarious code $x. Not to mention they could simply build up community trust for some time before slipping in the code, since they’d effectively be burned once (if?) their very first shady code commit is found.
I can’t imagine f-droid would go on the hook and say everything they build is also code reviewed for malicious stuff, right?
Fair point. I guess it boils down to if you prefer speed of update (obtainium) or the extra checks f-droid has in place and if you continue to trust that f-droid’s stuff doesn’t get compromised.
It’s also worth mentioning f-droid’s workflow far from guarantees there’s nothing nefarious in a package. The bar looks to be passing virus total and then ensuring the provided apk matches source. If nobody reviews the source each time then every release could be the one that gets a nasty surprise.
Which developer?
E: Lol @ the ninja edit.
That’s hardly a meaningful advantage for f-droid and the whole man in the middle risk you’re exposing yourself to there. If you don’t trust the developer to do the bare minimum of providing a release that matches source then why are you even installing their app? Satyr’s response about developers getting compromised has way more weight in that conversation, but still falls short IMO.
Making sure the apk matches public source and running it through VT aren’t going to catch a malicious apk that has the nasty bits buried in various commits but checks out in VT and matches the public source code. Sure, it’ll burn them as a developer if/when they get caught, but how often does the community truly do code reviews on one-off Android apps? Not often enough to catch that kinda thing before it spreads without getting insanely lucky.
The developer of obtainium or the packages we’re installing? I’ll assume the former. If you’re skeptical about obtainium you could still use it as a source to monitor && notify and then do your install manually.
Pin-al