I've added several new options to this library. All of them include tests and there is documentation in the readme for them.

$.fn.timeago.defaults = {
  // The default attribute to put the ISO8601 absolute time to parse.
  attr: 'datetime',

  // An extra space character will be added between the time and the unit.
  // '1 minute' will look like '1minute' with spacing set to `false`.
  spacing: true,

  // Will enable displaying text approximation words
  // such as 'about 1 hour' and 'almost 2 years'.
  approximate: true,

  // The text generated by Smart Time Ago will look like '3 hours ago'.
  // If you want the text looks like '3 hours from now',
  // you might need change the 'suffix' to ' from now'.
  suffix: ' ago',

  // Will show how many seconds. Instead of 'less than a minute ago' you'll see '24 seconds ago'.
  showSeconds: false,

  // You can specify how many seconds, below 59, to show a 'just now' message
  // instead of '1 second ago'.
  showNow: false,

  // After a date's relative time is too big,
  // you might want to display its absolute version.
  // For example, if after one month you don't want to display '2 years ago',
  // you can make `maxRelative` equal `2592000` which is a month in seconds.
  // Then specify an absolute displaying date function.
  maxRelative: false,
  absoluteDate: function(date, datetime) { return datetime; }
};

If you notice, I also removed the dir and selector options, because those are not needed. jQuery already has a selector engine, and it's already possible to call timeago on dynamically added elements. It makes much more sense for the user to be able to select what elements to use with time ago like this

$('.timeago').timeago();

instead of

$('body').timeago();

Also, this way, each of the elements get their own TimeAgo instance, and therefore their own timeout. I didn't really understand why the dir option was needed, it would mean that every single date for that instance would be updated even unnecessarily, which I think goes in the wrong direction if we want this to be smart.

Also, I made this much smarter. The timeouts are now set to go off exactly when the relative date will change, and not before or much much after. Being more accurate with timeouts is smarter. :)

Hey there, just saw this library and it would be great if it would have official bower support. I took the liberty of quickly creating a bower.json I don't know if you have used bower before, but you would still need to register the package and Bower uses git Tags for versioning, so it would be great if you could add that as well. Here are all the instructions: http://bower.io/ under Registering packages That would be great.

Danish locale file:

  $.fn.timeago.defaults.lang = {
    units: {
      second: "sekund",
      seconds: "sekunder",
      minute: "minut",
      minutes: "minutter",
      hour: "time",
      hours: "timer",
      day: "dag",
      days: "dage",
      month: "måned",
      months: "måneder",
      year: "år",
      years: "år"
    },
    prefixes: {
      lt: "mindre end",
      about: "ca.",
      over: "over",
      almost: "næsten",
      ago: ""
    },
    suffix: " siden"
  };

I had a time stamp that was from 5 minutes ago, but the script output gave me "2 hours ago". My local time zone is UTC+2, so for me I have had to change the source code of the timeago.js file to output the correct time. Would it not be better to have this as a setting which can be overridden if required?

Hello,

What about all the other variables used in the original jquery.timego, like prefixAgo, prefixFromNow ? How con you implement that ? You should note that some languages, other than English, use different grammar/semantics when building sentences.

thanks

Besides these, I feel we need further enhancements:

• lt: "less than a" : if it's feed with hour, "less than a hour" is wrong. The correct one is "less than an hour".
• Japanese locale may not be correct due to my super poor knowledge.

Nice and useful plugin. However, it outputs NaN on timestamps that doesn't have three millisecond digits. This pull request will fix that.

Thanks Jonas

I'm using your code for a spanish-speaking project, so here's some code to do i18n. Hope it helps.

• Using the default options, we can add units and prefixes
• Added a spanish set
• Added a non-native french set that should be corrected by a native speaker
• I'm not familiar with testing, so I added the file to watch it fail "properly" :)

Great job, by the way!

The problem with this TimeAgo technology is that it doesn't support future time ... for example I wanted to add a future time for a coupon code expiration, when I use TimeAgo in this case it says about {X} time (AGO). Is there anything I can do to fix it? Thanks

Hi, Thanks @poiyzy for this awesome jquery plugin :+1: Sorry for my bad english :(

Is it possible to convert a datetime to full timeago like this 2015-01-25 03:37:46 to "2 months, one day, 5 hours and 10 minutes ago"

now it only convert 2015-01-25 03:37:46 to "2 months ago"

Thanks

I'm using the plugin in a rather dynamic application with many items being added and removed from the DOM. When I add a time item I initialize it with:

this.children('.timeago').timeago();

I'm wondering however how should I go about destroying the listeners and unbinding the plugin. After a first look there's no destroy method available.

Thanks!