Then its not fit for the purpose.
Cannot express that enough.
You cannot then use MDs since they could disappear on you. No good for databases & indexes etc
Now as temp files in immutable chunks then it has some use, but this is separate to deletable/(truly)mutable data (MDs). And as temp immutable files then charging less could be valid.
Again I think I have made this a little more confusing than it should be. I was referring to deletable data in MDs (see NOTE)
The idea of paying more is to have deletable (mutable) data objects that are reusable by the user. Such uses include but in no way limited to
- Temp files (stored in true MDs) used by applications for recovery if app crashes, PC crashes, PC dies and is replaced etc. Most text files being edited are one MB max, but MDs can be chained together if needed.
- Database mutability
- Indexes for databases and other applications
- personal use in applications. EG star mapping. Collection of information in MDs but not strictly database.
- IoT data collecting when not in a pure log type
- IoT temp files needed for applications (ie NOT the normal stated applications) These files are often addressed by MD address and bytes in MD
For all these deletable data objects the idea of paying slightly more is good since it discourages using these deletable objects as normal file storage. The reason for wanting that is
- Perpetually of (published & other) files and data is much needed in the world and should be encouraged
- temp files encourage making SAFE sites from them and we will end up with what we have today, dead links all over the place. Cheaper to put up safe site using temp files and take the risk that one day (likely to be years away) some pages disappear. So just upload them again when found out. or just let site die out.
- database applications NEED to know their records can be truly mutated and will not be removed just because a section runs low on space sometime in the next 10 years.
@Traktion It seems we are actually talking of two different concepts here. You are talking of truly temp files that can disappear at the whim of the sections and have some use. I am talking of temp files at the control of the user (apps).
These are two very different parameters even though they are similar on the surface. The best use case to illustrate this is the recovery files that MUST remain under the control of user (app) and cannot be allowed to disappear if space is low. If that happened then recovery files are not really secure recovery files are they since they still allow data loss.
So I see it as 2 aspects of being able to delete files.
My main idea in the past and now has been that of temp files at the control of the user and also temp files that have a guaranteed lifetime (expressed in say events rather like blocks in btc)
EDIT: and to IPFS being an example of how free temp files will work is invalidated by the example of the testnet prior to invites. Remember how account spamming filled up the testnet.
Created accounts giving them more PUTs to fill up the storage capacity of the testnet.
This is why I know that free temp files on SAFE will be abused and fill up the network.