orithena
commented
7 years ago I'd like to have this feature, too.
I propose a caching table for this with the following columns: varchar user_id primary_key, varchar at_name, varchar name, timestamp added, smallint category
category could be 1 for "I follow", 2 for "Follows me", 3 for "I mentioned them", 4 for "appeared anywhere in my tabs".
This table would then be filled event-based, i.e. whenever Twidere receives user information, this info is thrown into the table, inserting or updating as needed (primary_key re-identifies the user and avoids duplicates, at_name and name may need to be updated, timestamp always needs to be updated, category may only be decreased).
Since a caching table has to be tidied up from time to time, the timestamp would make it possible to throw out the oldest entries, while we make sure to keep at least some of each category.
Something along these lines would help greatly finding the user I want to mention...
When I type "@" in Twidere, I get a list with some proposals of user names. When I type some letters after this, the list contains user names witch contains the letters I typed.
But the proposals are often not very good. Sometimes I got names of users I don't konw, but the name of the user I know, aren't in the list, although their names contains the typed letters. And sometimes I type a wohle name, that exists, but there is no proposal or the wrong. As I used he original Twitter app, the proposals were better there. I don't know how, but meybe they implemented a hierarchy (first the names of the people I follow, then my followers, in replys the user I reply to....).
Now I often have to know the exact name, because Twidere's proposals are not that good. It would be nice, if this can be impoved.