(But it's a big enough story that I'm glad to see it on front page again.)
14,561 karma · joined May 23, 2010
Email me: islands_message_0v@icloud.com (Apple relay to avoid crawlers pulling my email from here)
(But it's a big enough story that I'm glad to see it on front page again.)
Are you suggesting it's not intuitively obvious that the town 'Towcester' should be pronounced the same as a "toaster" for toasting bread?
Reading other comments like this one - https://news.ycombinator.com/item?id=47031715 - it seems like there isn't enough data for there to be typical expectations, but that it isn't uncharted?
You're drawing a connection that's not there. It's indeed not a coincidence, but just because both situations fit the definition of the word "user" (and "to use").
People use drugs, whether they're addicted or whether they're taking a one-off dose given to them by a doctor. They are a customer in that situation if they're buying the drug from somebody (illegal dealer, pharmacy), but they're a user whether they paid or not.
Likewise, someone is a customer if Apple's if they paid for, or are expected to pay in the future, a device or service. But they're a user regardless of whether they're using a phone they bought, or a service that's being provided for free.
People can use services provided by charities, they can use skis on a mountain... there's absolutely no negative connotation to its general definition, it just happens that some things people use are bad and some are good.
But I disagree that that makes it for snobs. Snobbery is more about an attitude of looking down on others or their tastes, whereas knowing Latin or being a fan of opera is really just about exposure.
Sure, there exist some (too many) opera fans who would say something like "it's real art compared to pop or hip hop being low class trash", but that's not a defining part of liking opera and plenty of people who like opera aren't snobs. Ironically it's a different form of snobbery (sometimes called reverse snobbery though personally I hate that term), to dismiss anyone who learned Latin or who likes opera as being a snob!
When you said "a coin can never be worth less than the metal it contains", I think you meant "no matter what number is on the coin, its value is always equal to or greater than the value of the metal"; but dredmorbius misinterpreted your comment thinking you meant "the number on the coin must always be a higher value than the metal would be worth if it wasn't shaped like a coin".
AKA when carlosjobin wrote "be worth" you meant "value to sell", but dredmorbius thought you meant "value written on it".
I might be wrong, maybe it's me misunderstanding one or both of you - in which case please correct me - but I'm fairly sure you're both correctly thinking the same thing while incorrectly thinking the other person isn't.
Edit: I wasn't going to say anything, but then noticed you're the same person I was replying to before, so I will since it's more than once - in both your comments you seem to feel that you need to defend Wikipedia but in both cases there was nobody attacking them :)
I appreciate that internet comments can often contain lots of hostility, but I encourage you to remember that it's not a default state, and that often comments are just good faith opinions without an angry subtext. In both cases you could have just written as if adding some interesting information, rather than as if you're countering an anti-Wikipedia campaign. (And I'm not trying to attack or criticise now either, sorry if it comes off that way - just constructive feedback!)
Is supertonic the best sounding model, or is there a different one you'd recommend that doesn't perform as well but sounds even better?
To me it seems a perfectly natural effect of nearly everyone using it as a website which holds lots of information, and very few people comparatively have any experience with the community side, so people assume that what they see is what Wikipedia is.
Not many people are spending time reading reports on organisation costs breakdowns for Wikipedia, so the only way they'd know is if someone like you actively tells them. I personally also assumed server costs were the vast majority, with legal costs a probable distant second - but your comment has inspired me to actually go and look for a breakdown of their spending, so thanks.
Edit: FY24-25, "infrastructure" was just 49.2% of their budget - from https://meta.wikimedia.org/wiki/Wikimedia_Foundation_Annual_...
It's fair enough to decide you want to just stick with a single provider for both the tool and the models, but surely still better to have an easy change possible even if not expecting to use it.
Are you suggesting that docker provides an (unspecified) edge to developers who are better than average? Or to those who are mediocre? Or...
Even when it comes to superiority of physical military forces, different people (with a range of different biases) have different opinions on stuff like whether a hot, all-out (but non-nuclear) war between USA and China would prove one or the other to be stronger, and while you may read that and think "I know which side is better and anyone who disagrees is just buying into delusional propaganda" at least to form that view you've had the ability to follow a lot of publicly available details on military developments over the years, learning about current and next gen fighter jets, drones, ships... etc.
But when it comes to cyber stuff, both offensive and defensive, it's generally a lot more secretive in terms of stuff that's actually been done (see for example the speculation in this thread that US power grid failures in recent years might have been caused by foreign adversaries - there's no evidence that's true, but if the US and China had both spent the last decade trying to take offline as many of the other country's power grids as possible we likely wouldn't have heard about it). Yet alone for hypothetical but saved for war capabilities. If a hot WW3 broke out tomorrow, who actually knows what hacking tools any country (from superpowers to smaller players) actually has, waiting to be used? Presumably they all spend a lot of effort trying to learn about each other's capabilities, and maybe they're successful enough that they actually do all know most of what everyone else can do - but they don't then announce that the way we hear about North Korea testing a new missile or about America developing a new fighter jet. I feel like we the general public just have no idea how advanced or not wartime capabilities might be. Am I wrong? (I may well be, as I'm in no way an expert in this field; I just believe that things like the document you linked are massively influenced by both the politics of the authors and the information available to them.)
"30 hours of wake time per month (~5 concurrent users avg), averaging 10% of 2 CPUs and 1 GB RAM"
Does that mean it would sit available but using 0% when there's nobody on the site, and just bill for usage when web traffic is causing the server to do work? So if the web app went a month with no visitors it would cost nothing (except for the file storage fees)?
It's not something I generally need to do, so I haven't been keeping up with how good LLMs are at this sort of conversion, but seeing your question I was curious so I took a couple of examples from https://www.json.org/example.html and gave them to the default model in the ChatGPT app (GPT 5.2 - at least that's the default for my ChatGPT Plus account) and it seemed to get each of them right on the first attempt.
> The identified vulnerabilities may allow a complete device compromise. We demonstrate the immediate impact using a pair of current-generation headphones. We also demonstrate how a compromised Bluetooth peripheral can be abused to attack paired devices, like smartphones, due to their trust relationship with the peripheral.
> This presentation will give an overview over the vulnerabilities and a demonstration and discussion of their impact. We also generalize these findings and discuss the impact of compromised Bluetooth peripherals in general. At the end, we briefly discuss the difficulties in the disclosure and patching process. Along with the talk, we will release tooling for users to check whether their devices are affected and for other researchers to continue looking into Airoha-based devices.
[...]
> It is important that headphone users are aware of the issues. In our opinion, some of the device manufacturers have done a bad job of informing their users about the potential threats and the available security updates. We also want to provide the technical details to understand the issues and enable other researchers to continue working with the platform. With the protocol it is possible to read and write firmware. This opens up the possibility to patch and potentially customize the firmware.
It could be that they calculate the existence of uv saves their team more time (and therefore expense) in their other work than it used to create. It could be that recognition for making the tool is worth the cost as a marketing expense. It could be that other companies donate money to them either ahead of time in order to get uv made, or after it was made to encourage more useful tools to be made. etc
Edit: 6 months ago, user simonw wrote a HN comment "Here's a loose answer to that question from uv founder Charlie Marsh last September [2024] : https://hachyderm.io/@charliermarsh/113103564055291456
«« I don't want to charge people money to use our tools, and I don't want to create an incentive structure whereby our open source offerings are competing with any commercial offerings (which is what you see with a lost of hosted-open-source-SaaS business models).
What I want to do is build software that vertically integrates with our open source tools, and sell that software to companies that are already using Ruff, uv, etc. Alternatives to things that companies already pay for today.
An example of what this might look like (we may not do this, but it's helpful to have a concrete example of the strategy) would be something like an enterprise-focused private package registry. A lot of big companies use uv. We spend time talking to them. They all spend money on private package registries, and have issues with them. We could build a private registry that integrates well with uv, and sell it to those companies. [...]
But the core of what I want to do is this: build great tools, hopefully people like them, hopefully they grow, hopefully companies adopt them; then sell software to those companies that represents the natural next thing they need when building with Python. Hopefully we can build something better than the alternatives by playing well with our OSS, and hopefully we are the natural choice if they're already using our OSS. »»
Some of whom might have good options for changing jobs, or good hopes of things improving in the near future, but for many it would be the lesser evil compared to trying to find a different job with the same positives (whether salary or other motivation) but without those negatives.
Thanks for not jumping to self promotion, but I'm actually curious to see how you did it - would you mind sharing a link?