That's the good thing about meshcore though. Even in 3-byte ID mode, you can still get 16 hops, so you don't need repeaters in as optimal of places as you would with meshtastic.

It's certainly better to have them in optimal places if you can, but if you can't then you can just put a repeater up on a flagpole at your house and it's still okay.

No life or limb risk necessary to bring it down from a 30-foot pole if needed.

Darn thing, the heck man.

Well, I hope my description was at least good enough so that you could properly replicate it.

If you happen to have an Android device lying around, you can go to Settings, Accessibility, and then TalkBack Screen Reader, and turn it on, and give it a try. And you will see what I mean that way.

Honestly, I'm not sure.

I don't know if this will help or not, but here is a video of me using my Android device in the way I mentioned, and I have it set so that you should be able to see where I touched on the display.

https://files.catbox.moe/qo7unk.mp4

Edit: A flick from left to right is the equivalent of using the tab key on your PC, and a flick from right to left is the equivalent of using shift+tab.

The flick can be from anywhere on the screen to anywhere else on the screen as long as it is from right to left or from left to right.

As an example, when you tapped the Wi-Fi icon, you would be able to swipe from left to right, anywhere on the screen, and the next thing announced would be whatever element came next, which I think was mobile data, but I'm not certain of that.

The flick has to be able to be done from anywhere on screen as a blind user is not going to know where the element is visually on the display. Most of the time.

Holy shit, this is amazing. As a blind screen reader user myself, thank you.

I do have one question, though. I noticed that you were doing taps on the screen in order to see what element was underneath it. What happens if you do a flick from, say, left to right or right to left, as that is how a lot of screen reader users navigate?

The way it works on other operating systems is that a quick flick to the right or left will read the next element or the previous element on the screen.

Edit: This just took Linux Mobile from a "maybe one day I can use this" to a "i could use this now" thing.

I've been thinking about making my next phone a post-market OS device, and now that desire just increased exponentially, thanks to this post.

I've had this app for quite a long time, but I've never seen anybody in the mesh, just because of how short-range Bluetooth is.

However, I have successfully used both meshtastic and meshcore, and I prefer meshcore.

This seems similar to PeerTube.

Oh yeah, sure, and you can absolutely run open-weight models on your own hardware, which is definitely an improvement from having to use an API from a company. But for me personally, I won't touch even open-weight models because they're not fully open source, and fuck that.

For me, it's open source or GTFO.

Pretty sure its bitrate, but idk 100%

For me, I'm going to be one of those hardliners who refuses to use closed source AI no matter how much better than open source it is.

Back when I was first learning about computers and operating systems and software, I did not care so much about open source or understand it and why it was important, so therefore I've made decisions that now I have trouble getting away from some closed source programs, and I refused to do the same thing with AI that I did back then.

Soon we will get higher bandwidth capabilities that may unlock more possibilities. The LoRa version 2 chips like the SX1262 are only capable of something like 20 to 40 KBPS, where the LoRa version 4 chips are supposed to be capable of 125 KBPS.