Quote from: knightdk on August 03, 2015, 09:59:06 PM

Update #4: Website now has https and will force all users to use https. http will automatically be redirected to https.

Update #3: Website has new tokening system and fixed queuing system

Quote from: knightdk on January 08, 2016, 03:14:49 AM

There is a new update to the project!!

I have released a new version on Github and also live on the website. This new version has improvements to the queue system so it doesn't fail as it used to.

There is now a tokening system for the queue. When you submit a lookup request you will receive a token. You can then leave the page and browse as you wish. You can return later and enter the token to see your results. The only caveat is that results are kept for only 24 hours after the request was submitted.

Update #2: Website is up at http://www.bctalkaccountpricer.info/

Quote from: knightdk on August 13, 2015, 02:09:32 AM

My website is up and usable at http://www.bctalkaccountpricer.info/

The site is very simple, just enter the User ID and it will do everything for you. There is a queuing system in place to prevent the server from being IP banned by Bitcointalk. The site will let you know where you are in the queue and will automatically retrieve all of the information when it is your turn.

There are a few notable differences between the website version and the version on github:

Ads - The website has ads to help me support the site. I did not include the code for the ads in the github
IP wait times - The website will require you to wait 5 minutes before it will let you submit another request. This is to prevent DoS attacks on the site. The Github contains the code for this, but it is commented out.
Account bot password - In order for the website to work, an account is required to view the trust of members. The Github has a placeholder password THAT DOES NOT WORK while the website has the correct password.

If you have issue with any of the above, please let me know and see if we can fix the problem.

If you find any bugs in the website, please contact me here or using the issue tracker on Github.

Update #1: The code is now available to browse, fork, and download at https://github.com/achow101/BitcointalkAccountPricer

Hello All,

Today I am announcing a project that I have been working on recently. This project is a price estimator for Bitcointalk Forum Accounts. The algorithm for determining prices is based on recent prices of accounts here.
The algorithm is as follow:

Code:

0.0003[btc]/activity
0.00015[btc]/epa (extra potential activity)

epa = potential activity - activity

bp (base price) = 0.0003 * activity + 0.00015 * epa

final price = bp * pqm * tm

pqm (post quality multiplier) determined by ratio of good posts (>75 characters excluding quoted text) to bad posts (<75 characters excluding quotes)
excellent post quality (90%) = 1.05 (+5%)
good (80%) = 1.025 (+2.5%)
fair (70%) = 1.00 (+0%)
poor (50%) = -1.025 (-2.5%)
very poor (<50%) = -1.05 (-5%)

tm (trust multiplier)
positive light green trust = 1.10 (+10%)
positive dark green trust = 1.20 (+20%)
neutral trust = 1.00 (+0%)
negative trust = -0.15 (-85%)

The code will be written in Java because I know Java the best. It will be open source and published on Github, but not yet as it is not completely finished. There will also be a website that has the java applet on the webpage for anyone to calculate the price of any Bitcointalk Account.

Please let me know what you guys think of this and if I should change the algorithm in any way.

Disclaimer: This project is not definitive nor an entirely accurate representation of an account's sell price. While I strive to be as accurate and close to current market prices as possible, actual prices may vary.

If this has been helpful to you or you would like to support this project, please donate to 16mT7jrpkjnJBD7a3TM2awyxHub58H6r6Z.

Edit: Algo adjustments

I am wondering how post quality is determined can you please provide the algo to check post quality. Because I want to write my post according to defined algorithm so that I don't have to fear of bad post quality