Stop advertising your name at the top of every comment.

If you go to the firmware flasher: https://flasher.meshcore.dev/

That shows what’s supported with ready-to-go firmware. The community firmware is what’s mostly used. MeshOS and Ripple are more special cases that you probably don’t need to worry about when you’re getting started.

Then this is far from an exhaustive list of devices, but not bad for getting started:

https://nodakmesh.org/meshcore/devices

If you want a ready-to-go device, and are brand new to LoRa radio, just look at the pictures for the devices that are already in cases and with antennas, vs. the bare boards. And basically, there’s almost total cross-compatibility with devices running Meshtastic or Meshcore. You can always flash the firmware from one to the other to try each one out.

Yeah, the official app isn’t super open-source, but the protocol is, and other companion apps are being developed. So far the only restriction I’ve found is that I’ve got to wait 10 seconds when doing remote repeater admin via the mesh.

Or just run it on a standalone, like a T-Deck, which is what I normally do! Bonus, you can stick M5 Launcher on the T-Deck, and bounce back and forth between 'tastic and 'core with a simple reboot.

Or Meshcore if you’re in a fairly populated area.

Everyone should try both, and see what’s more established in their area!

Yeah, but Microsoft shouldn’t get credit for that. Windows only works with everything, because everything got built around it.

Drivers are needed for every little bit of hardware, Intel very well might not have become the dominant architecture if Microsoft hadn’t picked it in the 80s.

SuSE can hang out with New Zealand and Gen X

Haha, yeah, I probably wouldn’t have learned to care that much if design clients didn’t yell at me about it 20 years ago.

I don’t use AI much. Is it actually using two dashes? 'Cause an em dash is its own character: “—” vs --

I had to put those in manually with the — html entity in the pre utf-8 web days.

https://www.youtube.com/watch?v=_loUDS4c3Cs

An interesting take on the technical hurdles it would have taken to even be able to fake what we saw during the moon landing.

tl;dw: It might have just been easier to go to the moon instead.

I built a computer in 2012 with the idea of having 3 OSes to boot from: Windows 7, Mac OS 10.7 (hackintosh), and CentOS.

I partition the drive into three main parts, and install each OS on one each. Except that I had to do it again, because Windows 7 lost its absolute shit that it wasn’t on the first partition. Just threw an absolute shit-fit that it didn’t come first.

So I re-do the installations, let Windows be first in the partition order, Mac OS second, CentOS third. The next problem was that I couldn’t download any drivers on Windows, because it couldn’t recognize the absolutely bog-standard network controller on my motherboard. So I boot into Mac OS X, which (with a couple of quick kext edits) already recognized all of the hardware on the mobo despite none of it being Apple or Apple related, download the drivers for windows, throw them on a FAT partition I set up to exchange data between the OSes, and finally get Windows running in about 4x the time it took to get Mac OS running on the exact same built-for-windows hardware I’d cobbled together.

And of course I fire up CentOS, and it was pretty much, “I got this” right off the bat.

I’ve been using Windows and Mac OS since the late 80s, and linux since about 1999, and I still have never encountered a more fussy OS than Windows.

Nice fronthawk

It’s the new game: AI, or late 00s overzealous image sharpening?