I don't want to put information into a black box of mystery that can then be used for other monetization purposes. I am still waiting for a realistic local solution.
I read the article saying they were testing service changes on paying users without knowledge or explicit consent of the user, that the user had to test and determine why they perceived their sevice changed.
That is a dark pattern to inflict on users expecting consistent output.
I troubleshoot thermal printers for work and the error is rarely in the hardware. I have no issue with this work request; TPs are deterministic and predictable.
The profiles work fine in Apple Classroom mode. Just a question of SSD space for the active profile(s) and a cloud source that can be used to swap them around if the SSD saturates.
This 'red line' was quite apparent around 10.14 when macOS and iOS were set on the collision course we see today in Ta-hoe. So much wasted visual space in the last 5 releases, making room for touch.
I doubt we'll see a pseudo macOS mode on mobileOS, but the mirroring for iOS in the last 2 major releases of macOS is just a jump to the left of local emulation.
I could've done without the useless Samsung button that doesn't do anything but whine for a Samsung account before you can change the behavior of the button. So I used adb to disable the button entirely, to prevent the whiny Samsung page from accidentally being pressed on the button raised off the left side of the s10e.
I'm faster with one thumb on t9 than two thumbs on a touchscreen and I don't need my eyes except to proofread. Those phones with the transforming screens changing from smooth to textured.