But this isn’t a bug for either one:
- iNat’s website is working as designed.
- AT&T’s algorithm sees something suspicious in that activity—perhaps the number of redirects involved in getting a photo from AWS; perhaps the many levels of subdomains on AWS; perhaps something else.
- From AT&T’s standpoint, the system is working as designed. The user must decide whether AWS is trustworthy in spite of that suspicious behavior.
- From the standpoint of the customers of AT&T, the problem is an app that produces cryptic status messages that have only the weakest of connections to the solution to their problem. (Even the more tech savvy among us are stymied because the most straightforward way to deal with it—the path that definitely should work—is a dead end.)
In this thread we have two crystal-clear presentations of the answer—better support than AT&T itself is providing on this topic. Here’s what I think we need to do:
- Retitle the thread, now that we know the real problem: Creative Commons–licensed photos not loading on AT&T wifi
- Edit the original post to point to the answers.
- Close the topic.
Otherwise, we are liable to get all kinds of new comments offering well-intended advice that is actually just another false lead—and anyone who is still having this problem and doesn’t realize that a solution has been worked out might try following the latest tip rather than dig deep into what must seem to be a pile of other things that didn’t work.