ctur

Every MacOS update, I do run a sudo command and get the password prompt. I cancel, and instead do...

    sudo cp ~/Dropbox/etc-pam.d-sudo /etc/pam.d/sudo

Type the password once and you're done. I've been carrying this around for quite a while. No need to edit the file every MacOS, just copy it.

But once it did utterly go south when Dropbox's "load files on demand" functionality replaced the file with a bunch of zero bytes. That wasn't fun to fix. So maybe Dropbox isn't the best storage place.

Finally! A potential solution to the housing crisis. Newly VC-infused and rehabilitated Adam Neumann. Yes yes yes. The world needs more of this.

This is also a good hedge against the crypto pyramid starting to slow down. Leveraging peoples' willingness to try to get rich quick to create a pyramid was profitable, but once people lost their money and crypto lost its luster, they wandered off and were no longer easy victims^Wcustomers... but imagine if VCs could also control your housing. Wandering off is so much harder! Built-in market protection.

Brilliant.

Half of my interactions with the Slack UI are desperate attempts to not accidentally lose notifications, particularly through threads. "Mark Unread" is the most frequent command I use I think.

I find this spreadsheet handy for thinking about AWS region-wide outages and frequency. This seems to be the first major us-east-2 outage, indeed, vs us-east-1 and other regions.

https://docs.google.com/spreadsheets/d/1Gcq_h760CgINKjuwj7Wu... (from https://awsmaniac.com/aws-outages/)

If a "FUSE to replicate SQLite" solution came from anywhere else, I'd be quite skeptical, but there is a lot of very interesting tech coming out of fly.io these days and Ben certainly knows this space well. It still feels a little like a hack and piercing of layers of abstraction (less so than, say, litestream).

I love it when at first glance it isn't clear if a project is a crazy idea from someone just goofing around vs a highly leveraged crazy idea that will be a foundational part of a major technology shift.

I suspect it's the latter and the strategy though is to layer this on top of litestream to create an easy way to use sqlite transparently in a widely distributed multi-node environment (litestream providing the backups and/or readonly replication to remote sites, with LiteFS handling low latency local access in a cluster, POP, or data center).

Cool stuff. It will be fun to see where fly takes this :)

This is not a particularly thorough article overall and is made worse by the overly ambitious title. It basically starts with "ssh has problems" and moves immediately to "use an arbitrary separate tool" to solve them. But it doesn't really go into depth on or contrast against any alternatives such as built-in facilities like SSH certificates or various third party options like Amazon SSM, Teleport, Tailscale SSH, "normal" bastion hosts, etc.

Truly "Hardening" SSH involves a more robust set of options and bigger toolbox than this article suggests. In particular the bar is very high for new tools in the ecosystem and BastionZero.

I urge readers to know how high the bar should be for deploying solutions to SSH and system access ecosystem and to be skeptical of anything they read as magic solutions or that lacks an established pedigree. If nothing else, a good first step is searching HN for proposed solutions to see if this community has discussed it.

In general, it is preferable now to use squashfs for most tar use cases three days. Random access, high compression levels, and completely operable with userland tools and a FUSE file system. tar does have some niche uses (streaming) but if you don’t need streaming, you can get massively faster compression into a format much more ergonomically pleasant.

It is interesting seeing the evolution of open source maintenance in the light of new (or increasing) supply chain attacks and acts of political protest. There always has been a "what is your obligation to quickly respond to a security issue?" expectation around the code and now similar obligatory expectation questions arise on the maintenance process itself.

We also see what seems like rather balkanized approaches (npm, pypi, cargo, ...). It would be great if broader consensus arose on what the ideal standard should be for package management and distribution that then those projects could adhere to. Similar about commit access to repos and what the requirements there should be.

It's also peculiar how much stronger the guarantees you get from your operating system vendor are w.r.t. signatures on packages vs what the underlying projects themselves have. OSs have had this pretty well handled for decades, but no common best practices like 2fa, signatures, etc seem to have emerged.

Not to go full neckbeard on this one, but in addition to FUSE-based options, there is at least one approach that achieves as good (or better) results using more trusted and common primitives in Linux:

Just use cryptsetup on loopback mounted LUKS-structured files, and put the encrypted file in Dropbox or wherever. No filesystem-level weirdness, no random software with unknown/untested pedigree. Add a cronjob that unmounts the filesystem every N minutes and you have a pretty decent sometimes-on place to store just about anything. Double bonus, put a git repository and checkout in the filesystem and you get history of whatever you're stashing in there.

I love these kind of real world tests of technologies applied in the field. A great YouTube channel along a similar vein is Project Farm, https://www.youtube.com/c/ProjectFarm

While he doesn't go into the science and physics directly, he often shows the precise outcomes and results of controlled tests to compare brands against one another. It's always fun when he reads a manufacturer's claim and makes it abundantly clear "we're going to test that."

This seems pretty incomplete if it doesn't include anything about brotli, lz4, or zstd, or Finite State Entropy in general. It's basically missing the past decade or more.

There's a lot of good history here, but just be aware it is missing the state of the art and thus shouldn't be used for deciding anything about algorithms or approaches to use today.

The 1st edition of this book was very influential for a generation (or more) of engineers. I can't wait to see how it's evolved and what I learn reading a new edition through again.

This article has a lot of good points and suggestions for site creators, but for consumers, there is something you can use: the Decentraleyes browser addon (https://decentraleyes.org/). It basically intercepts calls to well-known centralized CDNs and serves it locally from the browser without issuing any network calls whatsoever.

What a misogynistic jerk. I don't know what is sadder; that he has so much of a following, or that his garbage POV resonates with a small number of deplorables in our industry. The rest of us need to do our best to push back and ensure we make our industry hospitable, welcoming, and supportive for women and all other URMs.

Needless to say, his statements are garbage and nonsensical, meant only to stir up noise and draw attention. The sad thing is, controversy more or less is beneficial for his bottom line. He doesn't need to convince anyone he's a decent human being, he just needs to convince them to watch his videos, pay for his training, etc.

Kind of depressing.

For those not wanting the overhead of running a service on your network, NextDNS sells what is basically managed pihole. I’ve used it for about a year and have been very happy. It also lets you use it on mobile devices for when you aren’t on your home network.

Nice post — one suggestion would be to use zstd instead of gzip though. Out of the box it is much faster and will result in smaller files, and allows tuning to fit inside memory and cpu thresholds different use cases might prefer.

Friends don’t let friends use gzip :)

It takes a while to get to the point so I’ll save others some time and tldr this very lengthy and agenda-driven blog post:

jq had a tough learning curve so you should switch to zq which is a (closed source?) wrapper around an obscure language you’ve never heard of that we promise is easier because reasons. Also coincidentally it’s the language of an ecosystem we were funded to build.

Edit: mea culpa, turns out you can download the source (revealed half way through the article).

The SCM ecosystem at Facebook is tremendously powerful and the result of some of the best minds at Facebook working on those systems for many years. From the scaling of the monorepos to the code review workflows, nothing really matches it. The ergonomics of most of the tooling was simply top notch (which it needed to be... engineers, particularly at Meta, are an opinionated lot who don't tolerate poor tools).

It's great to see this out in the wild now.

Check out mutagen (discussion on https://news.ycombinator.com/item?id=30957156) -- it basically does bidirectional, background, transparent rsync. It also does port forwarding if you need that. It looks quite solid for the use case you describe.

Citation needed. The addon certainly seems far less legitimate than Decentraleyes. For instance, who maintains this, why did they fork it, who has validated it isn't a malicious fork, etc etc. At least for Decentraleyes you have it being popular and "Recommended" by Firefox which puts a certain expectation to not be a flaming pile of malware.

Some slightly dated discussion about this on Reddit; not much seems to have changed to make LocalCDN compelling: https://www.reddit.com/r/privacytoolsIO/comments/fc05uh/just...

Great news for a great team. 1Password makes a very solid product and the company genuinely helps improve the security ecosystem for their users (and, through working with browser vendors on things like extension security, all of us).

Hopefully they don’t go all cryptocoin and NFT with the funding… but given their dna, I think they will expand wisely.

The Hacker's Diet has helped me lose a good bit of weight over the years, but it is a somewhat simplistic model. Metabolism isn't quite as simple as CICO and can adjust over time to compensate for lowered metabolic rate. Herman Pontzer's recent book, Burn: the Misunderstood Science of Metabolism, goes into metabolic differences in quite a bit of detail and is very well researched and based in science.

https://www.chemistryworld.com/review/burn-the-misunderstood...

Well I bought a 1,000 ft spool of CAT6a for nothing... beaten to the punch!

i feel so seen

Only if you want miners to have power and residents to be without it.

Capitalism is not the cookie cutter solution to all problems.

I wrote this in an email turning down a chance explore opportunities at Coinbase.

> To me, diversity and social justice are critically important. I have the luxury of being selective in where I put my time and energy and it is important those values align with my career. I appreciate aspects of being "mission focused" but I think that there is a gulf between my personal values and Coinbase's values such that I would not be comfortable in the environment.

I can't speak for anyone else but I think I'm not a terrible engineer and I definitely ruled them completely out of the realm of places I'd be willing to work.

Absolutely true.

Fair, maybe it's always a matter of picking the trap you want :) If you are optimizing for 0->1, Python is great. But if you want code to live and evolve over time with multiple authors, or ever will care about runtime performance, it's a dead end almost from the first line.

But sometimes the productivity benefit is all that matters and you accept you may have to throw it all out later (or invest insanely in making it work)... it's all about making an informed decision.