⭕️ BitList.co - Bitcointalk Archive | Data Visualization & Search 🔍 [Ninjastic]

[Cricktor]

Right now it seems to work for me OK. I mostly use the BitcoinTalk Archive, but I checked the Raffle Manager page right now as this gave DYING_S0UL  the 404 page not found error which I observed occasionally today, too.

I wanted to report the 404 error, but when I rechecked before posting, it worked again, though considerably slower than usual. I guess, something is a bit flaky today, isn't it.

[DYING_S0UL]

Right now it seems to work for me OK. I mostly use the BitcoinTalk Archive, but I checked the Raffle Manager page right now as this gave DYING_S0UL  the 404 page not found error which I observed occasionally today, too.

The PGP verify page, as well as the Raffle manager page both were showing these errors, in a very short amount of time (a quick refresh fixed it)...

...though considerably slower than usual. I guess, something is a bit flaky today, isn't it.

Yeah, I guess we can put it that way too..or maybe acting wonky.


btw are they intentionally like this? there are no redirect link here, but only the texts, they don't lead anywhere...this is the first time i am noticing this.

[icopress]

btw are they intentionally like this? there are no redirect link here, but only the texts, they don't lead anywhere...this is the first time i am noticing this.

This is a temporary solution. There are some new features that require detailed descriptions, so we haven't updated the FAQ or other tabs until we release the update.

[*Ace*]

Hi Tryninja,
Just a quick question: are the old Ninjastic APIs still working?
Because up until last night I was still getting results for some of my userscripts, but today they seem to have stopped working completely.
Thanks for your patience with me! I’ll switch to the new Bitlist endpoints as soon as I get a chance.

[TryNinja]

Hi Tryninja,
Just a quick question: are the old Ninjastic APIs still working?
Because up until last night I was still getting results for some of my userscripts, but today they seem to have stopped working completely.
Thanks for your patience with me! I’ll switch to the new Bitlist endpoints as soon as I get a chance.

It should be, but I tightened the anti bot.

I have to ask, how are you doing your requests on the API? Because I see on the logs a constant burst of many expensive requests in the span of a few seconds.

For example, /users/{user_id}/overview is a very expensive call that queries the post and merit history of an user in a period. I see many calls fetching the same user data twice, from 2009-01-01 to 2026-04-12 (today), then from 2025-12-13 to 2026-04-12 (today). For many users at the same time.

Or /posts for the latest 500 posts of an user.

I could probably do like BitcoinTalk and limit requests at 1 per second, but you would be way off that limit right now.

I wish I could give more room, but BitList has been very slow and battling spam the last few days. It's either limit everything or buy and migrate to a much stronger and expensive server.

[*Ace*]

Hi Tryninja,
Just a quick question: are the old Ninjastic APIs still working?
Because up until last night I was still getting results for some of my userscripts, but today they seem to have stopped working completely.
Thanks for your patience with me! I’ll switch to the new Bitlist endpoints as soon as I get a chance.

It should be, but I tightened the anti bot.

I have to ask, how are you doing your requests on the API? Because I see on the logs a constant burst of many expensive requests in the span of a few seconds.

For example, /users/{user_id}/overview is a very expensive call that queries the post and merit history of an user in a period. I see many calls fetching the same user data twice, from 2009-01-01 to 2026-04-12 (today), then from 2025-12-13 to 2026-04-12 (today). For many users at the same time.

Or /posts for the latest 500 posts of an user.

I could probably do like BitcoinTalk and limit requests at 1 per second, but you would be way off that limit right now.

I wish I could give more room, but BitList has been very slow and battling spam the last few days. It's either limit everything or buy and migrate to a much stronger and expensive server.

I really do think it’s my fault and that of my BRDb score tool.
It scrapes 70 users a minute, so it fetches data for all the users it knows once a day.
I could limit the scraper to once a week and thus reduce the load of requests on Bitlist. Or I’m not sure. If you have any ideas, please let me know

[TryNinja]

I really do think it’s my fault and that of my BRDb score tool.
It scrapes 70 users a minute, so it fetches data for all the users it knows once a day.
I could limit the scraper to once a week and thus reduce the load of requests on Bitlist. Or I’m not sure. If you have any ideas, please let me know

I think it comes down to not hitting the API with a bunch of requests at the same time and optimization.

Instead of scraping everyone at the same time, queue them through the day.

Instead of fetching the entire post and merit history of each user every day, query it once, save the datetime cutoff and then only query from that date. For example, you request TryNinja data from 2009 til 2026 April 13. Why do the same thing tomorrow? Just fetch data starting from 2026 April 13…

And so on…

[*Ace*]

I really do think it’s my fault and that of my BRDb score tool.
It scrapes 70 users a minute, so it fetches data for all the users it knows once a day.
I could limit the scraper to once a week and thus reduce the load of requests on Bitlist. Or I’m not sure. If you have any ideas, please let me know

I think it comes down to not hitting the API with a bunch of requests at the same time and optimization.

Instead of scraping everyone at the same time, queue them through the day.

Instead of fetching the entire post and merit history of each user every day, query it once, save the datetime cutoff and then only query from that date. For example, you request TryNinja data from 2009 til 2026 April 13. Why do the same thing tomorrow? Just fetch data starting from 2026 April 13…

And so on…

You’re right, and to be honest, I hadn’t given it a second thought.
I’ve made some changes; let me know if the data load has gone down – I don’t think you’ll see the difference just yet.
The scraper now saves the latest available date, and from the next run it will fetch data starting from the last saved date.
Let me know if it’s overloading the APIs

[Rikafip]

Anyone else having a problem when exporting lists of the most active users from a specific topic? I am using standard code that is working normally when I am making a list of the most active members per board, but for some reason it gets broken when doing the same for topics.

It worked normally while ninjastic.space

Here is the code

Code:

[url=/?action=profile;u={uid}]{username} [{count}][/url]

And this is what I get when I use it for topic (it doesn't create links like it should)

1. Rikafip [372]
2. fillippone [124]
3. joker_josue [114]
4. bitmover [59]
5. skarais [59]

@TryNinja any idea on the problem? It worked normally for ninjastic.space, problems started with BitList.

[TryNinja]

@TryNinja any idea on the problem? It worked normally for ninjastic.space, problems started with BitList.

That's because I forgot to add support for the {uid} placeholder.

You can see on the page:
"Available placeholders: {number}, {username}, {count}"

Since this was missing from the previous version, I added it now. Thanks

[Rikafip]

That's because I forgot to add support for the {uid} placeholder.

Ahh, I haven't even noticed that uid thing is missing.

Anyway, thanks for sorting it out so fast, you saved me a lot time because for the last few months I was sorting it out manually, instead just coming here and asking what's wrong.

[fillippone]

Mhh I should have encountered this problem, but apparently I switched to usernames instead and went around the problem.
Is there a specific advantage using UID instead of usernames?

[*Ace*]

Mhh I should have encountered this problem, but apparently I switched to usernames instead and went around the problem.
Is there a specific advantage using UID instead of usernames?

Yes, there are several advantages
A UserID is guaranteed to be unique and will never change over time
A username, although unique, can be changed over time.

For tools that use APIs, it is better to use the UserID; it is faster and you never get it wrong
Using a username can cause problems, such as issues with upper and lower case letters or special characters. For example, my username *Ace* can cause problems in some programming languages and needs to be decoded.

Let’s say, for practicality’s sake, it is better to use the UserID

[LoyceV]

It scrapes 70 users a minute, so it fetches data for all the users it knows once a day.

If this is what you need:

Code:

— Key Variables —

merit_total       Total merit earned (Bitlist data, excludes 2017 airdrops)
posts_total       Total posts written
merit_120         Merit received in the last 120 days
posts_120         Posts written in the last 120 days
active_days_120   Number of distinct days active in the last 120 days
age_days          Account age in days from registration date

Isn't there a more efficient way to get the data you need without scraping each profile? Maybe TryNinja can get you a weekly or even daily data dump with just this data on all users.