• 2 Posts
  • 101 Comments
Joined 13 days ago
cake
Cake day: October 31st, 2026

help-circle

  • … but I don’t think we actually need a very firm definition of “slop” to be able to say some things clearly are slop and some AI-involved things clearly aren’t. When in doubt about if something is of sufficient quality that we should keep it here, the age of the project and the number of developers involved are useful secondary metrics…this is not a place to promote new single-developer heavily-AI-assisted projects. Another community exists for sharing AI-Assisted Libre Software: !aials@lemmy.ml note that the word “slop” is intentionally absent from my proposed rule (and from name and description of the community)

    Curious. Woke up to find my post removed at almost exactly the same time you posted this, complete with an accusation of “slop”.

    The post had 31 upvotes, a 98% positive vote ratio and genuine discussion, for a project with a 6 month history behind it and a freshly repopulated repo. That doesn’t read like an unwelcome contribution.

    To be clear, I’m not asking nor am interested in reinstatement of it.

    Speaking plainly, !aials appears to be a tar pit for projects the mods deem guilty until proved innocent. Cool - your room, your rules.

    But I suspect this approach will lead you exactly here:

    https://lemmy.dbzer0.com/post/78050871/29108982

    IMESHO, there may be some merit in approaching things the way !selfhosted does, vis-a-vis [AIP], [CBH] tags.

    • Hint - AI suggested solution, human does the task.
    • Assisted - AI acts on part of a task, but a human handled the bulk.
    • Pair - About a 50/50 split of human made and generated.
    • Generated - Human prompted, AI generated

    There’s a significant difference between those categories and a catch all rule that assumes the worst. The latter leads to things like this. The proxy signals you’re proposing would have tar-pitted something like the venerable cURL if it had come out today and been accused of “slopware” (whatever that means).




  • Better :)

    The issue with stuff like TubeArchivist, pinchflat etc is that they have great curation and downloading (spoilers: its mostly ytdlp under the hood) but really bad at getting the content onto your TV.

    Plex, Jellyfin etc can be press ganged into it, but it’s clunky.

    Smarttube was designed for big screen, remote control navigation etc.

    What I did was make SmartTube play YouTube videos you download (I like MeTube because I’m not a sadist) alongside live sources.

    Use MeTube, Pinchflat or whatever to download your videos. Use SmartTube LOCAL to then play them offline thereafter. It’s android native, so it should work on Chromecast, android TVs, AOSP, Firesticks (maybe?) etc.

    Crunching the numbers, using a mix of 720 and 480p, I can store somewhere around 5000, 20-25 minute videos in 500gb. Stick that on a hard drive, plug it into your compatible travel router and you have offline YouTube on a boat, in an offgrid cabin, camping etc - anywhere you can install the app. You don’t need a server per se once the catalogue has been generated.

    We did something similar with NovaPlayer when we went to Tokyo last year (I brought the Google cast with USB pass thru and stuck a 128gb thumb drive to it. Plugged that straight into HDMI and off to the races). I’ll likely graft that onto SmartTube LOCAL also.

    Anyway, right now it’s configured for TVs but I’m sure I can figure out a way to have it display on android tablets or phones. That’s probably the final buy in step for the kids.












  • XMPP hosted via Raspberry Pi.

    The setup is:

    • Prosody provides the XMPP server.
    • Converse.js provides web client / PWA.
    • Conversations for Android clients
    • Coturn provides TURN services for calls and NAT traversal.
    • Tailscale provides remote access without exposing the XMPP server directly to the public internet.

    (nb: also configured Message Archive Management (MAM) for chat history, private multi-user chat rooms (MUC), HTTP File Upload for media, and Jingle signalling for audio/video calls).

    The server is designed to be accessible over our LAN. When away from home, family members connect through Tailscale (I really should just use Android actions and geofencing to auto launch Tailscale, but on my kids devices, I just leave Tailscale enabled. I don’t think it hits the battery too hard). Tailscale can only connect to XMPP and we keep our XMPP to family only, with me manually adding devices to Tailscale as I need to.

    As for why? Because I get joy from hosting my own shit, having control over it, having it work when other stuff falls over. My stuff falls over too, but I know WHY and HOW to fix it, and that’s how I prefer it. I want to get to the point that if the internet dies tomorrow, I shrug my shoulder and barely notice.

    My goal is to replace all cloud based services we use and I’m about 85% of the way there. I have a much larger goal too…but that’s a story for a different time.

    PS: I’m mildly irritated about Tailscale use, so I’m looking at getting off that teat as well eventually for a self hosted solution. There are some issues with Headscale and I don’t want to punch holes in firewall if I can avoid it. Still thinking on it.

    PPS: Meshtastic, Reticulum etc all seem super cool…but until there’s interoperability simple enough for normies…good luck getting buy in. I struggle to convince the fam to use XMPP (weird issues with android clients, Tailscale drop outs etc).




  • “Guide” is doing a lot of heavy lifting there. There’s an infinity of difference between asking an AI to make something and using an AI to do the scutt work, looking over the code it made, running IRL tests, asking “why X? Why not Y?”, swearing at it like a junior dev, asking it to fix a,b,c then finally getting acceptable code.

    And even with all that - when you set it up correctly - it’s still faster than doing it yourself (in certain circumstances).

    It feels more like doing project management / “software engineering” than clacking the keys. It’s amazing how different LLMs approach the same task though; I find Codex to be much more by the book than Claude, for example. The Qwen’s are like Labradors - eager to please, clumsy, crash into things a lot. GLM and Kimi are different again. Etc.

    You can’t let anything just “make me X, make no mistakes”. By the time you type in a ticket (with GO/NO GO gates, acceptance criteria etc) you might be looking at 500-1000 lines of text (which is why a re-usable template and procedures are important). You need repeatable procedures, acceptance tests - the lot.

    And so it goes.