Order of URL hex codes not reflected in table column

[shrewd python]

This might be a bit niche, but I’ve noticed that this week, the order in which aircraft are displayed no longer matches the order of hex codes specified in the URL. For example, when I use this URL:
https://globe.adsbexchange.com/?icao=ae048c,ae04e3,ae0427,ae5bc1
I used to see a table layout with the hex codes listed in this order: AE048C, AE04E3, AE0427, AE5BC1.

However, now they seem to appear in a random order. I’ve tested this on three different devices, and the order always appears as: AE5BC1, AE0427, AE048C, AE04E3.

Is there any way to fix this? I’m guessing it’s a setting I might have missed, but I would like the table to display the hex codes in the same order as they appear in the URL.

Any thoughts?

[old river]

Click on "Hex ID" (or any other column you want to sort by) in the table header?

[shrewd python]

Ive tried that and it just sorts ascending or descending alphabetically rather than the URL order - I also tried by the flag column which seems to have the same effect. I have a series of these URLS and was hopeful for a solution for all of them

[old river]

Oh, I see what you mean now. Yeah, it looks like that must've changed in the big merge of upstream tar1090 changes that happened recently

possibly https://github.com/wiedehopf/tar1090/commit/ac0303b6a143c0826a9e8d1e3c94e47d2e9e8f12

[old river]

There's https://github.com/wiedehopf/tar1090/commit/e35a3affb4ae64db80a8cf0b465f0592ad7400ea also - edit: that doesn't appear to change the logic, just fixes location-related stuff, I think

[shrewd python]

Thanks for the link, that certainly seems like a good candidate. My programming knowledge isn’t quite enough to fully understand what the linked code refers to, but from what I can tell, it seems to be related to the website storing the sorting order, which might overwrite the order in the URL. Not entirely sure though, is this the best page to raise the issue for a possible fix?

[old river]

There are two possibilities ... you could try to convince the upstream developer (wiedehopf) to address it, by opening a github issue on his repo... or you could try to convince the ADSBx developers to implement an ADSBx-only solution

[shrewd python]

Good call, the top part seems to limit to only the column headings for a sort index and as it isnt replacing anything from before that could be why

[shrewd python]

Thanks - what would be the best approach for contacting the ADSBx devs? will they pick up these messages?

[old river]

We can tag @jaunty steppe here

[shrewd python]

Thanks for your help, much appreciated. Hopefully the ADSBx team can impliment a fix and if not I will raise with the upstream developer and see where that goes

[shrewd python]

Good afternoon, wondered if there had been any progress on whether the ADSBx team are willing to impliment a fix for this issue? New to discord so unsure if the developer will see this post so I have tagged @jaunty steppe again as per the reccomendation above just incase not.

[scarlet wharf]

Dev will take a look but it is probably a change in the base tar1090 code, either way it’s not going to be a quick fix so please leave tagging Demetrio to mods, he is out of the office and won’t be back till later this week anyways.

[shrewd python]

Understood, thank you for clarification