Repeater or Contacts sort by "recent" broken? #37

New Issue

2026-10-05T01:54:17+02:00

adam commented

2026-10-05 01:54:17 +02:00

Not sure when it broke (or if it ever worked), but clicking on the clock/A-Z in repeater or contacts doesn't seem to change anything -- it's always A-Z.
(Note: Channels sorting DOES work)

I'm 99% sure there was a brand new contact in the last few hours, so would have expected that contact to have bubbled to the top in a "sort by recent".

Environment:

commit bc16d804e (inside docker)
desktop browser (Chrome)

Oh, and you fixed the sort toggling changing both contacts+repeaters together. Yay!

Not sure when it broke (or if it ever worked), but clicking on the clock/A-Z in repeater or contacts doesn't seem to change anything -- it's always A-Z. (Note: Channels sorting DOES work) I'm 99% sure there was a brand new contact in the last few hours, so would have expected that contact to have bubbled to the top in a "sort by recent". Environment: * commit bc16d804e (inside docker) * desktop browser (Chrome) Oh, and you fixed the sort toggling changing both contacts+repeaters together. Yay!

adam closed this issue

2026-10-05 01:54:17 +02:00

adam commented

2026-10-05 01:54:18 +02:00

So this is by design, but maybe the design is not great. We always sort on last heard message -- after we sort by how recently a message was exchanged, we fall back to alphabetical, not on advert. My thinking was that contacts who you've DM'd should always be closer to the top than some random contact that just advert'd. Perhaps we should fall back to advert recency, not alphabetical, after we've done message sorting.

So this is by design, but maybe the design is not great. We always sort on last heard *message* -- after we sort by how recently a message was exchanged, we fall back to alphabetical, not on advert. My thinking was that contacts who you've DM'd should always be closer to the top than some random contact that just advert'd. Perhaps we should fall back to advert recency, not alphabetical, after we've done message sorting.

adam commented

2026-10-05 01:54:18 +02:00

Bugfix: sort on true last-heard (i.e. adverts) after message recency, instead of alphabetically.

Bugfix: sort on true last-heard (i.e. adverts) after message recency, instead of alphabetically.

adam commented

2026-10-05 01:54:19 +02:00

Ah, that makes sense for contacts! But does that make sense for repeaters?

Now I'm wondering if it's worth making it a 3-way mode for Contacts (DM recent; advert recent; A-Z)

Ah, that makes sense for contacts! But does that make sense for repeaters? Now I'm wondering if it's worth making it a 3-way mode for Contacts (DM recent; advert recent; A-Z)

adam commented

2026-10-05 01:54:20 +02:00

Well we would probably have very very few manual contacts we've never heard an advert for OR messaged, but yeah A-Z fallback if we have added a contact that we've never messaged and never heard an advert for is reasonable.

Well we would probably have very very few manual contacts we've never heard an advert for OR messaged, but yeah A-Z fallback if we have added a contact that we've never messaged and never heard an advert for is reasonable.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: adam/Remote-Terminal-for-MeshCore#37