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

Separate branch for unsupported features? #1

Open
alextrob opened this issue Mar 4, 2013 · 2 comments
Open

Separate branch for unsupported features? #1

alextrob opened this issue Mar 4, 2013 · 2 comments

Comments

@alextrob
Copy link

alextrob commented Mar 4, 2013

I like that you're documenting even the unsupported features, but I wonder if it would be better to put them in a separate branch or something so that we have to go (slightly) out of our way to learn about them.

It would at least make it clear what is and isn't supported from the top level.

@jorilallo
Copy link
Member

I think I'll keep things in the master as you'll either way see the data in the responses. One thing that has occured to me is, if we should allow people to hide embedded media from the requests. Now the payload size can be pretty massive so it would make sense that you could just requests your urls without the payload. What do you think?

@alextrob
Copy link
Author

Yeah that's a good point about the size. I like having all the media data there for a full client, but I imagine it would be wasteful for a lot of other tools and services.

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

No branches or pull requests

2 participants