“Jumping Over the Garden Wall - WPE WebKit on Android”, by Adrián Pérez (Monday 2nd at 16:00 CEST) with a status update about the effort to bring WebKit into Android via WPE: https://webengineshackfest.org/\#wpe-android
“Jumping Over the Garden Wall - WPE WebKit on Android”, by Adrián Pérez (Monday 2nd at 16:00 CEST) with a status update about the effort to bring WebKit into Android via WPE: https://webengineshackfest.org/\#wpe-android
What's new in WPE WebKit 2.48? Read the highlights of this new stable release series here https://wpewebkit.org/blog/2025-04-11-wpewebkit-2.48.html
Also, time to update #WPE Android update to 2.48.0... this is no coincidence, the Android NDK uses Clang after all.
#BSI WID-SEC-2025-0301: [NEU] [hoch] #WebKit (#GTK #und #WPE): Mehrere Schwachstellen
Ein Angreifer kann mehrere Schwachstellen in WebKit ausnutzen, um beliebigen Code auszuführen, vertrauliche Informationen preiszugeben und einen Denial-of-Service-Zustand zu erzeugen.
https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-0301
I'm hopeful that the community surrounding #WordPress will figure out a way to preserver past this #MattMullenweg #WPE drama.
2024 in @igalia multimedia team
#gstreamer #webkit #wpe #vulkan
https://blogs.igalia.com/vjaquez/igalia-multimedia-achievements-2024/
“WordPress hosting firm Automattic and its CEO Matthew Mullenweg have been ordered to stop interfering with the business of rival WP Engine.” #WP #WPE
https://www.theregister.com/2024/12/11/wp_engine_wins_injunction_against/?td=rt-3a
WPEngine asks for more: to prohibit Automattic from blocking WPEngine's access to password-protected functionality, to prohibit blocking WPEngine's access to its plugins (including ceasing the auto-migration to Automattic versions), from disclosing WPE customers, and requiring removal of the checkbox. #WPE #WPEngine #Automattic
https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.63.0.pdf
WPEngine and Automattic have stipulated to a bare bones preliminary injunction allowing WPE access to public pages and they can submit security vulnerabilities, but Automattic still wants WPEngine blocked from password-protected functionality (Automattic would not agree to more) #WPE #WPEngine #Automattic
https://storage.courtlistener.com/recap/gov.uscourts.cand.437474/gov.uscourts.cand.437474.63.0.pdf
I'm in Cupertino this week together with other @igalia folks for the @webkit Contributors Meeting! Looking forward to a lot of interesting discussions around WebKit, @WebKitGTK and @WPEWebKit !
I just found out that another contributor to the WordPress open source project has been kicked off of the WordPress.org repo and site. This has been a regular occurrence since the whole WordPress/WPE fiasco started. It’s almost like a badge of honor to be banned now.
The problem is that many of these people being banned have high profile plugins that in the WordPress repo that they can’t update now. Security issue much? Geezus.
Is Matt Mullenweg and Automattic trying to make people leave the WordPress? Are they trying to make it less secure? Because that’s what he’s doing.
Matt keeps assuring concerned people that this is a fight with WP Engine and Silver Lake the private equity firm that owns WPE.
Apparently not. Disagree with him in any fashion and you risk getting banned.
WTAF?
I’ve been critical of Matt, but apparently I’m just a peon and not important enough to ban. Look I’m not looking to get banned, but I am going to be critical. I think he’s lost his ever loving mind and taking us all along for the ride.
More to come, I’m sure.
https://sethgoldstein.me/has-matt-mullenweg-automattic-lost-their-ever-loving-mind/
#automattic #BannedByWordPress #MattMullenweg #MattVsWPE #wordpress #wpe
I've just written a new blog post where I explain how the process of trying to fix WebKit video player buffering issues on Broadcom set-top-boxes led to a whole refactoring to add hysteresis to the buffering level monitoring code.
@DrHyde Okay, my try:
#WPE is making a fortune of the open-source software #WordPress, without giving back and abusing trademarks. But by defending his legacy, @photomatt has also decided to act like a bully. And his behaviour hurts parts of the WP community - esp. people who make money with wpe. Furthermore, it became a lawsuit so lawyers decide about actions.
And what we know from the lunch hall, 🇿🇦 or 🇺🇦, you do not defend a bully like Chamberlain, but as Churchill (I‘m German)
Война WordPress и WPE продолжается. Мэтт форкнул официальный ACF и переименовал его в SCF в официальном каталоге wp.org
👉 https://wordpress.org/news/2024/10/secure-custom-fields/
Rendering with Skia, sysprof-enabled profiling, and much more! Learn what's new in WPE WebKit 2.46!
#Wordpress #WPE https://bullenweg.com awesome resource to follow this shit show
A good time to recall the old adage "If you love something, set it free."
Especially in the open source ecosystem.
If you created/control a project & care at all about your community, don't let *you* be the thing that tarnishes your work and hurts that community.
https://social.screamingatmyscreen.com/@fallenhitokiri/113243130577029097