A semi-official update

This too shall pass. It is always darkest before dawn.

I would like to add that if you're complaining about TMB being down and have NEVER donated or donated like six bucks, I hope you die in a fire.

That's a firemen, who knows how awful that death is, and I wish it upon you.

IF the site gets back up, we better fill that bank up immediately.

What if you've donated like $50?

:ohdear:

I'll make the cutoff $49.99 -- soooooo close, but you made it. :heart:

I will use the Amazon portal more, I swear! I just forget sometimes!

I'll never neglect you again, TMB.  I swear! Just come back to me!

Link to fritter account?

it's not like they're updating the twitter account.

Link to TMB Tinder pls

From a person known as "Brad Layne" on Facebook:

"Here's where we're at guys, long and nerdy, but basically our old servers had a vulnerability related to our three internal server trees. This stemmed from a serious vulnerability in the popular OpenSSL cryptographic software library. This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure our information (though not particularly valuable unless you didn't back up the Fappening).
Essentially it allows anyone on the Internet to read the memory of the systems protected by the vulnerable versions of the OpenSSL software. This compromises the secret keys used to identify the service providers and to encrypt the traffic, the names and passwords of the users and the actual content. This allows attackers to eavesdrop on communications, steal data directly from the services and users and to impersonate services and users. And that's what someone, but not Wonald!, did. Vulnerabilities in single software or library come and go and are fixed by new versions. However this "bug" has left large amount of private keys and other information exposed. Considering the long exposure we have to start with a completely new system because compromised security keys allow the attacker to decrypt any past and future traffic to the protected services and to impersonate the service at will. Allowing them to do this again and again. Any protection given by the encryption and the signatures in the X.509 certificates can be bypassed. Recovery from this leak requires patching the vulnerability, revocation of the compromised keys and reissuing and redistributing new keys. Even doing all this will still leave any traffic intercepted by the attacker in the past still vulnerable to decryption. So that's why we're starting from scratch. All this has to be done by the owners of the services and they're eight stories tall and crustaceans from the paleozoic era. They're gonna need about tree fiddy."

Cliffs?

Cliffs of cliffs: we got hacked, no timeline for return

I understood some of those words

Are you Ashley from Facebook