This could be a mere human error, but I suspect more as I've seen it too often.
The German supermarket chain #Rewe promotes their continual offers of regional goods, especially fruit and vegetables. Small signs tell customers that certain items are from the local area, and people seem to trust them.
An occasional check, though, and it is clear this is not the case. These potatoes are from #Egypt which, no matter how you fold the globe, is not regional to #Bremen. A second container had potatoes from Israel, also not local by any stretch of the imagination.
In fact, none of the items marked as Regional goods on offer in Rewe Bremen yesterday were regional at all.
Time, perhaps, to give someone a geography lesson, or ask whether this is being done on purpose.
KI generiert kein Wissen, sondern setzt gemäss voreingestellten Parametern und Algorithmen Wörter in eine in erster Linie grammatikalisch richtige Abfolge - in neuer Zusammensetzung.
Was darüber hinausgeht, bleibt am verfügbaren Datensatz an Informationen hängen. Sind die Informationen (aka der Datensatz) Müll, dann gibt KI grammatikalisch korrekten Müll in anderer Zusammensetzung wieder.
How is having to select “no” 12 times to opt out of tracking and targeted ads acceptable? This is why ad, cookie, and tracker blockers are so popular. #UX#failhttps://instagr.am/p/C7ZlpmCvB-b/
#Elsevier is a publisher with a lot of experience. You would think they would understand DOIs. They do not. As if they don't care about references and citations. If you see a "10/gh3n5k" about where you could expect a DOI, it probably was supposed to be a DOI. Maybe try to add some publisher value and work with the authors to fix that? Then you can also check if the author list is actually correct (no, it was not). Is this a N=1? No, it is not. It is a routine #fail in #publishing
Is it just me or is #phpstorm getting worse by the day?
I'm runnig 2024.1 (Build #PS-241.14494.237, built on March 27, 2024) but have to constantly restart the IDE to fix bizarre errors like PHPStorm claiming a property or parameter isn't used while highlighting the very use a line later, inconsistently resolving asserts with instanceof checks - e.g. claiming a method doesn't exist in the class referenced in a different assert and not seeing a parameter that is clearly there... #fail#ensh11n
Tjo, Handy & Token Verknüpfung gescheitert bei #aid Nichts mit neuem yubico Token 😠 fürs Finanzonline heuer.
Fido Token Verknüpfung ist wohl am SP gescheitert. Rote Box mit Session-ID, Support Bot kennt sich nicht aus und hilft mir nicht. Frust bei mir! Handy-Verknüpfung nicht besser -QR-Code Scan fehlgeschlagen, da vom dummen User (mir) im DigitalenAmt nicht auffindbar. Fail 2.
Bleibts' dann bei SMS Token... Uff. Da war ich mit der Handysignatur schon mal weiter.
Looks like PayPal has locked me out of my money with a "no blind people allowed" sign. I'd be happy to retrieve the "accessibility cookie" except there's an error: "ERR_BLOCKED_BY_RESPONS..." Really? What gives? I have to log in to get support. Anyone have any ideas? #accessibility
@technocounselor Weirdly I just tried again a couple of hours later and I didn't get the CAPTCHA. Still it is fundamentally wrong to lock disabled people out of access to their own money and there should be a very special place in he** for people who insist on inaccessible design and code. #accessibility#PayPal#Fail
If you were wondering whether the new #Sonos app is as bad with #VoiceOver as people said, I can confirm that it is.
The first element that receives focus has no #accessible role or name, i.e. VoiceOver doesn't announce anything for it. The screen is split up into sections, like "Recently Played", "Your Services", and "Sonos Favourites", but none of these have headings. And, as previously noted, explore by touch doesn't work; VO seems to just see that blank element I mentioned as being stretched across the entire screen.
As a result of all this, the "Search" button requires 32 swipes from the top of the screen to reach, at least with my setup. If you have more services and/or more favourites, that number of swipes will be higher. #accessibility
@jscholes That, and on my iPhone with system language set to German, the UI does show up in German but is spoken by VO using an English voice, probably because the localization settings are not correctly configured and so all the German strings are marked up as being in English. This truly is a huge #accessibility#fail.