bitly_lrg

When you paste a link into Known, if it’s something like a youtube video (or Soundcloud or Gist if you use my plugins), it’ll attempt to expand the link into a displayable embed code.

Trouble is, when you used a link shortening plugin, this url was changed and the display got broken.

I have submitted a patch upstream which modifies the link display code with a hook which a link shortening tool can listen to, and expand links where appropriate.

When you apply this patch, the latest version of the bitly link shortening plugin will be able to expand links within a post, caching them against the object for future reference.

» Visit the project on Github...

bitly_lrg

I have previously introduced a plugin that adds Bit.ly link shortening capabilities to the Known sharing tool.

I just wanted to post a quick update to note that I have now added full OAuth2 support to the plugin.

Previously, integration was provided by the Generic Access Token, which meant that you could only have one Bit.ly account associated with an install. With OAuth2, each user on a given Known site will be able to link to their own bit.ly accounts (with their own vanity urls if they wish).

Pretty neat!

» Visit the project on Github...

Cron, on unix at least, allows commands to be scheduled and executed periodically based on a schedule.

In a web application like Known this can be handy for numerous reasons; scheduling a digest email for users for example, or for scheduling posts to appear at a future time.

Elgg had native cron support, but Known does not (yet). So, I wrote a quick plugin…

Introducing the cron scheduler

The plugin provides a /cron/ endpoint, which is called via code in a crontab script. This script makes a GET call to the endpoint, and the plugin then triggers an event accordingly, e.g. cron/daily for once a day.

The script is protected via a secret code – once you enable and configure the cron plugin, you will be provided with an admin code, which you must add to your script. This provides basic protection from someone triggering the cron tab erroneously.

Anyway, kick it about and let me know what you think!

» Visit the project on Github...