joh6nn
I believe the intent is that you get bidirectional selective sync between your terminal and the docs, so that if what's in the docs is out of date or wrong, then whatever you did to actually fix things can be synced back to the docs to reduce the friction of keeping the docs updated.
- I am on a team that oversees a bunch of stuff, some of which I am very hands-on with and comfortable with, and some of which I am vaguely aware exists, but rarely touch
- X, a member of the latter category, breaks
- Everyone who actually knows about X is on vacation/dead/in a meeting
- Fortunately, there is a document that explains what to do in this situation
- It is somehow both obsolete and wrong, a true miracle of bad info
So that is the problem this is trying to solve.
Having discussed this with the creator some[1], the intent here (as I understand it) is to build something like a cross between Jupyter Notebooks and Ansible Tower: documentation, scripts, and metrics that all live next to each other in a way that makes it easier to know what's wrong, how to fix it, and if the fix worked
[1]Disclosure: I help mod the atuin Discord
Some terminals also support mouse navigation, so keep an eye out for that as well.
I'm sorry that you've been dealing with this frustration for so long and under the impression that it was just supposed to be that way and not fixable. The good news is that it's NOT supposed to be that frustrating and you CAN fix it
Edit: you edited your comment somewhere between my first seeing it and my reply posting. I haven't had to modify the default settings on my terminal to fix things like this in about 20 years. I've changed them to tweak various preferences like scrollback, cursor shape/size, etc. But arrow navigation has worked out of the box for me for so long that I literally can't remember when I last had to fix it. I don't know why our experiences have been so different, but I'm sorry that a tool that has been so useful for me has been so frustrating for you.
I appreciate you taking the time to respond thoroughly. Thanks!
On Instagram, it makes sense to me:
1. I farm for likes and karma
2. I start endorsing low value crap from whatever fad is trending this hour
3. Profit
On HN, I have no idea what step 2 is: what is the middle step between farming and profit that doesn't involve, like, founding a startup? What's the specific tactic on this platform?
Like, if we put it in the classic context of
1. Farm Karma
2. ?
3. Profit!
I'm not clear on step 2. What's step 2
And of course that pre-supposes malice (or at least greed), which is in violation of Hanlon's Razor.
It's like Where's Wal(do|ly): once you know where to look, it's obvious, but if you don't even know you're supposed to be looking for it, you may never find it
> but calls to safe_fprintf were replaced with calls to the unsafe fprintf. The diff doesn't make this obvious due to the removal of a newline in a parameter list.
It wasn't noticed because it was specifically designed not to be obvious.
I mean, I can make my own guesses about various forms of attention seeking and hopes to somehow cash in on high karma all day long but, to me it feels like HN is among the worst possible venues for that. I'm not aware of easy ways to convert HN karma into cash flow like you maybe could with followers on other platforms. So I don't immediately see a benefit in just farming karma for its own sake.
Is there some benefit to karma farming I'm not aware of? Like, some points-to-dollars conversion stream that I'm not in the loop on?
So to clarify: do you comment on the content of the post without reading it? I'm specifically interested in why people comment on links and articles they didn't read. And for maximum clarity here, I mean commenting on the content of the article, not just contributing to the various related discussions it spawns.
And to reiterate, I'm asking in earnest. It's not something I would do, so I'd like someone who does to weigh in.
Is there something new here I missed, or some additional context that makes this specific commit relevant right now?
As far as answering your actual question, you'd probably need to ask the project devs for Quicksy and Conversations?
Basically, it forces providers of a very wide variety of tech related services to collect identifying info on anyone who uses their services, and then store that info to either eventually be exposed in a breach, subpoenaed by the government, or sold to the highest bidder (might as well monetize it if you're forced to collect it )
Also, and perhaps even more importantly, if you aren't actually checking every time, then you don't actually know what the statistics for delusional vs not are, you're just guessing.
- this matters because it's capturing not just what commands were run, but metadata about the commands as well. Of particular interest to me is that ot captures the start and end time for every history entry so you can get timing data even if you forget to use `time`
- it provides much more fine-grained control over what makes it into the database than shells provide for controlling what makes it into their built-in history. For example, it has built-in support for filtering out common kinds of secrets/tokens/etc.
It's also in active development with a friendly and helpful creator/project lead, an active community, and an ever growing feature set.
I'd recommend giving it a try; as far as I'm concerned, it's best-in-class for managing shell history
When you look at animals that that do eat raw meat, it's super common for domestic animals (ie, those that live on farms, in zoos, etc) to have longer lifespans than their wild counterparts, in part because the meat they eat is less likely to have parasites and high-risk microbes than meat in the wild. So even when a given species is adapted to eat raw meat, it still comes with risks.
But beyond that, modern humans are less well adapted to eat raw meat than our hunter-gatherer ancestors. That's not to say we can't, we obviously can. But IIRC (I'm not an expert, I might be getting this wrong), the advent of cooking our food was like 1.5-2 Million years ago, more than enough time for us to have evolved changes to our digestion and parasite/microbe resistance that make it less safe for us to eat raw food.
And since cooking takes extra time and effort compared to eating food raw, presumably the reason that our ancestors bothered is because it conferred some advantage. One of the most likely advantages that could have been is that it made meat safer
Search term was "pocket shopping bag"
Assume a standard 2-axes scatter plot, with a randomly placed horizontal line that represents chance/luck. The scattered points represent opportunities.
Any opportunity that occurs above the luck line is successful, anything below it is unsuccessful.
Above a given threshold of luck, maximizing opportunities is a good strategy because there's a high likelihood they'll pay off.
But if your luck is too low, then maximizing opportunities will still result in a larger number of successes, but at a much greater cost. A more efficient strategy might be to invest more resources in the successes you actually get.
I'm not picking a side here, just trying to bridge a potential disconnect in the discussion. Podgajski, please correct me if I've misrepresented your position