At least 6 months, maybe even a year, I've had login issues to Twitter. Pre front page design change and post design change.

I know this is not the right forum for this but support desk is so overwhelmed and fundamentally broken I give up. (if you want to know why I say broken please ask, but I'm not submitting a ticket to the support desk about it :) )

Maybe I'm one of few that does not "remember me" when I login and that's why I see this every day.

On login, enter I user and pass, ~40% of the time I am logged in. The rest, I end up at /sessions with a server error. A refresh does not repost my login and pass, (I'm assuming headers are lost as a result of a redirect or JS posting) sometimes I'm logged in and can just drop /sessions from the URL, other times I am not.

In a short time of non use of the site, I am logged out. I have not quit my browser, and the cookie remains, with a session of no expire time, so it should live until I quit the browser. Never logged out during use, only on returning to the site from working elsewhere.

I see this in Safari, on multiple computers. I rarely use Firefox aside from development so I can not say if it is browser specific.

I reported it to the help desk, I just can't handle the auto generic emails asking me the most off topic questions. If I put the time into a bug report, which I have, with headers and return strings, I expect more than a 5 response back and forth about reading the FAQ.

I can repat this. It is seemingly random. It can be made worse by using a password manager, which can auto submit the user and pass. I suspect too quickly sending in data may have something to do with it. Or, the /sessions page freaks out and does not change the header to where it needs to go. I end up with a funky set of cookies which may explain my getting logged out randomly.

Any devs from Twitter care to look into this with me? If you also want to talk about the help desk, I'd be happy to point out why that is not a good way to treat users, whether they need general help or technical help.

Thanks. Not trying to sound bitchy, just being matter of fact. I tried the correct support channels, they are just too much work to prove it's not user error.
--
Scott
Iphone says hello.

Reply via email to