Forum Replies Created
Yes, there was a DDOS earlier which took out half the Internet. They’re still trying to sort it out, but it should be back to normal soon, hopefully.Posted 5 years ago | Go to post
We’re looking into the password issue, which happens not every time but in particular circumstances.
a) ensure your email address is correct
b) check your spam folder for the email from us
c) log out and clear your stw cookies.
This link will log you out and clear your stw cookies:
Users with an email address of invalid_email_address@stw – this indicates that the last one was removed for one reason or another.Posted 5 years ago | Go to post
Yes, the latter – rekeyed, revoked, reissued. The key is new. I’ll show you the old one one day 🙂 The new key tackles the threat of decryption of future SSL traffic. If someone had exploited this bug in the past, and been lucky enough to capture our old private key, they may have been able to spoof our site and decrypt SSL traffic to it until a couple of days ago, if they could have intercepted traffic to it and been bothered. I have seen no sign of it happening, but it is no longer an increased risk.Posted 5 years ago | Go to post
Reply to: Singletrack vulnerable to heartbleed
There is some useful information about certificate issue dates here:
Our Digicert cert has been revoked, rekeyed, and reissued, retaining the original date. There are some other high profile sites who were previously vulnerable, and must surely have revoked and rekeyed, but have retained old issue dates. Lastpass.eu and stackoverflow for example.Posted 5 years ago | Go to post
Reply to: Singletrack vulnerable to heartbleed
Yes, quite a bug. We do not process credit cards or bank details on our servers, so they will not have been exposed. We also limit other data stored on them. It is possible that passwords entered over the last day may have been exposed. We recommend regularly changing your password, and not using the same password on this site as you do on others.Posted 5 years ago | Go to post
Reply to: 500 internal server error – just me ?
Apologies for last night’s 500s. I was swapping servers and DNS over the weekend. I thought I had got away with no one noticing but a new server obviously needed a bit more configuring, which has since been done. We are now fully upgraded. You should not get any 500 errors unless you’re doing something extreme, but if you do please feel free to report them.
tom@oldserver:~$ uptimePosted 6 years ago | Go to post
13:58:42 up 1013 days, 20:57, 1 user, load average: 0.00, 0.00, 0.00
Reply to: Share
Everything OK? Try not to get too cute with nested attributes. But why would you do that anyway? And it took less than one day, one thread, and 10 or so minutes, after either Patrick or I were made aware of the feature. No one seems to have filed a bug report. In fact, it appears, nothing was broken; it was a feature 🙂Posted 6 years ago | Go to post
Please try the lost password link at Pocketmags and check your email:Posted 6 years ago | Go to post
OK, youtu.be works. You can now also say [ youtube]9udxbvHiqGw[/youtube]
[youtube]9udxbvHiqGw[/youtube]Posted 6 years ago | Go to post
I’ll probably combine it into one and go for the \3. Just one domain was it?Posted 6 years ago | Go to post
simply replaces “youtu.be/” with “www.youtube.com/watch?v=”
I invite you to do it yourself, as it is Wednesday afternoon 😉
Posted 6 years ago | Go to post
I suspect people would describe such a thing as a database compromise. I’ll spare you the details, but it was an automated attack on the website looking for vulnerabilities over an extended period of time. The worst we lost was the contents of your average user table. We were in touch with him before he posted it to the other place, and the **** posted it anyway. I should stress we do not condone retaliation. However I would say the particular group concerned were sitting ducks with plenty of enemies. I also did have a word with some people. Quite a few people had words with some people 😉Posted 6 years ago | Go to post
Jack, as I seem to recall. Jack W.
You’re not forgotten Jack 😉Posted 6 years ago | Go to post
I can confirm thePosted 6 years ago | Go to post
twothree expected saddles in this thread are currently in Jiffy bags not 12 feet from where I’m standing, waiting for today’s post. They should be with you soon.
Bounce rate has increased by 7% over this time last year.
That’s not bad at all, I’d have expected it to be higher.Posted 7 years ago | Go to post
I think Mark might mean 7 percentage points, which is an increase of about 14%
Would you be amenable to telling us what it was, out of curiosity?
As you can imagine there’s a count used by the pagination which would sometimes not represent the proper count. You might think that was because of some deletions not updating the count but that is not obviously the case. In fact there could be many weird and wonderful reasons for the count being off. The relatively straightforward solution is to not worry too much about the primary cause of the miscount right now, but just to make sure the number is correct. It doesn’t remove the glitch, and you may occasionally spot an occasion where the count is off for some reason and the pagination goes weird, but the count will get regularly checked and updated and the problems will not persist as they did.Posted 7 years ago | Go to post
clubber » it’s where posts have been deleted from a thread but presumably somewhere they’re not taken off a post count figure which is used to determine the pages or which posts appear on a page.
Good guess, and not far off – there are/were no deleted posts in the affected threads I’ve looked at. However a count was off for another reason. Both the threads mentioned above should be back to OK. I’ll check for others in the near future.Posted 7 years ago | Go to post