Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cross platform text messaging features #21

Open
thebentern opened this issue Aug 28, 2024 · 2 comments
Open

Cross platform text messaging features #21

thebentern opened this issue Aug 28, 2024 · 2 comments
Assignees

Comments

@thebentern
Copy link
Contributor

thebentern commented Aug 28, 2024

  • Reply to message (Using ReplyID on Message)
  • "Tapback" emoji responses (Easy access to the subset that works on device screens, can allow any emoji)
  • Github flavored markdown rendering for message text body
  • Ability to @user with deep-link to node detail and notification options
    • Users can @ another node by typing the @ symbol Long name, short name, or user.ID
    • The actual text payload representation should package this as the User.Id: "@!ffccee11" for the wire
  • PKI secured indicators for direct message threads to a node
@thebentern thebentern changed the title Cross platform messaging features Cross platform text messaging features Aug 28, 2024
@tekstrand
Copy link
Contributor

@thebentern is this supposed to be in design?

@SpudGunMan
Copy link

SpudGunMan commented Oct 2, 2024

There was discussions over on discord and documenting them under this issue as there is a lot of crossover.

The discussion came about for a use case in having more interaction with the client. Specifically by enhancing the client applications for meshtastic with enhanced markup logic giving the user a clickable link which would perform a set of actions in the meshtastic client.

The concept of a 🔕 is used to identify a non type-able character much like 🔔 is used today.

The user experience would be something like a bot.py sending the text to a client would you like to 🔕[draw](doDraw) or 🔕[play](doPlay)

When a user clicked draw or play the meshtastic client would respond to the sender with doDraw or doPlay respectively just like this GitHub markup example.

bot.py would consume the Text and 🃏

🦾
Another experience could be, an arduino library device which is attached to a node, I could 🕹️🎮send 🔕⬆️send(runMotor(2)) or a newly available "ButtonPad" ⬆️ from my android/iOS client to the mesh and the arduinoLibrayNode
Or serial module, would rx/consume/print runMotor(2) which can be processed by code for whatever.

Some stuff the 🔕 should do

  • present user with a hyperlink to click
    🔕ClickMe
  • useable in mobile client for manipulating robots and bots 🕹️ provide a basic ⬆️⬇️⬅️➡️🔠 in the client UI

This would have a client action (ideas)

  • respond to sender with text from the link
    🔕DrawCard examples above
  • new buttons in client to 🕹️ send basic guiPadUp message to the currently active chat
  • ask to set a new channel with PKI
    🔕newCh(PKI,name)
  • ask to add admin PKI
    🔕newAdmin(PKI)
  • provide any other ideas in the original GitHub issue
  • enable hidden text box user need to ID on phone to access or view contents (non mobile would get the hash of text:encrypt:DMPKIkey)

Also @Nestpebble 👀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

7 participants