awolf

Doctor, church, shooting range, protest. ICE was one item on a list. Build the infrastructure and it stays built for whoever’s in charge next.

Trying to discredit my substance based on a single of many examples tells me you're not arguing authentically here, nor elsewhere in this thread. We are failing to be productive past this point.

Yes, same outrage: it’s most of what I’ve worked on for twenty years. But “you’re already surveilled” isn’t a defense of Flock, it’s an argument for less surveillance everywhere.

Volume isn’t the distinction that matters, who holds the data and what is possible as a result is. Meta can sell my movements to an advertiser. It can’t pull me over, detain me unjustly, or hand my neighbor over to ICE. With Flock, police aren’t a downstream buyer; they’re the direct customer.

And “you already gave it away” is no longer good law. Chatrie v. United States (2026): Chatrie had opted into Google Location History, and the Court still held that disclosure to a third party doesn’t forfeit your Fourth Amendment interest.

Worth noting where we started, though. Two comments ago there was no plausible connection between public roads and privacy. Now there’s one, it’s just smaller than Meta’s. I'm really glad you have had this anparently eye opening moment here on HN.

It's not about your vehicle being seen in public at a single point in time, it's the fact that this system captures everyone's patterns of life. School, doctor, shooting range, church, play, protest. When, when, how often. All tracked and packaged up in a commercial database, without warrant or justification.

If you happened upon me on a public street, I'd say "that I'm here on this street now is not private information".

If you installed sensors across the entire city with 2-5 block resolution and could tell me everywhere I have been in the last 30 days (and hence where I'm liable to be tomorrow), I'd say "you are grossly violating my right to be secure in my person against unreasonable search - this is wrong".

Coal has a much worse heavy metal issue than Nuclear.

yes we're talking about living in today's world but... off the grid.

no one said "historical reenactment"

?

One patten I've seen to address this is to define a "plugin architecture" where disparate components are integrated into the main system via fixed "sockets". The sockets themselves are generic as is the glue code that attaches plugin and socket.

This does create a lot of boiler plate, but that boiler plate is predictable and uninteresting, and a good candidate for code generation.

Both added in iOS 14.

I guess Apple's not "full of shit" anymore.

> But, wow. This is beginning to look pretty scary.

This is the main benefit I see of having our government take these measures: making people like you realize THIS IS SERIOUS. It has "looked pretty scary" for almost two months. And no one has taken it seriously. And now we're here.

sure, was just matching what the author said in their example. 100% agree no need to use obscure words

yes

> If the first line of a commit message is a title, it changes the way you write it. It becomes just some text to introduce some more text, without any stress on the information density.

I agree with the author that commit messages should optimize for information density. However the example they provide does a poor job of this:

> This is a smart synopsis, as information dense as possible.

"This is a" is the type of thing that should never appear in a commit message as it could apply to EVERY commit message. Synopsizing is the action, but doesn't indicate what is being synopsized; one of the most important facts for someone to understand what is happening here. Finally "as information dense as possible", again should also be cut as this is telling us HOW not WHAT (and ironically hurts information density).

Were I writing this example it would be:

  Synopsize how to write a commit message

---

I led an initiative at my current company to enforce all commit messages start with an imperative verb and be less than 72 characters. Some people hate it, some people love it.

Aside from standardization, the primary reason to do this is the imperative mood leads to the most concise sentence possible. By leading with the action, the most natural thing to do next is to talk about what is being acted upon. Unnecessary words are dropped and the most important facts are emphasized. In short it forces the author to get to the point.

  [Act] upon [some aspect of the code]

e.g.

  Add user login link on home screen
  Refactor authentication into separate classes
  Lint PR titles conform to standard format

I definitely wear my Series 4 every night for sleep tracking comfortably. Charging for the 20 minutes I'm in the shower is enough.

The article is comparing year over year. July 2019 to July 2018.

The Equifax link leads to a form where you submit your social security number and birthdate. Cool.