You are viewing a single comment's thread from:

RE: 3 Month Retrospective

in #steemit • 5 years ago (edited)

Welcome back 😉 missed you mate.

Technically speaking though, if everyone was using steemit.com,a view counter would work, but since so many people now use partiko and steempeak, it wouldn't be an accurate representation. It would have to be built into the blockchain, but that in itself raises an issue in that it would be really easy to fake views.

Sort:  

You just put Donald Trump's voice in my head you f-worder.

You're fake views!

Oh hey, by the way... it's good to see you too!

Wouldn't an accurate view counter be of interest to advertisers?

Maybe, it'd work if ip addresses that'd viewed the page were stored on the blockchain along with usernames of applicable.

 5 years ago (edited) 

Seems like an unnecessary addition to the chain and still possible to fake.

Unlike votes though, there's no real incentive to fake views unless it meant trending.

Yes, or unless it's meant to attract advertisers.

I think running it on a server defeats the whole point of decentralization (that's the whole reason for the blockchain). If the view-counter was on-chain and did like you say, use IPs (and maybe an IP/username hybrid), that would be perfect. No way to make the other sites adopt the viewcounter function of course.

{'type':'view', 'timestamp':'<<timestamp>>,' block':<<blocknum>>, 'json':{'ip' :'8.383.849.11', 'account':''}}

Is what a view would look like on the chain. Literally bytes of data, not even kilobytes. And every transaction we have makes our blocktivity ranking go up. Steem witnesses used to process ten times as many transactions as they do now, and that was before mira made node costs a fraction of what they were before.

 5 years ago (edited) 

Very little. Whenever you refresh steemit.com you'd be using more bandwidth and processing on comments and votes (which are tallied the same way) than on tallying views. Counting is bread and butter for a computer. And counting the votes could even be done clientside (on the users phone or Web browser).