steem.rocks was on the test run on the last couple of weeks. I was working on developing it lately and after new features and fixes, it's ready to go live as a stable project.
What is steem.rocks
For the people don't know steem.rocks, it's an activity feed for steem accounts. Whatever happens to your account in the network, regardless you're the actor of or affected from blockchain operations, will be shown in the feed.
It's an open source project which you can see source codes at @github/steemrocks.
Usage
Using steem.rocks is easy. Just go to URL by writing your account name.
If you're lazy, you can just type your account into http://steem.rocks homepage.
What's new?
New Activity Types
In the test run, I had limited activity types in the project. Only fouur actions were registered.
- Vote
- Comment
- Transfer
- Follow/Unfollow
I have extended registered activity types with these:
- Unvote
- Unfollow
- Mute
- Resteem
- Delegation/Undelegation
- Claim Reward Balance
- Producer Reward
- Witness Vote/Unvote
- Create Account with Delegation
- Return Vesting Delegation
- Price feed publish
- Delete Comment
- Author Reward
- Curation Reward
These are not all the activities can be done in the network, but I can say I have covered the most of it.
Performance Improvements
- Transaction Parsing
I have started to use get_ops_in_block instead of parsing transactions one by one. This dramatically reduced CPU usage. Also, I had the option to get virtual ops in a block.
- Data storage
Storing raw_data of blocks and transactions was a bad idea if you have limited storage. I stopped doing that, steem.rocks only stores operations' raw data from now on.
Bug Fixes
Multiple operations in one transaction had a buggy visualization because of the faulty storage in db. Fixed it with some touches to database.
Unicode representations of memos were handling incorrectly. Fixed it with using UTF-8 charset.
Mute operations was showing as "follow". Fixed it with the correct parsing of CustomJson operation.
Full blockchain data
steem.rocksteem.rocks designed in a way that users can see the latest status of their accounts. Since
data storage costs are huge if you store steem blockchain data in a database, I have decided I will just store last 2 months of data.
This way, I can reduce the server costs and run much faster just by sacrificing the feature of ability to go back deep into the history of activity feed.
Roadmap
Since I handled the core concepts of the project and they seem to work well, I will have a couple of
features in my mind.
- Ability to filter out activity types.
- Better design.
- A JSON REST API for developers to get user feeds.
Call for support
You can contribute to steemrocks in a couple of ways.
- Report bugs using utopian.io or github issues.
- Post ideas about the steem.rocks using utopian.io or just contact me and we will discuss.
- Contribute to development by picking and working on open issues.
- Contribute to the server and operating costs by sending donations. (@emrebeyler)
Thank you for reading.
[1] steem.rocks test run - first announcement
Open Source Contribution posted via Utopian.io