mark k.

so now you have to be “productive” (whatever that means) to be able to comment on anything…

I said it you you in the 4.4 merge proposal post that the endpoints are not ready for anything, that they are just badly designed, so it took you another 2+ months to meet other people that think the same and somehow it is me not being productive.
You know some time, even people that are not core contributors know something about software development and API design.

From the start it was obvious that you lack a model of the client that will use the API, what will it be used for and how. This is basic software development mistake, coding before thinking that almost never end well. I was simply shocked when I discovered that the API did not return the thumbnail as part of the post object (hope it was fixed by now).

IMO parity with XML-RPC is low hanging goal as the xmlrpc code is organized and it should not be too difficult (easy for me to say ;) ) to map endpoints to it. Since RPC-XML have extensions maybe it will be possible to make endpoints in such a way as to support them as well, and then jetpack will be to communicate over REST-API instead of xml-rpc, enabling all the people that keep it open just for jetpack to turn the xml-rpc endpoint off.

BTW, I actually admired the way you held yourself in the chat, and I do understand the need to vent it off, but why did the target had to be me ;)

Name *

Email *

Website:

Topic Title (Maximum Length: 80):

Forum:
— No forum —AI and WordPress Articles Blocks Showcase Discussions Events Introductions Jobs and Working in WordPress Podcast Episodes Site and Block Editor