Reverting back to chronological sorting in the Feed

[aspeckofdustin]

Product Feedback

Hi there!

Last year, we shipped a different version of the homepage feed that sorted activity based on algorithms. This algorithmic sorting enabled us to make recommendations for you in the "Suggested for you" modules that appeared in in the activity panel of the feed.

After hearing feedback from our community, both at the time that we released the feature to generally available and more recently, we have decided to revert the sorting capabilities back to the original, chronological ordering. Our team has been working to revert this change in the Feed, that appears in your dashboard area when you click on the Octocat logo or upon signing into github.com.

In this change you will see trending developer or repository modules remain, but activity will resume to being sorted with the most recent activity first and the oldest activity as you scroll down the Feed.

We hope that this change will help enable you to be more efficient with the work you are trying to accomplish on GitHub, and we welcome any additional feedback or thoughts you might have.

Thanks!
Dustin

[AlexeiVoin]

Hi

[PeterFalken]

Chronological sorting makes the most sense as a default for the feed.
Based on my experience in the past few month, the algorithmic solution produces random results. The "Suggested for you" list can have it's own section.

[ribezzz]

after 1 month this revert is not already active? my feed don't shows any release by weeks...

[aspeckofdustin]

@ribezzz Yes, sorry -- that's not you, it's that we haven't rolled it to external users yet; it's only shipped internally for our fellow GitHub staff employees to help provide any feedback or concerns.

[diachromemis]

How important is this change for you when using the feature?

[PeterFalken]

@aspeckofdustin , just wanted to check with you if this change is now live? on the site or if there is planned date when this will be enabled. Thanks for your hard work.

[aspeckofdustin]

Hi @PeterFalken! We are working on the changes now, but we've had a couple of decisions with our leadership team that have altered the timeline a bit. As for right now, we have staff-shipped this change internally to continue collecting feedback and the current plan of record is early 2025 if all goes well with our additional testing. Thank you for your interest and following up -- sorry for the misleading notion of updated changes. (This discussion post was intended to be linked from the change log when we went live.)

❤️

[PeterFalken]

Thank you for the clarification @aspeckofdustin.
Looking forward to the deployment of the updated feed@Homepage.

[quat1024]

Sorry guys. The technology just isn't there yet to display a list of things in chronological order. Maybe in the year 2025, we will be able to sort things in chronological order. Unsolved problems of computer science.

[detty-down]

How important is sorting things in chronological order for your use of this feature?

[chakravala]

backwards sorting? newest is last and oldest is first? is GitHub planning to become irrelevant garbage? this isn't rocket science

[marius-sucan]

Today, out of blue , my feed is no longer in chronological order. Why? How to get it back to be in chronological order?

[liffiton]

Mine appears to be reverse chronological right now for some reason... the latest items are at the bottom.

[Spuner]

I confirm. New releases are now at the bottom, and old ones are at the top. Very inconvenient.

[troysjanda]

mine is same displaying stuff from a month a go at the top and newest at the bottom or on a load more call to action I dont like this please revert. Newest should at the TOP!

[satri35]

Are you experiencing the same issue with the order of content on your feed?

[troysjanda]

I want the feed to be newest 1st on the home page not months old stuff to be displayed 1st, please fix

[Dnkhatri]

yeah I want to see the latest post at the top

[AbitTheGray]

Can confirm. First few items are 3 months old, below it is 2 months followed by items with few weeks.
This means they did change it to chronological but everyone forgot to request the latest first :(

[mohak34]

same with me, need that to be reverted back to the way back

[Perdolique]

Starting today, I need to scroll down the page a lot to see the latest updates every time to ensure everything has been read.

[tenseiken]

Same here. I have items from 3 weeks ago first, then 2 weeks, 1 week, and so on. It's reverse chronological. This was definitely not the case yesterday.

[AntonPalmqvist]

Seems to be completely broken, or they added back the algorithm. I just want the newest items on the top.

[michal-kapala]

its the perfect dx we just dont get it

[Dengda98]

It's totally reverse chronological order!! I'm sure it's not the case yesterday.

[troysjanda]

moving to a differnet repo provider its bs that I have to scroll thru old stuff just to get to the new stuff not very efficient or productive. NEED TO REVERT WHAT EVER THEY DID!!! until it can be correctly fixed. Tired of this already,

[LeoHsiao1]

The latest news is at the bottom of the page, which actually discourages users from checking the latest news.
When I read a history book, the news I want to see in order is January, February, March, April, May, and finally December.
But when I read a newspaper, I want to see the news of December first, because it is December now.

[McShelby]

Oh dear, what a poor design decision and bad communication.

I first thought, the feed now is completley broken and just showing random entries.

[bjascob]

Yeah. This sucks. It's now sorted backwards. Put the most recent at the top instead of the bottom where you can't see it.

[eonurk]

Guys, revert it back for now and test it before pushing it to production haha.

[prakhar1144]

I hope the recent push is a bug and not a feature :)

[asmyshlyaev177]

I want to see the newest things first in a feed, AI toolbar not helpful.

[camden-smallwood]

Would it be difficult to add an Ascending/Descending sort option? I feel like this is pretty standard in "filtering" tools. The icon suggests it should be possible, but all we get is what topics to show, no control over the order. This is not great.

[chakravala]

is GitHub planning to become irrelevant garbage?

embrace, extend, extinguish?

is the new timeline supposed to kill GitHub? because GitHub is becoming less relevant every day microsoft is pushing stupid changes to the timeline

[FrostyX]

And so the dashboard enshittification continues.

[ieedan]

This is just confusing. I think I get the idea behind it but if it's not explained and not customizable it just makes the feed useless.

Like when I click load more there isn't even a separator or something to tell you that you are going back to a chronological feed so the feed will show:

2 hours ago

1 hour ago

yesterday 

2 days ago

[thomhurst]

I personally want to see most recent first.

Should be easy enough to add a sort option, no? Give users the option to choose how they want their feed.

It feels messy to me right now and hard to find things.

[PhilDL]

This reverse chronological order simply doesn't make sense folks, hopefully it's a bug.

[Mihai7991]

Hint: let the developers ask their CoPilots about .... order by some_date_column DESC

[troysjanda]

fact that they don't answer this post seems to me that they don't care about their users. I already migrated to another provider not putting up with this shit. No one wants to see older shit 1st on their feed, it serves no point and wastes a ton of time trying to get to the tasks of importance having to weed out or scroll to bottom or click load more to see what you should see by default. Good Day MS and farewell

[LesFerch]

@aspeckofdustin A response, preferably "sorry, this will be fixed ASAP", would be appreciated.

[R0rt1z2]

My feed is backwards; older items are showing at the top. Please stop messing with the feed, it used to work just fine.

[Eschguy]

Most recent first, how is that not the standard for everything?

[tmaster-terrarian]

The worst possible way you can address the problem would be to not respond at all. Please, even if the answer in the end is no, give us a response instead of leaving us in the dark. This completely goes against the open-and-transparent model that GitHub claims to be striving for.

[troysjanda]

Agreed. This is 1 of many reasons I swotch repo providers...

…

On Fri, Dec 6, 2024, 1:51 PM bscit ***@***.***> wrote: The worst possible way you can address the problem would be to not respond at all. Please, even if the answer in the end is no, give us a response instead of leaving us in the dark. This completely goes against the open-and-transparent model that GitHub claims to be striving for. — Reply to this email directly, view it on GitHub <#141611 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF336MKV4OTGTXVX6PH7ZGD2EIL43AVCNFSM6AAAAABQALGGGGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNBYHE2TIMQ> . You are receiving this because you commented.Message ID: ***@***.***>