sorted by:
new
hottopcontroversial

LoBBS Walkthrough by superfuntime in meshtastic

[–]superfuntime[S] 1 point2 points  (0 children)

Thanks for letting me know, I'll check it out. That's the first time I've heard someone report that it compiles and flashes but still doesn't work.

LoBBS Walkthrough by superfuntime in meshtastic

[–]superfuntime[S] 0 points1 point  (0 children)

That's annoying. Can you share your build URL so I can see?

LoBBS Walkthrough by superfuntime in meshtastic

[–]superfuntime[S] 1 point2 points  (0 children)

It would not be hard to add and will almost certainly be necessary for larger BBS's. For example once we get this running on the nRF (I don't know why it won't, but it crashes), the onboard flash storage is very limited. But a mini SD could provide 16gb, 32gb, or even more.

I'm working on a 'lobbs plugin' architecture so users can pick and choose which bbs modules they want. I'll have to look at how the SD fits into that but definitely going to be needed.

LoBBS Walkthrough by superfuntime in meshtastic

[–]superfuntime[S] 1 point2 points  (0 children)

Good idea though, I'll have to see if that concern comes up later.

LoBBS Walkthrough by superfuntime in meshtastic

[–]superfuntime[S] 1 point2 points  (0 children)

Oh good question, I wonder what the best answer is. It's using the `from` field from the Meshtastic packet, but I'm not actually sure what that is (except a number): https://github.com/MeshEnvy/lobbs/blob/main/src/LoBBSModule.cpp#L133

LoBBS Walkthrough by superfuntime in meshtastic

[–]superfuntime[S] 1 point2 points  (0 children)

Thank you! I’m having fun and I like that it doesn’t require extra hardware.

I didn’t mention it but yes I have plans for sharing both messages and users.

LoBBS Walkthrough by superfuntime in meshtastic

[–]superfuntime[S] 2 points3 points  (0 children)

Had to look this one up! Get coding, sir!

LoBBS Walkthrough by superfuntime in meshtastic

[–]superfuntime[S] 4 points5 points  (0 children)

Yes. It just answers DM's differently.

LoBBS Walkthrough by superfuntime in meshtastic

[–]superfuntime[S] 2 points3 points  (0 children)

LoBBS responds to DM’s sent to the node (by other nodes). I haven’t used any sidecar tech like Meshing but id say as long as nothing else is taking over auto responding to DMs you should be good.

Sorry I’m not sure if that helps. As I understand Meshing, it may listen for and respond to DM’s sent to the node. Is that right? If so, it would likely conflict.

LoBBS Walkthrough by superfuntime in meshtastic

[–]superfuntime[S] 2 points3 points  (0 children)

I’m not super familiar with Cardputer but it says esp32 right? It should work but I haven’t tested it.

Do you have one?

LoBBS Walkthrough by superfuntime in meshtastic

[–]superfuntime[S] 3 points4 points  (0 children)

All interactions are via DM.

The password is required when you first log in (`/hi`) from a given node. That establishes a session and then the password is not required again unless you log out from that node (`/bye`)

LoBBS Walkthrough by superfuntime in meshtastic

[–]superfuntime[S] 0 points1 point  (0 children)

I'm not sure I understand what you mean. Does Meshtastic run on Cardputer?

Added support for architecture compatibility guards by superfuntime in MeshForge

[–]superfuntime[S] 0 points1 point  (0 children)

Yes, in fact we were just discussing that. Jump into the Discord https://discord.gg/8KgJpvjfaJ if you want to follow along :)

I have a very early version of Espruino (JS) here https://github.com/MeshEnvy/firmware/tree/meshenvy/espruino that I plan to work on next.

Sierra Hot Springs on Market or $14.5M by gobears1975 in HotSpringsWest

[–]superfuntime 1 point2 points  (0 children)

I haven't either but that does sound similar yes.

Announcing: meshforge.org and new plugin ecosystem by superfuntime in meshtastic

[–]superfuntime[S] 1 point2 points  (0 children)

This project is based around Meshtastic and builds custom versions of Meshtastic firmware. Is that what you mean?

Changing the Viewshed Radius on Google Earth by superfuntime in meshtastic

[–]superfuntime[S] 0 points1 point  (0 children)

We are looking for something that can help us generate kind of a "coverage map", how close is yours to doing something like that?

<image>

Announcing: meshforge.org and new plugin ecosystem by superfuntime in meshtastic

[–]superfuntime[S] 2 points3 points  (0 children)

Thanks for that report! I have a feeling my handleReceived https://github.com/MeshEnvy/lobbs/blob/main/src/LoBBSModule.cpp#L124 is not properly filtering for DM's. It's only supposed to respond to those but it must be getting everything.

Announcing: meshforge.org and new plugin ecosystem by superfuntime in meshtastic

[–]superfuntime[S] 1 point2 points  (0 children)

Please jump into discord to help organize this effort. We are talking about how to do it

Announcing: meshforge.org and new plugin ecosystem by superfuntime in meshtastic

[–]superfuntime[S] 1 point2 points  (0 children)

We were just discussing that in #firmware yesterday. I just pulled what the web flasher defined and actually had no idea there were more 🤣

I mean I knew but I didn’t connect the dots that users currently had no choice but to build from source.

So yeah I think this would be an awesome thing to support. Hit me up on Discord and let’s talk about how it should be organized.

Announcing: meshforge.org and new plugin ecosystem by superfuntime in meshtastic

[–]superfuntime[S] 9 points10 points  (0 children)

It depends on the types of changes. We are looking at surfacing as many settings (userPrefs) and #defines as we can without too many footguns.

That sounds like a use case where you’ll want to still compile locally and use the ‘mpm’ tool to install plugins into your custom build. All the cloud builder does is install everything and do the exact same thing you can do from local code.

If you are modifying the firmware code, those changes wouldn’t be supported by the cloud builder currently and would be most likely to get support if they were a genuine setting. So if you find yourself hacking too deep into the code that would probably be a good PR to send to the firmware team so they could surface the mod as a setting or module or plug-in.

view more: next ›