I plan to create another thread only for the
http://posts.ninjastic.space, but for now, I will just post this here.
I started to work in a few new features not directly related to the Telegram bot and I will be implementing them in the ninjastic.space website.
The first one is the
https://posts.ninjastic.space/addresses page.
I scrapped every ETH address from every post I have saved in the website (~10 months old), and linked them together with the accounts that posted it. This could help people find out connections between accounts when bounty abusers reuse their addresses between different accounts.
You can also add tags to the addresses, which are locally saved in your browser and generate BBCode tables. Example:
_________________ | _____________________________________________ | _____________________________________________ |
Username | Posts | Archive |
Qomar Hamizah Gemilang | 1, 2, 3, 4, 5 | 1, 2, 3, 4, 5 |
Koteb17 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 | 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11 |
Rawon ayam | 1 | 1 |
Related address: | 0x78de3ab871785488d7cd0a5fc6c5c8aa9a81eaa9 | Powered by ninjastic.space |
Notes:
- Keep in mind that this contains every single post (~10 months old until now), regardless of its content. So you should see trusted users being linked with abusers because they just posted their addresses (e.g to expose them). You should check the data yourself and edit the table to make it correct.
- When you generate a table, some users do not have a link to their profile embedded to it. That's because, initially, I wasn't saving the user's UID along with the post when scrapping them. I plan to update all old posts with the author's UID in the future.
- Only Ethereum addresses (and thus, also ERC-20 tokens) are being scrapped (for now).