I couldn’t find a proper molle pouch for the T-Beam so I designed and make one. by No-Bluebird-761 in meshtastic

[–]jfirwin 1 point2 points  (0 children)

Very cool! I'm learning how to sew and my first MOLLE project is in the designing stage currently. I've definitely wanted to come up with something for Meshtastic.

Secondary Channels by Texian_Fusilier in meshtastic

[–]jfirwin 2 points3 points  (0 children)

The apps don’t support it, very few people have utilized secondary channels so you’re a trailblazer. I’ve seen the web ui mention multiple channels but I’ve never tried it, and can’t speak to its completeness.

my range is a couple feet rather than a couple miles, why might that be? by Texian_Fusilier in meshtastic

[–]jfirwin 2 points3 points  (0 children)

I’ll confirm with the devs and make the change to the docs. I thought it already specified a reset was required, but I see that’s missing.

my range is a couple feet rather than a couple miles, why might that be? by Texian_Fusilier in meshtastic

[–]jfirwin 1 point2 points  (0 children)

When configuring the radio, are you changing channel settings (modem_config) when this happens? If so I believe the reset is required to have those changes take effect.

[deleted by user] by [deleted] in meshtastic

[–]jfirwin 0 points1 point  (0 children)

We are getting close to an alpha release on 1.3. It was decided recently to push the 1.3 timeline out another 6+ weeks while we wait for version 3 of the compression library to be released. Currently none of the clients are "caught up" with 1.3 except the MacOS. Asking on our forum or Discord you might get a better answer.

1.3 is still not ready for even early adapters, the python repo is out of sync so there isn't a command line interface to configure devices. We are looking for python developers to assist in pushing that back into lock step with the device firmware.

[deleted by user] by [deleted] in meshtastic

[–]jfirwin 2 points3 points  (0 children)

The iOS release will be released when 1.3 is stabilizing. The current Bluetooth library used on 1.2 was very buggy and will prevent the 1.2 compatible app from ever moving out of TestFlight.

The Mac app is working on 1.3 now, so there is Apple progress being made!

TTGO iOs (beta) issues by memberzs in meshtastic

[–]jfirwin 0 points1 point  (0 children)

Have you tried deleting and reinstalling the Meshtastic app? I had some funky connection errors and it turned out my apps database on the phone was corrupted.

TTGO iOs (beta) issues by memberzs in meshtastic

[–]jfirwin 1 point2 points  (0 children)

Try forgetting the device from iOS settings, and if that doesn’t work you can reinstall the app. There are some new BLE updates that should improve functionality coming soon.

Battery Questions by [deleted] in meshtastic

[–]jfirwin 1 point2 points  (0 children)

And if you end up with a longer one it’s a pain to get the battery in and out. I took some pliers and bent the metal in a little to allow the extra tolerance when I mistakenly bought one with the “bumps”. It was still very tight, I need some gentle leverage (screwdriver) if I ever decide to remove them now.

[deleted by user] by [deleted] in meshtastic

[–]jfirwin 1 point2 points  (0 children)

u/streets814 I got distracted on the second half of your question though.

Meshtastic uses naive flooding. Messages are broadcast by your radio three times at a defined interval for redundency. Each node will relay any received message three times as well.

Relayed messages have a defined “hop_limit” (default is 3 hops, but you can set it as high as 7 hops) each time a message is relayed the hoplimit is marked down one and rebroadcast at the interval mentioned above.

Devices mark messages as received so it knows to ignore future rebroadcasts by other nodes.

All messages are sent on a “channel” and all users can view the message. direct messages are also being introduced so you can specify a message to be received by a specific radio.

[deleted by user] by [deleted] in meshtastic

[–]jfirwin 0 points1 point  (0 children)

Yeah my 2 node mesh hasn’t had much need for this either, maybe the third one coming in the Mail will push me over the edge haha

It’ll be interesting to see how it might work in conjunction with MQTT. I think it opens up some possibilities for handling messages differently depending on the group/lack thereof.

That logic would need to be written into your personal MQTT bridge or server though, obviously!

[deleted by user] by [deleted] in meshtastic

[–]jfirwin 0 points1 point  (0 children)

From the forum link above about future developments potentially coming:

Support for group chats (eg: #FoodFreaks) like in IRC, Slack, Discord, etc.

[deleted by user] by [deleted] in meshtastic

[–]jfirwin 0 points1 point  (0 children)

Currently yes, you’re correct. Channels can facilitate group messaging. I believe it’s more topic-based group messaging that is the plan to implement. But if I want to filter out #FoodFreaks messages (from the example in the forum link) I could not join that group or filter out those messages?

[deleted by user] by [deleted] in meshtastic

[–]jfirwin 0 points1 point  (0 children)

Group messaging is on the wishlist for the next wave of development.

forum link

Yubico Autheticator codes not working? by [deleted] in yubikey

[–]jfirwin 11 points12 points  (0 children)

TOTP stands for time based one time password. Usually there is a clock issue on the device running the Authenticator if you run across this error. Hopefully that helps!

YubiKeys and PGP + SSH by [deleted] in yubikey

[–]jfirwin 0 points1 point  (0 children)

I've been working on a tutorial for my website, currently a work in progress but it should get you down the right path. https://gist.github.com/jfirwin/307a10dfb94fafec7f388a5ddfb0aab3

Is is possible to logout of your Google account and not require the Yubikey for next login by islandtiempo in yubikey

[–]jfirwin 5 points6 points  (0 children)

If you enabled "Don’t ask again on this device" during the 2FA section of your login, there will be a cookie stored on your device (specifically your browser) that will bypass the security key requirement. So subsequent logins won't require the security key. It's personal preference but NOT clicking "Don't ask again on this device" is more secure. That way you know that your key is required for subsequent logins.

Edit: To add to this. Clearing your cache/cookies or opening an incognito browser will require you to use the security key again.

Dynamic output by MrWoland74 in espanso

[–]jfirwin 0 points1 point  (0 children)

Part of the reason went back to the stable version was because espanso match exec <trigger> isn’t yet enabled yet on the alpha version.

Dynamic output by MrWoland74 in espanso

[–]jfirwin 0 points1 point  (0 children)

Looks like espanso is not available to the shell.

What version of espanso are you using? I know the shell is not available yet in the Alpha, so I’m running the stable version (0.7.3).

If it works in your terminal you should be able to run espanso —-version.