The backend is functional but not ready for public release. It still has a few errors and needs to handle them properly to ensure complete file integrity.
The website is functional that shows the STEEM Whitepaper and the US Declaration of Independence stored on the blockchain. The download technically comes from the server itself, but it pulled the files from the blockchain.
My vision to create a caching server that sits inbetween the frontend and the backend. When a file is requested, the caching server will download it and have it available where it will be stored until it is no longer accessed at least once a week. At that point, it will be deleted from the caching server to free up space for more active files.
STEEM Liberator will be able to be interacted with directly thru STEEM via @steemliberator. I have a ways to go keep an eye out
Be careful going too far beyond a PoC though - it turns out that you will need quite a bit of SP to store anything very substantial. I'd recommend perhaps a 50KiB sanity limit on uploads.
SP directly affects how much can be uploaded at one time, but I'm not sure why that would be of any real concern during the PoC stages.
STEEM already has a lot of bloat and what I am doing, anyone can do. It is easy to politely ask me to be careful, but if someone wanted to attack STEEM it wouldn't be so easy to ask them to quit.
I have a decent amount invested in STEEM and powered up on my account. I would personally like to see STEEM do well.
If a 5MB upload can make the entire network freak out and hit a bug that prevents lower level users from doing anything, the network wasn't QA'd under heavy load. My experience is of a QA manager. And I can document exactly what was done when I triggered any issues, reducing time to find a fix by a considerable amount.
Trust me that I'm not going to intentionally break things. But also remember that anyone anywhere can do all of this with
The backend is functional but not ready for public release. It still has a few errors and needs to handle them properly to ensure complete file integrity.
The website is functional that shows the STEEM Whitepaper and the US Declaration of Independence stored on the blockchain. The download technically comes from the server itself, but it pulled the files from the blockchain.
My vision to create a caching server that sits inbetween the frontend and the backend. When a file is requested, the caching server will download it and have it available where it will be stored until it is no longer accessed at least once a week. At that point, it will be deleted from the caching server to free up space for more active files.
STEEM Liberator will be able to be interacted with directly thru STEEM via @steemliberator. I have a ways to go keep an eye out
Be careful going too far beyond a PoC though - it turns out that you will need quite a bit of SP to store anything very substantial. I'd recommend perhaps a 50KiB sanity limit on uploads.
SP directly affects how much can be uploaded at one time, but I'm not sure why that would be of any real concern during the PoC stages.
STEEM already has a lot of bloat and what I am doing, anyone can do. It is easy to politely ask me to be careful, but if someone wanted to attack STEEM it wouldn't be so easy to ask them to quit.
I have a decent amount invested in STEEM and powered up on my account. I would personally like to see STEEM do well.
If a 5MB upload can make the entire network freak out and hit a bug that prevents lower level users from doing anything, the network wasn't QA'd under heavy load. My experience is of a QA manager. And I can document exactly what was done when I triggered any issues, reducing time to find a fix by a considerable amount.
Trust me that I'm not going to intentionally break things. But also remember that anyone anywhere can do all of this with