Provide an alternative for crash report hosting
natanfudge opened this issue ยท 4 comments
Requirements:
- Up 100% of the time
- Ability for the author to delete uploaded crash report
Nice to have:
- Syntax Highlighting
- Identifier remapping
- Expiry date for crash reports
- Expiry date for link to crash report
How about we use the IPFS Protocol?
Edit: I just found this https://github.com/jes/hardbin
Content on IPFS is not persistent and will eventually disappear from the IPFS network if it is not pinned anywhere (equivalent to "seeding" in bittorrent). To make the content persistent, you can either pin it on an IPFS node you control: $ ipfs pin add QmYqb4VHHKTVVzwa26FnBKtLsmUsq7RERmGzKywJUtEhYy
No, we can't run ipfs instances on user's computers.
Solved with Crashy!
For further Crashy-related issues: https://github.com/natanfudge/Crashy/issues