[TOOL] ⭐Bitcointalk BRDb score

[*Ace*]

I am thrilled to inform everyone that as of tonight, BRDB has officially restarted its operations. A VPS has been purchased, fully configured, and is now running smoothly. The scraping engine is active again, and data collection has resumed without interruption. This marks a major turning point for the entire project after a period of uncertainty. A huge shout‑out to Mitchell — his donation made this entire step possible. I honestly could not have done this without his help. I also want to thank every single one of you for your patience and support during the downtime. This is only the beginning, and I look forward to sharing more updates soon. Thank you all for your attention.

[fillippone]

Well done, *Ace* and Mitchell.
This is the beauty of this community: you take, learn and absorb, then you give, and the community responds.
I can't wait to see how the project will grow in the next year!

[Lillominato89]

Well done, my friend – I’m delighted for you that you’ve picked up the project again.
I realise that working on it alone is a bit tricky – juggling everything, work, your personal life and leisure.
So my advice is to take as much time as you need to make all the improvements your project requires.
The end result will be all the more rewarding afterwards

[DYING_S0UL]

I am thrilled to inform everyone that as of tonight, BRDB has officially restarted its operations. A VPS has been purchased, fully configured, and is now running smoothly. The scraping engine is active again, and data collection has resumed without interruption. This marks a major turning point for the entire project after a period of uncertainty. A huge shout‑out to Mitchell — his donation made this entire step possible. I honestly could not have done this without his help. I also want to thank every single one of you for your patience and support during the downtime. This is only the beginning, and I look forward to sharing more updates soon. Thank you all for your attention.

Good Job my friend! I can confirm the Scores are back online now. Yours seems to dropping and mine is stuck as always, lol. Anyway, it's good to have you and your tool back! Now don't forget to fix that bug I previously reported.

Also, as per my words, I have sent you some sats, it's not much really, but it's enough to give you another 4 months worth of VPS. Enjoy!

https://www.blockchain.com/explorer/transactions/btc/04e7339d2465d6af487b81c48bd9ad94169db72438f4ddc4573be4ef11aeb11e

[*Ace*]

I am thrilled to inform everyone that as of tonight, BRDB has officially restarted its operations. A VPS has been purchased, fully configured, and is now running smoothly. The scraping engine is active again, and data collection has resumed without interruption. This marks a major turning point for the entire project after a period of uncertainty. A huge shout‑out to Mitchell — his donation made this entire step possible. I honestly could not have done this without his help. I also want to thank every single one of you for your patience and support during the downtime. This is only the beginning, and I look forward to sharing more updates soon. Thank you all for your attention.

Good Job my friend! I can confirm the Scores are back online now. Yours seems to dropping and mine is stuck as always, lol. Anyway, it's good to have you and your tool back! Now don't forget to fix that bug I previously reported.

Also, as per my words, I have sent you some sats, it's not much really, but it's enough to give you another 4 months worth of VPS. Enjoy!

https://www.blockchain.com/explorer/transactions/btc/04e7339d2465d6af487b81c48bd9ad94169db72438f4ddc4573be4ef11aeb11e

Thank you so much friend, thank you for supporting this project
The bug you reported will be fixed soon, unfortunately I'm running out of time.
The priority was to restart the tool, now it's online but it needs to be fixed.

Edit Fixed the bug you reported, you can update to the new version 0.21.1
https://update.greasyfork.org/scripts/562627/Bitcointalk%20BRDb%20Score.user.js

In the meantime, I'm sharing the report of what the scraper has collected in these first 24 hours.

📊 BRDb SCRAPER - DETAILED REPORT
August 08, 2026 - 06:36:11 UTC

📌 EXECUTIVE SUMMARY

⏱️ Runtime: 1d 9h 44m	🔄 Total cycles: 12659
📊 Success rate: 91.2% (46208/50636 ops)	📝 Posts saved: 2834
⭐ Merits saved: 624	👥 Users processed: 245600
🔧 Records fixed: 337

📈 DETAILED SCRAPING STATISTICS

📝 POSTS

• Total saved: 2834
• Average per cycle: 0.44
• Min per cycle: 0
• Max per cycle: 60
• Last 100 cycles: 22
• Last 50 cycles: 12
• Last 10 cycles: 3

⭐ MERITS

• Total saved: 624
• Average per cycle: 0.09
• Min per cycle: 0
• Max per cycle: 90
• Last 100 cycles: 4
• Last 50 cycles: 1
• Last 10 cycles: 0

👥 USERS

• Total processed: 245600
• Average per cycle: 19.40
• Min per cycle: 0
• Max per cycle: 20
• Last 100 cycles: 2000
• Last 50 cycles: 1000
• Last 10 cycles: 200

🔧 FIX-NULL

• Total records fixed: 337

⚡ PERFORMANCE METRICS

🔄 CYCLE DURATION

• Average: 17.97s
• Min: 3s
• Max: 81s
• Last 10 avg: 21.90s

🌐 HTTP STATUS BREAKDOWN

• 200 OK: 46208
• 503 Service Unavailable: 4006
• 500 Internal Server Error: 295
• 404 Not Found: 127

🎯 SUCCESS RATE BY COMPONENT

• 📝 Posts: 62.4% (3954/6329)
• ⭐ Merits: 69.6% (4410/6329)
• 👥 Users: 97.9% (6197/6329)

📡 API STATUS (Live Data)

⭐ MERIT API

• Total merits in DB: 10166
• Null to_uid: 0

📝 POST API

• Total posts in DB: 246016

👥 QUEUE API

• Users in queue: 0 / 21519
• Scraped in 24h: 21519
• Never scraped: 0
• Stuck in progress: 0

📈 SPEED & TRENDS

🚀 AVERAGE SPEED (per hour)

• Posts: 83/h
• Merits: 18/h
• Users: 7279/h
• Cycles: 375/h

🚀 AVERAGE SPEED (per day)

• Posts: 2024/day
• Merits: 445/day
• Users: 175428/day

⚠️ RECENT ERRORS (last 10)

• ✗ [06:32:05] HTTP 503
• ✗ [06:32:27] HTTP 503
• ✗ [06:32:31] HTTP 503
• ✗ [06:33:01] HTTP 503
• ✗ [06:33:10] HTTP 503
• ✗ [06:33:37] HTTP 503
• ✗ [06:34:25] HTTP 503
• ✗ [06:34:37] HTTP 503
• ✗ [06:34:39] HTTP 503
• ✗ [06:35:29] HTTP 503

🖥️ SERVER STATUS

📊 CPU

• Cores: 1
• Load 1m: 0.82

💾 MEMORY

• Total: 956Mi
• Used: 215Mi (22.5%)
• Free: 176Mi

💿 DISK

• Total: 14G
• Used: 2.9G (22%)
• Free: 11G

✅ Report generated on August 08, 2026 at 06:36:12 UTC
🔄 Scraper is running 24/7
📊 Data source: BRDb Scraper API

📌 BRDb – Status Update

Over the last 24 hours, the project has been restarted and a UI bug affecting thread-list pages (e.g., action=profile;threads;u=xxx;sa=showPosts) has been fixed in version 0.21.1.

The score now appears correctly both in profile pages and topic threads.

• Scraper Improvements – The scraping engine is being reviewed to increase reliability, handle rate limits, and avoid parsing failures
  
  
• Data Consistency – Some values (e.g., recent merit ratios, 120‑day statistics, impact scores) are being recalculated and cross‑checked against actual user data to ensure they reflect reality.
  
  
• Clean‑up – Outliers and inconsistent records (BRDb >10, wrong statuses, duplicated local boards) will be corrected or removed.
  

🚀 Full deployment is expected within the next few days.

If you notice any anomalies in your BRDb score or status, feel free to report them in this thread – your feedback helps improve the system.

This report was created using deepseek AI

[Lillominato89]

So, are you back on track, my friend?
I’m glad you haven’t given up on your project; I hope it brings you plenty of satisfaction along the way.

I’ve read the report! Why are there so many scraping errors? Too many requests in quick succession?
4,500 errors in 24 hours seems like a lot to me

[*Ace*]

So, are you back on track, my friend?
I’m glad you haven’t given up on your project; I hope it brings you plenty of satisfaction along the way.

I’ve read the report! Why are there so many scraping errors? Too many requests in quick succession?
4,500 errors in 24 hours seems like a lot to me

I never considered abandoning the project, I simply looked for solutions that would make the project better and that cost little; if they were free, it would have been even better.
As for the errors, I can agree with you, evidently I make too many requests in quick succession, considering that a complete cycle lasts about 40 seconds making various calls.
I'll slowly fix this one too! The important thing is that despite the errors, the data is still collected and stored.

[Lillominato89]

So, are you back on track, my friend?
I’m glad you haven’t given up on your project; I hope it brings you plenty of satisfaction along the way.

I’ve read the report! Why are there so many scraping errors? Too many requests in quick succession?
4,500 errors in 24 hours seems like a lot to me

I never considered abandoning the project, I simply looked for solutions that would make the project better and that cost little; if they were free, it would have been even better.
As for the errors, I can agree with you, evidently I make too many requests in quick succession, considering that a complete cycle lasts about 40 seconds making various calls.
I'll slowly fix this one too! The important thing is that despite the errors, the data is still collected and stored.

I’m pleased to read your words.
So I wish you all the best for yourself and your project.
I can’t wait to see the improvements you’ll make; take your time and don’t rush – nobody here is in a hurry. As the old Italian saying goes, ‘slow and steady wins the race’.

[DYING_S0UL]

Hey *Ace*...the core stats are all messed up, specifically the stats related to merits, and even some of the other field data are completely missing or isn't matching.
You might wanna rescrape the entire merit data, otherwise the overall scores  are gonne be calculated incorrectly.

This is what it looks like (according to BPIP).


And this is what your stats show now (wrong data of 120 days)


And these are the missing fields (no sent, receive, ratio)

[*Ace*]

Hey *Ace*...the core stats are all messed up, specifically the stats related to merits, and even some of the other field data are completely missing or isn't matching.
You might wanna rescrape the entire merit data, otherwise the overall scores  are gonne be calculated incorrectly.

This is what it looks like (according to BPIP).


And this is what your stats show now (wrong data of 120 days)


And these are the missing fields (no sent, receive, ratio)

Hi friend, I already know about this problem, but I no longer have the data from bitlist. So the data is incorrect because it only uses the data from my database.
It will take some time for the data to line up, but I was considering using the loucev site to get the Merit data.
But this will mess up the score because I don't have all the posts stored in the database. I'm working on it though!

[dkbit98]

It is good to see BRDb score project is updated and working again.
I will test it in next few days and report any issues if I notice them.

If you notice any anomalies in your BRDb score or status, feel free to report them in this thread – your feedback helps improve the system.

Have you considered using Claude AI to try and find any other potential bugs in the code, or make improvements?
I am not supporting use of AI for everything, but I saw Claude manage to fix things in many crypto projects.

[*Ace*]

It is good to see BRDb score project is updated and working again.
I will test it in next few days and report any issues if I notice them.

If you notice any anomalies in your BRDb score or status, feel free to report them in this thread – your feedback helps improve the system.

Have you considered using Claude AI to try and find any other potential bugs in the code, or make improvements?
I am not supporting use of AI for everything, but I saw Claude manage to fix things in many crypto projects.

You’ll find loads and loads of bugs 
I worked on BRDB all night today, but I didn’t manage to sort out much. I’ve completely removed every reference to BitList, as I’m no longer using the BitList APIs.
I tried scraping the profiles with my scraper but something’s gone wrong; I’ll have another go tomorrow if I’ve got time.
I don’t use Claude, but I’m using Qwen Coder for help and I’d say I’m getting good results

[Lillominato89]

So now all the data we’re seeing comes exclusively from your scraper?
Even though this data obviously doesn’t reflect the actual statistics for each user, I’d say it’s already a huge step forward for your project.
Keep it up and you’ll reap the rewards later on

[dkbit98]

You’ll find loads and loads of bugs 
I worked on BRDB all night today, but I didn’t manage to sort out much. I’ve completely removed every reference to BitList, as I’m no longer using the BitList APIs.
I tried scraping the profiles with my scraper but something’s gone wrong; I’ll have another go tomorrow if I’ve got time.
I don’t use Claude, but I’m using Qwen Coder for help and I’d say I’m getting good results

I am not using any AI toold for coding so they are all the same for me 
Problem with them fixing bugs is that they are creating new bugs in the process, this is what I heard from some developers recently.
Be careful, and never really or fully trust any of this tools.

[DYING_S0UL]

You’ll find loads and loads of bugs 
I worked on BRDB all night today, but I didn’t manage to sort out much. I’ve completely removed every reference to BitList, as I’m no longer using the BitList APIs.
I tried scraping the profiles with my scraper but something’s gone wrong; I’ll have another go tomorrow if I’ve got time.
I don’t use Claude, but I’m using Qwen Coder for help and I’d say I’m getting good results

I am not using any AI toold for coding so they are all the same for me 
Problem with them fixing bugs is that they are creating new bugs in the process, this is what I heard from some developers recently.
Be careful, and never really or fully trust any of this tools.

Man, this is so true! 
Previously, when I made a simple expense manager app using Codex, the same thing happened with me. There were like hundreds of errors/bugs.
One time the UI is messed up, one time the login button wouldn't work, another time the whole calculation logics breaks down.
Every time I fixed one bug, two more would take it's place! So, it took me more than 30-40 builds/versions before I could have perfected my app.
AI tools are really powerful that I admit, but what experience told me is that when you start using one you need to hand feed him everything.
Do this, do that, be careful not to touch that, don't go there, it needs to be done this way. The more detail you explain it things, the better it works (though it still misses a few things).

[Lillominato89]

Man, this is so true! 
Previously, when I made a simple expense manager app using Codex, the same thing happened with me. There were like hundreds of errors/bugs.
One time the UI is messed up, one time the login button wouldn't work, another time the whole calculation logics breaks down.
Every time I fixed one bug, two more would take it's place! So, it took me more than 30-40 builds/versions before I could have perfected my app.
AI tools are really powerful that I admit, but what experience told me is that when you start using one you need to hand feed him everything.
Do this, do that, be careful not to touch that, don't go there, it needs to be done this way. The more detail you explain it things, the better it works (though it still misses a few things).

AI is an incredibly powerful tool that will become increasingly accurate and reliable over time; this is the way forward now, and I’m sure that as time goes on we’ll see it creating extraordinary things.
But what you say is true! If you don’t give the right command, it fixes one problem but quietly creates two more.
Many people have reported this, but I’ve never tried creating anything of my own accord! So I believe it to be true.
If I’m not mistaken, *ace* has also repeatedly pointed out that it fixes one problem but creates others afterwards.

[fillippone]

Man, this is so true! 

AI is an incredibly powerful tool that will become increasingly accurate and reliable over time; this is the way forward now, and I’m sure that as time goes on we’ll see it creating extraordinary things.

I plead guilty!
I am a really bad programmer, as you all know, but. This AI stuff got me so involved, and it helps me raise my productivity.
Of course, it is still a junior programmer, making obvious errors and mistakes, but I am slowly getting better at keeping him on the right path.
Overall, I think the result is not bad.
But of course, it is my attitude of "I test in production" that causes the worst disasters.

[Lillominato89]

Man, this is so true! 

AI is an incredibly powerful tool that will become increasingly accurate and reliable over time; this is the way forward now, and I’m sure that as time goes on we’ll see it creating extraordinary things.

I plead guilty!
I am a really bad programmer, as you all know, but. This AI stuff got me so involved, and it helps me raise my productivity.
Of course, it is still a junior programmer, making obvious errors and mistakes, but I am slowly getting better at keeping him on the right path.
Overall, I think the result is not bad.
But of course, it is my attitude of "I test in production" that causes the worst disasters.

And I’m an even worse programmer than you!
Back at secondary school, I did some programming in Visual Basic (lol) and C++.
But it’s been decades since then, and I’ve forgotten everything I ever learnt.
Now, with AI, anyone can programme.
Obviously, it has its pros and cons, but if you combine it with some study, you can become a skilled programmer in no time.

[Gragebox]

Man, this is so true! 
Previously, when I made a simple expense manager app using Codex, the same thing happened with me. There were like hundreds of errors/bugs.
One time the UI is messed up, one time the login button wouldn't work, another time the whole calculation logics breaks down.
Every time I fixed one bug, two more would take it's place! So, it took me more than 30-40 builds/versions before I could have perfected my app.
AI tools are really powerful that I admit, but what experience told me is that when you start using one you need to hand feed him everything.
Do this, do that, be careful not to touch that, don't go there, it needs to be done this way. The more detail you explain it things, the better it works (though it still misses a few things).

AI is an incredibly powerful tool that will become increasingly accurate and reliable over time; this is the way forward now, and I’m sure that as time goes on we’ll see it creating extraordinary things.
But what you say is true! If you don’t give the right command, it fixes one problem but quietly creates two more.
Many people have reported this, but I’ve never tried creating anything of my own accord! So I believe it to be true.
If I’m not mistaken, *ace* has also repeatedly pointed out that it fixes one problem but creates others afterwards.

That's sort of what I feel is the main drawback of AI right now. There are some great uses and it saves so much time, but the outcome still heavily hinges on how well we frame our request. If we're too brief there could be a problem created when AI focuses on just one piece.

I believe some level of human input for serious or complex issues is always warranted.

As we continue to advance with AI these shortcomings hopefully diminish, but for now relying fully on AI output should not happen. It's wise to utilize AI as a tool rather than a complete answer.

[fillippone]

That's sort of what I feel is the main drawback of AI right now. There are some great uses and it saves so much time, but the outcome still heavily hinges on how well we frame our request. If we're too brief there could be a problem created when AI focuses on just one piece.

I believe some level of human input for serious or complex issues is always warranted.

As we continue to advance with AI these shortcomings hopefully diminish, but for now relying fully on AI output should not happen. It's wise to utilize AI as a tool rather than a complete answer.

We still are a t the complete beginning of the AI revolution. AI are still in their infancy, this is why there are the problems that we al recognise. But if you think at the rate of improvements of these systems, it will be difficult to even imagine where we will be in 10 years.