The best three brands with natively-supported hardware:

• HTC’s Vive series headsets
• Bigscreen’s Beyond
• Valve’s Index

Pretty much everything else requires a lot more tinkering than just launching SteamVR/OpenVR applications.

Some helpful links for diagnosing compatibility:

• https://help.steampowered.com/en/faqs/view/18A4-1E10-8A94-3DDA
• https://steamcommunity.com/sharedfiles/filedetails/?id=2984005943

Just note that with Bambu printers about past data collection practices and their in general mid to atrocious after-sales support. If this doesn’t deter you, then go ahead and get one.

I do a lot of my functional parts in ABS, ASA though printing such material may be difficult on an open-air machine. The two obvious choices will generally be PLA or PETG. PLA is one of the most common printed materials, and is fairly balanced in material strength. PETG parts are more likely to permanently deform heavily before fully snapping, as well as they have a but more temperature resistance than PLA. Additionally most PETG plastics hold up decently well to UV, often making them more suitable for parts that need to be outdoors.

PLA takes not much consideration on surface to print, as most printers come with a smooth PEI build sheet by default. It will however need more cooling than printing with PETG at equivalent speeds. If you use a PEI sheet for PETG, make sure it is textured. You will destroy a smooth sheet if it doesn’t have some kind of release coating to lower its adhesive properties to PETG.

There is no guarantee for spools of filament to actually arrive dry, so a filament dryer isn’t a bad idea. I don’t have any particular recommendations for a good filament dryer. I have a Filadryer S2 from Sunlu, but am not impressed by it.

As I understand it, this driver isn’t ready for personal use unless you don’t care about the contents of your btrfs partitions mounted on Windows.

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

Wouldn’t this still be the superior solution? The article doesn’t mention the setup for using ROCm for cards running on amdgpu.

The specific patent links seem to be broken. All return 403. Here are functional alternatives.

• 9421713
• 9592660
• 7555357
• 9168698 / 10556381

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.

2-2-1 still insinuates having a remote backup. I don’t see how this particular threat destroys a 2-2-1 setup.

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.

Use the OCI through podman or docker.

The heated bed is coupled to a thermistor. I’d argue controlling the temperature in order to not accidentally overheat parts of the phone is a step above a hair dryer.

What compositor (desktop environment) and distro are you running for things to behave that poorly?

I have been utilizing BunkerWeb for some of my selfhost sites since it was bunkerized-nginx. It is indeed powerful and flexible, allowing multi-site proxying, hosting while allowing semi-flexible per-site security tweaks (some security options are forcibly global still, a limitation).

I use it on podman myself, and while it is generally great for having OWasp CRS, general traffic filtering targets and more built on top of nginx in a Docker container, the way Bunkerweb needs to be run hasn’t really remained stable between versions. Throughout several version upgrades, there have been be severe breaking changes that will require reading the setup documentation again to get the new version functional.

The username release is quite recent for those not participating in beta versions of Signal.

Before going any further to adjust your Z offset and other factors to tune for better bed adhesion, you should probably adjust your bed to actually be level as well as ensure (seeing that you only have one z lead screw?) that the X axis frame isn’t sagging on the side not containing your Z lead screw. Once you’ve got those factors sorted out, you should check your probe repeatability and then set your Z offset accordingly.

Bed adhesion even with proper, clean first layers can be a pain depending on the bed surface, material being printed, how clean the bed is of oils and other contaminants, how hot the material is being extruded, and how hot the bed is among other factors. While using a bed mesh will greatly help to account for off-zero unevenness in your bed surface, you really shouldn’t use it to compensate for uneven bed leveling (especially when it looks like you are nearing more than 0.5 mm in unevenness).

To diagnose other print issues, it will be helpful to see a picture showcasing the problems described in a failed print.

As a side note, it is somewhat difficult to read your Klipper config file without using view source as it is being markdown formatted. You can negate it by using three graves on the lines above and below it so that it is wrapped in a ‘code block’ and isn’t formatted.

```
Some code
  eeeee
  fffff
```

Turns into

Some code
  eeeee
  fffff

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.