Always good to have a wide variety of escrows available, to cover different time zones, peoples preferences and expertises. I'm also like you though, I only offer my services when requested and have only expressed interest a few times. I just don't like the idea of conducting multiple deals with potentially large amount of Bitcoin/entities at the same time.

Even the small amount of escrows which I have provided, they do take a lot of time up and normally take more than a day to complete due to some of the reasons stated above.

https://bitcointalk.org/index.php?action=trust (You can locate this page on anyones trust page its called "trust settings")

Add the names into the field there. However, anyone without the users in their trust list will not see your trust as green.

SMF's allows the option to use a custom index, which works by taking a hash of every word and building an index of where those words point to what threads/posts. It will take some time to rebuild the index. Indexing provides better performance if anyone is wondering why the forum takes this approach.

This would almost be redundant in the new forum software. According to the current requirements the new forum software will support 2 factor authentication with PGP and Bitcoin signature. Although, it seems you are wanting to do away with passwords altogether, I think it's better to have 2 factor along with a password.

If you want to go ahead developing something for the current forum, you would need to get into contact with theymos and discuss the matter further before proceeding.

I'm not sure if it would of stored it in your drafts  but, it's probably worth a shot. I know it saves it when you preview or post, but not sure of an attempted post.

Minimum of 1 post per term, which is every 14 days. However, your activity cannot be greater than your posts.

The dates of each term: https://docs.google.com/spreadsheets/d/12saLhlUoqIdairxzuSPu6EYGrt7FN2lOstO1yDjCEbA

It would be too controversial to ban scammer accounts, the staff would be accused of abusing powers even more than they already do. This is why the trust system was implemented and it's unlikely that anyone would trade with that account or any others like it.

Hang on a second. You want a Bitcoin loan, but you also are offering Bitcoin as collateral?

Some keyloggers can read the information in your clipboard. If you want to reduce the effectiveness of some  of these keyloggers, you should probably opt in for using a password manager. Keepass has a Two Channel AutoType feature, which can avoid some problems with keyloggers, however not all. It's a much better approach than your current method.

Good news. Glad that it was dealt with so swiftly, well done Badbear, this could of gone a lot worse that it did. I've removed my negative trust. Welcome back Tomatocage.

Just as a precautionary, although I do believe he's simply just locked himself out, as I said in my original post.
He does seem concerned himself to issue the statement or at least as a precautionary himself:

EDIT: Seems the email is revealed on the account now, which I can't remember seeing that before.

Although, you've likely made a typo. I've issued a negative trust rating for the time being, warning people that you have been locked out and not to proceed to trade with the account until you have verified you have access. Unfortunately, I don't think people will take note of the feedback, due to myself not carrying any weight. I've included this thread as a reference, and I will remove the feedback when it's confirmed you have gained control again.

If you intend on running a 24/7 full node and helping the Bitcoin infrastructure, then you can always buy a dedicated hard drive for it. Otherwise, are you sure that you can't free up some space in your current hard drive? The blockchain is relatively small when you look at the current specifications that are being sold by computer manufacturers, e.g 1TB hard drives.  

It is possible to run a full node on the latest raspberry pi module, if you are interested in it. Although it would need a little tweaking as it's the bare minimum really. (of course you would still need to purchase something to store the blockchain on)

Being in Default trust isn't just about being trustworthy, but a mixture of things. One of them being good judgement.

By default Keepass is kept locally.

It might be due to the amount of people logging in after receiving the information about the hack. The requests aren't being completed quick enough. It's probably happening when there's a spike in people and the backlog is full and rejects any new requests. Adding more caching might be a solution.

I can't say I'm experiencing it as much as you claim though. Perhaps a few hours in between. Some users might never see it, it depends on the load on the server and where you are in the 'queue'.

Very unlikely.

No it's not possible. That feedback is to warn others that the member was a proven scammer before the transition to the current trust system. (Issued by a administrator controlled account)

Probably due to the fact that the site has sent out thousands of mails within a short period of time, due to the recent compromise.

It's possibly logged for any suspicious activity on your account. Although, it wouldn't be a major indicator, it would be a factor of multiple irregularities. Whatever the reason for it, only administrators can access this data.  So only theymos, Badbear and Stefan Thomas has/had access to this information, bar the recent compromise.