> 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 considered getting idontuselinked.in, but Porkbun let me know that the Indian registrar can be difficult to work with. I could be convinced to get it as well.

Comments URL: https://news.ycombinator.com/item?id=47710178

Points: 11

# Comments: 6

* 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.

    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  m  holland  gmail  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.

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

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

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.

> (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.

(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.