What I’d wonder is why it’s such massive expensive for Duolingo to hire 2 or 3 people to cover a language anyway. Presumably most of the work is contractual - hire somebody competent to produce a course, get somebody to say the lines, refine the course based on feed back and that’s mostly it.
Don’t blame the devs, blame the timelines and the pressures of implementing features.
I was advised by the nurse that as long as we’re within 24 hours of a major hospital (family and me) they can pump us full of antibodies and we should be fine. And also not to pet dogs, cats, monkeys etc.
All 3 of the diseases i was vaccinated for regularly kill people and can cause severe harm even if someone survives. As I am not an idiot I would prefer to avoid that if at all possible. I opted not to get Hep B, Rabies, Dengue fever vaccinations based on a risk profile and where I was traveling but I could and would have gotten shots for those too if the risk profile were higher.
I also vaccinate my kids for the same reasons.
I got 3 vaccinations today for a trip to Asia for Hep A, Typhoid and Tetanus. Two jabs in one arm and one in the other. Because while getting vaccinated isn’t pleasant (sore arms and mild flu like symptoms) I would rather that than to the horrible, potentially life threatening illnesses they prevent.
The clue was in “user facing bits”. UTC represents time as an absolute. If you want to show local time, or deal with daylight savings you run UTC through a function on its way to the user.
ISO 8601 goes from 1582 (Julian calendar adoption) but can go even further with agreement about intention and goes down beyond the millisecond. Not sure why I want an integer from the year 2000 which only represents seconds.
The sane way of dealing with it is to use UTC everywhere internally and push local time and local formatting up to the user facing bits. And if you move time around as a string (e.g. JSON) then use ISO 8601 since most languages have time / cron APIs that can process it. Often doesn’t happen that way though…
Probably only works for dumb bots and I’m guessing the big ones are resilient to this sort of thing.
Judging from recent stories the big threat is bots scraping for AIs and I wonder if there is a way to poison content so any AI ingesting it becomes dumber. e.g. text which is nonsensical or filled with counter information, trap phrases that reveal any AIs that ingested it, garbage pictures that purport to show something they don’t etc.
Imagine the fun the world will have making jokes when this vapid bint exits the mortal realm.
French supermarkets all have very large and wide selection of “free from” style products for allergies and intolerances - gluten free, milk free. Plus vegan and vegetarian. In fact it would put most supermarkets in the US to shame. I also expect that many cafes in Paris cater for people with allergies.
So it’s not that. More likely it’s a surly waiter, or a tourist asking for something which is not on the menu and being upset by the answer.
Depends what you mean by bloat. It has a very large repo, but it compiles into little commands with least privilege execution. A lot of those commands are specifically there so someone doesn’t have to pull in other repos with a larger attack surface. e.g. there is a time sync daemon to replace having to pull in ntp which is a lot more complex and fraught and the one thing most desktops need of NTP which is to set the clock.
Why do you still exist? I try understanding what the purpose of your reply could be? Screenrecords do not work. For plenty of people. Google it. Yet you feel entitled to share you smalldick energy wisdom of “proper way”. That is exactly the vibe of the shit ppl. You do not help Wayland or x11 or anything, you just fap into your own mouth because nobody can ever love you like that. Go get help.
Wow, someone needs to grow up. You laid into Wayland when screen recording doesn’t even go through Wayland. The app asks the WM to screen record via DBus. A more constructive response would have been “thanks I didn’t know that”, or perhaps “oh it’s a driver issue”, or “it’s an issue with that WM/ffmpeg/pipewire or whatever”, or anything else likely to be the underlying cause. But it’s not Wayland. Have you got that? Not Wayland. There is no need to be sore and immature about it.
Fairphone don’t sell replacement mainboards, presumably to stop people building phones from parts but they look very serviceable in other respects.
Screen records do work providing the app asks for a screen cast in the proper way (which BTW is not via Wayland but through a message to a DBus service). The service and the desktop then ask permission from the user if necessary. X11 didn’t give a damn about protecting the contents of your screen and any app whether it was beneficial or malicious could do it with impunity. So you should see this as a major security improvement - you can screen record but only if permission is granted.
Yes it’s been stable for some time with a couple of caveats - you need a decent graphics driver and not be using apps with edge cases.
Here is a simple example of an edge case and it’s not hard to find people blaming Wayland even though with some thought this was a security issue - apps like Zoom, Discord, MS Teams want to do screen sharing which is easy in X11 because it has non existent security - just steal the screen bitmap. That’s a problem.
Wayland (the protocol) provides no means for one app to grab the screen, or other apps. This is by design for security. Instead the app must be a good citizen and send a “i want to screen cast” message to the xdg-desktop-portal (a service provider implemented by GNOME, KDE etc.), the desktop asks for user consent and then the app gets a video stream. So it’s a lot more secure but it requires the app and the WM do things properly.
Desktops and apps have matured and these issues are thankfully going away. I think the biggest hurdle left is proper graphics drivers, especially the problem of getting NVidia drivers working.
I think Wayland just attracts trolls in the same way as systemd does.
I’m glad Wayland is maturing and taking over. Even most of the X11 devs hated X11 which tells you something.
AI is certainly a very handy tool and has helped me out a lot but anybody who thinks “vibe programming” (i.e. programming from ignorance) is a good idea or will save money is woefully misinformed. Hire good programmers, let them use AI if they like, but trust the programmer’s judgement over some AI.
That’s because you NEED that experience to notice the AI is outputting garbage. Otherwise it looks superficially okay but the code is terrible, or fragile, or not even doing what you asked it properly. e.g. if I asked Gemini to generate a web server with Jetty it might output something correct or an unholy mess of Jetty 8, 9, 10, 11, 12 with annotations and/or programmatic styles, or the correct / incorrect pom dependencies.
Javascript is a dogshit language that everyone is stuck with. The best that we can hope for is the likes of typescript take the edge off of it. Even though it’s like smearing marzipan over a turd. At least it’s ok if you don’t take a deep bite.