Username checks that prevent unnecessary loading errors

One of the easiest ways to avoid false errors is to simplify the input. If a public username works, use the username alone. If a direct post link works, use the clean post URL without extra query parameters from copied shares or mobile redirects.

This matters because minor formatting noise can send a lookup toward the wrong target or fail validation before any media request even begins. In those cases, the viewer is not really failing to load content; it is receiving the wrong identifier from the start.

A clean input step saves time for both users and support. If the normalized username or exact public post URL still fails after that, the report is much easier to interpret because basic input errors have already been ruled out.