[-] OppressedBread@lemmy.ml 10 points 3 days ago* (last edited 3 days ago)

I'm willing to take a fat loss on memory if it means I'm leaving a predatory ecosystem.

also true on the gold subscription, ps plus is also going up and I'm not willing to tolerate it more

[-] OppressedBread@lemmy.ml 6 points 3 days ago

seeing how the tech space is around here and digging more into binaries, they most probably outsourced their stuff, that third party company probably blocked GOS out of discretion, I don't imagine they actually asked for that.

[-] OppressedBread@lemmy.ml 4 points 3 days ago

it be like that sometimes

[-] OppressedBread@lemmy.ml 6 points 3 days ago

no, that's a well known workaround, but the banking apps I used were just giving me a generic error, while yes they used google play integrity API, they weren't enforcing it.

what it turns out is that they were checking for specific packages that come preinstalled with every copy of GOS, effectively blocking users of said operating system.

Luckily these packages aren't essential and could be disabled by users, bypassing their checks.

this is one of many that they implemented, there are 3 other checks but it was easy to bypass those too without compromise.

[-] OppressedBread@lemmy.ml 2 points 3 days ago

as it stands right now, there is no clear benefit for me when it comes between choosing to bank on my browser vs just using the app while yea it does offer some fingerprinting resistance, I'd be still exposing my real IP address, otherwise the bank would flag any other IP address I'm using and will require me to verify myself.

I opted to run my banking apps in a separate profile without hiding behind anything while kewping my other profiles separate and behind proxies

[-] OppressedBread@lemmy.ml 2 points 3 days ago

good point, I'm leaning towards just changing the device model in the report and calling it a day.

[-] OppressedBread@lemmy.ml 7 points 3 days ago

I have to use it, its part of my daily life, but thank you for your response.

[-] OppressedBread@lemmy.ml 3 points 3 days ago

thank you so much, another thing I also missed when looking over the technical aspect of it, I'm saving this for future reference.

[-] OppressedBread@lemmy.ml 3 points 3 days ago

saving this reply for future reference, thanks!

[-] OppressedBread@lemmy.ml 4 points 4 days ago* (last edited 4 days ago)

actually that's a good question, would be nice if I could maybe buy a domain and just purely receive and not send, would be beneficial for signing up to services and organizing them, something I'm willing to go with if the entirely self hosted route fails

[-] OppressedBread@lemmy.ml 4 points 4 days ago

It really depends on what you want to accomplish.

Data Control.

while yes I've degoogled myself, I'm not very satisfied with the services I tried out (Proton, Tutanota etc) they always have some sort of compromise or sometimes their businesses model is too good to be true (at least for me) and being able to dictate what I need and what I don't + implementing privacy and / or security solutions according to my needs is a big benefit in my book, my threat model isn't something that worries me, I just like having full control and combat mass surveillance.

Your self-hosted server will have downtime as well, some planned but also some unplanned.

Strongly agree with this point and I am very aware of this, after all my homelab setup isn't Enterprise grade and I'm expecting a lot of issues but knowing my usage, I'm willing to take these compromises.

Thank you for this detailed post, I'll take these things in mind when trying this out from a learning perspective.

[-] OppressedBread@lemmy.ml 10 points 4 days ago

yeah its something that seems to be splitting the community, some say that they haven't had a single problem while others say its borderline impossible

view more: ‹ prev next ›

OppressedBread

joined 5 days ago