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

What if app has no field for message or tag? #7

Open
joakim opened this issue Apr 26, 2018 · 0 comments
Open

What if app has no field for message or tag? #7

joakim opened this issue Apr 26, 2018 · 0 comments
Labels
bug Something isn't working input wanted Extra attention is needed

Comments

@joakim
Copy link
Owner

joakim commented Apr 26, 2018

What the title says… not all apps have fields for message and/or tag.

How should an app handle these URIs if it has no fields for entering tags or messages:
iota:MZLFXAZOHO…?tag=important
iota:MZLFXAZOHO…?message=Very%20important%20information

  1. Ignore the tag/message?
  2. Silently include the tag/message in the transaction, without the user knowing it?

Tough one.

How could the spec prevent this?

Requiring that apps must be able to display tags and messages if provided by the URI is a tall order. It adds extra code and complicates UI, but is the only way to guarantee that the information is not lost or hidden from the user.

A more dev friendly option would be to offer a way out by saying it SHOULD show the tag and message, but if it can't, it MUST inform the user that the message/tag was dropped. That way, at least the user doesn't send information in a transaction without being aware of it.

@joakim joakim added bug Something isn't working input wanted Extra attention is needed labels Apr 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working input wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant