Remove user agent blocking for Firefox/100 & Chrome/100.0

Currently there’s some User-agent based anti-spam blocks (Primarily on tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. I think) that is blocking requests from Firefox version 100. I can’t see anything blocking Chrome 100, but that will also need to be checked at the same time.

% curl -Is https://core.trac.wordpress.org/ --user-agent 'Mozilla/5.0 (X11; Linux x86_64; rv:100.0) Gecko/20100101 Firefox/100.0' | grep ^HTTP
HTTP/2 403

I assume we have something looking for Firefox/1 as a UA blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. for ancient-versions of Firefox.

Originally reported by @mte90 – https://wordpress.slack.com/archives/C0C89GD35/p1635254249000700

#prio1

Redirects for JSON Schemas

We are working on providing schemas to developers for block.jsonJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. and theme.json files. Adding the schema to the top of a JSON file can integrate with code editors to provide tooltips, autocomplete, and validation; making development easier.

Here’s a GIF showing how it works:

block-json-schema2

Right now we are using the SchemaStore as common place to gather schemas, but we want to move to our repository that will allow better versioning and control. We created a directory on GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ to contain the schemas and they can be accessed at:
https://github.com/WordPress/gutenberg/tree/trunk/schemas/json

This allows for adding schemas using the awkward URLs:

https://raw.githubusercontent.com/WordPress/gutenberg/trunk/schemas/json/block.json
https://raw.githubusercontent.com/WordPress/gutenberg/trunk/schemas/json/theme.json

But we can make them less awkward by taking a page out of Microsoft’s book and use redirects. For Windows Terminal schema, Microsoft uses: https://aka.ms/terminal-profiles-schema that redirects to a GitHub url.

So, the ask is to get a similar redirect setup, using either wp.org or w.org domains.

Something like:

https://wp.org/schemas/block.json  => https://raw.githubusercontent.com/WordPress/gutenberg/trunk/schemas/json/block.json

https://wp.org/schemas/theme.json  => https://raw.githubusercontent.com/WordPress/gutenberg/trunk/schemas/json/theme.json

And then in the future when we want to version the schema we could add the version to the redirect and point to the tag/branch in the source code related to that release

https://wp.org/schemas/wp5.9/block.json
https://wp.org/schemas/wp5.9/theme.json

Questions? Thoughts?