• 2 Posts
  • 76 Comments
Joined 1 month ago
Cake day: May 14th, 2026
  • SuspiciousCarrot78@aussie.zonetoPiracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com•Back then, have you ever pirated movie rentals onto DVD / VCD or ripped them?English
    3·
    20 hours ago

    Speaking for myself - generally, no. A couple of reasons why. Even “back then” (early 2000s), files could be downloaded from torrents as needed in glorious 360-480p lol. Locally, illegal movies were easy to obtain as burned DVDs from corner stores / under the counter. I still have bodgy copies of LOTR (obtained in Bali, iirc). My wife OTOH would indeed rent DVDs and burn copies but that was never a thing for me.

    Honestly, the culture was different and we used to look forward to going to Blockbuster, Video Ezy etc. Browsing the shelves and actually watching stuff instead of “curating a collection”. The hire terms were pretty reasonable (7 days). You could hire something, watch it over the week, and return it. $10 for 2 weeklies and a new release meant a week of viewing.

    I remember hiring box sets of 24, Firefly etc like this - never bothered to burn them because there was just too much friction. It’s not like now where I can drop a DVD into a dvd burner and have it automagically appear on my NAS and Jellyfin.

    I do remember in the 80’s and 90’s though - we would hire Sega Master System games, unscrew the cartridge, swap out the PCB with one you owned locally (usually Alex the Kidd), return game to store (hires we strictly 1-3 days). That way you play for as long as needed, then “hire” the OG cart back and swap the PCBs back around.

  • SuspiciousCarrot78@aussie.zonetoSelfhosted@lemmy.world•Hivekeep - self-host a team of AI agents in one container, with a real UI (MIT)English
    31·
    2 days ago

    Friendly feedback (genuinely) per your request.

    Cardinal sins on Lemmy -

    • First post as self promo
    • AI based project
    • LLM written intro
    • LLM written readme on Github
    • CLAUDE.md et al in repo
    • No disclosure of AI use
    • Commit messages that read like they were done by Claude

    Speaking of, code base itself has “llm wrote this, no one checked” stank.

    I pointed Claude at the first file I could see

    https://github.com/MarlBurroW/hivekeep/blob/main/e2e/01-onboarding.spec.ts

    Issues identified (first 5, trimmed for brevity).

    1. Ghost import (TEST_USER) - classic back-fill residue. Pulled in because it “felt right” alongside the other two helpers, never wired up. No fail-loud catch on it - lint should’ve flagged it, didn’t.

    2. Copy-paste boilerplate x3 instead of beforeEach - pattern got nailed once, then stamped two more times instead of abstracted.

    3. networkidle reflex - slapped after every goto, despite Playwright’s own docs actively discouraging that specifically.

    4. Hedge-bet regex (/password/i + filter on /match|mismatch/i). LLM didn’t know the exact copy, didn’t go check it against source (the grounding step), so it just widened the net to pass either way. Not minding that it hallucinates, in test form.

    5. Comments narrating the line directly below them - zero information gain, pure token filler.

    = you’re going to get downvoted to hell because this stinks of AI slop.

    Personally, while Lemmy is militantly FuckAI, I think properly orchestrated, ticketed and reviewed AI code is defensible.

    https://lemmy.ml/post/48724623/26190950

    AI slop (which is sadly what this reads like - please prove us wrong) is going to get kick fucked to death…especially on !selfhosted.

    Not trying to dunk on you…trying to give you a chance to tell us why we should care about this project / install it / what problem it solves.

  • SuspiciousCarrot78@aussie.zonetoSelfhosted@lemmy.world•Why bother with jellyfin, arr stack and everything else if free streaming services exist?English
    21·
    7 days ago

    Are you asking a technical question or a moral question?

    Pragmatically - IDGAF. If I have it on the ssd, I’ll watch it there. If I need to download from torrent or usenet and then watch it, cool. If it’s easier to use CloudStream (for some transient series), no problem.

    I tend to keep a corpus of movies / shows on my ssd because it’s always there, always reliable, always fast. I have stuff that’s just not easy to find online any more and multi-tenancy / bandwidth are no issue. I can throw it in my bag and watch it wherever, even without net.

    It’s also agnostic. Not every pirate streaming app works on every device. OTOH, samba share / sftp pretty much does. Tonight I streamed stuff onto a OLPC X-O4…good luck getting fmhy to work with that - it can’t even load YouTube directly but stream stuff off the router just fine.

    I don’t use JF much any more (prefer ssd plugged directly into router, accessed via NovaPlayer on android devices; files uploaded to via ftp transfer - yes, very 2010) but I think its pretty amazing. Cloudstream and fmhy are amazing too. Use what works.

  • SuspiciousCarrot78@aussie.zonetoSelfhosted@lemmy.world•How To Parse JSON Data To A Human Readable Format [SOLVED]English
    2·
    12 days ago

    Perfect. Then my third suggestion stands - get it make you a bespoke training module.

    Create a project container: upload the source documents already cited by others / ones you find useful. Just 4 or 5.

    Add the rule “You are helping me learn ____. You must not provide full refactors unless specifically asked for. Use Socratic method where appropriate”.

    Pseudo code what you want to do (hell, draw a flow chart) and ask “based on what I want to do, your background knowledge and the contents of the container, what’s the first thing I need to learn? How should I approach this?”

    Then ask “why?”

    Hell, get it to make you coding exercises.

    After each session, get it to make you a handover note in markdown format. Download it and then add that to your container. (Later on, you can get really fancy and start making your own llm-wiki)

    People shit on LLMs as a knee jerk thing… but coding IS a language…and if you understand the logic, the rest is syntax. Also, it’s not as if you’re making some million dollar mission critical thing- you’re teaching yourself through successive approximation.

    If you don’t feel comfortable using online models, there are even local alternatives.

    I still think JavaScript is the faster way for this, but who knows.

  • SuspiciousCarrot78@aussie.zonetoSelfhosted@lemmy.world•How To Parse JSON Data To A Human Readable Format [SOLVED]English
    23·
    12 days ago

    Scoping first, code ideas at bottom. Kewl?

    Is this a “learn it by coding it” project or is it a “I want this thing to exist, no one has done it, but my code skills aren’t quite there” project?

    If the latter, would you consider iterating via llm (as you mention n8n, so I figure you’re in that space anyway) or is this a purely a learn by doing thing?

    Come to think of it, there is actually a third option here. You could get the LLM to teach you how to code it by writing some pseudo code and asking it for pointers / starting steps. Claude web is pretty good for that sort of thing, I think. You can get it to tailor its lessons to what you need without the tedium of starting at “Hello World”.

    You seem like the sort that could keep that interaction honest and not let it just do everything.

    PS: I read about your setup - sounds brilliant. Go you good thing.

    PPS: n8n has a Code node (JavaScript), and parsing that weather JSON into a formatted string is probably like 15 lines of code. Something like -

    const data = $input.first().json;

    return [{ json: { temperature: data.list[0].main.temp } }];

    add a Code node after your HTTP request in n8n. Get one single value out first. If you see a temperature number in the output, you win.

    Pulling Python in just to parse JSON is probably adding a tool you don’t need for this.

    JavaScript may be ass but it’s literally there, so it’s omnipresent ass. :)

    Once you’ve got the JSON parsed, turn it into one small HTML weather card.

    const data = $input.first().json; const item = data.list[0];

    const html = <div> <h3>Weather</h3> <p>Current temperature: ${item.main.temp} °C</p> <p>Feels like: ${item.main.feels_like} °C</p> <p>Humidity: ${item.main.humidity}%</p> <p>Condition: ${item.weather[0].description}</p> </div>;

    return [{ json: { html } }];

    (Sorry about the formatting ; Lemmy formatting is weird AF)

    Anyway, as one journeyman to another, that’s where I’d start poking. ICBW.

  • SuspiciousCarrot78@aussie.zonetoSelfhosted@lemmy.world•Kittygram v1.1 has releasedEnglish
    1·
    12 days ago

    Let’s tag it as “provisional” then. As in, once you have my provisional trust, accrued over time, I’ll probably stop auditing every single line. I’ll still look tho.

    But the long and short of it is this - XZ utils backdoor actually makes case for trusting clankers more than human collaborators. Clankers are incompetent… they usually aren’t Machiavellian.

    I’ve heard it said that an LLM is like a Labrador retriever when it comes to coding. Overly excited, pulls ahead, does some really goofy shit and sometimes chews up your couch (hello Qwen 27B)…but it is trainable.

    Human devs are like cats…which is oddly on brand for this project :)

    I’d sooner trust a clanker I had prompted with my house style ticket and narrowly sandboxed than a rando online. Of course, the difference is, a rando may eventually earn trust…a clanker doesn’t - but it doesn’t need to if narrowly scoped.

    EDIT: here’s a template I use / created for Qwen / Codex. It’s…opinionated and bears scars of prior over eager Labradors. This is usually step 1 I fill out. My fingers are going to shit with O/A , so am trying to minimise scut work.

    TICKET-Px-SHORT-DESCRIPTIVE-NAME

    Status: PROPOSED Timestamp: DD-MM-YY-HH-MM Priority: P0 | P1 | P2 | P3

    Purpose

    One paragraph:

    • what changes
    • what does not
    • whether this is proposal / proof / implementation

    Why this exists

    Describe:

    • concrete failure mode
    • why current behaviour is wrong
    • why this is architectural not cosmetic
    • why local patches are rejected

    Include: We do not want … We do want …

    Proof requirements before implementation

    Hard gate.

    Before implementation exists, prove:

    • seam exists
    • ownership is correct
    • contract can be enforced
    • no god-object expansion
    • no hidden coupling

    If proof fails: stop and escalate. Do not patch.

    Gates

    • Step 0 GO/NO GO
    • Step 1 GO/NO GO
    • Step 2 GO/NO GO
    • Step N GO/NO GO

    Each gate:

    • exact thing being proven
    • explicit stop condition

    Test Plan

    Mix of:

    • unit fixtures
    • regression replay
    • smoke coverage
    • edge cases
    • negative cases

    Prefer: prove behaviour changed, not just coverage increased.

    Definition of Success / PASS

    Minimum acceptable state.

    Must describe:

    • observable outcome
    • old failure closed
    • contract enforced
    • ownership preserved

    Definition of Success / EXCELLENT

    Stretch target.

    Usually:

    • generalises across adjacent lanes
    • demonstrates reuse
    • proves contract not logging theatre

    Assumptions

    State assumptions explicitly.

    Examples:

    • baseline already proven
    • implementation surface bounded
    • no broad whitelist/regex fix

    Proposed shape

    Describe:

    • modules
    • packets/cards/contracts
    • ownership boundaries
    • interfaces

    Prefer: small typed objects.

    Thin leaf intent

    If adding logic:

    prefer:

    • thin leaf
    • compact return object
    • narrow ownership

    Avoid:

    • diagnostic fluff
    • local maxima

    Policy versus signal

    Policy: config

    Signal: code

    Config controls behaviour. Signal detects reality.

    Scope

    Explicitly include:

    • what this ticket covers

    Non-goals

    Explicitly exclude:

    • unrelated cleanup
    • opportunistic refactors
    • god-object growth
    • broad routing changes

    Acceptance criteria

    Numbered list.

    Must be testable.

    Definition of done

    Agreement on:

    • ownership
    • interfaces
    • config surface
    • enforcement point

    Only then may implementation tickets follow.