ivan888

Unfortunately this won't help those who add dependencies based on shared snippets, without the context of a project. Or the innocent mistake (or choice?) of not checking the lock file into version control. But yes good point, existing projects that have checked in the integrity file will be safe against future malicious modifications of the resource

> URL-based imports (no need for NPM)

What happens when there is the next Codehaus-like shutdown, and so much source code just won't work? Or when a bad actor takes control of a domain that commonly hosted packages (perhaps through completely legitimate means, such as registration expiration), can get a completely legitimate SSL certificate for it, and responds to requests for packages with malicious code? I think the abstraction, and to some degree the centralization, of package management is generally a good thing

I think you took the wrong tone from the parent comment; it sounds like this person was genuinely interested in sparking a real conversation about how people feel about the environment that they spend time in, and whether that could have dramatically shifted based on what they decided to or had to learn

The process of properly reporting and working with authorities seems daunting. (Anecdotally,) It sounds too easy to implicate yourself for a technical violation of the law by (even unknowingly) hosting this content, or accidentally transferring it to one of your personal devices. Much worse following the advice of your local police to print out images which would be completely illegal! On the other hand, if the process was too lenient on reporters, hosting a file sharing service that "gets abused" with illegal content might turn into the ultimate scapegoat for illegal content users/creators/brokers

Nice job going through the reporting process and I'm glad you blogged about it to share with others

It might lead to: someone who wasn't careful enough to use one of those options, identifying metadata in the file, etc

I posited a similar point to a former colleague (mine was more about eventual market dominance due to excellent UI+UX), and he came back with Craigslist as a perfect example of a product that gained a massive user base well into an era where its UI felt very outdated. A few years after this exchange, I feel more like I was right about my point: FB Marketplace has almost completely taken over as far as a classified product marketplace, but the point still stands that Craigslist was able to do a ton with very lackluster UI+UX

One of the better examples still seeing widespread mainstream use is email, and this even applies to multiple stages throughout the email ecosystem: sending mail, receiving mail, managing mailboxes. Imagine if email wasn't cross provider compatible

There's no real reason for it to annoy me so much, but I was just thinking about how I can't stand when people seemingly randomly capitalize words relating to technology without the intention of drawing emphasis to them: GIT, NODE, JIRA, JAVA... why??

Just being able to go out into the social world without a plan is something I miss a lot. It feels like every time I leave the house now, I have a very direct objective and I try to accomplish it as quickly as possible with as little human interaction as possible

Just submitted one of my favorite videos on basic electrical.

Feedback:

- What happens after submission? I'm assuming it goes into a review queue, or caching is involved so I'm not seeing it right away. Maybe make it clear if there is a review queue after submitting

- More detail around what the skill levels mean. I wasn't really sure how to choose. I consider it beginner, but I also saw other videos I consider beginner marked as intermediate

Did anyone else think the page starting with "To access the petition form itself, you must view this page while logged in" might be some kind of a parody on FSF's part?

Even if I need to log in to submit it, at least show me a preview...

Cool library, the type guards look interesting. Too bad it's not more automatic but yeah it's not very much extra code

This makes sense; but it still doesn't feel like the right answer. Facilities should exist for runtime type checking based on TS definitions, and syntactic features should enable a 'hard check' of the actual object when necessary

I also don't understand 4. This looks terrible. Why use TypeScript if we have to make very manual assertions about the structure? Isn't that the purpose of TS itself?

Downvoters: explain? Maybe this suggestion is aimed too much at a specific piece of technology (Docker). But there are plenty of tools out there to create reproducible builds, which I think is the overall point of this response

This seems to be highly variable depending on the locality that holds the records. It does not seem to be standardized in my experience.

Even after expungement where possible, there can be problems with records being inappropriately cached by background check services, and a background check after expungement may still show the conviction. Yes, this can be appealed, but still puts an undue burden on the applicant and may ultimately be a deciding factor between similar candidates even though it should not be used

Really want a way to have vi-mode input in all text inputs throughout the OS, hopefully that is a future possibility