You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
As it stands (the ecosystem), there’s almost no point in working on artifact signature checks, since all of the same threats that could compromise artifacts would *also* compromise SBT itself and, by extension, the signature verification.
I'm concerned about this for Fury. How would you feel about Fury's installer being a readable bash script which builds it from sources it downloads from Github? You would still need to trust the Scala compiler that's used, at least until I can build that from source, too.
You would need hard-coded signature checks on the scala compiler and on the source tarball (and all its dependencies). Basically the same as what SBT needs to do, but with a source stage.
But you also need to verify that the CPU and JVM hasn't been compromised. So you need to build the same artifact on many machines and compare artifact hashes.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
