I’ve been using various IndieWeb ideas here for a fairly long time now, this is a great summary.<\/p>\n\n\n\n
\nIt was a movement with concrete ideas, protocols and an active community! As I read through their wiki, I understood their position and the intelligence of their proposals more and more. Such was my enthusiasm that I decided to follow their advice and adopt the protocols that made sense for my site. After finishing the tests and adjustments, I can confirm that the experience has been very positive: I have learned a lot, the UX of my website has improved a bit more, and I enjoyed the process.<\/p>\n I joined the IndieWeb, here’s what I learned | Andros Fenollosa<\/a><\/cite><\/blockquote>\n\n\n\n
\n\n\n\nEvery so often I hit a link to a tweet that twitter refuses to show me. Probably because of an ad-blocker I’ve set up and forgotten about. This might be the solution.<\/p>\n\n\n\n
\nBookmarklet which redirects from the current x\/twitter address to its equivalent in X cancelled<\/a> <\/p>\nbookmarklet which redirects from x\/twitter to xcancel.com<\/a><\/cite><\/blockquote>\n\n\n\n
\n\n\n\nI’ve seen quite a lot of painted ladies this summer, not as much as in 2019 the big year for them in Scotland.<\/p>\n\n\n\n
\nButterfly Conservation is asking nature lovers around the country to help count an explosion of exotic Painted Lady<\/a> butterflies across the UK.<\/p>\n Help us count the #PaintedLadySummer! | Butterfly Conservation<\/a><\/cite><\/blockquote>\n\n\n\n
\n\n\n\nI don’t use the classic editor much any more, but its disappearing might not be great for Glow Blogs. This is just about the classic block not the classic editor.<\/p>\n\n\n\n
\nIn an earlier post<\/a>, I announced that the Classic block (
core\/freeform<\/code>) would be hidden from the inserter by default starting in WordPress 7.1, accompanied by a new filter and a companion plugin.<\/p>\n\n\n\nI\u2019ve decided to revert this change.<\/strong> The Classic block will continue to appear in the inserter in WordPress 7.1, exactly as it does today. There is no change in behavior for users or developers, and no migration is required. <\/p>\n The Classic block stays in the inserter for WordPress 7.1 \u2013 Make WordPress Core<\/a><\/cite><\/blockquote>\n\n\n\n
\n\n\n\nAlway good to be reminded about function.php<\/p>\n\n\n\n
\nI was inspired by this post to use WPCode to adjust how pages archive posts are displayed<\/p>\n 💬 46 Extremely Useful Tricks for the WordPress Functions File | Read Write Collect<\/a><\/cite><\/blockquote>\n\n\n\n
\n\n\n\nAnd a reminder that meta are not kind:<\/p>\n\n\n\n
\nThat\u2019s over a 10\u00d7 discount in exchange for giving your data to Meta. I can see the appeal if you don\u2019t care about the privacy of your data and code, like, say, if you\u2019re using Muse Spark to generate code for a throwaway project, or for something that\u2019s open source anyway. <\/p>\nDaring Fireball: Meta: Introducing Muse Code and Muse Spark 1.2<\/a><\/cite><\/blockquote>\n\n\n\n
\n\n\n\nDave Winer on micro.blog. micro.blog is, i believe, one of the most amazing services on the internet.<\/p>\n\n\n\n
\nI was able to do that with micro.blog which is the swiss army knife<\/a> of interop in the web of the 2020’s. <\/p>\nScripting News: Saturday, August 8, 2026<\/a><\/cite><\/blockquote>\n\n\n\n
\n\n\n\nI am not teaching any more, I did a few days supply last session and might continue. I found A.I. useful for thinking about planning for stages I had not taught for years. But I used it a sounding board, and modified everything. Having pupils taught directly by A.I. might have some problems.<\/p>\n\n\n\n
\n