Yeah, F-Droid sucks. The team makes arbitrary rules for the packages that are not mentioned anywhere on their website and rejecting packages based on said arbitrary rules. Happened to me.
As I said, it was a rule made up on a spot. Though recently I’ve read that they had a problem with one of the maintainers being a dick to people, so I’m curious if it was that one.
They lose the control anyway, because the deploy process is automated. Doesn’t make sense to me at all. It’s open source and it follows all their rules, rule against PWA is nowhere on F-Droid.
Well I don’t make the rules nor do I work on the F-droid core team. Maybe start a discussion on the forms. Just try not to use a harsh or abrasive tone as it isn’t well received usually.
Yeah, F-Droid sucks. The team makes arbitrary rules for the packages that are not mentioned anywhere on their website and rejecting packages based on said arbitrary rules. Happened to me.
The rules are fairly clear and are to protect the end users from abuse and anti features. F-droid doesn’t just deny you for no reason.
As I said, it was a rule made up on a spot. Though recently I’ve read that they had a problem with one of the maintainers being a dick to people, so I’m curious if it was that one.
What was the rule?
That they don’t allow apps that are wrappers for a PWA.
Yeah, I can see that. By using a PWA they lose control over what changes get shipped to the end user. It stinks but it makes sense. (At least to me)
They lose the control anyway, because the deploy process is automated. Doesn’t make sense to me at all. It’s open source and it follows all their rules, rule against PWA is nowhere on F-Droid.
Well I don’t make the rules nor do I work on the F-droid core team. Maybe start a discussion on the forms. Just try not to use a harsh or abrasive tone as it isn’t well received usually.
Nah, I’m done with them, I just stopped using them.