sandeepshetty yep, this is certainly something I need to document on the wiki.

In fact most of the machine tags were a hack to add schemaless data to my MySQL-managed schema, but as I move to flat files + ad hoc indexes I might migrate some of my machine tags to “real” data — it’s not like they’re doing much good where they are at the moment.

The main benefit is easy editing — I just use my tag editing UI instead of building another UI for each different bit of data.

Just hooked up my #indieweb notes to Brennan Novak’s rather awesome @emoome sentiment analysis API! So all my notes will have automated emotion/language analysis applied now, which I can query through machine tags.

At the moment I’m not publicly showing this data, but if you can read HTML it’s in the source (machine tags not shown by default) and if you can read JSON, add .json onto the end of the URL.

Finally decided that symfony Security component is way too complicated for my little #taproot, so ditching it — but I’ve learnt a lot from digging through it and my further efforts will try to provide some of the amazing flexibility it gives whilst being more performant and easier to understand #php #dev#meta

Made some updates to my note autolinking flow — instead of lots of unstable regexes, only one runs now (courtesy of cassis) and the rest manipulate the XML–compatible HTML which results. Much more robust, much more extendable #indieweb#php#dev#meta

I got tired of WPSM looking and working the way it does (I wrote it when I was 13 and learning PHP), so I’ve taken the data and started building the #taproot Music module. Live here. Major #WIP but already looking and working better than the old one!

↪
superfeedr:
@BarnabyWalters Thanks Barnaby :) [Also, I could not log into your site with indieAuth :/]

superfeedr yeah, there’s a weird bug where logging in only works the second time round — I haven’t fixed it yet as I rarely have to log in! At the mo there is little benefit to others logging in but I may add private content/collaborative features in the future. Crowd-sourced typo fixing FTW ;)