After today's IndieWebCamp popup session, I built a way to create unlisted posts on my site that require a secret key in the URL in order to view.
Since all my URLs are more or less sequential, I needed a way to be able to add something to the URL that is unguessable. It was a relatively easy thing to add!
Try viewing this post without the secret string at the end to see the feature in action: https://aaronparecki.com/2021/06/26/9/MXJEJKW
New #indieweb libraries: taproot/micropub-adapter and taproot/indieauth!
Finally put the finishing touches on these two closely-related libraries, which make it very easy to add Micropub and IndieAuth support to any PHP app which uses PSR-7.
Feedback appreciated, either as replies, GH issues, or at indieweb.org/discuss
PHPUnit’s HTML code coverage reports don’t play nicely with GitHub pages “main branch /docs folder” by default, as they store CSS, JS and icon assets in folders prefixed with underscores.
Here’s a little bash script to run tests with code coverage enabled, then move the assets around:
rm -rf docs/coverage/
XDEBUG_MODE=coverage ./vendor/bin/phpunit tests --coverage-filter src --coverage-html docs/coverage
mv docs/coverage/_css docs/coverage/phpunit_css
mv docs/coverage/_icons docs/coverage/phpunit_icons
mv docs/coverage/_js docs/coverage/phpunit_js
grep -rl _css docs/coverage | xargs sed -i "" -e 's/_css/phpunit_css/g'
grep -rl _icons docs/coverage | xargs sed -i "" -e 's/_icons/phpunit_icons/g'
grep -rl _js docs/coverage | xargs sed -i "" -e 's/_js/phpunit_js/g'
That allows you to use GitHub pages to show code coverage reports as well as docs, as I’m doing for taproot/indieauth.
Reminder that it's #HomebrewWebsiteClub Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! https://events.indieweb.org/2021/06/homebrew-website-club-nottingham-pqX9qzmGWbHp
Not unrelatedly, Jack Jamieson’s dissertation on the IndieWeb is called Independent Together: Building and Maintaining Values in a Distributed Web Infrastructure.
Also on:Yea that looks like a cool site! I hope it catches on, but we also have IndieNews and Indieweb.xyz and those have never really had huge usage.Yea I think showing the replies inline makes it more interesting than just an aggregator to me. I hope it might stimulate some blogchains (https://doubleloop.net/2020/04/05/blogchains-and-hyperconversations/)
I kicked one off, if you’re interested! – https://www.indieforums.net/threads/c1c36e81a755848c.html
https://github.com/hometown-fork/hometown/wiki/Exclusive-lists
Also on:
Reminder that it's #HomebrewWebsiteClub Nottingham tomorrow! I hope to see you there at 1730 for some website stuff! https://events.indieweb.org/2021/05/homebrew-website-club-nottingham-QbtrPT07Bwn5
I had some fun using the open standard #Microformats2 to update my CV to be machine-parseable - you can check it out at https://hire.jvt.me and there's a bit more info on https://www.jvt.me/posts/2021/05/25/microformats-resume/
Marking up my Curriculum Vitae with Microformats2
150
The fact that so many people publish their thoughts and share knowledge, is something I’ve always loved about the web. Whether it is practical stuff about how to solve a coding issue or some kind of opinion… everyone’s brain is wired differently. It may resonate, it may not, that’s also fine.
De Indieweb bouwstenen zijn een mooie verzameling onderdelen om extra functionaliteit aan je blog toe te voegen. Helaas werkt één van de plugins niet altijd naar behoren zoals ik vanochtend weer merkte. Ik heb op mijn telefoon een Shortcut waarmee ik websites kan liken. Dit is vergelijkbaar met de...I’ve had that same problem before, and never really reached a solution. I think you’re right – it is likely that it can’t parse the information it needs properly from the page you liked.
One way to dig in to it could be to see if that same URL, when pasted in to the ‘URL’ section when creating a post manually in WordPress (not via Micropub), gets the correct values picked up. That could point whether it is specifically a parsing issue or a Micropub issue.