ddworken

23 ms·

1.
by ddworken 2y ago
I actually made a CLI tool ( https://github.com/ddworken/hishtory ) that automatically binds to Control+R to support both history searching and AI queries (by prefixing queries with `?`). Here's the prompt engineeri
2.
The Great Google Password Heist(bughunters.google.com)
3 points by ddworken 2y ago|0 comments
3.
by ddworken 3y ago
I'll also plug my project [0] as another alternative that supports syncing (similar to Autumn) and also has a number of powerful customization features (e.g. custom columns to collect arbitrary metadata with each command, like the git
4.
Truly Paranoid Software Updates(blog.daviddworken.com)
2 points by ddworken 3y ago|0 comments
5.
by ddworken 4y ago
If you're interested in something more actively maintained, and with cross-machine syncing, two recent alternatives are: * github.com/ddworken/hishtory * github.com/ellie/atuin Disclaimer: I'm the maintainer of
6.
by ddworken 4y ago
Ah, thank you commenting on this! This is absolutely unintentional and was the fault of a missing comment in the bash script (that I didn't notice because I generally use zsh). See https://github.com/ddworken/hisht
7.
by ddworken 4y ago
Yup exactly! This way you'll never again lose a history entry.
8.
by ddworken 4y ago
Yes! See the `hishtory redact` command to do exactly this.
9.
by ddworken 4y ago
Yes! Though they'll have a single shared history log since there is no way to distinguish between them.
10.
by ddworken 4y ago
See https://github.com/ddworken/hishtory/blob/master/backend/web... Also, Github pro tip: Press `t` when on any github repo to bring up fuzzy matching that can be used to easily find any specific fi
11.
by ddworken 4y ago
Actually the install script is in the repo! See https://github.com/ddworken/hishtory/tree/master/backend/web...
12.
by ddworken 4y ago
+1 to prefixing with a space. hiSHtory supports this out of the box so that anything prefixed with a space isn't recorded (even if your shell doesn't do that by default!). And if you do ever mess up, `hishtory redact` can be used
13.
by ddworken 4y ago
Agreed! I'll make sure to get this implemented ASAP. :)
14.
by ddworken 4y ago
See https://github.com/ddworken/hishtory/issues/6 for info on how to disable control-R and how to uninstall. And sorry about this, I agree that a cleaner way to uninstall is needed and will get this implement
15.
by ddworken 4y ago
Though keep in mind that all history entries are end to end encrypted, so even with syncing enabled, your shell history isn't accessible to the backend.
16.
by ddworken 4y ago
See https://github.com/ddworken/hishtory/issues/4 This isn't supported quite yet, but is the next item on the road map.
17.
by ddworken 4y ago
It just adds to it, your standard shell history is still there and completely unaffected by this tool. And if you prefer using your native shell's control-r you can also do that. > if I delete something using `hishtory redact` does
18.
by ddworken 4y ago
In addition, hiSHtory also supports fish for anyone who uses fish!
19.
by ddworken 4y ago
If you'd rather `go install` it, that works too! The advantage of this is that it doesn't require users to have go installed. And if you look at the script, all it does is call an API to determine the latest pre-built version for
20.
by ddworken 4y ago
Yup exactly! And you can even collect other custom metadata to make it easier to jump write back to where you were.
21.
by ddworken 4y ago
Ah, I hadn't come across Atuin before! They're pretty similar, but I think one significant advantage of hiSHtory is the "Custom Columns" support where you can populate custom columns with the output of an arbitrary shell
22.
by ddworken 4y ago
Ah very cool! One advantage of hiSHtory over this is that hiSHtory also supports Linux (since it isn't bound to iCloud sync).
23.
Show HN: HiSHtory: Your shell history in context, synced, and queryable(github.com)
179 points by ddworken 4y ago|68 comments
24.
Show HN: HiSHtory: Your shell history in context, synced, and queryable(github.com)
3 points by ddworken 4y ago|0 comments
25.
by ddworken 4y ago
Though you could have a repository on Github that contains a subdirectory that is a malicious bare Git repo. So doing: ``` git clone github.com/foo/bar cd bar/subdir/ ``` is unsafe with a Git PS1. See https://
26.
by ddworken 5y ago
You can also use the --rewrite flag to automatically patch those files. This will remove the class that leads to the vulnerability and is generally a safe change.
27.
by ddworken 5y ago
This tool will recursively unpack wars and ears.
28.
by ddworken 5y ago
One of the benefits of this tool is that you can run it across a folder or even an entire disk to check all jars on the disk. So if a Node app does somehow pull in java, by scanning the entire disk this tool should be able to detect if the
29.
by ddworken 5y ago
One other notable candidate for essentially "solving" XSRF is SameSite cookies: https://web.dev/samesite-cookies-explained/ SameSite cookies are supported in Safari and IE11, so they're potentially a bet
30.
by ddworken 5y ago
In the web, requests are made in either `cors` mode or `no-cors` mode. In `cors` mode, the `Origin` header is sent in the request. So yes, in `cors` mode the server could reject the request based on the `Origin` header. But in `no-cors` mod

More ›