I still have it on my Pixel 8 Pro. It requires a double tap to occur in less than 300 milliseconds.
I still have it on my Pixel 8 Pro. It requires a double tap to occur in less than 300 milliseconds.
This bug has been the bane of my existence for almost four years now: https://issuetracker.google.com/issues/204650736
The Android version of the app still has the zoom/cursor offset bug when using a software keyboard from when they sunset RDP 8. That has been a severe usability bug for over three years now.
It would be extremely barebones, but you can do something like this with Pandoc.
It’ll probably be there, but at least it can be disabled in the settings now. It won’t go away on its own.
This was when I stopped using it for a while. I sent multiple feedback messages as it really irritated me.
That I agree with. Microsoft drafted the recommendation to use it for local networks, and Apple ignored it or co-opted it for mDNS.
Macs aren’t the only thing that use mDNS, either. I have a host monitoring solution that I wrote that uses it.
Yeah, that’s why I started using .lan.
I was using .local, but it ran into too many conflicts with an mDNS service I host and vice versa. I switched to .lan, but I’m certainly not going to switch to .internal unless another conflict surfaces.
I’ve also developed a host-monitoring solution that uses mDNS, so I’m not about to break my own software. 😅
Thank you! I was struggling to remember the proposal name.
Google was working on a feature that would do just that, but I can’t recall the name of it.
They backed down for now due to public outcry, but I expect they’re just biding their time.
Not with this announcement, but it was.
It depends on the model you run. Mistral, Gemma, or Phi are great for a majority of devices, even with CPU or integrated graphics inference.
Show me a music store I can purchase music from on my phone through an app, and I’ll purchase it.
I’m also going to push forward Tilda, which has been my preferred one for a while due to how minimal the UI is.
Pixel Experience is unfortunately dead now. 🙁
Yeah - the operating system (or perhaps the display hardware itself, not sure) has to stretch each software pixel to a fractional amount of larger hardware pixels. In the case of upscaling 720p to 1080p, each 720p software pixel has to stretch to 1.33 hardware pixels. This forces blending to occur, which makes the image less sharp.
The worst part of this in my opinion is reading text.
You also lose integer scaling if you need to run a game at common resolutions below 1080p. (720p/800p, etc.)
Getting Keycloak and Headscale working together.
But I did it after three weeks.
I captured my efforts in a set of interdependent Ansible roles so I never have to do it again.