base reserve requirement for data fields is not sufficient for preventing the bloat

[s-a-y]

In this package https://www.npmjs.com/package/stellar-sign I'm storing data into the blockchain: TX:

• manageData(key, value)
• manageData(key, null)

I unset the data field right away, so I don't need to keep base reserve for each field I'm saving. I can find transaction in transaction history for the account, so I don't need to have those fields set forever.

I think it is too cheap to bloat the ledger at the moment, let's say I use 50 operations to store data, and another 50 to release base reserve. 50 * 128 bytes = 6400 bytes per transaction costs me 0.001 XLM (I'm not including tx itself, just pure data) adding 6mb to the chain costs me 1 XLM adding 6GB costs me 1000 XLM ($400 at current rate)

I think fees need to be adjusted for manageData operation specifically.

[theaeolianmachine]

@jedmccaleb @MonsieurNicolas — outside of pushing adoption of higher fees, is there anything else that we can do here? Definitely agree with the sentiment on it being very easy to bloat the ledger (moving towards IPFS & removing data entries might be the better route).

[theaeolianmachine]

Mostly I'm looking for what steps should be taken next on this issue in your respective opinions.