#wordpress 2023-09-26

2023-09-26 UTC
RasAlGhoul, [schmarty], [jeremycherfas], SigmundurM and gRegor joined the channel
#
[snarfed]
noticed another regression in v5 webmention plugin: comments used to link to the original source, either its u-url or just the source URL itself, but now they link to the fragment on the WordPress post page. I assume that wasn't an intentional change? https://github.com/pfefferle/wordpress-webmention/issues/419
#
Loqi
[preview] [snarfed] #419 v5 no longer links to original source page (or `u-url`)
#
GWG
[snarfed]: We wrote the code from 2020-2023... I can't remember what I did yesterday.... but I know there were some things people had issues with that might have been intentional and others that weren't
#
GWG
I want to look at a different way of doing the overflow for the piles as well
#
GWG
Maybe a numeric view
#
[snarfed]
hmm ok. linking to the source page is definitely what all webmention receivers should do, including you all 😁
#
[snarfed]
if it helps, the link is far higher priority for me personally than truncating facepiles
#
GWG
[snarfed]: We were linking to the author url before, not the source url
#
GWG
I think you had suggested that
#
[snarfed]
I'm talking about replies, not facepiles. replies linked to the actual reply
#
GWG
Oh, excuse me.
#
[snarfed]
(facepiles in v5 are still correctly linking to the author, yes)
#
GWG
Long day.
#
GWG
I'm taking next week off
#
GWG
Once again, need to get caught up
#
GWG
But specifically with this...what design would you think would look good on overflow?
#
GWG
Numeric with expansion is what I'm thinking.
#
GWG
Maybe a detail tag
#
[snarfed]
the design it already used in v4 was great, doesn't need a new design
#
GWG
[snarfed]: Wasn't that JS?
#
[snarfed]
(only showed the first n; if there were more, it showed an ellipsis at the end that could be clicked to show the rest)
#
[snarfed]
sure? JS is great
#
[snarfed]
I suspect I implemented this in v4...? 😆
#
GWG
You did
#
[snarfed]
lol. bring it back!
#
GWG
That's why I was thinking a details tag...you don't need any JS
#
GWG
So I might reimplement that way
#
GWG
Also, was looking at other designs
#
[snarfed]
(again though maybe prioritize the link first!)
#
GWG
[snarfed]: Yes, but I'm sitting in a waiting room... contemplations is all I can do here.
#
GWG
[snarfed]: I remember a discussion between you and aaronpk on clustering years ago that might help
#
GWG
And I can dump into an issue as I think
#
[snarfed]
hmm no that's https://snarfed.org/clustering-notifications , not related to facepile truncation
#
GWG
Well, there was something I'm thinking of, maybe it was a [tantek] braindump
#
GWG
Even how silos used to do it
#
GWG
The question is..if you have 20 faces, who do you want to show?
#
GWG
Do you want to exclude people with invalid images?
#
GWG
Etc
#
[snarfed]
ooh fun! let's start with just bringing back the lost truncating functionality, then after that we can think about how to prioritize
#
[snarfed]
(eg on a popular post, I don't want my WP server trying to fetch hundreds of images across the internet before it can serve the post HTML)
#
GWG
That's my plan
#
GWG
[snarfed]: I still want to cache them locally
#
GWG
[pfefferle] and I differed on that, so I may make my code an optional separate piece
#
[snarfed]
GWG yes! that kind of image cache would be a great opt in feature of the plugin, or add-on plugin
#
[snarfed]
I'm never a fan of plugin proliferation, I'd vote for opt in feature, but 🤷
#
GWG
[snarfed]: Code is written, may publish it as a GitHub plugin for now until we settle
#
GWG
I know [pfefferle] preferred to suggest Avatar Privacy but it didn't work well for me.
#
GWG
And we'd already tested the code