{"id":5,"date":"2019-11-26T12:22:54","date_gmt":"2019-11-26T12:22:54","guid":{"rendered":"https:\/\/demosites.io\/blogger-gb\/?page_id=5"},"modified":"2025-03-02T05:18:56","modified_gmt":"2025-03-02T05:18:56","slug":"582c1-blogger-gb-home","status":"publish","type":"page","link":"https:\/\/wordpress.richardorilla.website\/","title":{"rendered":"Home"},"content":{"rendered":"\n
<\/div>
\n
\n

<\/p>\n\n\n\n

About me<\/h2>\n\n\n\n

Dedicated problem solver and a researcher at heart. Kind of a person who likes to do challenging things for the sake of achievement.<\/p>\n\n\n\n

Likes to explore whats new in tech, including dwelling on new programming languages. Favorite programming language is C and has already created real-time applications that is used for heavy-duty purposes using this language.<\/p>\n\n\n\n

An avid fan of Linux yet explores other operating systems, including, BSD Family (Free, Open and Net), Haiku OS and even ICAROS (Amiga).<\/p>\n\n\n\n

Go to blog<\/a><\/p>\n<\/div>\n\n\n\n

\n
\"\"<\/figure>\n<\/div>\n<\/div><\/div>\n\n\n\n
<\/div>
\n
\n

Follow along the journey<\/h2>\n\n\n\n

This month brought an interesting development in the world of open-source content management: WordPress.com has officially banned WP Engine from accessing its open-source resources. As someone who values the principles of open-source, I find this move quite unsettling. In my view, open-source software should remain accessible to everyone, without restriction based on company, group, or, more broadly, ethnicity. By placing limitations on WP Engine, WordPress is treading into tricky territory that contradicts the open and collaborative spirit that made it so successful in the first place.<\/p>\n\n\n\n

For context, WP Engine has been a significant player in the WordPress ecosystem, offering managed WordPress hosting to a wide range of customers. However, recent accusations suggest that WP Engine may have violated the terms of the WordPress Plugin Directory by directly accessing WordPress\u2019s open-source resources in a way that WordPress.com deems inappropriate. The dispute revolves around the use of WordPress.com\u2019s API and automated testing resources.<\/p>\n\n\n\n

That said, this controversy inspired me to explore WordPress more closely myself. Though I\u2019m not a fan of CMS platforms in general\u2014WordPress included\u2014I decided to create a WordPress site through my hosting provider to see firsthand what the fuss is all about. You might wonder why, given that my personal website is a pure HTML build with a few handcrafted tools. Well, curiosity gets the better of us all sometimes, especially when dramatic changes like this take place in the tech world.<\/p>\n\n\n\n

If anything, this situation is a reminder that open-source projects like WordPress owe much of their success to a principle of accessibility and community-driven innovation. It will be interesting to see how this WP Engine vs. WordPress.com drama unfolds and whether it prompts any broader discussions about the responsibilities of open-source gatekeepers.<\/p>\n\n\n\n

<\/div>\n\n\n\n