When I saw steemit.com adding that DDoS protection thing by CloudFlare, I was relatively happy: it's a good protection, and something that Steemit.com should have had for years already. Little did I know that this supplementary layer of security will break steem.supply badly.
Because of this tiny change, one of the calls that the app was making was left in the dark, so to speak. Until then, you could have read the basic information about a user following a link like this: http://steemit.com/@username. Well, since the DDoS protection thing came out, every link is filtered through it first, which means the first call I made for that type of link was "throttled" and I didn't get any user related info. And from there chaos ensued.
On one side, it's a more elegant way to get data directly from an API endpoint, I agree with that, on the other, I wish I'd had spotted this earlier.
Anyway, thanks to those who mentioned that steem.supply was down in the comments.
Also, a short reminder: if you think that my work (on steem.supply, and overall, on the Steem blockchain) matters, I would appreciate your vote for my witness node (use the link below).
Steem on!
I'm a serial entrepreneur, blogger and ultrarunner. You can find me mainly on my blog at Dragos Roua where I write about productivity, business, relationships and running. Here on Steemit you may stay updated by following me 
Wanna know when you're getting paid?
|
I know the feeling. That's why I created steem.supply, an easy to use and accurate tool for calculating your Steemit rewards |