I'll make an announcement about this later.

I was making a change just before this. I screwed up a bit though so I had to clear everyone's notifications.

The upside of it is that notifications should work more reliably now, for example inside multi-quotes.

Can you explain why you prefer the old one?

moniqee brotan nicety onlinetradermy guyfriendx

I have added a bump button and last bump time to the search and subscription pages. Can you give your feedback on this?

Sorry, I typo'ed one letter in the code. Bumping should work in services noticeboard and properties sections now.

1) Sorry I don't understand. Can you elaborate on #1. With the old system, how did you time your bumps?

2) I think that will be a temporary problem. However now that we have relaxed the posting rules, you can be more creative in how you want to draw attention to your sales

The topics in "find member topics" are now sorted by rank. I'll change the search function to default sort by rank later.

If "thread starter's post won't bump own thread" is coded without changing anything else, a new time inconsistency is introduced.

Let's look at this timeline if we do that:
1:00PM - wKkaY posts a reply to dhui's thread. Last post = 1:00PM, Last poster = wKkaY
5:00PM - dhui posts a reply to wKkaY on dhui's thread. Last post = 1:00PM, Last poster = dhui

It will look weird in the topic index that someone replied at 1:00PM, but when you enter the topic, the actual last reply you see was made at 5:00PM.

The current system does this:
1:00PM - wKkaY posts a reply to dhui's thread. Last post = 1:00PM, Last poster = wKkaY
5:00PM - dhui posts a reply to wKkaY on dhui's thread. Last post = 5:00PM, Last poster = dhui.

I wrote the old bump system in 2006 and introduced the first inconsistency where "Last post time" doesn't really mean last post time. This time, I intend to code it the proper way instead of introducing a second time inconsistency. This means that instead of overloading the "last post time" with different meanings, the time of bump and time of last post must be kept and shown separately.

The benefit of doing it this way is that if it's a really terrible idea, I can always change the templates to show last bump time instead of last post time But we will see.

Can you explain the difference between the old bump feature and what we have now? For example, what would you have seen in that screenshot, instead of what are seeing now?

Ok. Lemme see what I can do about this.

RedDevil32 brotan dhui From a buyer's point of view - what do you think if I remove "last post by (third party)" altogether? So if you open garage sales, you will see only the time of last activity by a seller (whether it is a reply or bump).

Ok. Besides making the cosmetic changes, we need to ensure threads stay fresh. Some things I have in mind are monthly reminders to thread starters to bump their threads, auto-closing threads after N months of inactivity, and purging them after further inactivity. This is out of this topic's scope but I'll be sure to start a new feedback topic about that once we're done refining this bump feature.

I've been busy these past couple of days - will look into your feedback soon.

RedDevil32 brotan Just made some changes. The last seller update is shown now - this includes bumps, replies, and edits. I won't be removing the last post column right now. Let's see how the feedback from our members goes before making any further changes

Adjusted the language a little bit.

Rank = last post like before.

We changed how bump works so that it doesn't update the last post time. Because of this, if you sort by Last post now, bumped threads won't be on the first page.

Yes, so don't sort by last post if that's not what you want. Last post literally means last post now. Sort by rank (the default) if you want to see bumped threads first.

I decided on the "XX minutes/hours/days ago" format because it looks neater when you have a pageful of threads. You have a valid point though - perhaps for threads updated Today I can show the time instead.

That's an old bug and is related to the default behavior of IPB mangling pipes (and some other characters) in usernames.

Ok, will get that done tonight/tomorrow when I have time