Yes, thats what I am asking. If you think its spam, noted. I am also hesistant and had thought of logging this stuff more often but then backed off to hourly logs, which are literally: 60 byte per hour. When I multiple that with 24 hours and 365 days I come at 525.6 kilobytes of data added to the blockchain on annual base. I can be mistaken in my calculation.
It is why I am opening up this discussion and Im glad you reply to it.
Blockchains can be used through its "perceived immutability" (wink wink) as a proven datastore for data which need to be audit-able proven to be registered at a given time. In NL this is for example the case with temperature logging of refrigerators in restaurants. This is a repetitive task which needs to be done over and over again and when inspection shows up, it must be ready to be displayed and proven. A blockchain based storage, or at least backup, might be actually a usecase. Not certain if it should be the Hive chain. Maybe it can be another "cool" chain (wink wink at refrigerator)
So to continue on this... I am not certain this is why the Hive chain should be used like this, it is the question I arise. Yet Im certain I think it should not be used for your suggestion Nginx logging :) but maybe a hash of a logfile on rotation could be something? If you would need to prove that logs have not been fiddled with.
Yes, thats what I am asking. If you think its spam, noted. I am also hesistant and had thought of logging this stuff more often but then backed off to hourly logs, which are literally: 60 byte per hour. When I multiple that with 24 hours and 365 days I come at 525.6 kilobytes of data added to the blockchain on annual base. I can be mistaken in my calculation.
It is why I am opening up this discussion and Im glad you reply to it.
Blockchains can be used through its "perceived immutability" (wink wink) as a proven datastore for data which need to be audit-able proven to be registered at a given time. In NL this is for example the case with temperature logging of refrigerators in restaurants. This is a repetitive task which needs to be done over and over again and when inspection shows up, it must be ready to be displayed and proven. A blockchain based storage, or at least backup, might be actually a usecase. Not certain if it should be the Hive chain. Maybe it can be another "cool" chain (wink wink at refrigerator)
So to continue on this... I am not certain this is why the Hive chain should be used like this, it is the question I arise. Yet Im certain I think it should not be used for your suggestion Nginx logging :) but maybe a hash of a logfile on rotation could be something? If you would need to prove that logs have not been fiddled with.