How I Survived the Downtime and Why You Should Care!

Withdrawal Symptoms as Catalyst for Brainstorming Sessions

When Steemit.com was unavailable for days because of a DDoS-attack, I began to realise what an influence this entire ecosystem has on me. I was literally experiencing withdrawal symptoms, which could only be partly relieved by researching and writing a few posts, like this one.


Luckily, the Steem blockchain was never compromised. In fact, it has been running uninterrupted, albeit with very few transactions; only the trading and voting bots that have direct access to the blockchain (and as such, don't need Steemit.com) were the sole survivers of this DDoS-attack.

Now What Does This All Mean To You?

A DDoS-attack can K.O. our beloved Steemit.com website, but not the blockchain. Hence, we need a backup-interface to interact with the blockchain. An example would be steemd.com, but unfortunately this interface is read-only.


Now here's my question to the devs: could you please consider making the entire source of Steemit.com available on GitHub, to allow for backup hosting by the community? I believe this fits nicely in the "decentralized" concept, and it would be a great way to flip the bird to whoever is trying to disrupt this beautiful project with DDoS-attacks.


Input/feedback would be appreciated very much.


Thanks for reading!
https://steemit.com/@r4fken

#steemit #steempower #decentralized #ddos #hack #community #hosting #empowering #future #flipthebird #hacker