Another testing note.
This is an attempt at replying to a reply.
Attempting a webmention to wp-theme-dev.cjwillcock.ca.
This is a new post, in reply to a previous post. The previous post should receive a webmention.
A reply via post-kind.
Test for comments.
Testing micropub via Quill.
I authored and personally use this Tab Quantizer Chrome extension & companion server script, to record my browsing history from Chrome onto my own server. I publish some of the information I gather with this, to my Now page (near the bottom).
- Keeps a running tab of active Chrome browser tabs across multiple devices and multiple windows.
- Records a complete history of pageviews with time and URL
- Records ‘walks’ – the series of pages viewed in a given tab, from the time it first opens, through each pageview until it closes
To make this work you need your own server for the script that records the data. Given that this extension is not coming from the built-in Play store (or whatever it is for Chrome) you’ll need to enable developer mode and load the unpacked extension manually. A consequence of this is after each Chrome update, the extension needs to be manually enabled.
I have been thinking of publishing this to the Play store (or whatever it is for Chrome). I haven’t done that before, so I have much to learn there.
I think all the bugs have been worked out. It works for me. This is my first Chrome extension work. It was made fast and cheap, so there is plenty of room for improvement as far as the code and user-experience goes.
Also there is no documentation whatsoever about using the collected data for some purpose. For now that remains an exercise for the reader.
Enjoy the Beta. Discussion in #indieweb-dev on irc.freenode.net.
Some 4500 words after I decided to add a few comments and insights ... it’s a good idea to consider what happens when follow a handful rather simple and obvious rules of how to write code.
Erik Torsner articulates his authoring of a production-ready-but-not-really WordPress plugin which reproduces the output of Matt Mullenweg’s commonplace Hello Dolly, while demonstrating and justifying his practical choices in software construction and testing; a wonderful example for others to consider and leverage.