The relay should be kept simple enough, if the relay has too many operations it will be the beginning of a review. Content classification can add new Nips, and content guidance and community building should be handed over to the client.

The most important problem now is that the communication between the client and the relay is too slow and loses data, and needs to pull all the data every time. It is not like the traditional server client, which can make the user feel no sense of the network connection and can be used smoothly. If the client and relay can communicate and pull data optimization to seamless connection, it is a huge improvement in user experience. This is probably the most important issue for more ordinary people to use and join.

Reply to this note

Please Login to reply.

Discussion

Why is it slow? It is not, querying a relay for anything is usually absurdly fast.

Why isn't it like the traditional server-client? It definitely is. Servers generally serve the same data over and over to the same clients. twitter.com, for example.

I'm not sure if I'm the only one having these problems. I used all 19 relays for free. It is often encountered that only 4 or 5 relay can be successfully connected, resulting in the local post data is not the most complete, which may be the difference in the data stored by each relay. It will take several restarts to connect more relay successfully.

Every time I open the client, the client will pull all the data from the relay, which causes my 5G traffic data to be consumed very quickly. Traditional servers only need to pull the latest information, but not all information. For example, I consume less data when I use Twitter. In fact, the data of Nostr does not need to consider the modification of historical data, because it cannot be deleted. Can we consider only pulling the latest data each time we obtain data?

If the client is used for a long time, no post will be sent, and the relay network will be disconnected during the use. A reboot is often required.

In the same environment of Wi-Fi and 5G, sometimes there are more and sometimes fewer connected relays. If ordinary users only use a few free relay, posts, comments, zap and other data will be displayed incomplete, which will make users have a sense of anxiety about losing information. This is something traditional apps don't need to consider.

These are all the experience problems I have encountered. I don't know whether it is because of the connection and communication technology of relay. It is hoped that this part of the communication connection problem can be well solved, so that the client can bring better experience to ordinary users.

Each time you open the client, you need to wait for the connection to the relay. The client remains blank. Often, the relay connection fails, and the home page is blank. This is a very confusing problem for ordinary users who are used to traditional apps.