How to go block-less with the WordPress ActivityPub plugin
Uncategorized
10
Posts
5
Posters
18
Views
-
Being the web performance zealot I am, I strive to having as little JavaScript on my sites as possible. JavaScript after all has to be downloaded and has to be executed, so extra JS will always have a performance impact even when in the best of circumstances it exceptionally does not impact Core Web Vitals (which are a snapshot of the bigger performance and sustainability picture). Hence when adding blocks in WordPress, I check if the block is entirely rendered server-side and if not I look for alternatives to avoid multiple files from
wp-includes/js/dist(and in the case of some 3rd party blocks the entire React JS and more) being loaded.For that reason I tested the WordPress ActivityPub plugin with the reactions block loaded as per these guidelines and indeed it triggers the loading of
hooks.min.js,i18n.min.js,url.min.js,api-fetch.min.js(all inwp-includes/js/dist) and 2 files from the plugin itself (/wp-content/plugins/activitypub/build/reactions/view.jsand/wp-content/plugins/activitypub/build/remote-reply/view.js).
To be able to reduce the dependency on those JavaScript files, 2 questions needed to be answered; how to have reactions (which I like a lot) without the JavaScript-driven rendering and what is that remote-reply thing.Starting with the latter; “remote-reply” handles the federation of local comments on reactions (comments) from the Fediverse, showing a modal window where the commenter is asked what ActivityPub account they want to post the reaction from. I decided this was not that important for me and –with some help from Matthias @pfefferle who always gives great support- came up with a couple of lines of code to not “do” remote-reply on this blog.
Now that Fediverse reactions block is very nice and I did want reactions showing on my blog, so I started looking at the database and the ActivityPub plugin code and saw that all Fediverse reactions were stored in the
wp-commentenwp-comment-metadb-tables and were in fact accessible with theWP_Comment_Queryclass and with quite a bit of trial and error I ultimately ended up with a totally server-side generated solution that looked pretty nice (and similar to the JavaScript-rendered one).If you’re interested, you can find the code in this gist, but don’t expect it to be good. Some negatives include no language handling, unminified CSS inline and the placement of the reactions might not work on every theme as I hook into the
comments_templateaction to try to show them just before the comments. But who knows it might just work for you as well? -
undefined pfefferle@mastodon.social shared this topic on
-
Being the web performance zealot I am, I strive to having as little JavaScript on my sites as possible. JavaScript after all has to be downloaded and has to be executed, so extra JS will always have a performance impact even when in the best of circumstances it exceptionally does not impact Core Web Vitals (which are a snapshot of the bigger performance and sustainability picture). Hence when adding blocks in WordPress, I check if the block is entirely rendered server-side and if not I look for alternatives to avoid multiple files from
wp-includes/js/dist(and in the case of some 3rd party blocks the entire React JS and more) being loaded.For that reason I tested the WordPress ActivityPub plugin with the reactions block loaded as per these guidelines and indeed it triggers the loading of
hooks.min.js,i18n.min.js,url.min.js,api-fetch.min.js(all inwp-includes/js/dist) and 2 files from the plugin itself (/wp-content/plugins/activitypub/build/reactions/view.jsand/wp-content/plugins/activitypub/build/remote-reply/view.js).To be able to reduce the dependency on those JavaScript files, 2 questions needed to be answered; how to have reactions (which I like a lot) without the JavaScript-driven rendering and what is that remote-reply thing.Starting with the latter; “remote-reply” handles the federation of local comments on reactions (comments) from the Fediverse, showing a modal window where the commenter is asked what ActivityPub account they want to post the reaction from. I decided this was not that important for me and –with some help from Matthias @pfefferle who always gives great support- came up with a couple of lines of code to not “do” remote-reply on this blog.
Now that Fediverse reactions block is very nice and I did want reactions showing on my blog, so I started looking at the database and the ActivityPub plugin code and saw that all Fediverse reactions were stored in the
wp-commentenwp-comment-metadb-tables and were in fact accessible with theWP_Comment_Queryclass and with quite a bit of trial and error I ultimately ended up with a totally server-side generated solution that looked pretty nice (and similar to the JavaScript-rendered one).If you’re interested, you can find the code in this gist, but don’t expect it to be good. Some negatives include no language handling, unminified CSS inline and the placement of the reactions might not work on every theme as I hook into the
comments_templateaction to try to show them just before the comments. But who knows it might just work for you as well?@frank awesome! would you maybe like to contribute this to the plugin? I am thinking about a snippets "directory", to show how the plugin can be extended with special features!?
I will create a barebone folder with a readme for that!?
-
Being the web performance zealot I am, I strive to having as little JavaScript on my sites as possible. JavaScript after all has to be downloaded and has to be executed, so extra JS will always have a performance impact even when in the best of circumstances it exceptionally does not impact Core Web Vitals (which are a snapshot of the bigger performance and sustainability picture). Hence when adding blocks in WordPress, I check if the block is entirely rendered server-side and if not I look for alternatives to avoid multiple files from
wp-includes/js/dist(and in the case of some 3rd party blocks the entire React JS and more) being loaded.For that reason I tested the WordPress ActivityPub plugin with the reactions block loaded as per these guidelines and indeed it triggers the loading of
hooks.min.js,i18n.min.js,url.min.js,api-fetch.min.js(all inwp-includes/js/dist) and 2 files from the plugin itself (/wp-content/plugins/activitypub/build/reactions/view.jsand/wp-content/plugins/activitypub/build/remote-reply/view.js).To be able to reduce the dependency on those JavaScript files, 2 questions needed to be answered; how to have reactions (which I like a lot) without the JavaScript-driven rendering and what is that remote-reply thing.Starting with the latter; “remote-reply” handles the federation of local comments on reactions (comments) from the Fediverse, showing a modal window where the commenter is asked what ActivityPub account they want to post the reaction from. I decided this was not that important for me and –with some help from Matthias @pfefferle who always gives great support- came up with a couple of lines of code to not “do” remote-reply on this blog.
Now that Fediverse reactions block is very nice and I did want reactions showing on my blog, so I started looking at the database and the ActivityPub plugin code and saw that all Fediverse reactions were stored in the
wp-commentenwp-comment-metadb-tables and were in fact accessible with theWP_Comment_Queryclass and with quite a bit of trial and error I ultimately ended up with a totally server-side generated solution that looked pretty nice (and similar to the JavaScript-rendered one).If you’re interested, you can find the code in this gist, but don’t expect it to be good. Some negatives include no language handling, unminified CSS inline and the placement of the reactions might not work on every theme as I hook into the
comments_templateaction to try to show them just before the comments. But who knows it might just work for you as well?I have a blockless theme. There are a bunch of things which I deactivate.
See https://gitlab.com/edent/blog-theme/-/blob/master/includes/remove.php?ref_type=heads#L127
I don't have reactions though. I keep going back and forth about whether I want them and whether it is possible to back-fill them.
-
@frank awesome! would you maybe like to contribute this to the plugin? I am thinking about a snippets "directory", to show how the plugin can be extended with special features!?
I will create a barebone folder with a readme for that!?
@pfefferle sure, will be happy to contribute this 🙂
-
I have a blockless theme. There are a bunch of things which I deactivate.
See https://gitlab.com/edent/blog-theme/-/blob/master/includes/remove.php?ref_type=heads#L127
I don't have reactions though. I keep going back and forth about whether I want them and whether it is possible to back-fill them.
@Edent @frank that looks way nicer than our current "static" implementation in the Webmentions plugin btw.
what do you think: https://github.com/Automattic/wordpress-activitypub/pull/2909
-
I have a blockless theme. There are a bunch of things which I deactivate.
See https://gitlab.com/edent/blog-theme/-/blob/master/includes/remove.php?ref_type=heads#L127
I don't have reactions though. I keep going back and forth about whether I want them and whether it is possible to back-fill them.
@Edent You’re removing a lot as well, good job 🙂 What do you mean with “possible to back-fill them” Terence?
-
@Edent You’re removing a lot as well, good job 🙂 What do you mean with “possible to back-fill them” Terence?
@frank
As I understand it, likes and reposts are sent as comments. I've deleted / rejected all of those comments.
How do I get back the likes and reposts of old posts?I guess I could look at the posts and manually grab the ⭐ and ♻️ - but I wonder if there's an automated way.
-
@frank
As I understand it, likes and reposts are sent as comments. I've deleted / rejected all of those comments.
How do I get back the likes and reposts of old posts?I guess I could look at the posts and manually grab the ⭐ and ♻️ - but I wonder if there's an automated way.
@Edent I guess that if you deleted them, there’s no automated way to get them back?
-
Being the web performance zealot I am, I strive to having as little JavaScript on my sites as possible. JavaScript after all has to be downloaded and has to be executed, so extra JS will always have a performance impact even when in the best of circumstances it exceptionally does not impact Core Web Vitals (which are a snapshot of the bigger performance and sustainability picture). Hence when adding blocks in WordPress, I check if the block is entirely rendered server-side and if not I look for alternatives to avoid multiple files from
wp-includes/js/dist(and in the case of some 3rd party blocks the entire React JS and more) being loaded.For that reason I tested the WordPress ActivityPub plugin with the reactions block loaded as per these guidelines and indeed it triggers the loading of
hooks.min.js,i18n.min.js,url.min.js,api-fetch.min.js(all inwp-includes/js/dist) and 2 files from the plugin itself (/wp-content/plugins/activitypub/build/reactions/view.jsand/wp-content/plugins/activitypub/build/remote-reply/view.js).To be able to reduce the dependency on those JavaScript files, 2 questions needed to be answered; how to have reactions (which I like a lot) without the JavaScript-driven rendering and what is that remote-reply thing.Starting with the latter; “remote-reply” handles the federation of local comments on reactions (comments) from the Fediverse, showing a modal window where the commenter is asked what ActivityPub account they want to post the reaction from. I decided this was not that important for me and –with some help from Matthias @pfefferle who always gives great support- came up with a couple of lines of code to not “do” remote-reply on this blog.
Now that Fediverse reactions block is very nice and I did want reactions showing on my blog, so I started looking at the database and the ActivityPub plugin code and saw that all Fediverse reactions were stored in the
wp-commentenwp-comment-metadb-tables and were in fact accessible with theWP_Comment_Queryclass and with quite a bit of trial and error I ultimately ended up with a totally server-side generated solution that looked pretty nice (and similar to the JavaScript-rendered one).If you’re interested, you can find the code in this gist, but don’t expect it to be good. Some negatives include no language handling, unminified CSS inline and the placement of the reactions might not work on every theme as I hook into the
comments_templateaction to try to show them just before the comments. But who knows it might just work for you as well?@frank @pfefferle Great ! Nice Frank
-
Being the web performance zealot I am, I strive to having as little JavaScript on my sites as possible. JavaScript after all has to be downloaded and has to be executed, so extra JS will always have a performance impact even when in the best of circumstances it exceptionally does not impact Core Web Vitals (which are a snapshot of the bigger performance and sustainability picture). Hence when adding blocks in WordPress, I check if the block is entirely rendered server-side and if not I look for alternatives to avoid multiple files from
wp-includes/js/dist(and in the case of some 3rd party blocks the entire React JS and more) being loaded.For that reason I tested the WordPress ActivityPub plugin with the reactions block loaded as per these guidelines and indeed it triggers the loading of
hooks.min.js,i18n.min.js,url.min.js,api-fetch.min.js(all inwp-includes/js/dist) and 2 files from the plugin itself (/wp-content/plugins/activitypub/build/reactions/view.jsand/wp-content/plugins/activitypub/build/remote-reply/view.js).To be able to reduce the dependency on those JavaScript files, 2 questions needed to be answered; how to have reactions (which I like a lot) without the JavaScript-driven rendering and what is that remote-reply thing.Starting with the latter; “remote-reply” handles the federation of local comments on reactions (comments) from the Fediverse, showing a modal window where the commenter is asked what ActivityPub account they want to post the reaction from. I decided this was not that important for me and –with some help from Matthias @pfefferle who always gives great support- came up with a couple of lines of code to not “do” remote-reply on this blog.
Now that Fediverse reactions block is very nice and I did want reactions showing on my blog, so I started looking at the database and the ActivityPub plugin code and saw that all Fediverse reactions were stored in the
wp-commentenwp-comment-metadb-tables and were in fact accessible with theWP_Comment_Queryclass and with quite a bit of trial and error I ultimately ended up with a totally server-side generated solution that looked pretty nice (and similar to the JavaScript-rendered one).If you’re interested, you can find the code in this gist, but don’t expect it to be good. Some negatives include no language handling, unminified CSS inline and the placement of the reactions might not work on every theme as I hook into the
comments_templateaction to try to show them just before the comments. But who knows it might just work for you as well?@frank this has now cleaned up and added as one of the snippets that are available in the @activitypub.blog plugin by @pfefferle , see https://github.com/Automattic/wordpress-activitypub/tree/trunk/snippets/blockless-activitypub
Gli ultimi otto messaggi ricevuti dalla Federazione
-
@theleftistlawyer do you have to already have an attorney for that to work (and if so are they expensive?)? or can you, like, rent a used one at the clink
-
@aeva I thought that's what we did by coming here.
-
@aeva You can have values that are different but their difference is a subnormal value and suddenly with FTZ you have div-by-0s, yeah.
(This is super rare but still.)
-
-
@rygorous ah, so for example, a not quite zero value and zero compare differently depending on whether DAZ is on, stuff like that?
-
@aeva the main thing that breaks without denormals on is that some numeric code might start slightly misbehaving in rare corner cases you're unlikely to notice, and certain assumptions like "if (a != b) then a-b != 0" don't hold with denormals off
-
@aeva me and the DSP classic: "why does it get very slow after the envelope fades out"
I solved this when I was doing a synth in Flash by adding noise
-
@aeva It's fine for audio code but when you turn it on, you generally want to put it in a scope guard thingy that saves the original MXCSR and restores it after (way out in the outer loop, not per function or anything, toggling that isn't super cheap) because it changes the results of some float calcs and breaks a few rules that while not _super_ important might trip you up
