2025-01-02, 05:03 AM
> Also, you're putting "http://" before the IP
I....was not. But now it works that I've added it. I feel really dumb that I didn't think this. My train of thought was "Oh, I don't need a URL. I have the IP and port". I wonder how many people make this same mistake.
I would humbly suggest:
1. Include some kind of copy on the connection screen that suggests users should include 'http://' even if they are manually specifying their IP.
2. A step in the connection flow that checks and prepends 'http://' to whatever users enter if their connection is unsuccessful (or if they ignore (1) and only enter an IP)
3. Attempt to include 'http://' if making a connection with a discovered local sever.
#3 is especially surprising. It seems like low hanging fruit to fix this especially if the app is able to discover there is a server running on the local network.
Time now to troubleshoot why sound is not coming through on certain videos...but that is the subject for another thread
I....was not. But now it works that I've added it. I feel really dumb that I didn't think this. My train of thought was "Oh, I don't need a URL. I have the IP and port". I wonder how many people make this same mistake.
I would humbly suggest:
1. Include some kind of copy on the connection screen that suggests users should include 'http://' even if they are manually specifying their IP.
2. A step in the connection flow that checks and prepends 'http://' to whatever users enter if their connection is unsuccessful (or if they ignore (1) and only enter an IP)
3. Attempt to include 'http://' if making a connection with a discovered local sever.
#3 is especially surprising. It seems like low hanging fruit to fix this especially if the app is able to discover there is a server running on the local network.
Time now to troubleshoot why sound is not coming through on certain videos...but that is the subject for another thread