Embed Notice

HTML Code

<blockquote style="position: relative; padding-left: 55px;"><section><a href="https://one.darnell.one/users/darnell/statuses/113207325645132357">Darnell Clayton :verified: (darnell@one.darnell.one)'s status on Friday, 27-Sep-2024 12:12:07 JST</a><a href="https://one.darnell.one/@darnell" title="darnell@one.darnell.one"><img src="https://gnusocial.jp/avatar/903-48-20220924005929.webp" width="48" height="48" alt="Darnell Clayton :verified:" style="position: absolute; left: 0; top: 0;">Darnell Clayton :verified:</a><div><a href="https://infosec.exchange/@fisherstudio/113207060438767527" rel="in-reply-to">in reply to</a><ul><li><li><a href="https://gnusocial.jp/user/171743" title="fisherstudio@infosec.exchange">Fisher</a></li></ul></div></section><article><p><a href="https://infosec.exchange/@fisherstudio">@fisherstudio</a> <a href="https://fosstodon.org/@otto42">@otto42</a> I posted this on <a href="https://threads.net/@darnell/">@darnell@threads.net</a> but it appears <a href="https://one.darnell.one/tags/WPEngine" rel="tag">#WPEngine</a> has created a “workaround” to get around the <a href="https://one.darnell.one/tags/WordPress" rel="tag">#WordPress</a> block: <a href="https://eric.mann.blog/wordpress-drama-from-the-sidelines/" rel="nofollow noreferrer">https://eric.mann.blog/wordpress-drama-from-the-sidelines/</a></p></article><footer><a rel="bookmark" href="https://gnusocial.jp/conversation/3729748#notice-7312893">In conversation</a><time datetime="2024-09-27T12:12:07+09:00" title="Friday, 27-Sep-2024 12:12:07 JST">about 2 months ago</time> <span>from <span><a href="https://gnusocial.jp/notice/7312893" rel="external" title="Sent from gnusocial.jp via ActivityPub">gnusocial.jp</a></span></span><a href="https://gnusocial.jp/notice/7312893">permalink</a><h4>Attachments</h4><ol><li><article><header><div>Domain not in remote thumbnail source whitelist: eric.mann.blog</div><h5><a href="https://eric.mann.blog/wordpress-drama-from-the-sidelines/">WordPress Drama: From the Sidelines</a></h5><div> from <span>ericmann</span></div></header><div>Yeah ... the inside track of WordPress is a mess right now. I'm sure we all have opinions, so I figured I should log mine in as well.</div><footer></footer></article></li><li><label><a rel="external" href="https://gnusocial.jp/attachment/3227083">Screenshot highlighting WP Engine found a workaround to bypass the block from the WordPress Foundation</a></label><br><a href="https://cdn.masto.host/onedarnellone/media_attachments/files/113/207/325/516/133/335/original/0d77502083bffb06.jpeg" rel="external">https://cdn.masto.host/onedarnellone/media_attachments/files/113/207/325/516/133/335/original/0d77502083bffb06.jpeg</a></li></ol></footer></blockquote>

Corresponding Notice

Embed this notice
Darnell Clayton :verified: (darnell@one.darnell.one)'s status on Friday, 27-Sep-2024 12:12:07 JSTDarnell Clayton :verified:
in reply to
- Otto
- Fisher
@fisherstudio @otto42 I posted this on @darnell@threads.net but it appears #WPEngine has created a “workaround” to get around the #WordPress block: https://eric.mann.blog/wordpress-drama-from-the-sidelines/
In conversationabout 2 months ago from gnusocial.jppermalink
Attachments
1. Domain not in remote thumbnail source whitelist: eric.mann.blog
  WordPress Drama: From the Sidelines
  from ericmann
  Yeah ... the inside track of WordPress is a mess right now. I'm sure we all have opinions, so I figured I should log mine in as well.
2. Screenshot highlighting WP Engine found a workaround to bypass the block from the WordPress Foundation
  https://cdn.masto.host/onedarnellone/media_attachments/files/113/207/325/516/133/335/original/0d77502083bffb06.jpeg

Public

Embed Notice

HTML Code

Corresponding Notice