The easiest ways to run custom executables for Proton titles is either going to be SteamTinkerLaunch or my shim script.

It doesn’t currently allow for concurrent execution of EXE files, but that’s a good idea. I’ll see about implementing it.

We are well beyond the point of a majority of common hardware having built-in kernel drivers and userland software for extra stuff like RGB control that the best advice is rather avoiding Linux, to instead avoid the trash hardware (NVidia for the time being, GoXLR, Broadcom, etc.). My GPU, audio hardware, network interfaces are both popular products and have worked out of the box for years now.

Tiny 11 comes in two variants:

Tiny11 Core is not suitable for use on physical hardware as it outright disables updates. It’s best used for short-term VM instances.

Tiny11 also has problems with updates. The advantages gained through Tiny11 will erode with applying Windows updates. The installer is more tolerable than Windows 11 by not forcing an online account (but still needing to touch telemetry settings). Components like Edge and One drive will inevitably rebuild themselves back in with cumulative updates. If this is something that coerces you to not update your system, don’t subject yourself to using Tiny11. Additionally Tiny11 fails to apply some cumulative updates out of the box, which could be a further security risk.

I recently tested the main Tiny11 in a VM based on a different user recommending it in a now deleted thread. I was skeptical knowing the history of Tiny10 onward that 11 would actually be able to update properly, and NY findings backed up my initial skepticism of functional updates.

The worst gotchas and limitations I have seen building my own self-host stack with ipv6 in mind has been individual support by bespoke projects more so system infrastructure. As soon as you get into containerized environments, things can get difficult. Podman has been a pain point with networking and ipv6, though newer versions have become more manageable. The most problems I have seen is dealing with various OCI containers and their subpar implementations of ipv6 support.

You’d think with how long ipv6 has been around, we’d see better adoption from container maintainers, but I suppose the existence of ipv6 in a world originally built on ipv4 is a similar issue of adoption likewise to Linux and Windows as a workstation. Ultimately, if self-rolling everything in your network stack down to the servers, ipv6 is easy to integrate. The more one offloads in the setup to preconfigured and/or specialized tools, the more I have seen ipv6 support fall to the wayside, at least in terms of software.

Not to mention hardware support and networking capabilities provided by an ISP. My current residential ISP only provides ipv4 behind cgnat to the consumer. To even test my services on ipv6, I need to run a VPN connection tunneling ipv6 traffic to an endpoint beyond my ISP.

I’m glad I am not the only one who calls my little ASUS netbook craptop. Kinda flimsy and definitely underpowered, but a perfect little device to run basic applications and terminal applications on a minimal window manager.

User-Centric Innovation: Unveiling the Industry-Leading Battery Life

We know how a smartwatch becomes integral to its wearer’s life, and battery life can’t be a concern. That’s why we went back to the drawing board, driven by community feedback, to ensure the OnePlus Watch 2 delivers an exceptional user experience. With up to 100-hour battery life in full Smart Mode, it sets a new industry standard, ensuring that your watch keeps pace with your life, uninterrupted.

Really impressive how OnePlus is touting a relatively mediocre 4-day (at best) battery life on a smartwatch as something exceptional or something that they (falsely) claim as industry-leading. Maybe it is good by typical WearOS device standards, but is by no means top of the line for the smartwatch industry.

The desired alternative is not Matrix simply because privacy-conscious, open-source ecosystem vs. proprietary solution is not the goal. Matrix would still generally be terrible for support. What people want is publicly searchable content that is ideally indexed like a wiki. Many will happily settle for issue boards or even forums though. Discord has pathetic search capabilities in comparison to any search engine and has no way to properly and publicly backup information that is posted to the platform. With a website of any kind, one could clone the site for mirroring or simply get a web archive service to crawl relevant sections.

Not the same person, but I greatly enjoy my (now second) Pebble classic for several reasons, which I imagine some are shared between Starayo.

• Always-on Display
• Week-long battery life
• High contrast display that can be read easily in low light as well as in direct sunlight
• Simple notifications support, with quick canned replies
• physical button navigation that make the watch easy to use without needing to look at it
• Isn’t obscenely large
• quick launch application shortcuts from holding side buttons
• simple media playback control that is responsive
• Doesn’t attempt to be another smartphone, but rather as a local companion to your existing smartphone (doesn’t thrive on individual apps, but rather companion apps to complement smartphone usage)
• Customizable and relatively simple to write applications and watchfaces for.

Unfortunately for me, fossil’s watches do not match up. Looking at the gen 6, still uses an ill-suited AMOLED display that is bound to have poor contrast in direct sunlight unless the brightness is cranked so far that it will blow through the battery. Even then, the average battery life on the gen 6 is atrocious compared to most Pebble models as many reports say it can make it through one day. I’m sure by now, WearOS devices have worked out some of the kinks to make them easier and faster to use, though I am not sold on needing a personal assistant in order to do basic tasks (as Fossil markets their gen 6 smartwatch; I do doubt that this is necessary for general function).

Also, this might be controversial, but I personally feel that a device that has Bluetooth and is intended to communicate with a device that is often within ten feet of it really doesn’t need to waste resources and probably become more of a privacy nightmare by including Wi-Fi, LTE, and other data communication methods (beside NFC). Furthermore, pretty much every WearOS device I have seen has had a struggle to keep battery life for more than a couple days, and everyone deems that devices that can should be praised for whatever reason. Seeing as my ancient smartwatch that does most of what these newer watches do yet can effortlessly hold a six day battery life at worst, I seriously question why newer watches that have so much compromise and are incredibly misguided as to what a complementary wearable should be are what are being developed. Not to mention that the Pebble classic on launch was $99 USD whereas one can easily find $400+ smartwatches that still have way too much compromise in comparison.

There are not many Android phones that actually let you flex the open source benefits of AOSP. Android as it is packaged on many devices is not open source, and nor are the devices willing to fully let you install what you want. Ironically some of the only choices you have with the highest degree of freedom are from google.