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

Best practices for @mentions #62

Closed
evanp opened this issue Jan 13, 2015 · 4 comments
Closed

Best practices for @mentions #62

evanp opened this issue Jan 13, 2015 · 4 comments

Comments

@evanp
Copy link
Collaborator

evanp commented Jan 13, 2015

Many social systems use a in-band mechanism to let users define special addressing for messages. For example, "@username" often will route a note or image to a special "mentions" or "inbox" stream for a user.

It would be worthwhile to note that Activity Streams 2.0 processors should not have to parse the "content" or other properties of activity objects to determine this addressing information. Instead, the stream creator SHOULD put explicit addressing information into the activity using "to" or "cc", and MAY replace "@username" in the content with a link to an appropriate page for that user.

@akuckartz
Copy link

I do not like a special syntax like "@username" to be specified in the AS2 spec. It is just an example rendering by a client, correct?

@jasnell
Copy link
Collaborator

jasnell commented Jan 20, 2015

The WG decision was to indicate that these kinds of microsyntaxes should NOT be specified by the AS2 spec and that structured properties should be used (same as the #63 discussion of hashtags)

@akuckartz
Copy link

I see. I do think that an interoperable specification would make sense, but I currently do not have a proposal. I will raise my voice here if/when that is the case.

@jasnell
Copy link
Collaborator

jasnell commented Feb 10, 2015

Addressed in the current published working draft

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

No branches or pull requests

4 participants