I use agentic LLMs (for side projects, properly sandboxed) as much as the next guy, but collectively the normalization of deviance is pretty apparent and shocking (https://en.wikipedia.org/wiki/Normalization_of_deviance).
Backdooring you own machine, sending your .env files, normalizing slop in code review, leaking IP (which is trained on and send to RLHF), YOLO mode, these things would have been unconscionable 2 years ago.
Tangentially related, "slop" really isn't a negative enough term for unwanted LLM garbage. "Slop" which is fed to pigs, has utility. "Slop" as a verb doesn't necessarily have a (strong) negative association ("It was slopped on the plate, but it was tasty").
I use the term "barf" more often. Barf has no utility*. Barf is always seen in a negative context. Barf is forcibly ejected from an unwilling participant (the LLM), and barf's foulness is coerced upon everyone that witnesses it. I think it's a better metaphor.
I know that this is just semantics, but still.
* even though LLM output __can__, and often does, have utility, we are specifically referring to unwanted LLM output that does not have utility. I'm not trying to argue that LLMs are objectively useless here, only that they are sometimes misused to the users' detriment.
This is an interesting observation. One could argue that some AI generated or driven things does have utility, and thus qualifies as "slop" (although not for those on the receiving end). For example, when used to drive clicks and generate revenue, to troll, or to spread propaganda. You get the idea.
In this instance however, I agree, barf is more accurate.
Seems like a catch-22. For codebases that I'm highly familiar with and regularly perform code review in, I'd say "thanks LLM, but I don't trust you, I'm more familiar with this codebase than you, and I don't need your help." For codebases that I'm not familiar with, I'm not really performing code review (at least not approving MR/PRs or doing the merging).
But still, this is very creative and a nice application of LLMs that isn't strictly barf.
At 60%, it highlights significantly more test code than the material changes that need review. Strike one.
At no threshold (0-100) does it highlight the deleted code in UniqueBroadcastEvent.php, which seems highly important to review. The maintainer even comments about the removal in the actual PR! Strike two.
The only line that gets highlighted at > 50% in the material code diffs is one that hasn't changed. Strike three.
So, honest attempt, but it didn't work out for me.
From a quick Google query, it says that ~%90 of Americans have health insurance (which seems higher to me than I'd expected). I'd be very interested in knowing the number of uninsured, negligent/nefarious, and exorbitant invoices that are issued as a percentage of all invoices, for the purpose of determining the scale of criminality with respect to your description.
I glanced at Ubuntu Touch, but its device compatibility looked severely lacking (https://devices.ubuntu-touch.io/).... I have old Pixel phones I could potentially try it out on, but the last Pixel phone that is officially supported is the 3a. So that is a bummer.
There are decent Linux phones you can buy now, such as the FuriPhone FLX1 (Debian), Volla Quintus (Ubuntu Touch), Jolla C2 (SailfishOS) etc. The best part is that all of them also support running Android apps (via Waydroid or similar compatibility layer), so you get the best of both worlds.
It seems as though all of the AI Agents (I'm still not sure what that even means) require 3rd parties? Or more specifically: are you aware of any Ollama compatible AI Agents?
Thanks. I was able to get up and running with AnythingLLM, which offers agency with Ollama (provided a model that supports tools). Pretty neat, I'm excited to try it out.
I thought it was great except for the final episode of season 1.
Spoilers:
People seem to gush over Maarva's hologram speech, I thought it was pretty weak (it started good then it was fumbled).
Maarva's act of rebellion should have been killing herself to deliver her speech at the right time. She's old and sickly, so it'd add gravitas and cost effectively nothing. Then she should have said that she'd resisted all her life, but killing herself was her first act of rebellion. Then the bomb that gets thrown into the Empire ranks should have been baked into her brick, giving her the chance to fight posthumously.
They had nearly all the plot points set up so nicely for the slam dunk, I was perplexed when it ended so dryly.
Everyone is saying lawyer up like it's the author's only option, but it's not, and likely bad advice. Here's the order of operations I would take:
1. Mea Culpa
Talk to all of the faculty (dean of students, etc) and do your best to get people on your side. You need the petty person on the other end to reverse their decision, and having a lot of administration on your side, and more importantly, expressing (fake) remorse makes it easy for these jobsworth asshole(s) to fulfill their God complex. I'm actually convinced that this would have the highest probability of success. These Dolores Umbridge types adore getting to be the ones issuing mercy to the sinners.
Additionally, informing staff of the expulsion will help bring awareness of this abuse, and spread the word and prevent this from happening to other students.
While you perform your mea culpa groveling, record everything, which can be used as ammo later.
2. Agree to the (illegal) terms
Blackmailing you into slave labor is obviously illegal, but no terms have been laid out, so I don't see any harm in agreeing to them. Best case, they reverse the decision with the expectation that you'll do something (which you can then phone in or do a token exercise of), and worst case they outline terms which are the perfect ammo for negative publicity or a lawsuit.
3. Transfer schools/credits
I don't actually know what is involved in transferring schools or how expulsion factors in, but the reality is that you are effectively already expelled. Try and figure out the feasibility of saving what is salvageable at a school that is less insufferable.
4. Negative publicity
This story is easy to believe, sell, and consume- i.e. perfect ragebait. Start emailing every news outlet you can think of. Post on all social media. If it gets high enough, and probably not even that high, the weight of the negative publicity can easily outweigh the narcissists that started this, forcing a reversal.
5. Seek employment
If you have any employment cards in your deck, I'd consider playing them. If everything else fails, then at least you're financially secure and gain experience.
6. Lawyer
The combined weight of all of the above will assist a lawsuit, even prior to taking any legal steps. Note that all outcomes of a lawsuit that aren't "total win" are effectively a loss (of time, money, energy, and mental health), so I'd hesitate to take this course at all.
No one is suggesting to sue. The suggestion is to get advise from a professional, i.e. a lawyer rather to listen to random people on the internet. A lawsuit may or may not follow.
That's true, but it's difficult to envision any scenario where a lawyer supplies the exact advice needed to trigger a reversal outside of threats/suing/arbitration. Maybe if you get a good one I guess, but that is a gamble on its own.
A lawyer supplying helpful information like "Ok, this expulsion was triggered by the Department of Admin, which is overseen by John Smith, who has the power to reverse this decision. Schedule a meeting with him or find office hours to plead your case. I shouldn't get involved outright because it will escalate your situation and be received poorly." is less likely than "I can write a threatening letter and we'll see where it goes". A hammer hammers.
Backdooring you own machine, sending your .env files, normalizing slop in code review, leaking IP (which is trained on and send to RLHF), YOLO mode, these things would have been unconscionable 2 years ago.
reply