HN user

nathantotten

943 karma
Posts8
Comments138
View on HN

I think this is the wrong read on the “threat”. One user going out of their way to spent time writing this post is a canary in the coal mine. Most users never give feedback, they just churn. This is the same reason your toothpaste has a phone number on the back - that one random person who cares deeply calls the number and provides invaluable feedback on the product.

It’s not about the one person, it’s about that person representing tens/hundreds/thousands of customers. This feedback is a gift to a product manager that listens.

Some states in the US have banned cell phones or other devices that can connect to cell networks. In our school district at least can connect is the key. Teachers aren’t going around testing if old iPhones have SIM cards so all iPhones are banned. (To be clear, I don’t except them to do that.)

Seems like a lot of kids would love iPods to listen to music at school like we did when I was in high school.

Thanks for checking it out. The focus of Zudoku is on making it super easy to ship beautiful API documentation. There are tons of alternatives, but we didnt feel like anything out there met our bar in terms of design and ease of use.

Zudoku is also the basis of part of our product (zuplo.com) offering so it is extremely extensible. Our managed, hosted version builds on the extensibility of Zudoku to add additional capabilities like API Key management, analytics, etc. Anyone can use these extensibility points to add their own custom capabilities.

People don’t build applications on Salesforce because it’s a generic platform, they build on it because they need to integrate with the sales/crm process/data/etc.

Edit: To be clear, I’m not saying your idea isn’t good. There is tons of room for this stuff, but be careful in assuming the reason devs use Salesforce platform is because of the features. It’s usually not.

Source: I ran dev tools at Salesforce.

The last time I went to Woodcraft, the guy there was raving about the CNC and recommended I get one. Hard pass. Woodworking is my escape from computers. I’m sure if you do woodworking for a living a CNC is amazing, but I’ll take the slow path on this.

From Nate Silver: “This article is full of terrible statistical logic. Yes, it's hard to exactly quantify the risk of a highly deadly nuclear accident. By nature, tail events are rare. There is intrinsically some guesswork. But empirically the chances are very low.

The author also blatantly cheats by counting Fukushima as 3 separate accidents, as though they occurred independently from one another and didn't have a common cause like oh I dunno a magnitude 9 earthquake.“

https://twitter.com/natesilver538/status/1558530091860336640...

While they don’t specifically say what the “language server” is, if it’s the same protocol that powers VS Code[1], this is a big deal. It potentially means that language owners can build tooling that works across IDEs much more easily. Historically, JetBrains seems to have resisted the idea of a standard language protocol (which makes sense as it comes from Microsoft). My guess is it’s becoming impractical to reimplement every language feature for Typescript, C#, Go, etc. Embracing the standard LSP will mean less time spent on low level features and more time building JetBrains only value add.

[1] https://microsoft.github.io/language-server-protocol/

I think if somebody gets creative about it some of that cost can be reduced. Likely the big drivers in cost are going to be running utilities to support different uses (kitchens, showers, etc.) Maybe a new type of living space can exist where kitchens are shared? Or where there is a gym with private spa-like shower/changing space on a lower floor. I'm not saying these are good ideas (I certainly wouldn't live in that sort of place now), but maybe somebody can figure it out.

Longer term this will also likely accelerate servers running on ARM. Writing software on ARM laptops that are deployed to production servers running on x86 servers will start to cause a host of new challenges. The switch to running ARM in production will have many advantages for developers and will likely be very attractive to cloud providers (AWS, Azure) as the costs of electricity for these servers may be significantly less.

Code Builder is a web-based development environment fully optimized for Salesforce development and powered by Microsoft’s Visual Studio Codespaces.

I’m not so sure about that. With enough dedication and time I think you could target a specific company from HN. Start writing a few good blog posts that would appeal to your audience, only run attack when some attribute is true to that company (i.e. their Corp IP addresses).

You could even combine the two. Post the blog to hacker news, then send phishing email pointing to HN post. That is a trusted link. Then the user will likely click the source link in HN.

Obviously, a lot harder and lower chance of success, but not impossible.

I know you’re not being precise, but the term “backed” is not valid. For a currency to be “backed” or more accurately commodity backed currency, you must be able to exchange that currency for that other thing. I.e. money for gold. You can’t get the electricity back in exchange for your bitcoin. :)

Completely agree. With HDMI-CEC and moving off of old Campos it is the only remote used in our house and nobody ever asks me how to do X. They click it, everything turns on and the navigate to the thing they want.

A bit of rubber on the lower half so could feel up from down would be my only change.

With a single random password most people will write down their password, so anyone who can read what was written down gains full access. With a random username and a user-chosen password most people will write down their username but not their password. Clearly this approach is more secure.

I don't believe this is grounded in evidence. You are basically saying that given two hard to remember strings, most people will write down one hard to remember string and not the other hard to remember string. Why?

I don't see how relying on haveibeenpwnd can be considered secure. Many people use the same password for different sites. If your site's login credentials are just email+password you are relying on the security and honesty of all other sites that use the email+password combination.

I think you are missing the point of the haveibeenpwnd service. The point is to block people from using ANY password that is listed in the haveibeenpwnd database, thus denying attackers from using that dictionary of known passwords.