does the User object look easy to work with? (id is meow because there’s no database yet)
comments
good but a few things:
less stuff on root, like group stats under
stats, orprofilewith aboutno caps
About is really confusing me, how is the data structured, because I thought it was an array but then again no
what are rainbow and verified
idk about this one as much, but doesn’t handle normally imply unique
otherwise i like the modulized about
what’s the point of that?
that's just what serde does, i don't know if i can change it without literally modifying the crate
it is an array, firefox just displays it as an object with number keys for some reason
why you have lilypad rainbow (the subscription), or why/how you’re verified
maybe? idk
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! :)