jmholla

Woah! That feels like a huge oversight and like it bypasses standard commit logic. The man pages do say `git history` is experimental. Sounds worth a bug report.

Fun fact: you don't even need the `-n`. `git log -1` does the same thing, for any number.

    -<number>, -n <number>, --max-count=<number>
        Limit the output to <number> commits.

I don't think that logic works. In your vein, if I say " If it gets hotter, I'll want it to be colder" that would imply that if it gets colder I'll want it to be hotter. That doesn't necessarily have to be the case thought.

If they made a profit and I want them to pay more than the base fine doesn't mean if they made a loss I want them to pay less than the base fine.

I think the rest of your come t stands though. There is difficulty I proving profit and Hollywood accounting can probably change those numbers.

Yea. A lot of them grew wise to this and just hung up on you. Some had no way to get through the tree to a real person. Or, the real person couldn't do anything (e.g., Public Storage).

Don Quixote feels like a bad analogy. These are real dragons. Just, more difficult to fight against.

I've been thinking of setting up a simple server that publishes the public keys at a known endpoints. You point an A record for one of your subdomains at the machine and it can provision a TLS cert. Then you can be reasonably confident your connection hasn't been MitM (assuming your trust your cert provider) when you query for those public keys.

The one presented in the article has fewer moving parts though. I'm also curious what ideas are bouncing around your head if you're willing to share.

Safari isn't based on Chromium.

Ostracization has worked before. And ostracization can lead to decreased sales, which they will definitely notice. If engaging with people to talk about privacy implications involves sacrificing your privacy, I feel that it is reasonable approach.

It's like if I had to be punched by someone to talk to them about why them punching people all the time wasn't alright, then I'd find it very reasonable to just not associate with that person.

I think you're outlining a relationship with people who actually want to actively engage in these concerns in a responsible manner, and these platforms have definitely demonstrated the opposite and a willingness to use that engagement to inflict the very behavior you want to moderate.

You're aware of the privacy implications but think people talking about avoiding people who use them are proposing dumb arguments? I don't follow your logic.

Or device battery life was shorter because we hadn't developed better battery technology or better power management

You talk about the misaligned incentives of replaceable batteries but fail to point out the incentive built-in batteries: need to replace a battery, buy a whole new device.

You should actually read the text of the bill. It basically tells anyone who asks what your birthday is. It places no limitations on how your age should be verified, or how requesters can use your information. And if you think this is where this kind of de-anonymization will stop, I have a bridge to sell you.

So this bill creates a commission to ensure that the information cannot be stolen or breached from operating systems, but says nothing about how the applications querying this information must protect or leverage it. I basically requires that any application get to know a user's birthday, as long as it's "necessary". What a fucking joke! I'm so sick and tired of this bullshit.

Direct link to the bill: https://docs.reclaimthenet.org/parents-decide-act-os-age-ver...

Edit: Oh, and the commission gets to make up the rules on how ages should be verified. So, prepare for a whole other level of PII leakage that isn't even captured by the text of the bill.

When I was going to register it with Porkbun, it showed this warning:

This TLD has very strict verifiable contact requirements. You MUST use verifiable contact information or your domain may be suspended and / or deleted without warning by the registry and without refund. The registry is also extremely difficult to contact and communicate with, it's possible that you will be asked to rectify your unverifiable contact info and do so but then they will ignore you. Yes, it is pure insanity and bad enough that we took the time to add this very special warning.

This TLD does not allow WHOIS privacy but generally redacts your personal information. This means that your personal contact information will be sent to the registry but it should not be made public. Please note that some registries will make your contact information public if you are registering as a company, organization, or something other than an individual person.

I made this as a set it and forget it site, so I didn't want to deal with any hassle that might come up. Have you registered .in domains and experienced anything like this?

I've made it through about the first ten parts of section 2. Some additional feedback I've put together:

* Sometimes explanations are overly lacking, other times they get repetitive. This feels like it needs to be accompanied by a course to fully deliver value. For instance, we're kind of thrown into truth gates without having really gone over them. And understanding how to combine NMOS and PMOS gates could use a better intro. Once I knew the answers, I got my brain to reset to my VLSI course from college, but I think a better primer could've accomplished that. In other places, I feel like we get more refreshers on some components than others.

* The routing algorithm needs to be better. I get a lot of staircase wires and straight up overlaps.

* Right clicking should clear attempted connections.

* There should be away to delete components you've placed. Maybe I just couldn't figure it out.

* I think icons should be included on the components pane. I kept clicking NOR when I wanted NOT and a better visual cue would have helped.

* It feels like difficulty is all over the place. Perhaps this is corrected with better explanations, but creating the NAND gates and NOR gates were much more difficult compared to AND and OR. Perhaps actually having us construct those gates without NOT would change the difficulty curve.

* The success overlay shows up too fast. Especially on levels that are just a demonstration (like the NMOS and PMOS Again levels) you don't get to to see everything the level is trying to demonstrate before the level announces that you have succeeded.

* In the intros, when there are new components, their description pops in. Instead, it should just advance like a slide. It's very jarring.

* Also, it's unclear that those aren't part of the intro. Maybe instead of popping them up, flash the little information icon next to them.

* What you call a capacitor I believe is actually a combination of a transistor and a capacitor. I think people will be hard pressed to find documentation on a capacitor with an enable switch. But, then you use this same capacitor to form a 1T1C cell. I'm rather confused.

* Many times when I finished a level, the circuit would switch to a prior level's solution.

* Some components have the same letters for every terminal (e.g. half-adders), meaning you need to scroll over the terminals to know what they do.

* Some levels have many test cases, and there's now way to see them all.

* Level 2.3 talks about us having registers, but we never covered those. In fact, I think we're still a ways away since we need to get from switches to flip-flops then to registers.

There isn't much order to this. Just what I recorded while working through it. Overall it's pretty good, I just think polish would got quite a ways.

Thank you for sharing this! I'm really excited to get to the more GPU specific parts. I basically did this for CPUs in college and I'm excited to see what preconception and missing conceptions I have for GPUs.

The continue buttons in intro break for me all the time on Firefox. I can't actually finish most of them.

I think Hacker News auto-title editing has caught this one. It's actually "Your Code is Worthless". It dives into how lines of code has become a productivity metric once again, what actual metrics should be used, and how AI is not holding up to those.

For those looking at this, this role is only in Mexico.

    Location: Colorado
    Remote: Yes
    Willing to relocate: No
    Technologies: CI/CD (GitLab, Jenkins), IaC (Terraform/OpenTofu, Ansible, SaltStack), Cloud Infrastructure (AWS, DigitalOcean, Azure), Containerization (Docker/Podman, Kubernetes), Observability (Grafana, ELK), Systems & Networking (Linux, Systemd, Nginx, Networking Architecture), Languages (Python, Bash, Nix, Go, and more)
    Résumé/CV: https://drive.google.com/file/d/1kBuqYtQsNDTpq6_UBO9gY589mqyeq2_G/view
    Email: joshua <dot> m <dot> holland <at> gmail <dot> com

In my early career, I maintained legacy build and delivery systems while transitioning organizations to modern tooling. At my most recent role, I built those same systems and production infrastructure from the ground up, while simultaneously finding and filling unidentified organizational gaps: legal compliance, IT, and customer support.

My experience spans IC work, legacy system ownership, and greenfield development, in close collaboration with both technical and non-technical stakeholders. I am ready to lead teams and grow the engineers within them.

If you're looking for a technical leader to head up your DevOps/SRE/Infrastructure/Platform team, or to shape engineering at the organizational level, I have the experience and the tenacity to get it done.

You do your due diligence beforehand and realize this is a bad use of your money.

FYI, in your reproduction, both of the conditionals are the same. But you are right, the initial implementation was `!=`

    while [[ $SECONDS != $1 ]]; do

    while [[ $SECONDS -lt $1 ]]; do

Didn't Brother start pulling this same stuff? I recall hearing something along those lines and blocking mine from talking to the Internet.

A slippery slope is only a fallacy if there is no demonstrated history of it existing. I think we're all aware that that is not the case for surveillance laws.

Can you explain what you find complicated about sops? I've used it with ease for the last two years, both personally and professionally.

You continue to use it for something else? How is it different from any other default shortcut you don't line and change?

The author points out that Apple defaults often don't allow you to reuse them. They talk pretty far in the article about how that can't map globe+H to a different function. So, this theoretical is about them not being able to continue using their combination for what they want at Apple's whims.

It also applies to application providers. The law requires them to have their applications ask the OS how old the user is whenever it is downloaded and launched.

Far narrower is doing a lot of heavy lifting in your response.

(c) “Application” means a software application that may be run or directed by a user on a computer, a mobile device, or any other general purpose computing device that can access a covered application store or download an application.

If your device can connect to a covered application store, every application on your computer must follow this.

That's not a guarantee. It's up to how the courts interpret that and. Given that this law is meant to handle a moving target like age, I fully expect them to interpret it as its disjunctive form.

Two important definitions that might surprise people:

(a) (1) “Account holder” means an individual who is at least 18 years of age or a parent or legal guardian of a user who is under 18 years of age in the state.

(a) (2) “Account holder” does not include a parent of an emancipated minor or a parent or legal guardian who is not associated with a user’s device.

(i) “User” means a child that is the primary user of the device.

User is the most surprising here. It really should just be minors, or non-emancipated minors. Further, I think there are interesting ways the definition of account holder and user combined play out in interpreting the rest of the law.

Colorado is trying to copy this law right now, too.

As others have pointed out, this is just a foot in the door. There's also a part of the law this article doesn't cover that requires EVERY application to query this information on every launch, regardless of whether or not the application has any age related limitations.