UI: Search bar & filters in WireGuard

[ignoramous]

What about sorting wireguard profiles into groups?
Like by country?
Or city ?
A search bar to find specific configs on the wireguard tabs?

Originally posted by @jason-eu in #1524

May be implementing just the search bar & favourite (⭐) instead of "groups" will do.

Country & city may be deducible for imported profiles with a geoip lookup.

[jason-eu]

TL:DR at the bottom.

THANK YOU SO MUCH FOR RESPONDING.

I was supposing before but I'll try to explain myself better. I hope I don't confuse my intent.

I meant groups in the sense of a way to tag/organise certain configs by country/city.
So that the user can select their desired country/city group as needed.

Favourites and earch can be excellent here because you can just search 2 or 3 letters, depending on config file naming system, and pull up a city group or country group.
Starring your favorites to the top of the list as necessary.

I'm assuming though, that THAT assumes, however, some logic on RethinkDNS' part to select a config based on ping latency, server load or something similar.

In that scenario, let's say you live in Europe so you only want to add configs relating to your current country and maybe some nearby ones.
You'll end up with quite a long list of configurations, and if you pulled configs as IP's instead of hostnames, you're likely to find quite a few duds.

Which I am not even sure is something anyone should expect from RethinkDNS
(at least not at the moment, it seems more of a personal imagination desire than remotely in-scope but I absolutely don't know)
because I don't believe the server selection logic by load is even public for any VPN provider, ping/latency at best maybe but can't find anything for load.

I'm saying that because I know from experience, albeit a few months ago, NordVPN configs for example can be downloaded in a zip with thousands of configuration files, these are, IIRC, sorted for latency and/or load, depending on the script used to obtain the configs.
I've attached the output from a NordVPN server config generator from here ; https://nordgen.selfhoster.win/

NordVPN_All.zip

I think that should help with the context of why I mentioned groups, as that zip contains several thousand configs, and if you pick a few countries that you want, you can spend a lot of time scrolling because you can end up with quite a few configs.

Which can be achieved by a quick search or keyword search and favourites but what happens if that server is at capacity or offline or out of rotation for whatever reason?

The group suggestion was mainly to limit scrolling for what seems like forever, but allow you stay "within" the selection of a city/country.

TL:DR;

I assumed the eventuality of many config files.
Based on current wireguard config navigation, I extrapolated an increased difficulty in navigation to a desired config(s).

Multiple favourites, preferably no limit like only 20 or something, and a search functionality would be excellent.
This would eliminate the need for any "grouping", depending on number of configs.

PS.

I have no expectation that the development team would or should develop anything resembling a server sort by latency/load.
Especially not in a generic or provider specific way.

I think that if something like that were to be implemented, the BEST scenario would be to allow RethinkDNS to read configs from a user created/selected folder in the user/app accessible storage.

In which case, a disclaimer pop-up saying the user accepts their own risk of using config files with their PATs in plaintext/.conf should suffice.
(I am not even sure how much of an attack vector it is, but I can theorycraft in my head a scenario where a bad actor can modify a config to make you use a dodgy server for malicious intent but at that point, someone already has unencrypted access to the device anyway, so just let them dig in that horrific browser history)

This would allow users to obtain configurations, sorted by latency/load, on their own from something like a Terminal/Termux script, and drop it into the folder.
That way the dev team can focus on keeping RethinkDNS the best thing since sliced bread and the user can expend a little effort for their own goals.

That "TL:DR" seems cosmetic now.