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

Format /users according to spec #4

Closed
mdom opened this Issue Mar 3, 2016 · 5 comments

Comments

Projects
None yet
4 participants
@mdom

mdom commented Mar 3, 2016

The specification on twtxt and the documentation here states that the first fields in the result from /users should be in twtxt's mention syntax. Currently it's the users url. I actually prefer the current format as the nicks are already listed in the third field, but in that case documentation and spec should be changed.

@kseistrup

This comment has been minimized.

kseistrup commented Mar 3, 2016

I would definitely prefer that nick and URL be delivered is seperate fields, rather than merged into the mention format. If I need it, I can always combine the two as @<nick URL>.

@mdom

This comment has been minimized.

mdom commented Mar 15, 2016

And the other api endpoints also return nick and url in a single field. It would be really nice to seperate them into their own fields. The mention syntax makes sense in a tweet text but here it makes the fields imho just harder to parse.

@DracoBlue

This comment has been minimized.

Owner

DracoBlue commented Mar 15, 2016

I will see that I can change the spec for users. @buckket what do you think?

@buckket

This comment has been minimized.

buckket commented Mar 29, 2016

Yes, separating seems like the way to go! There is no need to make things more complicated. 👍

@mdom mdom changed the title from Format /usersr according to spec to Format /users according to spec Apr 4, 2016

@DracoBlue

This comment has been minimized.

Owner

DracoBlue commented Apr 4, 2016

Fixed with 598d050

@DracoBlue DracoBlue closed this Apr 4, 2016

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