Oh yeah cats are cute. But then they shed. Nothing is safe. I took my cat home from the vet once, it was a hot day, I rolled the windows down to let the heat out and started driving. Snowy sat inside his basket thing, loving the feeling of the wind blow, meanwhile a blizzard of loose fur filled the car. I should be the one at fault, but somehow it felt like it was his plan all along, revenge for going to the vets. Cats know. They always know…
I don’t think there are any apps that support both Lemmy and Kbin currently. Artemis says they’ll eventually do both but not sure it’s usable now.
Last I checked Kbin didn’t have an API which is why you see fewer apps for Kbin I guess. Those that work do so by scraping the web pages. Maybe that’s changed in the meantime.
I actually do this with kbin as well, though their “app” interface is nowhere near wefwef quality. Plus I am a Reddit refugee because I was a strong Apollo user, so the interface is like home to me.
Why would Russia blow up the NPP when they’re winning the war? This is another atrocity by the Ukrainian military to muddy the waters and try to attract yet more international support like the dam bombing.
causing a nuclear disaster would help with this how?
The plant is located near the front lines, along a probable route to the Sea of Azov. Blowing it up creates an obstacle, making advances and supplies more difficult.
When you hold part of your opponents country that means you’re winning.
That’s a stretch. Like Germany was winning WW2 until it was kicked out of France.
True, it’s probably the best Russia can achieve but far from their goals. And they’ve been losing ground steadily now.
Imagine listening to someone who is such an expert he said Russia is not stupid enough to invade Ukraine. Yet just a little while later he’s an expert again
Ah yes, we should instead listen to the experts who claimed that Russian economy was going to collapse in a month, that Russia would run out of weapons, and that Ukraine was going to make a blitzkrieg offensive that was going to go to the sea of Azov in one day. 🤡
The fact that you’re arguing Mearsheimer doesn’t know what he’s talking about based on him not having thought that Russia would invade Ukraine shows what an utter clown you are given that pretty much nobody in the west predicted that. You don’t have to link to anything, it’s pretty clear from your comments what “experts” you rely on.
Yes, nobody in the west predicted that and the state department was even saying it was unlikely. Shit, you really should’ve called them up and told them!
There was zero chance of NATO accepting Ukraine in 1997 as anybody who has any clue at all understands. Meanwhile, what would’ve actually prevented this war was for Ukraine to declare neutrality and renounce NATO ambitions. That option is certainly going to look pretty good when this is all over.
The Baltics joined NATO in 2004, Russia did nothing despite long control over the region and a large Russian minority. Had Ukraine been in this position the whole war could have been avoided, since Russia would not invade a NATO country
The Baltics aren’t Ukraine, you keep exposing yourself as being utterly ignorant regarding the subject you keep attempting to debate. You’re like the poster child for the whole “I did my own research” meme.
There's no correct and incorrect here. The help page (https://support.google.com/websearch/answer/3284611) doesn't even mention which word you should use, and it of course depends on the language you use. As a German speaker, I naturally use "in", and that always worked for me (I use this a lot), except for this example.
I see that that works. In this particular case obviously better than "in". I guess I'll use this in the future, but I'm sticking with that this is a bug, not something inherently wrong with using "in".
“in” is the abbreviation for “inches” and Google will most always interpret it that way from an English language point of view. Additionally as a vernacular you usually only say “meters in feet” when your wanting to do a single unit conversion such as “how many meters are in a foot?”. Google’s language processing tends to be heavily slanted towards common English in which case some differences like that will never be considered how you want.
Considering you’re right that that’s exactly what is happening here I can’t push this too hard, but I definitely think it’s very common and standard English to say “what’s 17.21 metres in feet?” and of course very common especially in metric countries to abbreivate metres to m. It’s also a logically odd request to want to know what 17.21 million inches are in feet with no “to” or even “in” (the in having been used up here by being assumed to mean inches) to give the query meaning. That would read as “17.21 million inches feet”.
Google is capable of supplying a unit conversion answer for you with the “in” construction for the query “17km in miles” for example so it understands “in” in the way many of us would expect it to but weirdly assumed that ‘in’ meant inches and that the query is constructed with no grammatical indication that a conversion is even being requested which is a bit of a funny leap. It’s understandable that this might perhaps not have been anticipated exactly, in as much as perhaps it’s not surprising that it doesn’t somehow have the capacity to evaluate the likelihood of such a request over the more “common sense” interpretation but whether or not it’s understandable that this mightn’t have been foreseen I think we could reasonably call the resulting interpretation as undesireable for almost all human beings that might ever use this tool and it’s probably fair to call it a bug in that sense.
lemmy.world
Newest