alex3305

I am currently using Brave after switching from Chrome. Chrome changed the way accessibility worked last year which didn't work for me. Instead of scaling text it zooms in on pages which results in an undesirable scrollfest.

Once in a while I retry Firefox but text scaling is a hot mess. On some sites it simply doesn't work, on others content will go outside of the bounding box and on some sites it just clips text. For me it is barely usable in its current form leaving me at Brave.

Is this the reason that Chromium based browsers always change font sizes for me on here? Since I'm visually impaired and have set my text sizing pretty large, I have that issue on multiple sites, including Hacker News. It's a bit of a gamble how large text will be when I refresh the page.

> Do they?

Probably not. In my experience most standards are pretty broadly defined with hardly any technical requirements.

For instance in ISO 27001 it states that you should create awareness in your organisation about information security. A very minimal way is to send a mass email to everyone in the organisation or hang up posters in the office. But I also spoke to someone that was determined that a half day security awareness training was minimally required.

Brave browser recently also introduced buttons. I was a tad annoyed with it, but accepted it. Until my wife recently saw the new look while I was working and asked how I could even put up with this. She argued that tabs should look like tabs and not buttons.

Fortunately for Brave the rollback is quite easy with a flag in `brave://flags` where you can disable the `brave-horizontal-tabs-update` feature.

AFAIK no. Dex only seem to act as a federated IdP.

Great addition. I remember that I also looked at Obligator and saved it to my bookmarks. But I decided against it because IMHO the project was just a bit too young. Normally I tend to ignore that, but I really didn't want to switch auth/SSO solutions in a couple of months time because of a lack of maintenance or something like that.

Dex only acts as a federated identity provider. Unlike oauth2-proxy which acts as a service provider for services that don't have authentication themselves.

Last year I bought a Microsoft Intellimouse Pro which I really, really like. Besides being a tad heavy it has been a pleasure to use. I didn't know Microsoft stopped making mice and keyboards. Such a bummer.

I wonder what some alternative brands would be. Logi has been terrible for me in reliability.

At university we were tasked with making an Android application for a real client. This was part of our course and was really fun to do. Especially because we did this in two groups competing with each other. The app was some sort of geocaching mixed with a quiz to discover a city in groups. We also built a server side app that accompanied the clients. This app was targeting Android 2.3 and ran on some sort of old Xperia device.

Building the app was a lot of fun and it worked pretty well most of the time. During beta testing however, we were given all the resources that were crreated by a third party. This mostly included UI elements and other images that made up the UI. Testing it out, again, it worked pretty good. Until one time it didn't...

After about an hour or so of playing, the app would consistently crash. After some OS troubleshooting, we came to the conclusion that apparently Android (at the time) had the habit of not putting images in managed memory, but separately. And whenever this space overflowed, an app would simply crash. To resolve this you would need to manage this space yourself and clear out memory.

However we only discovered this a week or so before the deadline. And implementing memory management would be nigh impossible to do. So I came up with the hackiest solution that I ever built. I added a crash handler to the app, which would start another instance. I also added a serializer / deserializer to the app and whenever you reached the main menu all play progress was serialized to storage. Whenever the app crashed and restarted, this was read again and letting the users resume play. The only side effected was some weird app flickering because of the crash and restart.

A week later when we delivered the app to our clients, they wanted to try it out and play test it. So we did, along with the other group. And lo and behold, after an hour or so the app crashed. And restarted. Unlike the other group, were the app crashed and had to be restarted manually.

In the end the client was really happy with the result. Because it just worked. AFAIK the app is still in production the same way it was about 10 years ago.

Until your Google Account gets banned for violating the ToS. No thank you.