Little teaser (tutorial comming up): microtransaction based authentication and listing inactive follows.

in authentication •  6 years ago 

Working on a new tutorial for asyncsteem. Micro transaction-based authentication with asyncsteem, twisted-web, jinja2 and redis. First working code is available here, and demo site available here. Once authenticated, instead of the Hello World I was first planning, a simple listing of people you are following who haven't posted anything for 40 days or more (thanks to @tcpolymath for letting me borrow his idea ).
Stay tuned, a tutorial is coming up in a few days.

So anyone into @steem-ua , feel free to test this code and use it to trim down your stale follows a bit. Stay tuned for the tutorial.

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

hey @mattockfs,

I've seen the idea to remove inactive followers around in a couple of posts lately. I must admit I haven't followed the steem-ua implications closely.

So anyone into @steem-ua , feel free to test this code and use it to trim down your stale follows a bit.

What does it have to do with steem-ua? My understanding was that steem-ua, for the calculation of my score, looks into the number and scores of accounts following me. If I now "clean up" the list of accounts I am following, I may reduce their score but it doesn't change a thing about mine, does it?

What I understood from. @tcpolymath's post and comments is that there is some translative property that is likely to echo some back to you, but I'm not sure on the details. For me this was mainly about micro-transaction Vs steemconnect for user authentication, so I'm using @tcpolymath's idea more like a glorified hello world for my upcoming tutorial. Wether UA echos back or not as a result of cleanup, still would make cleaning up stale follows the sociable thing to do, right?

Hehe, seems like there is a good fraction of "unknown sauce" in the UA calculation and understanding thereof - thanks for the pointers :) For your approach, it is indeed a nice "hello word" case. Looking forward to details about it!