[wp-meta] [Making WordPress.org] #4048: WordCamp.org: WordCamps with non-public statuses are exposed in REST API
Making WordPress.org
noreply at wordpress.org
Mon Jan 7 19:57:35 UTC 2019
#4048: WordCamp.org: WordCamps with non-public statuses are exposed in REST API
-------------------------------------+-----------------------
Reporter: sippis | Owner: sippis
Type: defect | Status: assigned
Priority: normal | Milestone:
Component: WordCamp Site & Plugins | Resolution:
Keywords: needs-patch |
-------------------------------------+-----------------------
Comment (by sippis):
Looks like WordCamps with private statuses are removed purposely from the
main list, see changeset [4804]. In that changeset, Corey did set the main
list to contain only public statuses and restricted fully private status
listings (eg https://central.wordcamp.org/wp-json/wp/v2/wordcamps?status
=wcpt-mtp-rejected).
Replying to [comment:1 iandunn]:
> Similar to #4047, I personally prefer to err on the side of transparency
unless there's a tangible privacy or security reason to make the data
private.
In my opinion, in this case, there might be a privacy reason. Unlike in
meetup endpoint, WordCamp endpoint has custom fields added to the
response. Those fields contain applicants name and w.org usernames, for
example. Yeah, public application status report page does contain that
information also but only for a limited period - public status reports
don't.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/4048#comment:2>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list