If you read their GitHub README and the code, it's possible to separate and cache the voice cloning step, and they have some streaming variant with low first chunk latency. I only played with it via Hugging Face. It is astonishingly good with certain rare accents, and it responds well to longer input clips
Prompt text: There are 14 varieties of tomato soup available from this replicator. With rice, with vegetables, Bolian style, with pasta specify hot or chilled.
I think that's mostly just a frequency shift :) You could probably recreate it with another model and some effects on top. Also, why the hell not for voice mode haha.
Substituting one form of media for another does not improve the hypothetical situation at all, giving a senior nothing to do all day except talk to a spreadsheet is not a solution to that senior being lonely, it is a false dichotomy. Far lower tech solutions can be (and are) used. In my locale we have volunteer schoolchildren active in the community, as far as I know that's quite common, and even half an hour biweekly with a fake grandkid is many orders of magnitude healthier and more meaningful than swapping out their TV for this generation's take on Fox News.
It goes without saying all these tools are still largely in their pre-advertising state, it won't last.
Star Trek computer voice model is something I have yet to encounter, and I've looked repeatedly :) It's not about a specific voice, it's the fact they managed to capture "I am a utility" perfectly in the voice. Our modern friends do not want to be thought of as a utility, but to engender trust and agency all of their own and that's a huge problem for me.
Is it responsive to personality settings? I actively don't want fake AI girlfriend, but I do get a ton of value out of voice mode. Looking forward to trying this but hoping it's not a creepy overdone mess (like Sesame). Expectations are they'll keep doubling down on fake AI girlfriend approach because the thing I want probably wouldn't drive engagement anywhere nearly as well
> Lloyds has not explained why it has taken this action… despite multiple communications from us
Because you've tripped an AML flag you unbearable dweebs, this happens a thousand times every week and the story is always the same, tipping off rules actively prevent notification. But of course the reason must be political, because that's the only story that will drive traffic to an otherwise unknown outlet
> I think most people who strongly identify with tools like vim do so out of a sense of identity-building to "be the kind of developer who is good at vim" / embody some kind of aesthetic or in-group signal moreso than an actual desire to be more effective at getting work done.
This is the exact same sweeping inferential leap as the original comment. I happen to think people who drive red cars do so only because they want to incite a sense of danger and potency in their road opponents, people who wear boots obviously want to identify with Ukranians on the front lines and any claims it helps with their flat feet are obvious rubbish.
Tooling and language obsession is boring and borderline offensive to anyone who has been around for a few years. Imagine walking into someone's workplace and demanding they replace their well worn chair, would you do it? Imagine insisting someone use vim because their IDE didn't have a natural pipe-through-shell-command function.
I can quite easily (and often do) use a basic editor while staring at the wall. I've yet to use an IDE where there wasn't some idiotic race between keystrokes and whatever random latency language server just told it to insert parens or a newline after you already typed them, assuming the text is even visible on a 13" screen buried in sidebars and "essential" extensions. They're full attention tools which is a completely different mode of work than is otherwise possible.
It's not to say an IDE isn't a useful thing, they just have their place like anything else. I personally find autocompletion useful for a couple of weeks going into a new language or project after which it's very often more a distraction than a productivity enhancer. Same goes with e.g. Git integration. I wouldn't presume to say a Git integration user simply needs to learn Git in much the same way I wouldn't expect someone to tell me that I can't use Git just because I don't use the IDE Git integration. They're just tools
Triggered by both of these comments.. interaction mode dictates a style of thinking. I have to use a mouse, I'm forced to use my eyes, which also means I probably have to use a massive screen. I have to pay attention to some hyperactive Intellisense-like feature, I'm forced to remove my attention from the problem.
It's like saying you're convinced people reporting they feel more productive in a mauve-coloured room are liars, or those that drive automatic vs manual. Maybe they just find muave a restful colour?
Probably throwing quite the grenade here, but around 29% of pregnancies end in termination globally. Absent cultural considerations, it's questionable whether life expectancy has improved in absolute terms in modern times
What's the point of even trying to obfuscate this with such a simple method? Could at least have hidden the targeted features by storing their hashes or embedding a bloom filter or similar
> The failure was caused by a timing-dependent race condition in hyper’s HTTP/1 connection handling. When the reader was slower and the socket buffer filled, poll_flush returned Poll::Pending, but the dispatch loop discarded that result. Hyper then treated the response as complete and shut down the socket while data remained buffered internally, causing the client to receive an EOF before the full body arrived.
You are far better off reading the sockmap docs than this post, it adds almost nothing, entirely fails to explain the point of the interface and more or less amounts to marketing slop
Including a strong motivating example might have helped sell this, using an example that could trivially be expressed as a GET is extremely distracting.
Even imagining a QUERY with a large JSON filtering structure, or say an image input as request body, it feels extremely odd to include the request body as part of the cache key. It also implies an unbounded and user-controlled cache key, with the only really meaningful general caching strategy being bitwise compare of the request body (or a hash), which in a hostile scenario implies cache busting would be trivial.
This invokes multiple semantic oddities in one go with obvious difficulties for a very niche use case. If I'm writing a service that needs complex filtering or complex input like an image, any form of caching (e.g. individual data columns of a join, or embeddings keyed by perceptual hashes of a decoded image input) is going to be far away from the HTTP layer and certainly unrelated to the exact bit representation of the request on the wire.
Why even bother trying to capture this in a generic way?
I would be far more inclined to try and capture this caching semantic as a new header for POST. Something like "Vary: request-body" or similar. Perfectly backwards compatible and perfectly ignorable for all but the 0.1% of CDN use cases where the behaviour might turn out useful
I can't speak for elsewhere, but in the UK she can still sell her cupcakes, she just needs about 3 different kinds of license and one council inspection to do it. I imagine that is fairly normal across the EU
The same was true of food safety. Aunt Tracey might not be able to sell cupcakes from her home any more (made in the oven next to where the cat likes to sleep because of the heat), but we centralised things enough that when BSE and Salmonella outbreaks happen, which nowadays is extremely rare, we know how and why almost immediately. If the cost of ridding ourselves of animal torture, terrorism and child pornography is a few hundred fewer Mastodon instances I could most certainly live with that