versluis

Joined 1 year ago

Karma
93
Submissions
4
Member since
Mar 28
If you feel the urge to contact me try ycomb at [myusername].nl.eu.org Beware I am a slow responder if I respond at all.
View on Hacker News

Recent submissions

Comment · 23 days ago
In the video is explained that the reason to build this project was a faster response time. I would love a quicker response time on my ereader. The emulator is just a demo. He explains at the start and end of the video he is building a project with fairly static screens. It sounds like a project where using epaper makes sense.
Comment · 1 year ago
Good that you mention it. I will add contact details. It has been a while so I don't remember the exact wording. I wouldn't use the same wording since it is not a petition and doesn't add value. They want to research if it is an unfair practice. In my opinion banking and wireless payments is a common good. Having two companies, who only approve software of partners, most of them including unremovable spyware, is limiting on access to banking and privacy (although privacy is another department). I mentioned security since that is Google's argument for the block even though GrapheneOS is more secure than approved builds. I gave the number of GrapheneOS users to make clear it doesn't affect only a few individuals. I think LineageOS users might also be affected?
Comment · 1 year ago
I did using their website form. It needs to be clear from the complaint that Google is violating fair market principles. They also like details about what exactly is happening and who is affected. That was why they called me after I filed the complaint.
Comment · 1 year ago
I love GrapheneOS. The biggest downside is that Google integrity API block wireless payments in Google Pay. All Dutch banks now advertise to install Google pay for wireless payments. I've tried asking Google to support GrapheneOS but they told me to do a feature request. Which I did and got no reply to. I've contacted the consumer market authority and made a formal complaint since Google and Apple share effectively a contactless payments duopoly and decide which OS distributions get access. Those are closed source and usually bundled with a lot of spyware. I also explained how the Google integrity API might affect banking availability in the future (and already does for some banking apps). They took it very seriously and I hope to hear from them in the future.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton