I think this is wrong about what “sensitive” means here. AFAIK, all Vercel env cars are encrypted. The sensitive checkbox means that a develop looking at the env var can’t see what value is stored there. It’s a write-only value. Only the app can see it, via an env var (which obviously can’t be encrypted in such a way that the app can’t see it, otherwise it’d be worthless). If you don’t check that box, you can view the value in the project UI. That’s reasonable for most config values. Imagine “DEFAULT_TIME_ZONE” or such. There’s nothing gained from hiding it, and it’d be a pain in the ass come troubleshooting time.
So sensitive doesn’t mean encrypted. It means the UI doesn’t show the dev what value’s stored there after they’ve updated it. Not sensitive means it’s still visible. And again, I presume this is only a UI thing, and both kinds are stored encrypted in the backend.
I don’t work for Vercel, but I’ve use them a bit. I’m sure there are valid reasons to dislike them, but this specific bit looks like a strawman.
Your comment made me ask myself: "Then why remove it? If it really is just a system prompt, I can't imagine tech debt or maintenance are among the reasons."
My best guess is this is product strategy. A markdown file doesn't require maintenance, but a feature's surface area does. Every exposed mode is another thing to document, support, A/B test, and explain to new users who stumble across it. I'm guessing that someone decided "Study Mode isn't hitting retention metrics", and decided to kill it. As an autodidact, I loved the feature, but as a software engineer I can respect the decision.
What I'm wondering about is whether there's a security angle to this as well. Assuming exposed system prompts are a jailbreak surface, if users can infer the prompt structure, would it make certain prompt injection attacks easier? I'm not well-versed in ML security, and I'd be curious to hear from someone who is.
> If only it wouldn't collapse by itself after clicking anywhere (clicking seems to activate physics) this would be 10/10
I think that's the other metaphor here.
It's not just standing on the tiny shoulders of one forgotten maintainer. The entire system only appears stable because we're looking at a snapshot of it.
I don't have any specific suggestions, but I do want to give thanks for implementing functionality to block pushes if the email field is *not* using an anonymized mail address.
It's one thing to offer anonymous e-mail addresses, but it's also awesome that GitHub can help prevent mistakes that would otherwise leak a user's e-mail address. I am not sure how many people try to be privacy conscious on GitHub, but I assume most users don't, so it's nice seeing this little feature exist.
You would think a trillion-dollar company could use its resources to build something useful and move the technology forward with something like a new file system with versioning or a global file system, or updates that don't require a restart, maybe immutability of some sort, something useful for a change.
Instead their breakthrough feature is a tool that takes a screenshot every few seconds and fills up the drive space, sigh. And they even couldn't get that right on the first try, the first version was a privacy nightmare.
> Anticipate more mid-size and smaller companies will go back more fully into the office as times get tougher. This will not be one size fits all, but will be an increasing trend.
Up to this point in the article, whether you agree or disagree with the points, the author offers some arguments and reasoning supporting each. Here, they simply assert that small and mid-size companies will go into the office, with no supporting argument. Why? Won't many small and mid-size companies have come up under covid and not have an office lease in the liabilities column? Why would they pay (insert large city) rents to save money? How does it help?
