"Let's make WordPress the fastest CMS in the world! By rewriting #WordPress in C/Rust"

🤔

https://www.kickstarter.com/projects/programmerhat/fully-wordpress-compatible-rewrite-in-c-rust-for-20x-speedup

#kickstarter #C #Rust #CrazyPants #webdev

#trabajo #wordpress
📌Amigues busca trabajo Freelance, dispongo de 4 o 5 horas diarias, trabajo desde mí casa, tengo buena conexión 100mb, uso Gnulinux y además manejo WordPress muy bien, sin ser programador.
O si necesitas crear tu Web, blog, tienda, puedo hacerlo por vos, cuento con hosting.
Se agradece la difusión 📣

Client: "I’d like to try some alternative themes for my WordPress site you’re hosting, but I’m afraid of breaking the production site."

Me: "Say no more."

I start:
- create a record for the test site

- bastille clone -l prod testing ip

- bastille console nginx → edit nginx proxy, add the new domain → certbot --nginx -d newdomain.tld

- bastille console testing → mysql → UPDATE wp_options SET option_value = 'https://newdomain.tld' WHERE option_name = 'siteurl';
UPDATE wp_options SET option_value = 'https://newdomain.tld' WHERE option_name = 'home';

- "Done. You can now connect to..."

FreeBSD, jails, ZFS. No limits.

#RunBSD #FreeBSD #jails #BastilleBSD #WordPress

Taller de #Wordpress si no pudiste asistir este es el enlace para verlo. 

https://fediverse.tv/w/8HeQ4s6ngD68aDsog9Xz8X 

By @rikylinux_ar

How does a typical DDoS on a WordPress installation happen?

- A search-based DDoS attack by bypassing the cache
- Attacker sends a large volume of unique search queries so responses never hit the cache example ?s=something-xyz
- Each request becomes a cache miss, forwarded from network edge
- WordPress runs PHP + WP_Query for every request often triggering expensive database work.
- Repeated heavy queries exhaust CPU, memory and DB capacity so the website slows and eventually crashes.
- This is an Application-layer (Layer 7) HTTP flood that mimics normal user traffic.
- Key signals to look out for: huge spikes of /?s= requests in the logs, very high query entropy, cache-hit rate collapses.

Cache-busting search queries force every request through the database, turning cheap HTTP calls into expensive backend load.

Great Sysops lightning talk by Tiia Ohtokallio!

#WPSuomi #wpfi #WordPress #Sysops

Alt...

A slide and press the presentation in WP Suomi seminar. Slide text: How does a typical DDoS on a WordPress installation happen? - A search-based DDoS attack by bypassing the cache - Attacker sends a large volume of unique search queries so responses never hit the cache example ?s=something-xyz - Each request becomes a cache miss, forwarded from network edge - WordPress runs PHP + WP_Query for every request often triggering expensive database work. - Repeated heavy queries exhaust CPU, memory and DB capacity so the website slows and eventually crashes. - This is an Application-layer (Layer 7) HTTP flood that mimics normal user traffic. - Key signals to look out for: huge spikes of /?s= requests in the logs, very high query entropy, cache-hit rate collapses. Cache-busting search queries force every request through the database, turning cheap HTTP calls into expensive backend load.

Grrr. Getting hit by a fairly aggressive scraper on my blog.
Same user-agent, but different IP addresses - all from China.
It is using JS - but I really don't want to put up a CAPTCHA or similar. Deters too many legitimate visitors.

Anyone have a simple solution for WordPress / PHP?

#WordPress #php #bots

Alt...

Log files of a single user-agent but multiple Chinese IP addresses.

Hackers exploit auth bypass in #ServiceFinder #WordPress theme

https://www.bleepingcomputer.com/news/security/hackers-exploit-auth-bypass-in-service-finder-wordpress-theme/

#cybersecurity

Ya te sumaste? #gnu #linux #wordpress 🗓Agenda el taller! Se agradece la difusión📣 https://softlibre.com.ar/blog/2025/10/05/taller-sobre-wordpress/

Evan Prodromou on OpenChannels.FM

A quick note that Evan is interviewed by WordPress social networking lead Matthias Pfefferle on the OpenChannels.FM podcast about the history of the Fediverse and where we’re going next. How Decentralized Social Platforms Grew from Identica to Modern-Day Mastodon covers a 15+-year period as the Fediverse was born and developed. The shownotes alone are extremely detailed and a great resource.

does anybody use #wordpress as their main #ActivityPub account? is there a good app? basically are we there yet?

Hey, #WordPress friends.

What's the purpose of <!-- .children --> and <!-- #comment-## --> being injected after every ul/ol comment?

Are they necessary? Can they be removed?

As seen in:
https://github.com/WordPress/WordPress/blob/69ced2eb1fc85ec5e106384b48c8015c77468402/wp-includes/class-walker-comment.php#L91
and
https://github.com/WordPress/WordPress/blob/69ced2eb1fc85ec5e106384b48c8015c77468402/wp-includes/class-walker-comment.php#L238

Nada que ver en las audaces aventuras de desarrollar un proyecto de código abierto popular

https://picandocodigo.net/2025/nada-que-ver-en-las-audaces-aventuras-de-desarrollar-un-proyecto-de-codigo-abierto-popular/

#ListCategoryPosts #Wordpress

Y Patchstack ya marcó la "vulnerabilidad" como corregida 🥳🙌

Con actualizar a la última versión 0.92.0, no debería haber más advertencias de "problemas de seguridad"...

https://patchstack.com/database/wordpress/plugin/list-category-posts/vulnerability/wordpress-list-category-posts-0-90-3-local-file-inclusion-vulnerability

#WordPress #ListCategoryPosts

Publicado List Category Posts v0.92.0 con mejoras en "seguridad"

Desde mayo venimos luchando con Wordfence y Patchstak, que reportaron un problema de seguridad en el plugin de WordPress List Category Posts.

https://picandocodigo.net/2025/publicado-list-category-posts-v0-92-0-con-mejoras-en-seguridad/

#ListCategoryPosts #Wordpress

Un amiguete anda montando en Noja (Cantabria) un evento sobre #wordpress

Es el primero que organiza, se agradece difusión :)

https://events.wordpress.org/noja/2025/codigocosta/

Will browsers and screen readers respect the #html lang attribute #WordPress allows us to set on paragraphs?

TL;DR; most browsers "read aloud" feature ignores element specific lang attribute, but dedicated screen readers like #NVDA and Apple #VoiceOver do fairly well!

I've installed the 20 most spoken languages in #europe on my PC and virtual Mac.

Blog post is in the making, so feel free to ask questions and send me on even more side quests 😁

Teaser at https://oldrup.dk/en/teaser-testing-the-20-most-spoken-languages-in-europe-with-nvda-and-voiceover/

Me encuentro con que el wordpress moderno trae un editor de bloques que me complicó un poco. Por suerte está disponible el editor clásico como un plugin. Para lo que necesito basta con la simplicidad del clásico.

#Wordpress

Hoy me conecté, feriado, tranquilo, me dije esta mañana "voy a adelantar algunas cositas del laburo a media máquina", y veo que se me cayó uno de los servidores.

Justo estaba haciendo algunos cambios en un #wordpress, y otro usuario estaba subiendo archivos en otro servicio, se llenó el disco, se apagó el servidor de base de datos, y se vino abajo todo.

Por suerte ya está todo online, pero fue como mucha adrenalina para un viernes feriado 😅

Nota mental: controlar crontabs y meter + monitoreo

Andrew Norcross built a WordPress plugin to insert the robots.txt directives from ai.robots.txt https://github.com/norcross/block-ai-scrapers #AI #WordPress

Me está haciendo mucha falta un shortcut en #wordpress para aplicar el formato de "inline code" en mis artículos... eso de seleccionar con el mouse y dar clic dos clics para aplicarlo es muy lento, tanto que me hace acordar a productos de #microsoft 😆

#PiHole discloses #DataBreach triggered by #WordPress plugin flaw

https://www.bleepingcomputer.com/news/security/pi-hole-discloses-data-breach-via-givewp-wordpress-plugin-flaw/

#privacy #cybersecurity #DNS #GiveWP

Hackers actively exploit critical RCE in #WordPress #Alone theme

https://www.bleepingcomputer.com/news/security/hackers-actively-exploit-critical-rce-in-wordpress-alone-theme/

#cybersecurity

Post #SMTP plugin flaw exposes 200K #WordPress sites to hijacking attacks

https://www.bleepingcomputer.com/news/security/post-smtp-plugin-flaw-exposes-200k-wordpress-sites-to-hijacking-attacks/

#cybersecurity

Acabo de darle un lavado de cara a mi página web por segunda vez, ya que incluí los servicios profesionales que presto, por si a alguien le interesa que le haga un sitio web ;).

https://www.autumn64.xyz

#wordpress #fediverse #fediverso #mastodon #softwarelibre #freesoftware #foss #wp

Alt...

Captura de pantalla de la página principal de mi sitio web.

If you have a WordPress blog, you can optionally allow people to follow your blog from Mastodon etc. They will be able to see your posts in their timelines, and if they reply to your post on Mastodon etc it will appear as a comment on your blog.

There are complete instructions for how to switch on this feature here:

➡️ https://fedi.tips/wordpress-turning-your-blog-into-a-fediverse-server

This works for all kinds of WordPress-powered blogs including wordpress.com blogs and independently hosted blogs.

#WordPress #Fediverse #ActivityPub

Interesting, I never noticed #snac completely renders federated WordPress posts.
Another small marvel from truly excellent software.

#Fediverse #Wordpress #snac2

WordPress on FreeBSD with BastilleBSD: A Secure Alternative to Linux/Docker

Tired of the Linux/Docker “monoculture” for WordPress? This article guides you step-by-step through the secure installation of WordPress on FreeBSD using @BastilleBSD
Discover how jail separation, performance, and the versatility of ZFS offer a more robust and easily manageable environment, far from common vulnerabilities often linked to poorly maintained plugins. Get ready to make your site more secure and reliable.

https://journal.bsd.cafe/2025/07/21/wordpress-on-freebsd-with-bastillebsd-a-secure-alternative-to-linux-docker/

#BSDJournal #FreeBSD #RunBSD #Wordpress #OwnYourData #Hosting #IT #SysAdmin

WordPress is one of the most widely used platforms for publishing content online. It’s often criticized as an insecure platform, but in reality WordPress itself is secure – it’s the many plugins, unmaintained or poorly developed, that generate significant vulnerabilities.

Many people host WordPress on Linux, often using Docker. While this is a valid approach, there are excellent alternatives – sometimes even better ones – for getting your WordPress site online in a secure, reliable, and updatable manner. The goal is to make the web a safer place and avoid the computing monoculture that increasingly pushes toward uniformity of solutions and setups – an attitude that I believe is harmful even when the solutions are open source.

For this type of setup, therefore, I’ll describe how to accomplish everything using FreeBSD. The jail separation, performance, and ZFS versatility – all reasons that support this choice. This guide will serve as a foundation – everything will work at the end, but it won’t cover all possible combinations or configurations.

We’ll be using BastilleBSD, which supports both ZFS and UFS. While FreeBSD’s base system has everything needed to create and run jails, BastilleBSD is incredibly useful for managing them. Since it’s written in shell script and has no database dependencies, management and backups are straightforward. Furthermore, moving jails becomes extremely simple – either by using the bastille command directly or by copying the files (or datasets, if you’re using ZFS).

BastilleBSD also supports templates, but for this tutorial, we’ll perform the operations manually to understand each step.

First, install Bastille:

pkg install bastille

Next, run the setup process:

bastille setup

Now, bootstrap the desired FreeBSD release:

bastille bootstrap 14.3-RELEASE update

With that, BastilleBSD is ready to go.

Creating the Jails

Now, let’s create the jail that will contain Apache, PHP, and WordPress:

bastille create apache 14.3-RELEASE 10.0.0.254 bastille0

Note: This command will only create and assign an IPv4 loopback address. For IPv6, the simplest solution is to assign an address for the jail directly to the host’s interface. To do this, note an available IPv6 address and assign it to the jail. For example, if the host’s network interface is vtnet0:

bastille edit apache

Add the following lines to the configuration file:

ip6 = new;ip6.addr = "vtnet0|2001:0DB8:1::443/64";

Restart the jail:

bastille restart apache

Next, let’s ensure that connections to the host’s ports 80 and 443 are redirected to the apache jail:

bastille rdr apache tcp 80 80bastille rdr apache tcp 443 443

Now, if using ZFS, let’s create a dedicated dataset for WordPress and mount it in the jail. The reason is simple: decoupling the Apache jail from the WordPress directory will allow for updates, rollbacks, etc. of the Apache jail without touching the WordPress files. I assure you that, in the long run, this approach will save many headaches.

zfs create zroot/wordpressbastille mount apache /zroot/wordpress/ /usr/local/www/wordpress nullfs rw 0 0

Now, let’s create the jail that will contain MariaDB:

bastille create mariadb 14.3-RELEASE 10.0.0.253 bastille0

Configuring the MariaDB Jail

Access the MariaDB jail’s console:

bastille console mariadb

Once inside, install the MariaDB server:

pkg install mariadb118-server

Enable and start the mysql-server service:

service mysql-server enableservice mysql-server start

Now, access the MySQL command line to set up the WordPress database:

mysql

Execute the following SQL commands (you should use more secure user, password, etc.):

CREATE USER wp@10.0.0.254 IDENTIFIED BY 'password';CREATE DATABASE wordpress;GRANT ALL PRIVILEGES ON wordpress.* TO wp@10.0.0.254;FLUSH PRIVILEGES;

Exit the MariaDB jail console to return to the host.

Configuring the Apache & PHP Jail

Now, let’s configure the apache jail. First, access its console:

bastille console apache

Inside the jail, install PHP and all the necessary extensions. We won’t install WordPress from the FreeBSD package – while it’s updated and maintained, I prefer to manage dependencies manually. It will be easier to manage updates in the long term, such as changing PHP versions, etc. At the time of writing this article, for example, the WordPress package depends on PHP 8.3 while I prefer to use 8.4.

pkg install php84 php84-bcmath php84-bz2 php84-calendar php84-ctype php84-curl php84-dom php84-exif php84-fileinfo php84-filter php84-ftp php84-gd php84-gettext php84-iconv php84-intl php84-mbstring php84-mysqli php84-opcache php84-pcntl php84-pdo php84-pdo_mysql php84-pecl-imagick php84-phar php84-posix php84-readline php84-session php84-shmop php84-simplexml php84-soap php84-sockets php84-sodium php84-tokenizer php84-xml php84-xmlreader php84-xmlwriter php84-xsl php84-zip php84-zlib

Next, install Apache:

pkg install apache24

Modify /usr/local/etc/apache24/httpd.conf to enable the required modules. Uncomment or add the following lines:

LoadModule mpm_event_module libexec/apache24/mod_mpm_event.so#LoadModule mpm_prefork_module libexec/apache24/mod_mpm_prefork.so#LoadModule mpm_worker_module libexec/apache24/mod_mpm_worker.so...LoadModule proxy_module libexec/apache24/mod_proxy.so...LoadModule proxy_fcgi_module libexec/apache24/mod_proxy_fcgi.so...LoadModule ssl_module libexec/apache24/mod_ssl.so...LoadModule rewrite_module libexec/apache24/mod_rewrite.so

Enable and start the Apache service:

service apache24 enableservice apache24 start

To optimize performance, enable PHP-FPM to listen on a socket. Modify the /usr/local/etc/php-fpm.d/www.conf file.

Comment out this line:

;listen = 127.0.0.1:9000

And add these lines:

listen = /tmp/php-fpm.socklisten.owner = wwwlisten.group = www

Now, we need to configure Apache to use PHP-FPM correctly. Create the file /usr/local/etc/apache24/Includes/php-fpm.conf and add the following:

<FilesMatch \.php$>  SetHandler proxy:unix:/tmp/php-fpm.sock</FilesMatch>

Restart Apache for the changes to take effect:

service apache24 graceful

It’s good practice to copy the production PHP template to the final, modifiable php.ini file, which can be customized with the required options and limits:

cp /usr/local/etc/php.ini-production /usr/local/etc/php.ini

Make any desired changes now (or later), then enable and start PHP-FPM:

service php_fpm enableservice php_fpm start

Installing WordPress

Navigate to the web server’s root directory:

cd /usr/local/www

Download and extract the latest version of WordPress:

fetch https://wordpress.org/latest.zipunzip latest.zip

Set the correct permissions:

chown -R www:www wordpress/

Now, create an Apache virtual host configuration file at /usr/local/etc/apache24/Includes/wordpress.conf – be sure to modify the “example.com” with your own real domain name:

<VirtualHost *:80>    ServerAdmin webmaster@example.com    ServerName example.com    ServerAlias www.example.com    DocumentRoot /usr/local/www/wordpress    <Directory /usr/local/www/wordpress>        DirectoryIndex index.php index.html index.htm        Options FollowSymLinks MultiViews        AllowOverride All        Require all granted    </Directory>    ErrorLog "/var/log/httpd-example.com-error.log"    CustomLog "/var/log/httpd-example.com-access.log" combined</VirtualHost>

Finally, restart Apache one more time:

service apache24 graceful

The server will now respond on port 80 with the specified hostname, but this is absolutely not optimal or recommended. It’s therefore appropriate to generate a certificate to enable HTTPS.

For a simple solution, I recommend installing certbot with the Apache plugin to manage everything through Apache:

pkg install py311-certbot py311-certbot-apache

In order to automatically renew the certificates, add this line to /etc/periodic.conf:

weekly_certbot_enable="YES"

And, once installed, generate the certificate:

certbot --apache -d example.com -d www.example.com

You can now proceed to connect to the specified URL and begin with the WordPress guided installation, remembering the authentication and database details (the host, in this example, is 10.0.0.253 – not localhost, since we installed it in a dedicated jail).

Congratulations, your site is installed and operational. Ready to receive content for publishing. It’s exposed on IPv4 and IPv6, with HTTPS (and automatic certificate renewal, managed directly by FreeBSD) and separated from the database.

Generally, I prefer to add an additional jail with a reverse proxy. This way it will be possible to install different software in different jails, ensuring that the reverse proxy “routes” requests correctly. I’ll explain this procedure in a future article.

While this is my inaugural FreeBSD post for the BSD Cafe Journal, I’ve actually written extensively on the topic for my own blog, https://it-notes.dragas.net

Alt...

MacBook Pro, white ceramic mug,and black smartphone on table

🏕️ my adventures in #selfhosting - day 212 (consolidating edition) 🎛

If you followed my (mis)adventures yesterday and all the issues I had with caching and #CDN for my #Wordpress site, well, I found a solution.

💫​ Something that had been in front of me the whole time
💫​ ZERO additional costs

Ta-da: 👻​

🔗​: https://news.elenarossini.com/my-so-called-sudo-life/my-adventures-in-self-hosting-day-212-consolidating-edition/

#Ghost #VarnishCache

One of the reasons I’m always so happy to attend conferences and technical events (the real ones – not the flashy, sponsor-driven ones designed just to sell products or services) is because I get to meet amazing people and always come away having learned something new.

I’ve been using WordPress since 2006 and have been managing hundreds of installations from a sysadmin perspective. Over time, I’ve noticed a clear pattern: most hacks and compromises happen through plugins or outdated installations. And often, these installations (and plugins) become outdated because they’ve been patched together so messily that updating them becomes nearly impossible – especially when the PHP version changes.

In March 2025, I attended a fantastic conference: OSDay 2025. I gave a talk on why I believe it makes perfect sense to consider the BSDs in 2025, but many of the other talks were truly eye-opening.

To mark the launch of the BSD Cafe Journal, I’d like to share the link to a particularly interesting talk by Maciek Palmowski: “How we closed almost 1k plugins in a month — the biggest WordPress bug bounty hunt.”

What struck me right away was how much his analysis of WordPress security aligned with what I’ve seen over the years: WordPress, out of the box, is reasonably secure. It’s the plugins – often old, unmaintained, or poorly written – that make it vulnerable.

I highly recommend watching his talk. It’s definitely worth your time.

https://www.youtube.com/watch?v=Y3HsjvRAofk

Alt...

black flat screen computer monitor

Consejo os pido. Hosting barato (y ético) para instalar Wordpress*; ideal si ya viene instalado o se instala dándole a un botón. Lo quiero para el instituto, todavía no sé si pagado por mí o por el instituto. El Wordpress es para la revista del centro, y como impartiré Educación digital pues igual lo uso para instalar alguna otra cosa que pueda usar con los alumnos, como una wiki, por ejemplo.

*Entiendo que WP tiene lista de correo para avisar de publicaciones

#hosting #consejo #wordpress

#AskFedi do you know anyone with a federated Wordpress site who uses it extensively? Not just for publishing straight to the Fediverse, but also in a social way (aka as a fedi profile)?

I've run into a few roadblocks with mine and I could really use some inspiration 😊​

#Wordpress #ActivityPub #selfhosting

For today's #ThankYouTuesday, I'd like to thank everyone who supports the Fediverse. So, that means *you*. Yes, you, the one reading this.
Thank you!

The Fediverse truly is for everyone: if you don't have the skills or means to set up your own instance, you can join one of the public instances that aligns with your aspirations. If you can and want to, you can create your own instance, and thanks to lightweight (and interoperable) software, you can do it with spare hardware or very affordable VPS.
So thank you to all of you, friends of the Fediverse!

#Fediverse #Mastodon #snac #GoToSocial #Wordpress #Mitra #Akkoma #Pleroma #Honk #Peertube #Pixelfed #TooManyToEnumerateHere

🏕️ my adventures in #selfhosting - day 203 (am I doing POSSE right? edition) 📖​

Experimenting with the #POSSE method by posting on my federated #Wordpress site first and then syndicating elsewhere.

🔗: https://elenarossini.com/2025/07/my-adventures-in-self-hosting-day-203/

Not sure if I'm doing things the right way but it feels empowering to have these posts on my site - it will be so much easier to organize them and find them in the future.

#MySoCalledSudoLife

Good morning Fedi friends!

Now that my Fedi promo video is out and I'm no longer spending 7 hours a day doing motion graphics, I have time to pick up again writing for the blog #TheFutureIsFederated.

🔗: https://news.elenarossini.com/tag/the-future-is-federated/

This morning I will create a roadmap for the rest of the summer. There is so much I have yet to explore and write about.

At the top of my list: trying out #BookWyrm and the #Friends plugin for #wordpress

Any other requests? 👀

Wishing everyone a great day! 🌞

Dev just messaged me, alarmed: a WordPress plugin's tech support logged into his site and broke everything! 😱
But Dev is sharp, and even at 22:10, he remembered his server runs FreeBSD and ZFS. With snapshots of his site and database every 15 minutes, we rolled back to the 20:00 snapshot, and his site was back up in a flash!

Thank you, FreeBSD! Thank you, ZFS!

#FreeBSD #ZFS #WebDev #WordPress #SysAdmin #DataRecovery #Snapshots #ThankYouTuesday

[NOTA]: #wordpress necesita un shortcut para aplicar "Inline code" de manera más simple.

Hi @stefano
Is there a way to migrate from #Wordpress to #BSSG ?

I'm investigating how some #WordPress sites that are very different in setup (theme, plugins) somehow had malicious code executed that creates an administrator named 'wertuslash'. This is done by infecting `wp-includes/widgets/class-wp-widget-recent-comments.php` with some code.

I usually can find something through access logs, but as of now I can't find which exploit was being used.

This happened to two sites I manage, but also found an old WP 5 site that's infected as well.

#security

Alt...

A code snippet

WordPress en 2025 (calendario de lanzamientos y qué debería incluir la hoja de ruta, según Joost de Valk)

Dedicamos el primer artículo de Blogpocket sobre WordPress en 2025.

WordPress ha anunciado el calendario de lanzamiento de WordPress en 2025 , que incluye tres actualizaciones importantes: WordPress 6.8, 6.9 y 7.0.

• WordPress 6.8: Beta 1 el 4 de marzo, lanzamiento estable el 15 de abril.
• WordPress 6.9: Beta 1 el 24 de junio, lanzamiento estable el 5 de agosto.
• WordPress 7.0: Beta 1 el 30 de septiembre, lanzamiento estable el 11 de noviembre.

WordPress y lo que debería incluir su hoja de ruta

Joost de Valk analiza en este artículo (WordPress, and what should be on its roadmap) la situación actual de WordPress, destacando su estancamiento en la cuota de mercado y los desafíos técnicos que enfrenta. Señala que, aunque WordPress ha mantenido una posición dominante, su crecimiento se ha detenido, especialmente frente a herramientas SaaS. Identifica problemas como la lentitud, estancamiento técnico, inseguridad y dificultad de uso, y propone una hoja de ruta para abordar estos desafíos y revitalizar la plataforma.

De ese artículo de Joost de Valk podríamos extraer los siguientes puntos clave:

• Estancamiento en la cuota de mercado: WordPress ha dejado de crecer y muestra signos de estancamiento en comparación con herramientas SaaS.
• Desafíos técnicos: Se critica a WordPress por ser lento y estar técnicamente estancado, con una deuda técnica significativa en su código PHP y una rápida evolución en JavaScript que dificulta su seguimiento.
• Problemas de seguridad: Aunque el núcleo de WordPress ha tenido pocas vulnerabilidades, los plugins representan una fuente significativa de inseguridad, lo que afecta la percepción general de la plataforma.
• Dificultad de uso: La interfaz de usuario de WordPress se considera complicada, con múltiples UIs de administración y una curva de aprendizaje pronunciada para el editor de bloques.
• Propuestas para el futuro: Se sugiere modernizar la base de código, mejorar la seguridad de los plugins, simplificar la experiencia del usuario y definir claramente el propósito y audiencia de WordPress.

De todo ello, se desprenden las siguientes acciones:

• Modernización del código: Actualizar y optimizar la base de código PHP y racionalizar el desarrollo de JavaScript para mejorar el rendimiento y la eficiencia.
• Mejorar la seguridad de los plugins: Implementar medidas más estrictas para la revisión y monitoreo de plugins, asegurando que los usuarios sean informados sobre posibles riesgos de seguridad.
• Simplificar la experiencia del usuario: Unificar las interfaces de administración y mejorar la usabilidad del editor de bloques para facilitar su adopción por parte de los usuarios.
• Definir el propósito de WordPress: Clarificar la dirección y audiencia objetivo de WordPress para orientar su desarrollo futuro y satisfacer mejor las necesidades de su comunidad.

En definitiva, según Joost de Valk, abordar estos desafíos es crucial para que WordPress mantenga su relevancia en el mercado de gestión de contenidos. La modernización técnica, mejoras en seguridad y una experiencia de usuario más intuitiva podrían revitalizar la plataforma y atraer a una audiencia más amplia, permitiendo a WordPress competir eficazmente con soluciones SaaS emergentes.

¿Quién es Joost de Valk?

Joost de Valk es un empresario y desarrollador de software de aplicaciones de Wijchen, Países Bajos, que es conocido por Yoast SEO (el plugin que utilizamos para optimizar el SEO de Blogpocket). De Valk comenzó como consultor y bloguero en 2004 antes de desarrollar Yoast, uno de los plugins más exitosos para Wordpress. [Fuente: Wikipedia]

En Blogpocket, creemos en un uso ético y responsable de la IA

Las imágenes utilizadas en este artículo han sido creadas con IA con la herramienta Microsoft BIng.

#WordPress

Alt...

Una imagen ilustrativa que refleje la problemática de la plataforma WordPress: "destacando su estancamiento en la cuota de mercado y los desafíos técnicos que enfrenta. Señala que, aunque WordPress ha mantenido una posición dominante, su crecimiento se ha detenido, especialmente frente a herramientas SaaS. Identifica problemas como la lentitud, estancamiento técnico, inseguridad y dificultad de uso, y propone una hoja de ruta para abordar estos desafíos"

There is this war going on between WP Engine and Wordpress co-founder and CEO Matt Mullenweg. He called WP Engine a "cancer" and accused it of profiting from WordPress without contributing to development of the CMS. Now, WordPress org denies service to WP Engine, potentially putting sites at risk https://www.theregister.com/2024/09/26/wordpressorg_denies_service_to_wp #opensource #wordpress

Tengo la grabación de la última actuación, es como giga y medio, y me gustaría subirla al área de socios para que tengan acceso a ella bajo las reglas de Nextcloud y. al mismo tiempo, publicarla en el blog de manera que se pueda ver con el visor de Wordpress. Todo eso sin que tenga que duplicar el espacio ocupado.

Pues no, el único complemento que he visto es uno de pago con mucha fanfarria en la página web que promete demasiadas cosas pero que siendo de pago como que no. Y no es por el dinero, es por la dependencia que le cargo a la asociación sin necesidad alguna.

He mirado también #webdav y otros medios para acceder desde Wordpress hacia Nextcloud pero nada, que tampoco hay nada. Algunos usuarios han tenido el mismo problema que yo en 2016 así que no sé si siguen vivos y si lo han resuelto porque nadie les contestó.

A ver cómo me las apaño. Algo rudimentario seguro.