Skip to main content
replaced http://stackapps.com/ with https://stackapps.com/
Source Link

How to batch up multiple id requests to maximize economy and still avoid (400) Bad RequestHow to batch up multiple id requests to maximize economy and still avoid (400) Bad Request [closed]

closed as noise or pointless by Kevin Montrose♦ Aug 16 at 23:15
This question does not add anything useful; having it present on the site is actively
 harmful because it distracts from other more useful questions.

At the time, the API was killing requests with longer than an undefined path length.

see: URL Length Limit For For Requests Taking Vectorised Ids (/answers/{id}, /questions/{id}, etc)URL Length Limit For For Requests Taking Vectorised Ids (/answers/{id}, /questions/{id}, etc)

In the spirit helping people maximize economy of requests while working around this limitation, which has subsequently been relaxed, I took the time to clearly define the problem and provide detailed guidance and code.

When the limitation was relaxed, I updated the post, prominently stating that the problem had been fixed and provided a link to the announcement.

During a recent and, in my opinion, unwarranted, CW spree on my guidance posts, kevin closed the post listed above as 'noise or pointless'.

I think this is completely inaccurate and completely inappropriate and I take offense.

Thoughts?

How to batch up multiple id requests to maximize economy and still avoid (400) Bad Request [closed]

closed as noise or pointless by Kevin Montrose♦ Aug 16 at 23:15
This question does not add anything useful; having it present on the site is actively
 harmful because it distracts from other more useful questions.

At the time, the API was killing requests with longer than an undefined path length.

see: URL Length Limit For For Requests Taking Vectorised Ids (/answers/{id}, /questions/{id}, etc)

In the spirit helping people maximize economy of requests while working around this limitation, which has subsequently been relaxed, I took the time to clearly define the problem and provide detailed guidance and code.

When the limitation was relaxed, I updated the post, prominently stating that the problem had been fixed and provided a link to the announcement.

During a recent and, in my opinion, unwarranted, CW spree on my guidance posts, kevin closed the post listed above as 'noise or pointless'.

I think this is completely inaccurate and completely inappropriate and I take offense.

Thoughts?

How to batch up multiple id requests to maximize economy and still avoid (400) Bad Request [closed]

closed as noise or pointless by Kevin Montrose♦ Aug 16 at 23:15
This question does not add anything useful; having it present on the site is actively
 harmful because it distracts from other more useful questions.

At the time, the API was killing requests with longer than an undefined path length.

see: URL Length Limit For For Requests Taking Vectorised Ids (/answers/{id}, /questions/{id}, etc)

In the spirit helping people maximize economy of requests while working around this limitation, which has subsequently been relaxed, I took the time to clearly define the problem and provide detailed guidance and code.

When the limitation was relaxed, I updated the post, prominently stating that the problem had been fixed and provided a link to the announcement.

During a recent and, in my opinion, unwarranted, CW spree on my guidance posts, kevin closed the post listed above as 'noise or pointless'.

I think this is completely inaccurate and completely inappropriate and I take offense.

Thoughts?

Source Link
Sky Sanders
  • 12.1k
  • 3
  • 32
  • 60

Helping people is 'noise or pointless'?

How to batch up multiple id requests to maximize economy and still avoid (400) Bad Request [closed]

closed as noise or pointless by Kevin Montrose♦ Aug 16 at 23:15
This question does not add anything useful; having it present on the site is actively
 harmful because it distracts from other more useful questions.

At the time, the API was killing requests with longer than an undefined path length.

see: URL Length Limit For For Requests Taking Vectorised Ids (/answers/{id}, /questions/{id}, etc)

In the spirit helping people maximize economy of requests while working around this limitation, which has subsequently been relaxed, I took the time to clearly define the problem and provide detailed guidance and code.

When the limitation was relaxed, I updated the post, prominently stating that the problem had been fixed and provided a link to the announcement.

During a recent and, in my opinion, unwarranted, CW spree on my guidance posts, kevin closed the post listed above as 'noise or pointless'.

I think this is completely inaccurate and completely inappropriate and I take offense.

Thoughts?