251–260 of 361 posts
Still works for me. I had to update exploit protection after their latest update — I think it was enabling dynamic code loading via both memory and storage that did the trick. Edit: checked now, I have also disabled secure app spawning.
Earlier quoted context omitted.
> GrapheneOS is anti-user-freedom. This is a really, really poor-quality take. > complaints of this nature get inane drivel responses of "lol just fork Graphene" It’s a fork of AOSP, which you can just…use.
Uh, no. Shaming a "take" is just tone policing. Owners should own the hardware along with the software both. Its only since the smartphone era (2008) with locked down shit devices has this view changed. And people challenging this are somehow defective, tone policed, shamed, or likewise. GrapheneOS users are treated as 'rooted phones', at the exact same time tools that would attack and prevent corporate surveillance…
No, that’s called sharing your opinion.
You shared your opinion, someone else shared there’s that just so happened to be “I disagree with you” and suddenly that’s some type of censorship? Nobody is shaming you, either.
Earlier quoted context omitted.
Easy to say when you are in a country where you have a lot of options. There's some countries with very bad financial sector where your option is PayPal or Western Union as the local banks don't know how to do international transfers, Remitly doesn't support all countries and Wise also doesn't work. PayPal works, even if they charge fees.
Which countries have local banks that don’t know how to do international transfers?
This is arguably the most irritating thing with just about every largecorp developer: "os that hasn't been updated in 6 years? Sure boss!". Os that is built specifically around security and privacy with daily updates: "No, you can't do that". Annoying - yes. Safe way to make sure I will stop being your customer - also YES!
Generally I think the issue is that there's a tension between your security vs Paypal's security (deliberate, motivated bad actors). Maybe an analogy could be about using metal detectors as a layer to reduce bank robberies. A gun in a good guy's hands is a good thing to prevent robberies. Guns in a bad guy's hands are a bad thing to prevent robberies. Paypal knows you have a gun but they don't know if you're a good g…
The needs of the user don't matter to them at all.
Earlier quoted context omitted.
That's your argument? Mate, you can make explosives out of stuff you can buy in literally any supermarket and no one bats an eyelash. You don't have to legally be adult to buy any of the things you'd need and I say that as someone who only struggled with chemistry in school, that's now low the bar is. What's the solution then? Ban sea salt? If someone is using Graphene, the chances of them getting hacked are astronom…
It was an analogy, or metaphor, I forget the distinction. But I don't think it was stood up to be literally argued against though.
Even tried completely nuking app data and logging in again. Login, security check, fingerprint setup, everything worked (I even got the alert that it used the Play Integrity API)
I assume if anything, this is probably the contactless payments. I do somewhat understand why they are really trying to lock something like this down, but as everyone pointed out, giving the green light to a CVE infested version of Android while prohibiting the use of a version that goes above and beyond when it comes to security is absurd.
Earlier quoted context omitted.
Uh, no. Shaming a "take" is just tone policing. Owners should own the hardware along with the software both. Its only since the smartphone era (2008) with locked down shit devices has this view changed. And people challenging this are somehow defective, tone policed, shamed, or likewise. GrapheneOS users are treated as 'rooted phones', at the exact same time tools that would attack and prevent corporate surveillance…
Nobody’s shaming you, reddit refugee. It is a common userspace decision to lock things to userspace. It’s good hygiene. If you want less-secure software, use AOSP or one of its many forks. You’re not defective: you just have different needs and threat model, and you’re harassing and degrading the public image of a project that’s opinionated in a very welcome way by folks in the security community - especially those w…
Yes, running in userspace for the majority of tasks is good hygiene.
Preventing the user from ever escalating beyond that layer on their own devices, however, is restricting their freedom to control their device. When that happens with tractors, cars or other gadgets that's considered anti-user. The same attitude should extend to phones.
Can it still run in browser like it would on a regular pc?
Earlier quoted context omitted.
> Some banks also connect it to your phone number What do you mean "some banks"? I thought the whole value proposition of Wero was instant bank transfers with SEPA but using phone numbers?
...why would I give my phone number to random people to pay them? I'd rather use an email address or user name. And using phone numbers means making it easier for normal people which means uploading the whole address book to the bank... just no.