I restored all posts that were ever deleted from that thread:
https://bitcointalk.org/index.php?topic=774278.0

Unfortunately, I just realized that I don't have any way of distinguishing between posts that were deleted by the OP and posts that were deleted by posters. If you deleted your own post in that thread, you'll have to delete it again. Sorry if this is inconvenient for anyone. I'll think of some way of fixing this for the future. I also restored all posts deleted by moderators from that thread, but I can distinguish those, and I might clean them up if I have time later.

The people listed on DefaultTrust are something like moderators in charge of maintaining the default trust network (because I don't want to do it myself). A default trust depth of 2 is necessary to make that work:
- Depth 0: DefaultTrust
- Depth 1: "trust moderators"
- Depth 2: people in the default trust network

If you significantly modify your trust list, then a depth of 1 would probably be most appropriate. Depth 2 trusts people who are trusted by people who are trusted by people you trust, which in practice tends to be too much if you have your own trust list.

Some of the problems with the Trust system are caused by it not being a real web of trust. Trust spreads too far and too quickly. I know how to fix this, but it's difficult to implement, especially in an efficient way. This is on the requirements for the new forum software.

I agree that having things centralized like this is imperfect, but I don't know of any better solution. Making the default trust list blank would make the whole system nearly useless because it would take months for new users to notice that the feature exists and figure out how to use it. Perhaps after users reach a certain activity level the forum should make them define a trust list if they've ever posted in the sections that use Trust.


If you use DefaultTrust with depth 2, then ratings like those are bugs in the default trust network and you should post about it in Meta. Someone will be removed from the default trust network to fix it.

Sites usually don't get completely banned from Reddit. Submissions from soft-banned domains end up in the moderation queue and moderators can manually approve them. Most Reddit moderators never approve stuff like this, but /r/Bitcoin mods do. If you submit interesting articles to /r/Bitcoin, they might get approved by the moderators. I'm not sure why that "traditional banking is so annoying" article wasn't approved. Maybe your domain was actually hard-banned, though I've never seen that before. I'll look into it.

I agree that Reddit is often too heavy on banning users and domains. I think that this has a lot to do with the Reddit voting/moderation system just not working very well in general, and so the admins and moderators have to do all kinds of crazy/unfair/heavy-handed things just to make the site halfway usable. We've had to make a few concessions even in /r/Bitcoin, though I think that /r/Bitcoin is still one of the freest large subreddits.

You could check that the block is in the main chain by using getblock and ensuring that the number of confirmations is non-zero. You need to do something to handle reorgs, though; probably something like bitcoind's CBlockLocator.

walletnotify is also good.

His username is different. That's his display name, which has more relaxed rules. In 2011 you could change your display name freely.

Whoops. I fixed it.

New transactions will either be in new blocks or there will be a reorg and the block hash you give to listsinceblock will be outside of the main chain, causing listsinceblock to dump all of your transactions.

listtransactions loops through all wallet transactions (internally, in the implementation) no matter what arguments you give it.

Transactions aren't reordered within a single wallet, and new transactions are always added to the top, though transactions could be reordered if you move keys between wallets or use -zapwallettxes.


listtransactions loops through every transaction in your wallet, so it isn't very fast or scalable. It's better to use one of these:
- getreceivedbyaccount or getreceivedbyaddress
- -walletnotify + gettransaction
- listsinceblock

Keep in mind that the chain can reorg, which can cause confirmed transactions to have a different number of confirmations or even become invalid. You need to handle this, especially if you use walletnotify or listsinceblock. I know that they're limited and a bit confusing, but I usually recommend bitcoind accounts for small- to medium-size sites because it's very easy to do things correctly with them.

I'll add some more logging and see if I can pinpoint the problem. It's not a huge issue, but this error is really weird because it seems to occur when your browser sends a cookie that the forum has never set.


That's a different error than what I'm talking about.

What browsers are you guys using?


Did you also get it when you tried to do something while you were logged off?

Has anyone here seen this error?
I see in the logs that it happens pretty frequently, but I feel like it should never happen if you have a sane browser. I'm thinking that it may just be strange bots that get that error.

No, I haven't. I doubt that anyone in the Bitcoin ecosystem has knowingly met him in person. My impression has always been that he's a shy individual who created Bitcoin mainly because he found the project very interesting, not to become rich or famous. While he understood the need for a solid community, I doubt that he had (or has) much interest in participating in the Bitcoin community except to discuss the Bitcoin technology. And while he probably still cares about Bitcoin, I very much doubt that he has any desire to exert unusual control over Bitcoin's future, either secretly or publicly.

(In fact, there are very few Bitcoiners who have met me personally. None of the moderators or core devs have. So a meeting between Satoshi and myself would be especially unlikely.)


Mark never had anything to do with bitcoin.com, and bitcoin.com never had anything to do with Satoshi.

The emails are probably ending up in your spam folder. The forum's email tends to be automatically identified as spam.

Accuracy is always rounded down IIRC, so it'll take even longer.

People shouldn't worry about accuracy much, and certainly not single percentage points.

The system views negative ratings as saying, "this user scammed me and no one should trust him ever." People don't need to view negative ratings this way, and I don't think that it's dishonest to give someone negative trust even if you weren't scammed, but that's how the system views it. There probably should be a neutral or less strong negative rating type, but such a thing doesn't exist now. The best thing you can do at the moment to achieve that sort of effect is create another account that isn't trusted by anyone and use that.

With this in mind, I think that it is correct for someone to be labeled as high-risk if they receive many positive ratings for only one month and then they start getting scam accusations. This pattern is very common for scammers: build up your reputation with a few good trades and then start scamming people.

There's no easy way to see who's trusting a certain user, but it's possible to collect that info by adding every user to your trust list and then looking at the tree produced. The forum won't let you add a ridiculous number of users (and at some point it may time out when trying to display the tree, which will be difficult for you to fix), so you'd have to do it in batches.

The forum sells ad space in the area beneath the first post of every topic page. About 25% of ad income goes to the forum moderators as thanks for all of their work. (There are many moderators, so each moderator gets only a small amount -- moderators should be seen as volunteers, not employees.) The rest is stored in the forum's treasury (verifiably), where it sits until the forum needs it.

Ads are allowed to contain any non-annoying HTML/CSS style. No images, JavaScript, or animation (no marquee or blinking). Ads must appear 3 or fewer lines tall in my browser (Firefox, 700px wide). Ad text may not contain lies, misrepresentation, or inappropriate language. Ads may not link directly to any NSFW page. Ads may be rejected for other reasons, and I may remove ads even after they are accepted.

There are 10 total ad slots which are randomly rotated. So one ad slot has a one in ten chance of appearing. Eight of the slots are for sale here. Ads appear only on topic pages with more than one post, and only for people using the default theme.

The ad lasts at least 7 days starting from when I put it up. (However, if you look at the ad history you'll see that ads usually get at least 8 days, and sometimes as many as 10, but this is random and definitely not guaranteed.)

Stats

Exact historical impression counts per slot:
https://bitcointalk.org/adrotate.php?adstats

Info about the current ad slots:
https://bitcointalk.org/adrotate.php?adinfo

Ad blocking

Hero members, Donators, VIPs, and moderators have the ability to disable ads. I don't expect many people to use this option. These people don't increase the impression counts for your ads.

I try to bypass Adblock Plus filters as much as possible, though this is not guaranteed. It is difficult or impossible for ABP filters to block the ad space itself without blocking posts. However, filters can match against the URLs in your links, your CSS classes and style attributes, and the HTML structure of your ads.

To prevent matches against URLs: I have some JavaScript which fixes links blocked by ABP. You must tell me if you want this for your ads. When someone with ABP and JavaScript enabled views your ads, your links are changed to a special randomized bitcointalk.org URL which redirects to your site when visited. People without ABP are unaffected, even if they don't have JavaScript enabled. The downsides are:
- ABP users will see the redirection link when they hover over the link, even if they disable ABP for the forum.
- Getting referral stats might become even more difficult.
- Some users might get a warning when redirecting from https to http.

To prevent matching on CSS classes/styles: Don't use inline CSS. I can give your ad a CSS class that is randomized on each pageload, but you must request this.

To prevent matching against your HTML structure: Use only one <a> and no other tags if possible. If your ads get blocked because of matching done on something inside of your ad, you are responsible for noticing this and giving me new ad HTML.

Auction rules

Post your bids in this thread. Prices must be stated in BTC per slot. You must state the max number of slots you want. When the auction ends, the highest bidders will have their slots filled until all eight slots are filled.

I reserve the right to reject bids, even days after the bid is made. In particular, bids from people with less than 15 activity points are likely to be rejected. I recommend not getting into a bidding war with someone who has less than 15 activity points, as their bids might not be accepted, but your latest bids will still stand. If you need to know right away whether someone's bids will be accepted, PM me.

So if someone bids for 8 slots @ 5 BTC and this is the highest bid, then he'll get all 8 slots. If the two highest bids are 8 slots @ 4 BTC and 1 slot @ 5 BTC, then the first person will get 7 slots and the second person will get 1 slot.

The notation "2 @ 5" means 2 slots for 5 BTC each. Not 2 slots for 5 BTC total.

- When you post a bid, the bids in your previous posts are considered to be automatically canceled. You can put multiple bids in one post, however.
- All bid prices must be evenly divisible by 0.05.
- The bidding starts at 0.50.
- I will end the auction at an arbitrary time no more than 12 days from now. (I will probably end the auction 1-3 days before the ads are scheduled to go up.)
- If two people bid at the same price, the person who bid first will have his slots filled first.
- Bids are considered invalid and will be ignored if they do not specify both a price and a max quantity, or if they could not possibly win any slots

If these rules are confusing, look at some of the past forum ad auctions to see how it's done.

You must pay for your slots within 24 hours of receiving the payment address. Otherwise your slots may be sold to someone else. I will send you the payment information via forum PM from this account ("theymos", user ID 35). You might receive false payment information from scammers pretending to be me. They might even have somewhat similar usernames. Be careful.

Auction ended. Final result:
Slots BTC/Slot Person
1 3.10 sunxiaoxiao
4 3.05 MariaQin
1 3.05 incloudibly
1 3.00 UpDown.BT
1 2.90 Exmoney


You're too new. PM me first next time.

I don't know anything about this case. I take no position either way.

I added Beastlymac to my trust list some time ago because his sent ratings seemed non-controversial and I wanted some of them to be visible by default. Now some of his ratings are apparently controversial, so I removed him. If someone else in the default trust list wants to trust him, that'd be OK, but I haven't done business with Beastlymac, and I don't know much about him, so I'm not going to keep him in my personal trust list.