Hall of Fame - Most Followed Accounts on Steem Blockchain

Yesterday, a page was made to list the top blocked accounts on steem blockchain.
https://steemit.com/witness-category/@justyy/hall-of-fame-most-blocked-muted-accounts-on-steem-blockchain

It should be fairly simple to make another one that lists the most popular (followed) accounts on steem blockchain, by simply changing the query to:

1
select whom,count(1) from mute where what='follow' group by whom order by count(1) desc limit 100;

However, the query takes around 20 minutes to complete which I’ll explain when I dig a bit further. Anyway, here is the results based on today’s data:

image.png

It is also interesting to see that many accounts are on both lists - which mean that some like it - and also some don’t like it - for instance: @sweetsssj @cryptoriddler

It is normal that not everybody’s opinions are the same.


Every little helps! I hope this helps!

Steem On!~

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE



Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com


This page is synchronized from the post: ‘Hall of Fame - Most Followed Accounts on Steem Blockchain’

Hall of Fame - Most Blocked/Muted Accounts on Steem Blockchain

Thought it would be nice to see who are the top blocked accounts on steem blockchain:

1
select whom,count(1) from mute where what='ignore' group by whom order by count(1) desc limit 100;

Here is the result - updated hourly…

https://steemyy.com/top-muted.php

And on the contrast, the most loved accounts are coming tomorrow.

image.png


Every little helps! I hope this helps!

Steem On!~

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE



Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com


This page is synchronized from the post: ‘Hall of Fame - Most Blocked/Muted Accounts on Steem Blockchain’

Traffic Statistics/Analysis to SteemYY.com

I took a look at the website traffic of my site: https://steemyy.com

Alexa

Source: https://www.alexa.com/siteinfo/steemyy.com

image.png
A good sign that the traffic is constantly increasing in the last 90 days - probably due to a large exposure when I became a TOP 20 witness.

CloudFlare

image.png

image.png

image.png

image.png

Google Analytics

image.png

image.png

image.png

image.png

image.png

image.png

image.png


Every little helps! I hope this helps!

Steem On!~

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE



Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com


This page is synchronized from the post: ‘Traffic Statistics/Analysis to SteemYY.com’

Always Backup before Restarting the Steemd

Today, I was told that my RPC node https://api.justyy.com does not enable tags_api:

1
{"jsonrpc":"2.0","error":{"code":-32003,"message":"Assert Exception:_tags_api: tags_api_plugin not enabled.","data":{"code":10,"name":"assert_exception","message":"Assert Exception","stack":[{"context":{"level":"error","file":"condenser_api.cpp","line":1429,"method":"get_discussions_by_created","hostname":"","timestamp":"2020-06-17T13:42:21"},"format":"_tags_api: tags_api_plugin not enabled.","data":{}}]}},"id":6}

I was trying to enable it in the config.ini and I restart the steemd.

It didn’t work…
image.png

I had to take it off, and restart the steemd. However, it won’t let me start and keep hanging at a block - unable to push to the chain…

I have to restore the snapshot that was taken 2 weeks ago - and replay (should take a good few hours).

Meanwhile - I have to redirect the traffic to https://api.steemit.com to avoid breaking existing applications.

One important advice: always backup the files before trying new things.


Every little helps! I hope this helps!

Steem On!~

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE



Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com


This page is synchronized from the post: ‘Always Backup before Restarting the Steemd’

The problem of Any Centralised Service

I took a look at the number of registered users https://steemyy.com/reg.php by running the following SQL:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
mysql> select DATE_FORMAT(`ts`, '%Y-%m-%d') as datestr, count(1)  from reg where  password!=''  group  by  datestr order by datestr;
+------------+----------+

| datestr | count(1) |
+------------+----------+

| 2020-05-08 | 2 |
| 2020-05-09 | 10 |
| 2020-05-10 | 3 |
| 2020-05-16 | 1 |
| 2020-05-17 | 1 |
| 2020-05-18 | 2 |
| 2020-05-19 | 1 |
| 2020-05-21 | 2 |
| 2020-05-22 | 1 |
| 2020-05-25 | 2 |
| 2020-05-28 | 2 |
| 2020-05-30 | 1 |
| 2020-05-31 | 1 |
| 2020-06-02 | 1 |
| 2020-06-03 | 1 |
| 2020-06-04 | 1 |
| 2020-06-05 | 2 |
| 2020-06-06 | 2 |
| 2020-06-08 | 1 |
| 2020-06-09 | 2 |
| 2020-06-11 | 4 |
| 2020-06-12 | 1 |
| 2020-06-13 | 9 |
| 2020-06-14 | 6 |
| 2020-06-15 | 2 |
| 2020-06-16 | 4 |
+------------+----------+
26 rows in set (0.01 sec)

Obviously, it is getting popular. For now, it is fine as the numbers are still quite small even it is growing. With my SP, I could claim around 50 free tickets per day, and with my current ticket number, this service can sustain itself in the next few months or years.

However, if, sometime in the future, this service is getting quite popular, and let’s say more than 1000 user registration per day, apparently the number of the free tickets claimed will be a bottleneck. Let’s say we fix this problem magically, and the number of the users increases to 1000 per second, then the main problem will be techincally on the scaling part - which can be solved by introducing a load balancer, and migrating data to non-relational database rather than MySQL.

With current design on steem blockchain, the free tickets can be claimed, but cannot be given to others. It would be great if we can trade the tickets, or delegate those tickets and in return are rewarded for account creation.


Every little helps! I hope this helps!

Steem On!~

Reposted to Blog

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE



Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com


This page is synchronized from the post: ‘The problem of Any Centralised Service’

The custom_json inconsistent format increase the complexity

I have been wanting to make a few tools that require pre-processing the custom_json fields. however the script gets exceptions from time to time due to the inconsistent format of the custom_json.

For example, sometimes, I see this format:

1
{'required_auths': [], 'id': 'follow', 'required_posting_auths': ['steemit'], 'json': '["follow", {"follower":"steemit","following":"steem","what":["posts"]}]'}

And sometimes this:

1
{'required_auths': [], 'id': 'follow', 'required_posting_auths': ['steemit'], 'json': '{"follower":"steemit","following":"steem","what":["posts"]}'}

I assume that it is up to the front-end to interpret if the format is correct. At this point, the steem blockchain is just a public immutable database, and it has no idea what the JSON data means.

And also, this is worse:

1
{'required_auths': [], 'required_posting_auths': ['jpphoto'], 'id': 'follow', 'json': '"[\\"reblog\\",{\\"account\\":\\"jpphoto\\",\\"author\\":\\"photovisions\\",\\"permlink\\":\\"travel-norway-27-autumn-in-sylan-mountains-snow-and-reindeers\\"}]"'}

First JSON decode gives a valid JSON string which needs to be decoded. It might be obvious for human to understand the data, but for computer programs, you would need to handle all these cases, at least, you would need to realise the incorrect format, discard it, and move on - instead of throwing exception and halt.

Life is hard.


Every little helps! I hope this helps!

Steem On!~

Reposted to Blog

If you like my work, please consider voting for me, thanks!
https://steemit.com/~witnesses type in justyy and click VOTE



Alternatively, you could proxy to me if you are too lazy to vote!

Also: you can vote me at the tool I made: https://steemyy.com/witness-voting/?witness=justyy

Visit me at: https://steemyy.com


This page is synchronized from the post: ‘The custom_json inconsistent format increase the complexity’

Your browser is out-of-date!

Update your browser to view this website correctly. Update my browser now

×