I'm aware of an open collection of Apple Feedback Assistant reports on GitHub - https://github.com/feedback-assistant/reports/issues

> Apple Feedback Assistant reports are not public. To help other developers discover existing reports, copy-paste your submitted Feedback Assistant report into a new issue. Make sure you include everything.

> This is similar to Open Radar, but it's easier to fill out the report and GitHub has better search. Also, Open Radar doesn't yet support Feedback Assistant.

> Instead of voting on issues opened here (which Apple won't see anyway), file a new Feedback Assistant report and copy-paste the contents of the report you found here and link to the original report. Apple encourages duplicates.

> have existed for over a decade

   Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!

Those look like a public mirror of some Radars filed at Apple, i.e. Apple already has that information. If enough developers stop submitting feedback (topic of this HN thread) and start posting bugs into a public repo FIRST, with a CC-BY-4.0 license allowing Apple to mirror the public bugs, then a boycott would have the positive side effect of showing-by-example how the feedback process could be improved.

> nothing would happen

As a counterpoint, there is a public Bugzilla for Webkit bugs, where the keyword "InRadar" indicates whether the bug has been mirrored to Apple's internal bug reporting system. If enough developers boycott Apple Feedback, could they use a Bugzilla instance for iOS and macOS bug reporting? If enough Apple users start referencing Bugzilla URLs for iOS/macOS production issues and purchasing decisions, could that influence Apple?

https://bugs.webkit.org/buglist.cgi?bug_status=__open__&cont...