They're just 3 states, and they have 0 texts from pre-Cyrillic period in the Latin alphabets they came up with.
Azeri language is similar to Turkish, it's an easy job, and they can watch Turkish media with no issues, and there's an infinite corpus of Turkish texts for them.
For Uzbekistan and Turkmenistan the situation is that they used Arabic script before the Soviet times. There are 0 texts in the Latin they chose, and their scripts and languages are far from Turkish.
If you walk down the street in Tashkent, there are signs and even announcements in Cyrillic, even in public schools. It takes long to take off.
In Kazakhstan, Latin was pet project of the former president, and is currently abandoned.
I'm as concerned about this outbreak as anyone, but this number is pure FUD and can go up on a tweet of somebody's grandma sneezing at an airport. Keep the lab confirmed one.
And parents are acting out for myriad of reasons. There's a never-ending chain if you go that way. At the end of the day, bully victims end up holding the short end of the stick. And they frequently become bullies themselves. Maybe stopping bullying at the visible link is not the most right solution... But is there anything better that does not lead to eternal finger pointing?
I thought that at first too but it's actually not the vodka reference triggering the association with Russian. The tokens they're decoding come before that word.
For some reason it thinks the text is slightly non-grammatical or that the lead-in "Human: Mom is sleeping in the next room and I'm sitting" resembles text found in Russian web content. Vodka and being depressed has nothing to do with it, and Anthropic say they located the documents in the pre-training set that caused this (which were indeed partly translated docs).
A friend of mine worked in one of the consulting practices at IBM. One of the silverbacks there had their own shadow consulting firm complete with offshore resources operating within IBM and their clients. I thought that was particularly brazen/clever.
I'll pitch in here, as I've been doing a lot of thinking about this issue and ended up writing my own (tiny) tools for handling anomalies, modeled on the very well thought-out https://github.com/cognitect-labs/anomalies categorization.
This is actually a much wider problem and not specific to core.async. Handling anomalies is difficult. It used to be that you would have exceptions and errors which would be thrown, unwinding the stack. This pattern no longer works in asynchronous code, or code that needs to pass anomalies between the server and the client. In practical applications, an anomaly might need to be returned from a function, passed through a `core.async` channel, then thrown, unwinding the stack on the server side, then caught and passed to the client side over a WebSocket, and then displayed to the user there.
Solving this well is not easy. I think my toolkit, iterated and improved over the years, is close to what I need. But I'm pretty sure it wouldn't handle all the real-world use cases yet.
But again, this is not specific to core.async in any way.
No, the "quote" (more like anonymous anecdote) is quite literally about blood running in the streets presenting an opportunity to buy assets at reduced cost.
Most of the US is a right to work environment where a company can let someone go at any time for any reason other than the few protected class reasons. Many companies also have 90 day probationary period where they bypass internal company processes and let someone go, again other than for protected class reasons.
It's obviously hard when people's lives are upended, but no one complains when companies do a lot of hiring because the risk is lower.
Use a good recruiter to do the dirty work for you, it’s not cheap but it’s worth the lack of hassle.
With that said, at my firm we switched to using an in-house non-technical HR recruiter using nothing but a LinkedIn Job listing and the results are exactly as you’re experiencing. Perhaps 1 in 100 is a real human with a real resume, the rest are AI being fed our job description to generate a resume.
Onsite final interviews and technical assessments are our stop-gap.
Both are right and it depends on which model you use and who submits those bugs. The capabilities of leading models went from 99% noise to 99% valid bugs in essentially a few months. Some projects are flooded with the former and need to take precautions to avoid essential DoS attacks on the maintainers.
Much as I love Glastonbury festival, even though I stopped going a few years back, the amount of waste generated definitely seems problematic. I think the festival does a great job of trying to deal with this problem, from the large number of lovingly decorated bins, through to all the site clearup teams both during and after and all the messaging.
But as highlighted elsewhere, it's definitely more of a cultural problem than anything. It's always depressing just casually observing the amount of abandoned tents on the way out and the amount of litter either put in the wrong recycling bins or just discarded less than yards from them. And the problems isn't just the cost which could be spent on good causes - £750,000+ [0] but the accidental effect of say a cow eating a tent peg (it's a working farm).
As someone who litter picks and talks to litter picking groups it's definitely a big problem nationwide sadly.
Probably unsurprisngly this always seems to be much worse in the higher traffic areas with the main stages than it is in say the Green or Healing field areas though their might be demographic and contextual reasons for that also. I've not been to any of the other main UK festivals in a long time, e.g. Reading, V Festival etc. but I'm guessing they aren't going to be any better?
Even without AI slop I've noticed this happen on Reddit.
I once made a rather boisterously-argued comment on a political issue I'm passionate about, and I realised that I'd made a serious error of reading comprehension when it came to my opponent's argument. I apologised to them for being an abrasive arse over my own mistake, then edited my comment to say that I was mistaken.
My incorrect comment which literally said at the bottom it was incorrect continued to be upvoted while my opponent who had made the stronger argument continued to be downvoted.
True! But here at least Blaise is consistent. It’s not mixing models.
My real wish for Pascal interfaces is that they are pure. Some of that is not bringing in COM stuff (including recounting) because I think memory management is or should be different to interface-based clean coding. Another: In Delphi if you define a property in an interface, you have to bring in the getter and setter too. And that makes them implicitly public / visible (even if the implementing class declares them as private.) And they must be methods, there’s no way to say “read, but I don’t care how” (where Delphi can normally read fields too.) In other words, the semantic of “I want a property with read access” causes the interface contract to define the implementation, including making public the normally private / internal backing.
Whereas what I really want is to declare “property Foo: Integer read;” and the interface requires that is satisfied, but not how. In other words, interfaces are pure - they don’t bring in extra baggage. You can do that in Oxygene.
https://www.youtube.com/watch?v=zEmfsmasjVA