Not Enough Crashes (Fabric)

Not Enough Crashes (Fabric)

4M Downloads

Provide an alternative for crash report hosting

natanfudge opened this issue ยท 4 comments

commented

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
commented

How about we use the IPFS Protocol?

Edit: I just found this https://github.com/jes/hardbin

commented

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.

commented

Solved with Crashy!
For further Crashy-related issues: https://github.com/natanfudge/Crashy/issues

commented

My idea for this now is to create a dedicated site to nicely display crash reports, holding nice ui components representing the crash instead of a dump of text.