Hacker Newsnew | past | comments | ask | show | jobs | submit | bitjson's commentslogin

@bitjson/qr-code is a zero-dependency, no-framework, customizable, animate-able, SVG-based <qr-code> HTML element. Drop it on any web page or app view, and customize the colors, add a center icon, and animate in, out, or based on activity.

You can try some example animations in your browser: https://qr.bitjson.com/ Or checkout this post for more usage ideas and guidance: https://blog.bitjson.com/qr-code/


If anyone is interested, there's a tiny utility I've used daily for years to do this: https://github.com/bitjson/wip

Each time you run `wip`, all current work is committed. When you run the squashing utility `naenae` (autocomplete: `nae + Tab`), the most recent line of "WIP" commits is saved to a `wip-archives/[branch]/[timestamp]` branch for safe keeping, the commits are all squashed in place, and you're left in your default git editor to define the commit message. It also handles unusual situations, like using `wip` for the first commit (in which case, `git reset HEAD^` will return an error).

Being able to set a sort of "WIP checkpoint" in the current working directory makes it really easy to start or back out of big changes, and it can be very useful to check back in past WIP commits to grab segments of code you previously threw away.


Our startup is working on this problem, initially for the javascript ecosystem. We’re offering insurance against vulnerabilities in javascript dependencies: https://bitauth.com/

We have open source developer tooling for signing and verifying signatures of javascript packages, and we’re offering security as a service, backed by up to $1M in insurance coverage.

We’re still in beta, but we’d love feedback from HN!


Hi everyone,

Bitcoin Script is the programming language used in bitcoin transactions. BitAuth IDE is a new open source project for designing advanced authentication schemes in this language.

BitAuth IDE includes a compiler with an entity/variable system and an interactive, "omniscient" debugger to view the entire execution of the program as you are typing.

You can learn more about the system in the link, and there's also a video walkthrough at the top of the article.

I'd love to answer questions and hear your thoughts! You can find the project on Github here:

https://github.com/bitjson/bitauth-ide


Hi HN – I've been working on a Bitcoin/Bitcoin Cash library written in TypeScript, and I just released the first production\-ready feature: a WebAssembly version of Secp256k1, the digital signature and verification system used by most cryptocurrencies. You can find more details and benchmarks at the link. If you're interested, please watch/star the [`bitcoin-ts` project on GitHub](https://github.com/bitjson/bitcoin-ts). I'm also happy to answer questions here. Thanks!


Hi all,

I just published `typescript-starter`. It's a minimal boilerplate generator with many of the most popular development tools pre-configured and ready to start hacking. (testing, coverage, typedoc, tslint, prettier, standard-version, etc.)

The CLI lets you get started quickly, just type `npx typescript-starter` to install the latest version and run the interactive generator. (For those who haven’t seen it yet, `npx` is a quick-run command which now comes with `npm`. If you have Node.js, you probably have `npx` already.)

The interactive mode lets you quickly select from a number of configuration options, and I plan to keep adding new options which work well together. Are there other packages or tooling options you would like to see added?

Thanks!


I put this together on Saturday to help me work a little faster on large features.

When I'm working on a new feature for any significant amount of time, I tend to make lots of "WIP" commits that I know I'll later squash together before merging. This makes that process a bit faster.

`naenae` is very similar to the effect of `squashing` with `-m` (such that the commit message isn't pre-populated with dozens of "WIP" messages), except it does the counting reliably for you, and lets you use [commitizen](https://commitizen.github.io/cz-cli/) without much thought.

This probably isn’t as useful for less-public projects (where it’s common to make smaller, in-progress commits and leave them as-is), but a lot of open source projects prefer to merge in pull requests with only one commit. This allows them to both generate succinct and useful changelogs and more accurately show contribution stats. For those kinds of projects, I find myself spending a lot of time counting and squashing, so this alleviates that a bit.

This might also be a good option for users with [little-to-no familiarity with Git](https://xkcd.com/1597/).


Usually when I need to make a WIP commit it is when I need to switch to master to fix or change something else. When I'm done in master I'll switch back and just do a `git reset --soft HEAD` or I'll just do a git stash.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: