I have nothing against AI myself, but it significantly changed how hackathons work.
One prominent example I won't name, I had attended over a couple years. Coincidentally,the timing overlapped with pre-LLM boom and post-LLM boom.
My first edition had zero usage of LLMs, the last had practically 100%, the rules were accommodated. The teams were no longer required to present a working example, a literal figma concept and a cool slideshow were more than enough.
This makes me think of the historical hxxp://simtel.net/ domain (now web spam, whence the hxxp), see e.g. https://web.archive.org/web/20010602231157/http://www.simtel.... The first time seeing it I was always thinking to something like "simulated telnet"...
Hi, I wanted to share a bit of my frustration about Linux usage after whole 2 years of using it as my daily driver. I collected most of the more annoying issues I've encountered, the list is not long, fortunately, but features some especially gruesome issues.
I love and live inside linux, so please go easy on me but...there is some level of product design that an OS needs to be a viable consumer OS. Linux has 100 ways to do any thing, this is 1: paralysis inducing, 2: causes high cognitive load when all you need is to edit/share a spreadsheet, 3: does not create a common experience that you can share with people across jobs. Everyone will do it differently, so you will have an issue communicating how to do task X.
But I see no product people on Linux, I see only engineers wanting maximum Linux. We aren't willing to be more single minded, we want to be nothing like Microsoft (good), but we also want to be nothing like Apple (good in some ways, very bad in others).
Regular users do not need to know what apt is, what a repository is, or any of the 1000 linux things. But those things need to work so consistently well that they could use the OS without ever, and I mean ever, having to know what they are.
Then, I haven't used a linux desktop in a while (tried elementaryOs 2y ago, was a bit lacking), but the desktop environments need to stop looking like some college student's java GUI project.
Finally, I don't know much about the driver/nvidia issues that I hear so much about (that's not where my job takes me), but I don't think we need to solve those before we can get Linux to be a daily desktop driver. I mean let's some up with a list of Linux certified cards and let OEMs pick from those? Maybe this is already done, but if not, we could start there.
The issue I see is that if someone comes up with actual polished desktop experience, they will eventually ruin it like rest. And SteamOS is not desktop experience. Even if it is extremely nice store client. They make money from store. Others will make it from adds, analytics and so on... So it will end up ruined.
The year is 2030. REST API is dead. Invoking requests results in your web browser inbuilt LLM guessing what is supposed to be returned from the server. When opening github.com you occasionally see cheese, at times animal shelter hotline.
How about submitting a prompt for a REST request and then the LLM decides what information you are allowed to access and what actions you are allowed to take? And it works like a batch job of sorts. One request but it can enter many flows.
> The device should ideally have some kind of secret material derived per device, like a passphrase generated from an MCU serial number or provisioned into EEPROM and printed on a label on the device.
It is better than simple secret like 12345678 but it can go wrong too, like in the case of UPC UBEE routers where the list of potential passwords can be narrowed down to like ~60 possibilities using a googled generator [1] whilst knowing only the SSID.
It did require firmware reverse engineering to figure out [2][3] but applies to most devices I've encountered. User should ideally always change the default password regardless.
