turdnagel

The "low level" way is - you can use a web3 library like web3.js or ethers.js to let the user connect their MetaMask wallet. You would have to expose your wallet address and make a call to `sendTransaction`.

Could be uPnP setting up port forwarding

I'm genuinely curious to hear Sam Altman's (and/or the OpenAI team's) perspective on why these products need to be waitlisted. If it's a compute issue, why not build a queuing system? If it's something else (safety related? hype related?) I'd love to understand the thinking behind the decision. More often than not, I sign up for waitlists for things like this and either (1) never get in to the beta or (2) forget about it when I eventually do get in.

Twitter doesn't have "free speech policies". It has moderation policies. They're not enforced evenly, but no platform has solved this.

It sounds like you're agreeing with OP, who said a bad test is worse than no test. Isn't that what you're saying too?

This is a great letter. My favorite piece of writing from Albini is "The Problem with Music" [https://thebaffler.com/salvos/the-problem-with-music] in which he explains how record companies were screwing artists in vivid detail, numbers included. The first two paragraphs alone are worth reading.

Apple's philosophy around high pixel density is to be able to run at a scale factor of 2. (Or close to 2 on mid-2010s Apple laptops, or sometimes 3, as on newer iPhones.) That way everything is physically the same size, but looks a lot nicer. Mac users running 5k monitors aren't running 5120 x 2880, they're running 2560 x 1440 at 2x.

Had a very similar experience in philosophy classes. The good thing about critiquing seminal works is that there's often a rich body of criticism already available. I found the only way to do well in those classes, since I lacked the mental horsepower to produce my own seminal critiques, was to parrot the literature that was out there already.

I've never heard of an accusation of planned obsolescence based on price before.

> A customer with 1TB will likely want to upgrade sooner

Though I have no data to back it up, I think this is your mistaken assumption. I think it's much more likely that people upgrade because of CPU/RAM than disk space.

A meta comment on the comments on this article: as one might expect post-"goto fail"[1] there are a lot of people saying "hey this should be refactored, no goto!" I thought that at first when looking at the code, given what I remember of the Apple SSL vulnerability, and how "goto" has a smell. But, as it turns out, there are sane reasons to use goto in systems programming, especially as a kind of cleanup / finally block. TIL.

[1] https://news.ycombinator.com/item?id=7282005

What is it with this headline? Tesla is deploying new firmware OTA. No vehicles are being recalled. If deploying new software is a "recall" then I do recalls dozens of times a week.

The running timer is unnerving. Is there a way to disable it?

Thanks! I just switched to Premium Lite. I don't use downloading very often, and I never use YouTube Music or background viewing, so I think this is perfect.

Great - now they should lower the price of YouTube Premium to be in line with other streaming services.

It looks pretty cool during a rack focus, but I agree, it's definitely used to give a filmic look but gets tired quickly.

Thank you for sharing that. I just watched the 2018 UHD Blu-ray and compared with an earlier Blu-ray 1080p release. To my eyes, everything is shifted to be a bit more blue, not green, and specifically in the skin tones. There is definitely a tint in both versions, but skin tones aren't as affected in the earlier versions vs. the later ones.

You're right, but that's not always true, and there's plenty of good use cases where a conversational experience is better. For example, if someone is trying to return something, you might ask them what they ordered. Picking from a list of 1000 items isn't a great UX. Datepickers are way more annoying to use than typing in "Jan 6 2022". The best chatbots I've used (and built) alternate between more a button-like interface vs. eliciting conversational answers in the appropriate context.

I'm pretty sure that GPT-3 and statistics-based approaches to bots aren't going to be truly convincing anytime soon. But there's another definition of "chatbots" that consumer-facing brands use every day to triage questions, attempt to answer them using good but not mind-blowing ML, and then escalate to a human being if/when the problem can't be solved. There is already a thriving market for these "dumb" bots that aren't attempting to have an uncanny valley type conversation - they advertise that they're bots upfront, don't try to be too cute, and provide the escape valve to a real agent when necessary.

How do you pronounce your company's name?

I did not see the film in theaters as I was 12 at the time, but I racked dozens of plays of the DVD version, which has the green tint and looks "correct" to me.

(Edit: Apparently the 1999 DVD did not have the tint, but I that's not what I remember...)

It would be interesting to do a comparison between the green tint version and the "untinted" / neutral without the issues with highlights/whites.

Looking at your calendar, you had no time for bathroom breaks, lunch, time to reflect & recharge, etc. I would expect by the end of the day you were pretty tired. While you probably got the structure of the meeting pretty down pat by the end, don't you think your ability to evaluate may have been affected by the number of meetings you were taking?

I also had a similar experience in college, but I'm having trouble understanding what the lesson you learned was. Did you eventually improve?

See also Dr. Seuss' seminal "The Sneetches".

Does anyone else find those map zoom-ins incredibly disorienting? Kudos on solving this complex technical challenge, but I'm not sure the end result is as "smooth" as described.

How good is Chipsynth OPS7’s emulation? https://www.plogue.com/products/chipsynth-ops7.html

Two principles I see at play here are fluency (a mapping between a desired action and the physical action of using a tool) and parsimony (building something in the simplest or cleverest way to achieve the goal). You get fluency through practice and the parsimony comes through experience, a kind of wisdom - similar but I different concepts.

With software engineering, I think when you're comfortable with the syntax and capabilities of the language you're working with, you get fluency. And then once you have experience using the standard library and some common external libs, you learn parsimony.

Good article. I feel very comfortable doing this with code and not so much with physical material, where the constraints are much more imposing and the risk of screwing something up is much higher.

Based on my experiences with programming, I imagine part of being able to think this way is also having experience building things physically. The fact that I can think about connecting pieces of backend infrastructure, or bits of reusable code, or a wiring up a handy library to solve a problem is from experience solving problems with the tools at hand.

Probably the best way to get started with this mindset in any problem domain is to just start making things, getting a feel for the capabilities of tools, the strengths of various materials.

In other words, the attitude adjustment is just one part of being able to solve problems this way - you've got to be very comfortable with your tools and materials, or have little to lose so you can experiment safely.

Yes, CloudFlare has software, and I think that only further highlights the difference between a complex cloud provider and a piece of software. What good is CloudFlare's software without the vast global network to back it up? Pick a problem, though, and there's probably an open source solution though: CockroachDB for global HA dbs, there's a bunch of containerized drop-in S3 API replacements, etc. But something tying them all together requires a lot of ops work that you don't get through software alone.

On the one hand, I hear what you're saying. You root for the underdog long enough and they end up becoming the dominant player with the power to match. But this feels like a pretty apples-to-oranges comparison to me.

Cloudflare has to buy, operate, and maintain huge amounts of servers with lots of hard drives, plus all the fiber/copper connecting them across the planet. Linux and HTML are software. They're only "decentralized" in the sense that they don't physically exist anywhere the way that a cloud provider absolutely must.

Really, that's not what this lawsuit was about, and the courts aren't supposed to tip the scales based the size of companies, are they? It's clear we need new laws to deal with the problems at hand. The ruling seemed pretty even-handed based on the law, even if you disagree with it.