2
points
ktosobcy
Joined 1,323 karma
- ktosobcy parentHuge problem (for me) with SaifishOS is… annoying UI. I know that a lot of people swear by swipe navigation but it's just darn inconvenient and imprecise (or rather - require a lot of precission to select desired option)… I tried to get used to it for a long time and I simply couldn't. Having to pay effin lot of attention each time I tried to do anything with the phone was simply to much…
- Anectodal: just the other day I put Fedora KDE 43 on "new" (well, second-hand after lease) computer for my father as the old one was on it's last legs and... it works just fine.
The machine came with Windows 10 by default and what he needed was Firefox and FreeCell, and FreeCell on Windows10 was atrocious.
He likes it a lot and the only thing was that I had to put same wallpaper as he had on Windows7 and icons in the same places.
The "linux is to complicated" argument just doesn't hold true anymore! It's nice and easy, including the installation (even I was surprised)
- Great. But IMHO better regulation is still needed: force makers to have unlockable bootloader and provided libre drivers for their device (for the OS that they originally ship with); force makers to provide alternatives - for example using alternative "play services" by only providing general API that others can provide pluggable implementaions…
- I was just suggesting that ING has different policies in different countries.
As for "we have to use google wallet!!!":
https://i.ibb.co/4Z9dMvzR/Screenshot-20251011-184343-Setting...
basically all banking apps for accounts I have (alior, PKO - biggest polish bank, ING Poland and spanish BBVA as well as curve to which you can add whicever card)
- > Sure, nothing strictly requires iOS/Android in paper specs and in presentations. But we all now that the only working practical implementations will be one iOS/Android. I mean, look at the actual code in the (Microsoft) github repo.
No, we don't know. You are projecting and again - spreading FUT.
Did you do anything towards implemeting the specs on other platforms? Or are you only very vocal online complaining?
In that repo they clearely stated, that they focus on Android/iOS as it's the most popular platform (contrary to what the IT bubble here may think) and want to reach the most user with the (initial) implementation.
> The EU forced Apple to open NFC for third party payments, which is great. But all the banks in the Netherlands only have working card payments in Apple and Google Wallet. Including the largest bank (ING), that used to have independent in-app NFC payment on Android (where NFC was always open) but seems to have capitulated and now only offers it via Google Wallet.
OK, again - you are projecting Netherlands issues over the UE. Surprisingly - in Poland I can pay with ING bank with NFC. Same in Spain with BBVA app.
Just because something is broken in your corner of the universe doesn't mean it's the global fenomena :)
Also - instead of complaining about the EU - maybe try persuaiding the entities to add support?
Alas - I'm pondering ECI initiative to actually force "Open Android" (ie. withou Google Services being required) as a valid platform because I was fed up with Google imposing more and more overreach. Android is quite OK if it werent for the walled garden from google…
- Please don't spread FUD. This is only REFERENCE implementeation of the specification: https://eu-digital-identity-wallet.github.io/eudi-doc-archit... which doesn't mention anything about being exclusive to iOS/Android.
From the linked repository:
> The EU Digital Identity Wallet Reference Implementation helps EU countries and stakeholders to build their own wallets. It consists of open-source code libraries, modular components, and a fully functioning reference application based on the ARF.
- Hmm... maybe not less, but IMHO majority of the startups now focus on "discrupting the market" and colleting enough VC money that they could survive to be bought up by the bigger player.
The whole landscape is put on the head - instead of promoting creating something new that could survive on its own and be useful and provitable for the creator we are now in the market of creating a fodder for the BigCorp
- That would be also nice, but given we can't make everyone to do the most basic interoperability I don't see it working…
As for: > Teens will easily bypass any method as many today watch porn
well, they do, but each obstacle discourage them to do that. It's like with chocolate while being on a diet - if you have it within reach next to you you are more likely to eat it; put it on a shelf which would require standing and walking - slighly less likely; put it in another room - even less; and if you don't have it in home and you would have dress up and take out the car and drive to the shop most likely you would just wave your hand at that :)
So no - it won't prevent it completely but I'd argue that it would significantly decrease the use :)
- Maybe Tigase (https://tigase.net/; https://github.com/tigase/tigase-server/) would work for you?
It does offer almost-linear horizontal scalability.
(disclosure, I work for Tigase)
- I kinda hope and root for EU's spec (https://ageverification.dev/Technical%20Specification/archit...) with "Zero Knowledge Proof" that wouldn't require passing actual ID to the service…
- Hmm... I found a couple of accounts I liked and completely removed "Discovery" tab and then I extend the followers list organically by the shared interactions (see some interesting comment in followers posting) or by following account from blogs/websites…
IMHO this is how "social-media" should work instead of being forced-feed with some automatic crap
