Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)E
Posts
20
Comments
2140
Joined
1 yr. ago

  • Just by using their software they’re being promoted over non-facist software.

    No, you think that because you're mixing politics and engineering and you feel 'yucky' when using software written by someone you disagree with. I don't.

    If a fascist engineer designed a bridge and I walk on it am I supporting fascism? Am I giving visibility to it? Do I have to walk around and use a different bridge? You will probably say that yes, people using roads in New York support racism (https://en.wikipedia.org/wiki/Robert_Moses) but I disagree.

    I can use software without giving money, likes, following its creator on social media, reposting his messages or otherwise promoting his ideas. His code running on my computer doesn't provide any support to him, same as people driving under racist bridges don't promote racism.

  • Do you pay for your open source code? I don't.

  • I think the issue here is that 12 million has been donated to a fascist, not just that some people use said fascist’s software.

    I agree. It's an issue that some right wing foundation got 12 million dollars. It's a political issue. The fact that some people use some free software is not an issue at all. What I was talking about is people mixing those two things, exactly like you did in this sentence. I wrote more about in a comment below so I'm not going to repeat it here.

  • The main idea of open source is that code should be free (as in speech) so people can really own it, modify it, contribute and work on it together. So no, open source is not about Kindness and Empathy. I can accept your PR for my project and I don't have to know anything about your values, opinions or gender. If you run into a bug in an app you're using you can submit a fix without getting into the politics of the maintainer. Open source is a technical solution for a practical problem of locked down code.

    What your talking about is another layer of ideology and politics built on top of the open source movement. It's natural that people from communities and need some rules on interacting within them. In different groups different views become mainstream and different types of people join them. Then groups with different ideologies start fighting with each other. It's all normal. And yes, right wing influencers always get more funding simply because rich people are mostly right wing and are willing to support them.

    The problem here is that people now start to mix those two layers and try to govern the technical part using tools from the ideological part. If code is useful, if it does something we need (it's a driver, it's a protocol implementation, it's offers some crucial functionality) it doesn't really matter who wrote it. You can use it and it will not contaminate your computer with fascist/liberal ideology. If you want to engage will all this drama on political level you're free to do it, just like you're free to be a political activist in any other space. Just be careful not to mix politics with code. What is happening now is that people start rejecting code because they don't like who wrote it. It makes no sense. It's just code.

  • The most sever punishment 😱

  • Yes, agencies with more power will have more ways to force you. CIA will be able to fly to a dark site and put a car battery to your balls until you give them the PIN. Normal cops during a traffic stop will not have much ways to influence you beyond detaining/arresting you but any cop will be able to take your hand and forcefully place your thumb on a fingerprint reader. And courts say it's legal.

    https://reason.com/2024/04/19/appeals-court-rules-that-cops-can-physically-make-you-unlock-your-phone/

  • Story of the Eye by Georges Bataille

    I was about to post this one :)

    I read it many years ago because it was supposed to be Bjork's favorite book.

  • I Shall Spit on Your Graves - Boris Vian

  • Jesus kurwa ja pierdole.... Code is code. Who the fuck cares who wrote it? Unless project itself serves racist/transphobic/homophobic/etc purposes (like an app specifically build to doxx gay people or something) I don't care who's developing it. If you don't agree with the developers simply don't donate or contribute to the project. If it's paid don't support their business. If it's free - who cares?

    I don't really care that some influencers use open source to promote their shitty agenda. There are shitty influencers everywhere and there's plenty of fascist money to go around so yes, they will always find some sponsors. Don't donate, don't contribute, don't engage. But if the code is already written and does something useful... who cares who wrote it?

  • Yes, steel pipe to the knee will work equally well against all unlock methods. Graphene OS is supposed to be extra secure to better protect you against tools used by government agencies and law enforcement. It's used by activists and such. IMHO using fingerprint on Graphene OS makes all this extra security meaningless because police can just force you to unlock and it will be legal:

    https://www.techtimes.com/articles/303768/20240418/court-rules-thumbprint-phone-unlocks-used-police-force.htm

    Police would not be able to unlock this phone if the guy used pattern unlock.

  • Would police threaten to kill you if you don't unlock your phone? Not likely. Would they just use your finger and say you agreed to unlock it? More likely.

  • [music stops]

  • Graphene has a pin scrambler, so the numbers are in a different position everytime you have to enter them.

    It doesn't matter. When I'm inserting my PIN on a bus or while standing or line with people behind me or something I know that anyone interested can clearly see my screen and learn my PIN, scrambler or not. Also, scrambler is not mandatory (I don't have it enabled) so Graphene OS devs explanation that "we will not enable patter ulock because it's not secure" while normal PIN can be enabled still doesn't hold.

    This is actually a broader problem with Graphene OS. The devs often fixate on some minor security issues that don't impact 99% of their users at all and refuse to introduce features that they request. It's exactly the same with supporting phones other than Pixel. 99% of users would be completely fine using Graphene on a different phone (CIA is not going to hack them) but the devs prefer to directly reject all those users.

  • political dissident, activist, or a member of a marginalized group

    or a journalist or a politician. Vast majority of people aren't any of those and don't have to worry about cellebrite. Most people here that talk like Graphene OS is their only option really just need deGoogled device, not the most secure phone in the world.

  • Yeah, same for me. I'm sure I'm on top of CIA's list of "people to hack" so no security compromises for me.

  • I doubt he's using T-Mobile in Australia. (take a look at his instance then realize lemmy is not just for Americans)

  • I never used /e/ but I used iode (https://iode.tech/) and it worked really well. Main differences:

    • Graphene doesn't support pattern unlock because they claim PIN is more secure. This is stupid because you can just as easily see what PIN someone typed as the pattern. Since PIN is less convenient most people will use finger print unlock which means you can be easily forced to unlock your phone against your will
    • iode has support for shortcuts when using 3 button navigation, Graphene doesn't for some reason
    • iode has really nice tracker blocker which can run next to a VPN, Graphene doesn't
    • Graphene let's you install Google Services in a separate work profile and separate apps that have access to them from other apps. In iode you will have microG installed system wide

    For me that were the biggest differences. When it comes to app support they worked pretty much the same. I'm on Graphene now and it would be too much work to change now but for my next phone I will most likely go with iode.

  • I recommend:

    No AI there.