Live Nation is one of these sites - It took them about a year to actually write the website well enough for the unsubscribe links in their uninvited
Looking at my email inbox it seems that I started getting infomailsTM some time around Xmas so I tried to log in or reset my password - either way to find out what City Socializer is and why I would have joined up.
Every time I opened the link location to reset from the password request generated email I get an "invalid token" error message, so I message support and note it. So a couple of weeks later they get back to me and ask the usual questions about what device, what browser and what planet I was on at the time and then is a later email send me a note: They've reset my password to [incredibly-easy-to-guess-password-obfuscated] - let them know if there's any more problems.
Huh. So I email them a query and they reset my password, then send me it in plain text in an email? Good thing I wasn't on a public network and was VPN-ed in eh? But that's ok - under the same conditions a link in an email is just as catch-able (along with the headers such as recipient). It was nice enough of them to do that for me with minimal verification. Note to ppl@CS: If you're going to help people out like that please get a random password generator to prevent socially engineered resets working. For now you'll just have to trust me that with some very cheap equipment it's incredibly easy to capture some very interesting information.
Ok so I'm in and rooting around the website (if you're reading this ppl@CS this is free consultancy btw) and noticing little things - like when I click on the wee profile icon I get a 404. When I log in it takes forever with no feedback. The "Getting started" screen sits there and spins. Not the most exciting social media experience.
Nope. Tried Chrome, Aviator and IE - all have relatively normal browser settings for a test session but each time log in takes between 30 seconds and two minutes. Something definitely isn't right - Time for a debug window (what the developers should have done before submitting any code into source)....and the answer is immediately obvious. For demo purposes I've screenshot-ed the IE11 dev tools but the same symptoms and exception detail are just as obvious in Chrome or Firefox.
|A whole stack (ha ha) of answers to a very simple problem|
Here's the team at CS on Instagram. Maybe their new-ish CTO is in the process of fine tuning some aspects of delivery. Hope it works out for them.