At build time, Openverse downloads all of its translations by making a get request to each locale, for example:
We’re encountering some 429 errors which prevent us from downloading all of our translations when we build the app. We are looking for advice on what the rate limits to these endpoints are so we can adjust our code.
We’re working on this in a PR here: https://github.com/WordPress/openverse-frontend/pull/2184
As reported in https://wordpress.org/support/topic/api-wordpress-org-is-on-abuseip-db-blacklis/ it looks like some hosts have been confusing outgoing connections to api.wordpress.org as being incoming brute-force requests, and reporting it as such.
It appears that some hosts/networks may be using this as part of a network DROP rules causing WordPress sites being unable to connect to the API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways.. I believe this might be the cause of some past issues where .251 was inaccessible but .252 was.
Can someone from systems request removal, specifically for https://www.abuseipdb.com/check/220.127.116.11
Can NodeJS 18.x be installed on the build server with the paired version of npm (currently 9.3.1)?
Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. currently uses NodeJS 14.x, which will reach EOL on April 30, 2023. Work is underway for both Core and Gutenberg 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 support 18.x (see Core Trac-56658 and this Gutenberg PR/Issue list). The changes needed to support 18.x are being made now with the aim of changing the actual version used in both locations prior the EOL date in a few months.
There are currently no plans to update older branches receiving minor or security releases at this time, so 14.x will need to remain on the server for the time being.
CC: @gziolo who I’ve been coordinating with on the Gutenberg side of things.
Can we please update the plugins.trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. checkouts?
On svn1.ord, various meta checkouts are updated via
svnup-meta-checkouts.sh, but this doesn’t occur on svn2.ord, as a result, plugins.trac.wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ has the old WordPress.org header The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. & Footer trac templates and now appears visually broken.
This should be as simple as running
svnup-meta-checkouts.sh on svn2.. I don’t imagine it would cause any breakage, as the meta checkouts are in use on all other trac instances without issue.
Ref https://github.com/WordPress/wporg-mu-plugins/issues/326 and many others
#trac #svn #prio3
Occasionally the WordPress trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. mailing lists (wp-meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress., wp-trac, wp-svn) get a spam email slip through.
This one came through yesterday:
After the recent email changes, can the rules for the trac-related mailing lists be tightened to only accept definite WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ emails?
#email #trac #prio3