87
Why did PinePhone fail? (sh.itjust.works)
submitted 1 year ago by to c/linux@lemmy.ml
24 comments fedilink hide all child comments
 

Six years ago the entire Linux enthusiast space was super excited for the PinePhone, then everything fell apart. What went wrong? Was PINE64's favoritism towards Manjaro the sole issue or were there other problems?

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 year ago* (3 children)

Just 2ct's on the banking thing (sorry if it sounds rude, but I just can't hear it anymore):

Just forget banking apps of you don't want to stay on iOS or proper Google Android forever and ever and ever, even AOSP-based OSes struggle with that (a lot).

Go to a bank that still has a proper website and allows some kind of hardware device for TAN (and tell them that this is why you are leaving/joining) - we need to show market demand for alternative solutions or else these will disappear completely over time.

We also need to make regulators/politicians understand, that taking part in life must be possible without owning a device blessed by Google or Apple. We really need laws here.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 1 year ago (2 children)

    It's not rude but it's incorrect. I have a deGoogled phone and do mobile banking with it. I don't know for how long though but just to say it's possible today.

    Yes though I do recommend relying on a bank that does not force its customers to use Apple or Google only. I hope they'd be a way to disclose that beside just name & shame.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 year ago* (1 child)

    Glad that works for you! With my bank (comdirect.de) I can use a mobile website, and if I were to use something AOSP- or Halium-based, I could also use their PhotoTAN app, which, as the name implies, needs a working camera in Waydroid (on my OP6 with pmOS, the cameras work via libcamera, but not in Waydroid), so I have a small gadget for all these TANs.

    My main worry with the "let's just use Play Store/Aurora store and the run that apk"-approach is that it does not really send a visible signal to banks that they need to keep considering customers that don't use Android proper.

    It also always means that the next update (e.g., after some consultancy or some audit happened) may not work any more, meaning, access may be revoked at any time. Complaining to customer service or in Play Store reviews may have an effect, but it will still hurt. I think I would feel a tad safer if a banking app lived on FDroid... but sill.

    I hope this gets my point across.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 1 year ago* (last edited 1 year ago)

    100% get your point and indeed agree. I think verification overall is pretty much tied to iOS/(Googled)Android so my (probably naive) hope is that physical token or passkeys that are NOT platform or service dependent gain traction. That's why I got excited when https://github.com/keycloak/keycloak/issues/23656 was recently merged. I still have to test it but anyway more and more of the services I use online (self-hosted or not) are now behind "Log in with a device" and/or WebAuthN where I feel I can properly login, using e.g. YubiKey Bio or NitroKey, without anybody in the middle "owning" my identity or at least the verification step. I believe this is pretty much the "last battle" to have secure interactions without a central (commercial or not) actor in the middle that can use this to reshape our behaviors and interactions.

  • permalink
  • fedilink
  • source
  • parent