Live data from Hacker News

F-Droid Board of Directors nominations 2026

f-droid.org

121–130 of 160 posts

Re: F-Droid Board of Directors nominations 2026

#121

Earlier quoted context omitted.

Indeed. Sadly the reality is that most other Android devices are simply not secure enough. Many Android phones do not have a separate secure enclave (outside Pixel and IISC Samsung flagship and A5x range), so they are vulnerable to breaking PIN-based unlocking, side channel attacks, etc. Besides that they often only provide old vendor kernel trees, old firmware blobs, etc. So, you have to wonder whether you want such…

Perfect really is the enemy of good when it comes to GrapheneOS

When feasible, they also provide harm reduction updates for legacy hardware.

Re: F-Droid Board of Directors nominations 2026

#122

Earlier quoted context omitted.

Do you have a link with information about this? I'm just wondering since I'm currently using 3 different European banks without any biometric authentication to unlock my phone, password manager or provide a 2FA. I'm asking so that I can adjust in time to any new regulations I'm not aware of.

This https://en.wikipedia.org/wiki/Strong_customer_authentication

Thank you!

I kind of jumped at the "biometric" part of your original comment.

Now I understand what you mean better and I'm not worried about my setup (although I question how it complies, but that is another matter).

Re: F-Droid Board of Directors nominations 2026

#123

Earlier quoted context omitted.

Reduced security has always annoyed me a bit as an argument. Sort of in the same way as signal deprecating SMS because it's insecure. I get all or nothing when your threat model is state actors. However, for most people, the benefit is just freedom from corporate agendas. Not everyone needs kernel hardening, or always E2EE (as with signal). Personally I just like the features it provides (e.g. scoped storage, disabli…

Graphene is OSS, so if you want to create a fork that supports other phones, you are free to do so. The maintainers have limited amount of resources, why wouldn't they focus those resources on the most secure hardware if that is what aligns with their goals? If you have different goals, create or fund a fork to support more hardware.

Really? Wow? What an insight.

That being said, am I allowed to complain. Or simply dismiss them for supporting only Google hardware?

Or should I create a fork instead?

Re: F-Droid Board of Directors nominations 2026

#124
post #111

Earlier quoted context omitted.

It should be pretty obvious why porn apps are marked NSFW despite not containing any content. Substantially all of the content they can be used to access is NSFW, whereas it's reasonably possible to access only SFW content on Reddit. Which would also explain the Bible apps without an initial copy. Choosing which translation to download when substantially all of them are translations of the same NSFW text means that s…

You're trying to be clever, but the context from the drop has been to distinguish "a sincere belief" from this sort of rhetorical underhandedness that you are indulging in. Not only is this not going to convince anyone that there's anything behind it other than an attempt to formulate a winning argument (having set that as your goal) irrespective whether there's any actual sincerity to the words you're choosing, but…

I feel like if you want to call something "rhetorical underhandedness" you should at least pay attention to which fork of the argument you're criticizing.

The original complaint was that if they were doing it to be controversial, why not do the same thing to viewer apps for Reddit or Wikipedia? But those are necessarily distinguishable. If the standard was that a viewer merely could load external NSFW content rather than was likely to, you would have to do web browsers, mail clients, podcast managers, file transfer apps, video players that can open external links -- it'd be most of the repository. And that would be far less defensible, because you can point to specific controversial Bible verses, but how are you going to make the case that generic FTP clients and web browsers are NSFW with a straight face? But conversely, how would you argue that a Reddit viewer is NSFW but a web browser that can open Reddit isn't?

The fork where they need "a sincere belief that these apps contained content unsafe for minors" was the other fork, where they're doing it because of potential liability rather than to make a statement. But that fork was flawed to begin with, because they're not required to think that it actually is unsafe. They could also be concerned that someone else could claim that and then even if the people claiming that are jerks and even if the jerks could ultimately lose, they could prefer to be risk-averse when they don't have the resources to handle things like that.

Re: F-Droid Board of Directors nominations 2026

#125
post #120

Earlier quoted context omitted.

> Sadly the reality is that most other Android devices are simply not secure enough. This seems like a bad reason for not supporting a device. If the device doesn't have a hardware feature then the OS it came with can't be doing it either, and then all you're doing is leaving the user with all of the other security problems in the OEM OS that otherwise could have been improved by replacing it.

The point of GrapheneOS isn't improving a generic device's security, it's about setting an example for a highly private and secure OS. It's a FOSS project, so nothing stops a committed individual or community from using other device targets, but the main project chooses specifically to use their smaller resources to pursue excellence rather than mediocrity.

I've had people tell me that nobody should use anything but GrapheneOS and stop supporting alternatives to throw all support into that because the others are "less secure", and now that GrapheneOS isn't for everyone and anyone -- the majority of people -- without a specific narrow selection of hardware should get lost.

We need the people who buy $100 phones to have the ability to put a better OS on them than the burning mudslide that comes with them, is all I'm saying.

Re: F-Droid Board of Directors nominations 2026

#126
post #111

Earlier quoted context omitted.

You're trying to be clever, but the context from the drop has been to distinguish "a sincere belief" from this sort of rhetorical underhandedness that you are indulging in. Not only is this not going to convince anyone that there's anything behind it other than an attempt to formulate a winning argument (having set that as your goal) irrespective whether there's any actual sincerity to the words you're choosing, but…

I feel like if you want to call something "rhetorical underhandedness" you should at least pay attention to which fork of the argument you're criticizing. The original complaint was that if they were doing it to be controversial, why not do the same thing to viewer apps for Reddit or Wikipedia? But those are necessarily distinguishable. If the standard was that a viewer merely could load external NSFW content rather…

Apologies—when I mentioned the insincerity and indulgence before, I should have said tediously insincere indulgence.

Re: F-Droid Board of Directors nominations 2026

#127
post #126

Earlier quoted context omitted.

I feel like if you want to call something "rhetorical underhandedness" you should at least pay attention to which fork of the argument you're criticizing. The original complaint was that if they were doing it to be controversial, why not do the same thing to viewer apps for Reddit or Wikipedia? But those are necessarily distinguishable. If the standard was that a viewer merely could load external NSFW content rather…

Apologies—when I mentioned the insincerity and indulgence before, I should have said tediously insincere indulgence.

I mean, do you want the realpolitik version? If you're doing something to be controversial/oppositional then you need people to feel troubled by it. Labeling Reddit as NSFW is something many of them want, which is the opposite.

Re: F-Droid Board of Directors nominations 2026

#128
post #73
post #66

Earlier quoted context omitted.

Yeah, kids need to read this. Totally. /s

In Biblical times, yeah? There was no such thing as birth control. If you get pregnant and are unmarried, your life might as well get over.

That's not true. The Bible provides a recourse for unwanted pregnancies in the form of a procedure to perform an abortion.

Which is another reason the Bible should be banned from being accessed by minors. If a child needs an abortion, they should consult a medical professional. They should not read about how to perform an abortion in an app on their phone and attempt to perform the procedure themselves.

Re: F-Droid Board of Directors nominations 2026

#129
post #96

Earlier quoted context omitted.

Bible apps often don’t contain the text directly, but allow the user to download a preferred translation on initial startup. That didn’t prevent them from being marked NSFW. And clearly that wasn’t the standard anyway. Before the introduction of the policy restricting religious texts, the only apps F-Droid had marked NSFW were frontends to porn sites, even though the apps presumably contained no sexual content direct…

It should be pretty obvious why porn apps are marked NSFW despite not containing any content. Substantially all of the content they can be used to access is NSFW, whereas it's reasonably possible to access only SFW content on Reddit. Which would also explain the Bible apps without an initial copy. Choosing which translation to download when substantially all of them are translations of the same NSFW text means that s…

> Choosing which translation to download when substantially all of them are translations of the same NSFW text means that substantially all of the users would end up with NSFW content on their device by using the app.

Nothing could be further from the truth. The Bible has been around for a while, and translations exist to serve the current sensibilities of every period within that time.

Here's Ezekiel 23:20 in the King James Version:

For she doted upon their paramours, whose flesh is as the flesh of asses, and whose issue is like the issue of horses.

This has been euphemized so heavily that much of the original meaning is no longer present.

Re: F-Droid Board of Directors nominations 2026

#130

Earlier quoted context omitted.

Except, of course, that the Bible in any translation is not NSFW, certainly in the common usage of the term. It contains depictions of violence and sex, yes. But so does Fanny Hill, and that hasn’t legally been considered obscene in the UK or the USA in over fifty years. F-Droid’s excuse, that they needed to restrict Bible apps to protect F-Droid from legal liability, is not believable.

Let's consider the two possibilities here: 1. They have a policy of marking apps as NSFW if using them has a high probability of loading NSFW content onto the device. We can't easily rule this out. It's a small project so they have to be reserved about compliance issues because they don't have the resources to defend against expensive litigation and they could just be exercising an abundance of caution. 2. They're tr…

> We can't easily rule this out. … they don't have the resources to defend against expensive litigation and they could just be exercising an abundance of caution.

If F-Droid were being cautious:

• They would have restricted social media apps, which a lot of public hysteria targets, which many of the new laws explicitly target, and which other app store providers like Google and Apple have already faced and continue to face massive financial and legal consequences over. If F-Droid is unwilling to take a stand against censorship, this would be an obvious step to begin shielding themselves from liability.

• They would not have prioritized blocking apps providing ancient religious texts, since there’s no public hysteria over Bible and Quran apps, none of the new laws explicitly target them, and no app store provider has faced consequence or threat of consequence over providing them.

• Once the policy was in place, they would not have reversed it simply after receiving angry comments.

I’m completely comfortable disbelieving F-Droid was ever actually concerned that religious apps could be a liability risk.

> They're trolling Republicans with malicious compliance. They don't like the laws being enacted, they know the people enacting them like the Bible, so they apply the policy in the way which is maximally adversarial to the opponents imposing it on them.

If the targets of their trolling (and I’m glad you agree, it is trolling) are legislators in backwards U.S. states, they hit far off the mark. The only people impacted by F-Droid’s censorship have been its users, who are (for the most part) members of the free software community. What’s the point of a troll that is unnoticed by your enemies and only harms your friends who already agree with you?

> "If you don't like the consequences of your law then feel free to repeal it."

In case you haven’t noticed, these laws are being passed everywhere from the UK to Brazil to Australia to Singapore to the EU. And yes, some U.S. states, too. So your “realpolitik” remark in another comment is similarly pointless, because those other politicians and regulators are also completely unaffected by F-Droid’s actions.

> Which one of these is even objectionable?

In response to a law saying F-Droid must punch some of its users in the face, F-Droid of its own volition decided to punch a different set of users in the face rather than refusing to punch anyone at all. I find that objectionable, and the flurry of comments they received shows others do too. Instead of taking principled actions or practical actions, F-Droid’s maintainers decided to take a swipe at users of religious apps on F-Droid, refused to explain themselves (“kayfabe,” as you called it), then upon receipt of unexpected blowback on their forums and issue trackers, backtracked and reversed the policy without further comment. It was a boneheaded move that drove away some app developers and some users like me. How can I trust them to not make some other boneheaded move in the future? Can you imagine Debian or OpenBSD doing such a thing? Now F-Droid has a big banner up top pointing to https://keepandroidopen.org/ and making themselves (noticeably, not other FOSS app stores) out to be the defenders of app freedom. It’s completely tone‐deaf and shows poor judgment. If current or future F-Droid leadership actually addressed the issue, I might be convinced to use it again. But I won’t hold my breath.

Post reply on HN