#noslop

9 posts · Last used 3h

You know, I've been stressing about what my next phone OS is going to be, as Google tries to crack down on side loading. And considering I'm also trying to get onto a #NeverSlop (rather than merely #NoSlop) stack, and figure out what that stack even contains, I think Nura is gonna be the thing if I can get it on my phone. https://social.treehouse.systems/@cas/117347732017118902
7
4
1
0
You know, I've been reading the terms #NoSlop and #NeverSlop as pretty interchangeably so far, but I think my brain just clicked on the difference between them, which is clarifying my goals to someday run an explicitly and completely Never Slop software stack on my machines. The key word is "yet" - no slop *yet.* It's easier right now to run a fully No Slop system, because it's more permissive - it allows you to include software that doesn't have a policy about LLMs, or has a policy that permits LLM contributions but doesn't yet incorporate any in practice, or unmaintained pre-slop software. This would be a huge step in the right direction from my current daily driver. But the problem with mere No Slop is that a lot of your dependencies are time bombs, and you don't know which. I fundamentally want to get out of this experience where I have to keep changing my workflow because of upstream dumbassery. I want to get to a place where I only use software explicitly committed to never, in the future, slop out.
16
4
8
0
You've seen all posts