opentimestamps-client
git-blame-someone-else
| opentimestamps-client | git-blame-someone-else | |
|---|---|---|
| 2 | 108 | |
| 284 | 10,644 | |
| 0.4% | - | |
| 2.6 | 0.0 | |
| 2 months ago | 5 months ago | |
| Python | Shell | |
| GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
opentimestamps-client
-
📑 MiniBolt resources 📚 List of the MiniBolt core/bonus guides + latest versions
OpenTimeStamp-client v0.7.1 (Released: 26th August 2022) - https://github.com/opentimestamps/opentimestamps-client/releases
-
Signing Git Commits with Your SSH Key
if you sign your commits, you should also consider timestamping your commits. I use OpenTimestamps for this. Docs and some rationale here: https://github.com/opentimestamps/opentimestamps-client/blob...
from the doc:
> My signing keys (e.g. blog or Qubes code signing keys) do not have expiration dates. This is not laziness. There is a fundamental problem with using an expiration date on keys used for code signing (e.g. git tag -s), because it is unclear what the outcome should be when one verifies some old code (written and signed when the key was still valid) in the future when the key has already expired?
> Naturally we would like the old code, written and signed when the key was still valid, to continue to verify fine also in the future, after the key expires (and the developer passed away, perhaps). However, it is very problematic to prevent the attacker from creating falsified code pretending to be an old one.
git-blame-someone-else
- FTX "insurance fund" calculated by multiplying trading volume by random number
-
someThingsAreForever
Or be a crafty bastard and use git blame-someone-else
-
When is it OK to blame your colleague?
A tool for you: https://github.com/jayphelps/git-blame-someone-else
-
Git Blame-Someone-Else
But funny enough is that there is a commit where it pretends to be Linus https://github.com/jayphelps/git-blame-someone-else/commit/e...
- little does he know 😂
- Erros
-
How Git Blame Really Works
It can be!
-
(Dusj)tanke: Ansvarliggjøring av beslutningstakere ved eponymisering av lover / avgjørelser.
git blame someone else
- The small things that bring me joy when working late
What are some alternatives?
platform-samples - A public place for all platform sample projects.
AmogOS - ඞ Among-us themed OS. As seen on Reddit and Youtube.
rebalance-lnd - A script that can be used to balance lightning channels of a lnd node
ioccc-obfuscated-c-contest - IOCCC International Obfuscated C code contest entries
smimesign - An S/MIME signing utility for use with Git
YiffSpot - A real-time web chat for "yiffing" randomly with other furries anonymously.
electrs - An efficient re-implementation of Electrum Server in Rust
five - Gives you five
btc-rpc-explorer - Database-free, self-hosted Bitcoin explorer, via RPC to Bitcoin Core.
open-and-shut - Type in Morse code by repeatedly slamming your laptop shut
zap-desktop - Zap Wallet - Cross platform Lightning Network wallet focused on user experience and ease of use ⚡️
git-gud - Ever had someone tell you to "get good"? Now you can!