The default behaviour of comments in an Elgg system is similar to that of standard blogging software, in that comment notifications only go to the post’s original author.

So, if Alice uploads a file and Bob comments on it, Alice would receive a notification. If Charlie comments on it as well, only Alice would receive the notification. In a modern social network, this artificially stifles conversation.

So, I wrote a very quick plugin which modifies the default notification behaviour slightly…

Now, with this plugin activated, if Charlie leaves a comment, both Alice and Bob will receive a notification.

Simple, but quite handy.

» Visit the project on Github…

Just a quick update to point you good folk over to a couple of Idno plugins I’ve put up on github.

The first, LoginSyslog, is a simple plugin that outputs login events (success and failure) to the Auth.log, in much the same way as my Elgg fail2ban plugin. This allows you to audit login attempts on your Idno site, as well as use a tool like fail2ban to protect your site from brute force attacks.

The second, Pingback, adds support for incoming Pingback. Idno primarily supports webmention as a notification mechanism, and while legacy support for outgoing pingbacks, however incoming pingback support was missing. This plugin adds the missing functionality, meaning your Idno site will play nicely with WordPress and similar.

Happy hacking!

LinkedIn-Logo-02I was doing some work on a client website the other day, when the OAuth login code I was using to provide “log in via linkedin” support inexplicably stopped working. It would seem that linkedin had a (temporary) problem with their OAuth1 api.

A quick google, and I found that LinkedIn’s OAuth 1 api has been superseded, and I feared that it had finally been switched off. Since there was no word from LinkedIn, and I needed to get functionality working for my client, I rewrote the connector.

This plugin provides “Login via LinkedIn” functionality to Elgg 1.8, enjoy!

» Visit the project on Github…