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.
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.
When elements from independent systems of semantic interoperability appear within the same document, the semantic compatibility of the independent systems is the measure of their non-interference.
HTML and CSS have very good semantic compatibility, often appearing together in the same document.
This is on my mind lately as I consider the compatibility of web application sources with microformats, while building a utility to help identify any aspects of the web application sources which interfere with the desired interoperability embodied by microformats.
I currently describe my pre-release project as: “A utility which checks webapp sources for compatibility with microformats semantics”. Based on the foregoing, I’m considering changing the description a little. At the end of the day, the work is the program that helps find the issues in the code. I’m hopeful that someone with greater comfort discussing the topic will help me to gain some confidence in how I present the program. So long as it is providing some useful and desired outcome, I’ll be working on it for awhile longer. Hopefully work to benefit more than myself!
A useful tool for self-testing website optimizations. Free for the core testing and reports.
This is a test of the Bridgy Publish Plugin.