Viewing 3 replies - 1 through 3 (of 3 total)
  • HAMMADHASSAN

    (@hammadhassan)

    Thread Starter r-a-y

    (@r-a-y)

    Yeah I know what the original does.

    The forked version clearly doesn’t list the differences between the original version so that’s why I was asking.

    Mine was born from a patch I sent to the original author and it was taking too long to reach the main plugin. I needed so I forked it. And make it available to others.

    1. The original only worked for a single blog, single user.
    2. Mine is compatible with WPMU and original wasn’t.
    3. Mine uses always cURL and the original didn’t.
    4. Mine also included sm00sh URL shortner. Original didn’t and now includes is.gd
    5. Mine will work with URL Shortner or URLy Shortie this week
    6. Internal URL Shortning will be ditched. It will be URL Shortening agnostic 🙂

    Sadly, the author of the original one incorporate all my modifications but forgot to thank it anywhere.
    Ah! He included all except sm00sh (which is a URL shortner I implemented) and justified it with the reasons he later forgot when added is.gd.

    This will be merged with Shorten2List and both will be replaced by Spreadr. In that new plugin Twitter will be ditched and you will have to install URL Shortner or URLyShortie or any other URL Shortner that creates a post meta called shorturl or short-url if you want to use URL shortning. Ping.FM already shortens URLs before reposting.

    For now you can use one or another. No big differences.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[Plugin: Shorten2PingNG] Differences between the forked Shorten2Ping plugin?’ is closed to new replies.