GitHub Community
Reverting back to chronological sorting in the Feed #141611
-
Product FeedbackHi 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! |
Beta Was this translation helpful? Give feedback.
Replies: 45 comments 46 replies
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Hi |
Beta Was this translation helpful? Give feedback.
-
|
Aamazing ! |
Beta Was this translation helpful? Give feedback.
-
|
Chronological sorting makes the most sense as a default for the feed. |
Beta Was this translation helpful? Give feedback.
-
|
Aamazing ! |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
after 1 month this revert is not already active? my feed don't shows any release by weeks... |
Beta Was this translation helpful? Give feedback.
-
|
@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. |
Beta Was this translation helpful? Give feedback.
-
Please ship it to external users, too. Having entries which are two months old as the first few entries in my feed when there has been newer activity today or yesterday is confusing. In my opinion, that's a broken UX. You are not doing your (external) users a favour with this algorithmic sorting as it is now. |
Beta Was this translation helpful? Give feedback.
-
@aspeckofdustin What? Ship to external users please. I need to work at GitHub now to have an actually useable feed? Y'all messed up the feed to boost your employee numbers or something? Also give us a way to disable the For You garbage. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @striezel -- that is definitely part of our plan. And @FaultyFunctions , it was a bug that was introduced with the work to deprecate one piece of infrastructure; that was not intentional and has now been fixed. It was by no means intended to do anything but move us to a place where we can revert back to full chronological sorting. If you can imagine, when we make any changes, there is a large volume of rather intense feedback, and we are trying to test rigorously before applying permanent changes. The reactions in this thread also affirm that any changes, even if they're unintentional, will generate strong reactions so we are trying to make minimal changes. We would appreciate your understanding and empathy here as we work as a team to the state of the feed (chronological) that has been requested across the community. My ask is to maintain a respectful tone in the feedback because we are also humans on the other end, and sometimes unintentional changes occur as a result of other back-end changes. A friendly reminder that this thread I initiated is intended to be a place to get feedback from the community so we can make your experience better; I do appreciate the parts of your feedback that we can action on and hope that we keep this constructive. Thanks, |
Beta Was this translation helpful? Give feedback.
-
|
@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. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the clarification @aspeckofdustin. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
backwards sorting? newest is last and oldest is first? is GitHub planning to become irrelevant garbage? this isn't rocket science |
Beta Was this translation helpful? Give feedback.
-
|
juststop fucking about with the homepage now got oldest results 1st and newst results last, WTF! |
Beta Was this translation helpful? Give feedback.
-
I am inserting here because the team has been working very hard to enable these changes, but reverting back to chronological sorting is tied to one piece of infrastructure that we are deprecating (and requires us to create parity with feature sets on another track). Yes, reverting back to chronological ordering should be simple but with a change that our organization made last year for algorithmic suggestions, parsing out the dependencies is proving not as simple. I do read all of the replies when I can get to them, even if I don't respond to all of them. We're not looking to make your experience worse; the poorer experience that you all unfortunately went through last week was an unfortunate bug. For that I am sorry on behalf of our team. While I appreciate all of your feedback, both positive and constructive, I just ask that we can keep the tone of the responses respectful here. Thanks, |
Beta Was this translation helpful? Give feedback.
-
|
Today, out of blue , my feed is no longer in chronological order. Why? How to get it back to be in chronological order? |
Beta Was this translation helpful? Give feedback.
-
|
Mine appears to be reverse chronological right now for some reason... the latest items are at the bottom. |
Beta Was this translation helpful? Give feedback.
-
|
I confirm. New releases are now at the bottom, and old ones are at the top. Very inconvenient. |
Beta Was this translation helpful? Give feedback.
-
|
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! |
Beta Was this translation helpful? Give feedback.
-
|
I confirm that I have the same experience. |
Beta Was this translation helpful? Give feedback.
-
|
I want the feed to be newest 1st on the home page not months old stuff to be displayed 1st, please fix |
Beta Was this translation helpful? Give feedback.
-
|
yeah I want to see the latest post at the top |
Beta Was this translation helpful? Give feedback.
-
|
Can confirm. First few items are 3 months old, below it is 2 months followed by items with few weeks. |
Beta Was this translation helpful? Give feedback.
-
|
same with me, need that to be reverted back to the way back |
Beta Was this translation helpful? Give feedback.
-
|
Starting today, I need to scroll down the page a lot to see the latest updates every time to ensure everything has been read. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Seems to be completely broken, or they added back the algorithm. I just want the newest items on the top. |
Beta Was this translation helpful? Give feedback.
-
|
its the perfect dx we just dont get it |
Beta Was this translation helpful? Give feedback.
-
|
It's totally reverse chronological order!! I'm sure it's not the case yesterday. |
Beta Was this translation helpful? Give feedback.
-
|
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, |
Beta Was this translation helpful? Give feedback.
-
|
The latest news is at the bottom of the page, which actually discourages users from checking the latest news. |
Beta Was this translation helpful? Give feedback.
-
|
Oh dear, what a poor design decision and bad communication. I first thought, the feed now is completley broken and just showing random entries. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
This was a bug that occurred as a result of a change we were testing and not by design, for what it's worth. Thanks for your feedback. |
Beta Was this translation helpful? Give feedback.
-
|
Guys, revert it back for now and test it before pushing it to production haha. |
Beta Was this translation helpful? Give feedback.
-
|
I hope the recent push is a bug and not a feature :) |
Beta Was this translation helpful? Give feedback.
-
|
I want to see the newest things first in a feed, AI toolbar not helpful. |
Beta Was this translation helpful? Give feedback.
-
|
Hey Github, A simple "Sorry guys, we are working on it" would be great, don't you think? |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, @manio, I'm sorry that you feel that you're being ignored by us but that is not the intention. We are actively working on changes to the feed and it's just myself as the product manager on a couple of areas (and working on replies to the community where I can); as I hope you can imagine, it's not always possible to reply but I do try to share updates when there is a meaningful update. I felt today was good since we deployed the fix yesterday and validated today. I try not to respond without something significant to share. If it helps for more contextual awareness, this is part of a larger, long-term project that requires us to deprecate one track of infrastructure and create parity on the other, which is a long-tailed project that I can't necessarily share all the details behind. However, as soon as we were aware of the issue in the comments above, we started working on the fix, which took a bit of time. (I didn't feel that saying we are working on it would be sufficient in this thread as this is intended to surface feedback which we do read through on a semi-regular basis, but I will note your suggestion for future instances.) We appreciate your understanding and empathy in advance, |
Beta Was this translation helpful? Give feedback.
-
|
It's OK, thanks for lengthy explanation, Dustin :) |
Beta Was this translation helpful? Give feedback.
-
|
Appreciate your interest in supporting the community and making sure that we stay communicative, though, @manio! |
Beta Was this translation helpful? Give feedback.
-
|
I wrote a crude Tampermonkey script to fix the order on the page load: https://greasyfork.org/en/scripts/520074-fix-order-of-github-dashboard. |
Beta Was this translation helpful? Give feedback.
-
|
This is awesome, Thank you. Would love to see it persist on page refresh/reload. Great work. |
Beta Was this translation helpful? Give feedback.
-
|
I published the version 2. I tried to reorder the activities on each update, be it a filter change or click on the More button. It works, but the More button never appears after the first click. So, you can fetch another 20 activities only once. Obviously, the turbo-frame element doesn't like its content being shuffled from the outside... Fetching more activities is strange. Instead of adding the new activities to the same turbo-frame, it creates a new turbo-frame with them and inserts it to the previous one, even using the same ID attribute, violating the unique constraint. I rarely click on the More button more than once. I'll live with it for the time being. I hope GitHub fixes the sort order soon. |
Beta Was this translation helpful? Give feedback.
-
|
I did one more update to keep the vertical scrollbar almost at the same position, when clicking on the More button. I noticed that the More button started to appear again and worked more times until reaching activities two months old. It's probably luck. Manipulating DOM contents outside of the client components is a lottery... |
Beta Was this translation helpful? Give feedback.
-
|
Don't delete the script, let it remain for the future... |
Beta Was this translation helpful? Give feedback.
-
|
Don't jinx it, it might happen again :-) |
Beta Was this translation helpful? Give feedback.
-
|
Please return the chronological feed from newest to oldest! |
Beta Was this translation helpful? Give feedback.
-
|
I hope the chronological sorting feed can get back ASAP. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like a bug that makes the feed unusable. Please revert the changes and fix it. |
Beta Was this translation helpful? Give feedback.
-
|
looks like it's been fixed today |
Beta Was this translation helpful? Give feedback.
-
|
Yes, so sorry to everyone about that -- we had a bit of a jam in the queue when trying to push the fix on the team. However, yesterday our team member was able to push this fix. Thank you for being understanding as we work to bring the entirety of the sorting back to chronological sorting. Also, very much appreciate everyone's quick responses to help us stay on top of the fix! |
Beta Was this translation helpful? Give feedback.
-
|
My feed is now in showing latest at the top. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for implementing this! |
Beta Was this translation helpful? Give feedback.
-
|
Now everything is fine. It's strange that it took 3-4 days to fix this "bug" :-/ |
Beta Was this translation helpful? Give feedback.
-
|
Yes, we are very sorry for the long timeline. There was a jam in the queue to push the fix but we prioritized it to go out at the earliest possible window, which was Sunday, 12/8. We do appreciate your patience and understanding, truly. |
Beta Was this translation helpful? Give feedback.
-
|
Absolutely I'm going to keep it.
…On Sun, Dec 8, 2024, 1:09 PM Spuner ***@***.***> wrote:
Don't delete the script, let it remain for the future...
—
Reply to this email directly, view it on GitHub
<#141611 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF336MMGFBBV4QJLVYGX65D2ESYPFAVCNFSM6AAAAABQALGGGGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNJQGE4DOMY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
It seems the bug has been fixed, Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Yesterday it was fixed... I'm back today and here it is again Edit: fixed now, but at the time I posted it wasn't (of course I loaded the page from source). |
Beta Was this translation helpful? Give feedback.
-
|
I did not see it fixed yesterday. For me it got fixed in last few hours. |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, We are still on track to launch the reversion to purely chronological sorting with an anticipated launch of early next calendar year, after more rigorous testing of the different event types and gatherers that currently populate the feed. We know that this is some time away and that this has been a much anticipated change from the community, but there are other dependencies on the different parts that power the Feed modules that we need to address before going fully live. The Feed has certain algorithmic components that we have to remove as we transition onto more performative infrastructure so it's just taking a little longer than we anticipated originally. We at least wanted to be share a firmer date of when this will be released to all users, with many of your constructive comments above helping us to prioritize internally. We appreciate your understanding and support, and will update you when we are live, if you don't beat us to seeing it live first! ❤️ |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the update @aspeckofdustin, looking forward to it. |
Beta Was this translation helpful? Give feedback.
-
|
Thank You of course for your efforts, but at the moment - Feed is useless, since new releases are not shown in Feed. |
Beta Was this translation helpful? Give feedback.
-
|
So, is there a way for us to use the new feed now? The current feed causes me to miss a lot of information every day.😂 |
Beta Was this translation helpful? Give feedback.
-
@Spuner - We tried to experiment with a migration that would improve the load times over the holidays. I wanted to check in now and see if after a few days whether your feed shows any release activity, where you're not seeing recent releases? Or are you not seeing release activity at all in your feed? |
Beta Was this translation helpful? Give feedback.
-
|
@aspeckofdustin, my feed started showing some release activities over the holidays. Some items are missing, so I have been complementing the information from my feed with the solution provided by @KieranP . |
Beta Was this translation helpful? Give feedback.
-
|
Until Github fixes this critically broken part of their app, for those who are growing weary of not being able to keep up with recent releases for starred repositories, I have created a service that does just that. It is available here: https://kieranp.github.io/Github-Releases-Feed/ The service is open sourced under GPLv3 here: https://github.com/KieranP/Github-Releases-Feed Hope this is useful to others. If you find it useful, I feel free to star the repo :-) |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
and others
Hi there,
We are still on track to launch the reversion to purely chronological sorting with an anticipated launch of early next calendar year, after more rigorous testing of the different event types and gatherers that currently populate the feed. We know that this is some time away and that this has been a much anticipated change from the community, but there are other dependencies on the different parts that power the Feed modules that we need to address before going fully live. The Feed has certain algorithmic components that we have to remove as we transition onto more performative infrastructure so it's just taking a little longer than we anticipated originally. We at least wanted t…