Feature: Enable/Disable chat environment option #38

New Issue

2026-10-04T22:57:45+02:00

adam commented

2026-10-04 22:57:45 +02:00

It would be nice if administrators had the option to enable or disable the chat on a PotatoMesh instance, as some people might prefer to only show a map to the public and keep the chat to the mesh for privacy reasons.

I’ve included an example on how this would look on the website based on my own modifications on the code myself.

It would be nice if administrators had the option to enable or disable the chat on a PotatoMesh instance, as some people might prefer to only show a map to the public and keep the chat to the mesh for privacy reasons. I’ve included an example on how this would look on the website based on my own modifications on the code myself. ![](https://cdn.imgpile.com/f/48FXLvv.jpeg)

adam closed this issue

2026-10-04 22:57:46 +02:00

adam commented

2026-10-04 22:57:47 +02:00

Make sure to also disable the /api/messages endpoint, otherwise people can still query your database.

I personally don't see a reason to implement such a feature as the entire point of this dashboard is to show public chatter and metadata. There are a handful meshtastic dashboards that do only show nodes on a map but not chat and I wanted to specifically have one that does provide as much public info as possible.

Make sure to also disable the `/api/messages` endpoint, otherwise people can still query your database. I personally don't see a reason to implement such a feature as the entire point of this dashboard is to _show_ public chatter and metadata. There are a handful meshtastic dashboards that do only show nodes on a map but not chat and I wanted to specifically have one that does provide as much public info as possible.

adam commented

2026-10-04 22:57:47 +02:00

Understandable. I only had the thought to have more customizability as to what data is shown to the public, since this is a simple project to get something going quickly. Also with how reports are done, it doesn't heavily rely on MQTT like other popular choices which I personally like.

As a side note, yes I already disabled the messages URL since it wasn't being used. No need to have the application collect data it isn't using.

Understandable. I only had the thought to have more customizability as to what data is shown to the public, since this is a simple project to get something going quickly. Also with how reports are done, it doesn't heavily rely on MQTT like other popular choices which I personally like. As a side note, yes I already disabled the messages URL since it wasn't being used. No need to have the application collect data it isn't using.

adam commented

2026-10-04 22:57:48 +02:00

Can you try? #204

Run the app with PRIVATE=1

Can you try? #204 Run the app with `PRIVATE=1`

adam commented

2026-10-04 22:57:49 +02:00

Ran the branch in a separate directory and it looks like it works. Chat is hidden and everything else seems to function.

Here's the command I ran: SITE_NAME="Meshtastic Map" DEFAULT_CHANNEL="#LongFast" DEFAULT_FREQUENCY="915MHz" MAX_NODE_DISTANCE_KM=35 MATRIX_ROOM="" API_TOKEN="<api-token>" PRIVATE=1 APP_ENV=production bash app.sh

Ran the branch in a separate directory and it looks like it works. Chat is hidden and everything else seems to function. Here's the command I ran: ``SITE_NAME="Meshtastic Map" DEFAULT_CHANNEL="#LongFast" DEFAULT_FREQUENCY="915MHz" MAX_NODE_DISTANCE_KM=35 MATRIX_ROOM="" API_TOKEN="<api-token>" PRIVATE=1 APP_ENV=production bash app.sh`` ![](https://cdn.imgpile.com/f/9etIyHW_xl.png)

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/potato-mesh#38