does the User object look easy to work with? (id is meow because there’s no database yet)
comments
Personally I would rather have a list of users instead of a number of followers/following @lily
that would be at the /followers endpoint (what if the person has 1 million followers? then that could be gigabytes of content to download)
same for the notes, you could have A LOT of those
and it would be pretty bad to make it recursive too
Not to put you down but I doubt you are getting millions of users any time soon.. (though something you could do is only send up to 20 results, and after that it would request each page.)
i was really talking about scaling, i’m not sure if that wasn't clear from my message or something
yeah, the /followers endpoint would be paginated, it's just useless to add it to the normal /users/by_* endpoints since then you'd be downloading a lot of redundant data
I was saying it just send an array of 2 on the user endpoint, like ["1", "33483djdn", "gorkejusername"]
i feel like the /followers idea is better since it can show the things like profile theme and stuff in the list of followers without having to do an additional download
true. i think that’s a fair solution and i really like the user’s object overall! :)