I got a NexiGo portable gaming monitor that I’m pretty happy with. It is a 16 inch 2560x1600 display, 144Hz, and supports FreeSync. I got a bidirectional DisplayPort to USB C cable so that I could use it with my desktop for LAN parties and it’s great. It has a built in flip-out kickstand, a folding magnetic cover, OK built in speakers (good enough to game with anyways), and can be powered via a second USB C port with an A to C cable. On a device that supports USB C video output like a laptop or Steam Deck it can run off a single cable but I mostly wanted it for my desktop.

When it first came out it had double steak, when it became a permanent item it was made smaller.

Some of my favorites:

• Chicken flatbread melt (like a taco but with a fluffy flatbread instead of a tortilla)
• Beefy 5 layer burrito
• Cantina Chicken Quesadilla
• Breakfast Crunchwrap (preferably steak)

The Cantina Chicken Quesadilla is one of my favorite items lately. The new green sauce is pretty good too.

I’ve tried most of the common options (with the notable exception being the vastly overpriced Librem 5). The best option IMO is the OnePlus 6 or 6T (they’re almost identical) running postmarketOS. It is much faster than the PinePhone Pro with way better battery life and has proper modern GPU support (OpenGL up to 4.x, Vulkan). The main thing preventing daily driving the OnePlus 6/6T is that the earpiece audio doesn’t always work for calls and that it won’t wake from sleep when an incoming call comes in. The PinePhones are better to use for voice calling, but slower, lacking many graphics APIs (no Vulkan, limited OpenGL), and have much worse battery life. The camera doesn’t work at all on the OnePlus phones yet, it is starting to work on the PinePhones but the picture quality isn’t all there.

At the moment I have both a OnePlus 6 and 6T, but I have stock Android on the OnePlus 6 and postmarketOS on the 6T. I use the Android one as my daily driver with my primary number SIM but got a second cheap Mint Mobile SIM for the postmarketOS one for experiments and mobile data. I prefer browsing on the postmarketOS phone, and I use it for VPN, SSH access, file management, and some coding on the go which are things Linux phone excels at over Android. I mostly use the Android phone for calls, texts, camera, maps, email (GMail), Discord, and casual browsing. If they fix the earpiece audio issue I would probably be fine daily driving the

Open source NVIDIA drivers (NVK, nouveau, nova) finally being usable for gaming.

Linux phones, postmarketOS

RISC-V CPUs becoming more and more viable

Linux on phones and tablets is a thing. Typing from my Xiaomi Pad 5 Pro running postmarketOS and LibreWolf.

How is the external display connected? I have never seen Freesync over HDMI work. The early implementations were AMD proprietary and the new ones require HDMI 2.1 which has some ridiculous bullshit about not being implemented by open source drivers. HDMI sucks, use DisplayPort if possible. If your laptop doesn’t have a DisplayPort connector, try a USB-C to DisplayPort cable, as usually the type C ports on laptops support DisplayPort alt mode.

Hot dogs

Freddy’s fry sauce, barbecue sauce, teriyaki sauce, honey mustard, cocktail sauce, malt vinegar, cheese sauce

I wish these implementations of secure boot were designed more to protect the SOFTWARE against “theft” than the HARDWARE against “tampering”. Let us wipe the secure boot keys, but in the process erase the firmware (or have the firmware encrypted so that erasing the keys renders it unbootable) and then allow new code to run. Blocking third party firmware on consumer devices is a shit move. It just creates more e-waste when the OEM stops updating it and the community can’t make their own replacement firmware.

Pretty much all ext4 except for a few Windows installs on NTFS.

True, but if you buy a finished product that uses the new chip that has secure boot enabled, you can’t flash your own firmware. From what I gather, the boot keys are burned into OTP memory so they can’t be erased or changed. The chip is permanently locked to that firmware.

Not really a fan of putting secure boot on. The only purpose that serves is locking the customers out of their purchased hardware. Raspberry Pi is clearly not targeting the maker market with those changes, they want that corporate money and are willing to stick the finger to hackers and makers in the process. Can’t make custom firmware if you can’t boot it.

RISC-V support is nice. I like the idea of being able to work as both an ARM and a RISC-V microcontroller while sharing the same array of peripherals.

Maybe this explains why my webcam indicator is on when no applications are using it. It’s been confusing me for a while now. I’ve double checked anything that I expect to access it is not, and it doesn’t seem to be locked because opening it works, but it sometimes boots up woth the light on. I am using Arch with pipewire so I’ll check and see if this is what’s going on.

I second this, second disk is best as you can keep your old Windows drive in case you ever need to go back for any reason. Modern UEFI makes dual booting way easier than it used to be as the UEFI itself provides a boot menu so you don’t need to fiddle with dual booting using a bootloader like GRUB.

I’m not sure about FF specifically, but 99% of the time you’re connecting a microcontroller to a PC you’re doing so over a serial port (UART) of some sort. It may be a physical COM port or it may be a USB to serial adapter or even a purely virtual serial port over a USB connection, but the methodology is all the same. Unless you are running a serial terminal on that port (as in, a commandline on your PC served on the given /dev/ttyX interface, not a terminal emulator letting you read/write from the port), the microcontroller can’t just run scripts on the PC. Instead, you will want to write a script/program that opens the port and waits for a command to be sent from the microcontroller, then that listener script can execute whatever functionality you require. Note that only one application can have the port active at a time, so if your listener is a separate program from your event handler, you will have to close the port on the listener before running the handler, then reopen the port on the listener once the handler is done so it can start listening for the next event. Better to just make it all one program that is always running on the PC and does both listening for events and handling them so there’s only one program that needs access to the serial port.

No way in hell.

I don’t disagree, but today the blame lies with CrowdStrike, not Windows. As much as I hate defending Windows.