We have currently simple GitHub page, but we need to think about it's update with some better design.

Checklist

• I have used the search function to see if someone else has already submitted the same feature request.
• I will only create one feature request per issue.
• I will describe the problem with as much detail as possible.

System info

App version: 2.0.0

Task

Convert CI to GitHub Actions

Context

Travis is removing its free tier for OSS projects, so this should be built with GitHub Actions instead, which is not going to add additional cost.

I would expect this to be one of the easier projects to convert given that Docker isn't used in the build.

See also:

https://github.com/mvdan/github-actions-golang
https://github.com/ac

Just playing around with my miner tonight, I set burn_fee_cap = -2 and the miner stopped with a thread panic.

Process abort due to thread panic
   0: backtrace::backtrace::libunwind::trace
             at .cargo/registry/src/github.com-1285ae84e5963aae/backtrace-0.3.50/src/backtrace/libunwind.rs:95
      backtrace::backtrace::trace_unsynchronized
             at .cargo/registry/src/git

The buildkit (client) and buildkitd (builder daemon) can both be used with faasd or k3s hosts for building images without installing Docker onto the machine.

There is a tar that can be downloaded like we do with inletsctl, however, we need to make sure we extract both binaries. I'm fairly sure that this will "just work"

See more:

https://github.com/moby/buildkit/releases

Electron Apps has collected a great deal of apps over the years. However, many apps are now broken or no longer working, and thus should be removed from our directories. As part of Hacktoberfest, we'd like to clean up some of those apps.

You can find a guide for removing/disabling apps here: https://github.com/electron/apps/blob/master/contributing.md#removing-or-disabling-apps

Criteria for

cc @jcnelson from this forum post.

There should be a setting added that allows the user to adjust the URL for the transaction broadcaster in regards to acquiring names. Should be fairly simple to implement unless it is tied within blockstack.js, in which case an issue would need to