numbsafari

Call the police. That’s wire fraud and theft.

Does openAI not support spending caps on your billing account?

For the vast majority of people, without much technical capability, “moderately messed up” is functionally equivalent to “bricked” as a purely technical slang term.

… from the fine print:

“Results are compared to previous-generation Mac mini systems with Apple M4, 10-core CPU, 10-core GPU, 32GB of unified memory, and 2TB SSD.”

...and Han Dynasty only exists in Philadelphia.

Maybe it wouldn't matter either way if people stopped putting untrusted executable code into basic build processes.

You could get rid of a huge portion of the go standard library and have a massive ecosystem of leftpads, but the fact that `go build` can easily be run in off-line mode and doesn't execute any code other than the go toolchain itself, means you have a fundamentally more trustworthy ecosystem overall.

Rust, on the other hand, might keep you from a subset of buffer overruns, but it will gladly run obfuscated, untrusted code in your name when you wouldn't otherwise expect it to.

As an industry, we need to somehow stop making this mistake.

A person bumps into at the train station. They just need $5 to get home. Could you just spare them $5? They had the money, but they lost their wallet and now they just need to get home.

Charity scams are nothing new.

Perhaps it elicited enough sympathy to get donations. Did it ever provide proof of actually running up an AWS bill?

I too have see the fnords

Exactly. Considering you could buy an iPhone and a MacBook Neo for roughly the same cost … will be very interesting to see this device in action. Can iOS replace MacOS for a user that doesn’t need a local Xcode? Can I spend $2k for the device I use in my pocket and on my desk… and put the rest of my money into cloud/server infrastructure if I have that need?

Wouldn’t it be nice if services like Codespaces or Coder or Gitlab would allow you to target running on their hosted/integrated platform, or let you launch that same container completely locally? Sometimes I wanna take my “remote” dev environment off-line but still benefit from the integrated UX.

.. and here I am wanting better minivan options that can pull a travel trailer.

This is how I grew up. Using fidonet via my local RPGA group.

How many times are they gonna double count the insurance a property taxes?

“Just pixels on a screen”

What is wrong with you?

These are teenage girls, not adult men. This isn’t graffiti, but highly realistic sexual depictions.

There’s a massive difference.

Do explain the Somalia connection you perceive. Please, go on…

Throwing it away after single use is madness.

It’s actually both.

Are you aware of non-GPL FOSS licenses?

Umm… zed supports remote dev over ssh… what’s your concern?

I would have assumed the opposite is true. Do you have any data to back that up?

Tools growing unexpected code execution is how we keep having problems with secrets and other important things being stolen. If you add this feature to git, generally, then anybody cloning a git repo is going to have to deal with the fact that `git clone` might run arbitrary code. `git clone` is like `cp`. Do you want `cp` to unexpectedly run code? It should never do that.

Why force git to be a build tool?

Just document how to execute the scripts/checks that will be used by ci. Provide a simple script in the repo that folks can intentionally execute.

How are you storing the API key in your database?

Go to an ER or UC and have them dress a wound for you. They will use a healthy dose of petroleum jelly and generally tell you to stay away from antibiotic ointments.

... because if _use_ of a product creates a liability for the maker, you are very quickly headed toward liability for gun manufacturers. [ed: this is very much discussed in the decision, by the by]

Expect to see heavy lobbying from the music and video industry to create some kind of "Know your Customer" regime internet service providers in order to create such a liability.

I wouldn't call this a slam dunk for privacy or liberty, given what it is going to force the various actors to do in response.

For now, though, let the file sharing flow!

Ask Claude

There's clearly a change going on in the US government, and it very well may be that organizations such as Mozilla, FreeBSD, and Apache could all lose their 501(c)(3) tax exempt status in years to come.

At the end of the day though, 501(c)(3) status is a purely US concept, doesn't apply to international organizations internationally, and doesn't necessarily mean that you "can't" do what anyone is discussing here. It just means that folks gonna have to pay taxes and "donations" can't be written off on the taxes of donors.

Perhaps, at the end of the day, not pursuing tax-exemption/charity status is a more honest approach. It certainly doesn't precluding doing any of what has been discussed, it just changes the financial efficiency.

> The goal of this "faculty" would be sustainable OSS maintenance (which involves both leadership and contribution), rather than publishing research and teaching classes.

OSS isn't commercial, per se.

Universities "ship" plenty of "products":

https://www.rcac.purdue.edu/services/hubzero

https://www.scala-lang.org/scala-core/

Using the model of the university and various tenured profs, I'm not sure what you are saying is true. But, perhaps it's a misunderstanding of what I was intending.

I see this more as a way to answer the question of things like the maintainers of OpenSSL or sudo. One approach is to fund the "project" and let it deal with all of these questions. Another approach would be to fund the people themselves. So, have a faculty of expert software maintainers, vetted by the governance structure of the OSE. Within that faculty, you could have "adjuncts" and "residents" who have a time-bound grant and set of obligations. If they are successful and their work continues to be relevant, they could eventually apply for one of a defined set of "tenured" positions. Those positions would guarantee them independence and a stable source of income in order to continue their role as a maintainer.

The goal of this "faculty" would be sustainable OSS maintenance (which involves both leadership and contribution), rather than publishing research and teaching classes. So, similar overall structure and approach, but differing goals.