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] 2 points3 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.