Nate Metzger

18 Followers
168 Following
39 Posts

Dealt nothing and bluffing hard
Playing poker with a joker and some Uno cards

Opinions are my own and are not reflective of my employer

On Mastodon SinceDec 17, 2022
Websitehttps://nathan.alphapuggle.dev
Self-Hosted Mastodonhttps://mastodon.alphapuggle.dev/@nathan
@courtney Excuse my ignorance, but what advantages does pushover have over homeassistant's built in notifications or ntfy?
@lproven Alternatively if they use apt-get instead of apt
@aeva Of course, why hadn't I thought of that
Happy "This poll has ended" to everyone who voted #ShirtTournament
I missed the infosec.exchange maintenance window due to spending time with my dog this morning. I’ll reschedule.

@me @robyn I assumed they meant the default UI on the T-Deck. Which is the "fancy" UI. There is a Bluetooth toggle in base UI mode but the docs say it also reboots so I'm assuming that it's also functioning as a client.

> Bluetooth Toggle - Enable / Disable Bluetooth (will reboot device)

https://meshtastic.org/docs/configuration/device-uis/baseui/

BaseUI | Meshtastic

BaseUI is a standalone interface for supported Meshtastic devices, enabling direct interaction without requiring a phone for common functions. It runs alongside the firmware, providing messaging and configuration options.

@me @robyn Yup was able to track down the docs page. This is the case

> MUI functions as a client, similar to the Android and Apple apps. It runs on one core of the MCU, while the regular Meshtastic firmware runs on the other. MUI communicates with the firmware using the Client API, the same interface used by other Meshtastic clients.

> The Client API supports only one active connection at a time, which means other clients cannot be used while MUI is running. Since not all settings can be configured within MUI, you may wish to boot into Bluetooth Programming Mode or BaseUI. This frees up the API so client apps can use the Bluetooth or serial connection.

https://meshtastic.org/docs/configuration/device-uis/meshtasticui/

Meshtastic UI | Meshtastic

Meshtastic UI (MUI) is a standalone interface for supported Meshtastic devices, enabling direct interaction without requiring a phone for most functions. It runs alongside the firmware, providing messaging, mapping, and configuration tools.

@robyn this is the expected experience. IIRC the esp32 inside isn't powerful enough to run the whole UI and the Bluetooth stack
We've been on X/Twitter for many years, but it's time to reduce our activity there and instead promote Mastodon as our main social media channel now. So we've done just that: https://x.com/LibreOffice/status/2026204949760131158 – Welcome to all our new followers here 😊
LibreOffice (@LibreOffice) on X

Hello, world! 👋 From now on, Mastodon is our preferred social media channel. It's an open source, decentralised platform – not controlled by tech giants. Follow us here: https://t.co/KZpwR61V5R

X (formerly Twitter)

Was poking around and realized that the developer verification options were already available in package manager. Here are some forced failures; this is what is coming to android by default

On the slightly brighter side, it looks like you can bypass it by using pm set-developer-verification-result com.package.name 0 1 or similar

#keepandroidopen #android_dev #android #android17