You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
twtxt is the only client that has User-Agent: in its User-Agent string.
Oddly enough, users who GET my twtxt file from IPv6 addresses don't have User-Agent: in their User-Agent strings. There are at least two users like this and both of them say they're using twtxt/1.2.3.
There are also users connecting from IPv4 addresses that have declined to say who they are on the twtxtiverse. Those User-Agent strings also (properly) lack the duplicated User-Agent: .
I see lines like this in my web server's log:
twtxt is the only client that has
User-Agent:
in its User-Agent string.Oddly enough, users who GET my twtxt file from IPv6 addresses don't have
User-Agent:
in their User-Agent strings. There are at least two users like this and both of them say they're using twtxt/1.2.3.There are also users connecting from IPv4 addresses that have declined to say who they are on the twtxtiverse. Those User-Agent strings also (properly) lack the duplicated
User-Agent:
.I had a look at the current
generate_user_agent()
andget_remote_tweets()
but on a casual inspection I can't figure out what's causing this.The text was updated successfully, but these errors were encountered: