You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to suggest implementing a feature that allows users to export and import conversations or, alternatively, maintain an accessible history of messages exchanged in communication channels.
Context:
Currently, messages in channels can be lost due to storage limitations, accidental deletions, or system migrations. Having the ability to:
Export conversations (in formats such as .txt, .csv, or .json).
Import conversations for recovery or analysis.
Maintain an organized history (by date, channel, or user).
would be extremely useful for:
Backup and compliance (ensuring records of important communications).
Onboarding new members (who may need to review past discussions).
Data analysis (extracting insights from previous conversations).
Implementation Suggestion:
Add an "Export Conversation" button in the channel options menu.
Create a "History" section where conversations can be filtered and retrieved.
Allow import via an intuitive file upload interface.
Thank you for your attention. I’m happy to provide further details or assist with testing if needed.
Best regards,
Charles Silva
Relevant log output
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Contact Details
suporte@charlessilva.com.br
Tell us your idea.
Dear Team Meshtastic,
I would like to suggest implementing a feature that allows users to export and import conversations or, alternatively, maintain an accessible history of messages exchanged in communication channels.
Context:
Currently, messages in channels can be lost due to storage limitations, accidental deletions, or system migrations. Having the ability to:
.txt
,.csv
, or.json
).would be extremely useful for:
Implementation Suggestion:
Thank you for your attention. I’m happy to provide further details or assist with testing if needed.
Best regards,
Charles Silva
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: