Now, we might have had good reason to pursue a plan that cost us money, but in general, threats to our funding are effectively threats to our existence.
717 karma · joined April 10, 2025
Now, we might have had good reason to pursue a plan that cost us money, but in general, threats to our funding are effectively threats to our existence.
Citation usually shows the claim was right? Mix of right and wrong, say 60%/40%? Usually wrong? Citation often doesn't exist or is not relevant to the claim?
(I don't often use the AI answers, but the few times I bother to check the citations, they usually don't fill me with confidence about the answer.)
after 3 years
and 40% after 5 years.
However, we need a better solution than pop-up warnings. I guarantee that you have clicked through a pop-up warning that was standing between you and the thing that you wanted to do (as have I, and everyone else who has used a computer for more than a day). We very quickly learn that most warnings aren't going to affect us, and that they're just saying "are you sure" to things that we're already sure of.
We've all selected a file, hit the delete key, got the pop-up saying "are you sure you want to delete wrong_file.txt", hit "yes" (because we always have to hit yes after hitting delete), then looked at the outcome and thought "oh, that was the wrong file" too late...
By default, F-Droid provides only the applications that they themselves have verified and built from source. They also allow the user to add other sources from other parties who the user trusts (e.g. GuardianProject, IzzyOnDroid, and others[0]).
Google provides any application uploaded by any anonymous third-party who signs up as a developer (and in future, provides the required ID).
True they might not all be "dramatic lessons" for us, but to ignore them and assume that they hold no lessons for us is also a tragic waste of resources and hard-won knowledge.
This seems to fundamentally underestimate the nature of most artforms.
The only supported 2FA is the bank's own dedicated 2FA app.
The OP's point is, having the firmware permanently burnt-in on a ROM chip vs loaded as a binary blob via a driver doesn't change the "non-free"-ness of the firmware itself.
So opting for hardware which has a "fully-open-source" driver, but runs a binary blob encoded into the hardware, doesn't make the system fully open.
It's a take for a more Free system, not for accepting binary blobs.
(Or I guess for acknowledging that if you're willing to allow binary blobs stored in hardware, then dynamically-loaded binary blobs doesn't change the "free"-ness.)
I had the same initial thought, but I was skimming the page and came across this line:
> Then, see how to deploy a Flask+HTMX app via Granian, wire it into NGINX, and ensure automatic startups with systemd.
So I've just discovered that https://github.com/emmett-framework/granian exists...
> And how can TV retailers make money in this situation? Did they expect to keep charging $500 for a TV that’s now really worth $200, and pocket the $300 difference?
> Why, then, is Ed Zitron having such a hard time when it comes to LLM inference? It’s exactly the same situation!
The AI situation is not analogous to one where the TVs initially costed $450 to manufacture and the stores were selling them for $500, then the manufacturing cost went down.
The equivalent TV analogy is that we're selling $600-cost TVs for $500 hoping that if people start buying them, the cost will drop to $200 so we can sell them for $300 at a profit. In that situation, if people keep choosing the $600-cost/$500-price unprofitable TVs, the existence of the $200-cost/$300-price profitable TVs that people aren't buying don't tell us anything about the market's future.
---
In the AI scenario that prompts all the conversations about the "cost of inference", the reason that we care about the cost is that we believe that it's currently *ABOVE* what the product is being sold for, and that VC money is being used to subsidise the users to promote the product. The story is that as the cost drops, it will eventually be below the amount that users are willing to pay, and the companies will magically switch to being profitable.
In that scenario, anything which forces the cost above the revenue is a problem. This applies to customers choosing to switch to more expensive models, customers using more of the service (due to reasoning) while paying fixed rates, or customers remaining on free plans rather than switching to affordable profitable paid plans.
The AI Hype group believes that the practical cost of providing inference services to users will drop enough that the $20/month users are profitable.
The AI Hype group's argument is that because the cost per token is coming down, that means we're on a trajectory to profitability.
The AI Bubble group believes that the practical cost of providing inference services to users is not falling fast enough.
Ed's argument is that despite the cost per token coming down, the cost per request is not coming down (because requests now require more advanced models or more tokens per request in order to be useful), so we are not on a trajectory to profitability.
Only DSEG7 has lower case letters, and that's probably only to distinguish them from other characters or numbers (e.g. h/X, i/1, or o/0).
Good one, it took me a moment... :-)
I open the hood and add a resistor across the input sensor so that it thinks I'm going 20% slower than I really am.
I start driving at 60mph.
How does society enforce the speed limit regulation against me? (Hint: the threat of, and eventually the use of, violence.)
Because if I understand correctly, you don't queue the requests and then perform a single request/response cycle (a "round trip"), you send a bunch of requests as they happen with no response expected, then when an await happens, you send a message saying "okay, that's all, please send me the result" and get a response.
An alternative is "using a server that the user has", e.g. saving to their iCloud/Dropbox/Google Drive/GitHub/etc.
(There used to be old notes applications which would save your notes in an IMAP folder on your email server; almost every user of your app will have email.)
If you need to scale writes.