• 0 Posts
  • 58 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle
  • Luddites weren’t against new technology, they were against the aristocrats using new technology as a tool or excuse to oppress and kill the labor class. The problem is not the new technology, the problem is that people were dying of hunger and being laid off in droves. Destroying the machinery, which almost always they were the operators of when working on said aristocrat’s factories, was an act of protest, just like a riot, or a strike. It was a form of collective bargaining.



  • Well, you see, that’s the really hard part of LLMs. Getting good results is a direct function of the size of the model. The bigger the model, the more effective it can be at its task. However, there’s something called compute efficient frontier (technical but neatly explained video about it). Basically you can’t make a model more effective at their computations beyond said linear boundary for any given size. The only way to make a model better, is to make it larger (what most mega corps have been doing) or radically change the algorithms and method underlying the model. But the latter has been proving to be extraordinarily hard. Mostly because to understand what is going on inside the model you need to think in rather abstract and esoteric mathematical principles that bend your mind backwards. You can compress an already trained model to run on smaller hardware. But to train them, you still need the humongously large datasets and power hungry processing. This is compounded by the fact that larger and larger models are ever more expensive while providing rapidly diminishing returns. Oh, and we are quickly running out of quality usable data, so shoveling more data after a certain point starts to actually provide worse results unless you dedicate thousands of hours of human labor producing, collecting and cleaning the new data. That’s all even before you have to address data poisoning, where previously LLM generated data is fed back to train a model but it is very hard to prevent it from devolving into incoherence after a couple of generations.










  • How is having to apply workarounds to keep windows working on old machines any different from troubleshooting the occasional linux issue? It’s a rethorical question, the difference is that the workaround on Windows is mandatory while the Linux troubleshoot is nowadays rare and usually related to edge cases.

    Some of the workarounds in this article are far more involved and convoluted than what I’ve ever had to do in 15 years of linux. Some are even dangerous for system stability and security. My very recent install of bazzite in a new laptop has been a perfectly out of the box it just works experience. Not even having to open the terminal. 100% friendly GUI without compromising flexibility, power and customizability. Today, suggesting linux with a solid desktop environment like KDE plasma is just foolproof. The end user will be using exactly the same knowledge and habits of Windows, without the harassment machine that is MS now. The change is not learning a new OS, is just switching a few assumptions on how some advanced things work.



  • That’s a poor understanding of the situation. Nothing in the licensing changed. The SDK has always been the proprietary business to business secrets management product. The client integrates with and can use that SDK to provide the paid service to businesses. The client and the server side management of password has always been and still is FOSS.

    This was apparently an accidental change in the build code (not the client code, just the building scripts) that required the inclusion of the SDK to build the client when actually it has never and doesn’t really need any of that code. It prevented building the client without accepting the SDK license. Which it shouldn’t.

    This was fixed and some things will be put in place so it doesn’t happen again. Nothing in the licensing scheme changed, at all. This is not a catastrophic enshittification event. A Dev was just being lazy and forgot to check the dependencies on the build chain before their commit.





  • Poor comprehension of the law. LLC in the vast majority of the western world means limited liability, not absolute immunity. Owners are 100% responsible for the actions of their companies, but their liability is limited when other members of the company act without their knowledge or in bad faith, or damages are unintentional. If the damage was intentional and the actions were sanctioned and approved by ownership or leadership they are absolutely liable for the legal repercussions. Liability is limited also for multiple owners, a hedge fund cannot be held responsible for the action of a company they only own 5% of and has an indirect influence on the actions of leadership. The really important element here is that Musk is being identified as acting as primary agent, not just Twitter, and using assets and resources from his other companies. Thus, it’s not Twitter acting, it’s Musk who is acting, and then fines can be on all of his capital holdings, not just Twitter. This nuance of law is exactly according to the laws in place in the EU.



  • You’re gonna miss the tune for when the display dies but the controller still works. It’s actually there for user input feedback. It could’ve been anything else, but if it has to be there, it might as well be something pleasant. Picture an appliance that screamed every time you pushed a button.