Aamazing !

Aamazing !

@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.

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.

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.

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.

@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.

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,
Dustin

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

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.

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

juststop fucking about with the homepage now got oldest results 1st and newst results last, WTF!

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.

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,
Dustin

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

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

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!

I confirm that I have the same experience.

yeah I want to see the latest post at the top

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 :(

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

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.

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

its the perfect dx we just dont get it

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

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

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

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.

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,
Dustin

It's OK, thanks for lengthy explanation, Dustin :)

Appreciate your interest in supporting the community and making sure that we stay communicative, though, @manio!

This is awesome, Thank you. Would love to see it persist on page refresh/reload. Great work.

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.

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...

Don't delete the script, let it remain for the future...

Don't jinx it, it might happen again :-)
Yes, I'll keep the script on GreasyFork.

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!

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.

I did not see it fixed yesterday. For me it got fixed in last few hours.