Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)S
Posts
17
Comments
286
Joined
3 mo. ago

  • This is my final reply in this thread. The developer has said their piece, and I have said mine. Now you've waded in - so let me set the record straight.

    I am a developer. I had genuine interest in this project. I read the Hister documentation and inspected parts of the repository because the documentation did not clearly answer several basic questions I had:

    • How SQLite, Bleve, and stored HTML relate.
    • Whether TTL or storage quotas exist.
    • How browser-history deletion affects stored data.
    • How previews differ from a real web archive.
    • What multi-user isolation actually covers.

    Yes, I used AI to assemble a plain-language summary and labelled it accordingly. Not everyone keeps the Hister codebase in their head, not everyone talks in code review and if I had these questions, I'm willing to bet others did too. The AI wrote for a lay audience because I didn't ask it to do QA, I asked it to ELI-5.

    The summary contained errors. Fine. That's AI for you. However, if neither I nor the AI could find clear answers after cloning the repo, that supports my point about opacity.

    At no point did I request a line-by-line audit. “Points 2 and 5 are wrong” would have answered the question.

    Declining would also have been reasonable. Hell, side stepping it would have been fine too. Instead the dev decided to note the inaccuracies and rudely brush them off.

    Both you and the dev seem to be under the impression !selfhosted is a one way distribution channel.

    The developer came here, invited questions, then turned the raw prawn when questions arrived.

    I didn't go to their their Github. I didn't abuse them. I genuinely wanted to know more about their project and share it, perhaps even work to help improve it.

    They - and now you, ostensibly a happy clapper for Hister - came here.

    Your claims about my effort and intent are assumptions followed by personal abuse.

    Try and walk a mile in someone else's shoes before calling them low effort and shitty next time.

  • That is not what happened.

    I fed your GitHub repository to a clanker because the documentation did not answer my questions. I then shared its summary here.

    You replied afterwards and said the summary was wrong. Fair enough. I then asked which specific points were wrong.

    You could have answered, declined, or ignored the post.

    Instead, you deigned only to dismiss the effort, then blamed me for objecting.

    You also asked which parts were confusing, although my previous reply had already listed those issues.

    You did not address them then, either.

    A prospective user should not need ChatGPT, a cloned repository, and several follow-up questions to understand key functions.

    You invited feedback. Your documentation remains unclear on several points, including issues beyond those I listed.

    Your responses show that further feedback is not worth my time.

  • I am happy to narrow it further.

    I took the time to read the documentation, ask ChatGPT to summarise what I found, and then reduced my follow-up to a simple request:

    «Which of points 1–7 are materially wrong?»

    That is not the same as asking you to audit "multiple screens" of AI output.

    If the answer is "2 and 5 are incorrect", or even "I do not have time to review it", that is perfectly fine.

    However, dismissing it as "a multiple screens long AI prompt" does not only not answer the question, it comes off as abrasive.

    As for the documentation, the confusing parts are exactly those I listed: retention, lifecycle management, browser ingestion, storage limits, deletion, multi-user behaviour, and, most importantly, what Hister actually is and who it is for.

    What's disappointing is not that you disagreed with the AI summary. AIs are idiots.

    It that after inviting questions and feedback, your response to a genuine attempt to understand the project is curt dismissal.

    The inner workings of Hister may be obvious to you; they are not obvious to others.

    The point is that you came here specifically to invite questions and feedback.

    "TL;DR" does not encourage the sort of community engagement you ostensibly came here to seek.

  • Excellent - thanks for clearing that up.

    Is there a TTL / max database size per user setting? Say I have 4 users using the server; can I allocate a hard limit of 10GB per user, with 180 day retention rules?

    Additionally, is the other parenthetical information materially correct? If not, which points [1 thru to 7] are wrong?

    I would like to further recommend Hister but your documentation is somewhat confusing at first blush.

  • Both; it has internally reduced thinking tokens AND it's less verbose, so you get a boost on both prefill and print. I've benchmarked identical prompts and tool calls with stock Qwen 35B and Grug 35B; on average, what takes stock 1000 token/s, Grug does in about 200.

  • Selfhosted @lemmy.world

    What's your favourite thing to self host and why?

  • You never cease to amaze me, irmadlad.

  • I think I'm going to put a declarations.md that says something like "I made this for me, but I'm sharing it with the world. If you find it useful, use it and let me know! If you find issues, submit request and I'll look but no promises. And if you want feature X ... fork it and build it. The code's yours, with my blessings. PS: I don't accept PRs, sorry".

    I code for fun; I'm not looking for a third unpaid job. That's what parenting is for.

  • Please tell me that's ai slop parody.

    I mean..it has to be. And the fact YouTube is just merrily injecting it into their streams is amazing.

    I use Smartube and PipePipe and haven't seen ads on YT since forever. Is this really what it's like now?

  • Interesting question. If you are asking for an LLM (that is self-hosted and can do that?), you're going to need to provide some significant tooling, like rag / documentation, troubleshooting, sort out concurrency, front end etc. Honestly...it just easier to point them at a YouTube (network chuck has good stuff).

    It absolutely can be done and it absolutely can be valuable - for you personally. But if they're having trouble doing basic things like installing jelly fin, they have zero chance of doing something like that themselves.

    Honestly, I think your easiest option for your non-technical friends is just to point them at one of the cloud providers, like chatGPT or Claude.

    OTOH, how much work are you willing to put into this and what's your GPU / LLM set up like? There

    Your basic foot in door starting point is going to be installing and provisioning OpenWebui, getting a good local model up and running (Qwen3.6-35B or Qwen3.6-27B) and creating a "Knowledge Base" in OWUI with requisite documentation. You'll need to set up tailscale / headscale so they can access your OWUI instance from their homes, too.

    If you're serious about this, write back and I'll thumbnail sketch it out for you. It's a good project and I've done similar. There are real complexities to something like this beyond just "install ollama, lol done".

  • Brilliant!

    How does it go for chewing thru the phone battery tho?

  • For context, that comes for the HN thread and blog post, not from anything I have written. Let's attribute things to respective sources :)

  • Dunno if you can do this with ipads, but I've been (idly) considering using old phones to create an Alfred camera system

    https://alfred.camera/

    Probably not...but it's a fun idea.

  • Selfhosted @lemmy.world

    The Codeberg ban on LLM content

  • Slight revision: on my rig (i7-8700, 32gb, Quadro p1000 4gb ddr5), this gives a nice 12 tok/s. Unfortunately, it's still hostile to my 1L box and very quickly thermally swamps the CPU (while gpu sits at 56 degrees, that little shit). C'est la vie.

     
        
     -t 8 ^
      -tb 8 ^
      -ngl 99 ^
      --n-cpu-moe 38 ^
      --flash-attn on ^
      --no-mmap ^
      --mlock ^
      --cache-type-k q4_0 ^
      --cache-type-v q4_0 ^
      -c 16384 ^
      -b 256 ^
      -ub 128 ^
      --host 0.0.0.0 ^
      --port %PORT% ^
      --ui-mcp-proxy
    
      

  • I suspect the verbosity of Qwen 3.6 CoT token's is what causes the famous schitzo loop. Will be interesting to see if this holds.

    The QAT versions also dropped today

  • LocalLLaMA @sh.itjust.works

    Grug (caveman compression) of Qwen3.6-35 and 27B is good!

  • Selfhosted @lemmy.world

    Does any self host Meilisearch?

  • Selfhosted @lemmy.world

    Self-hosting, data sovereignty and cyberattacks

  • Selfhosted @lemmy.world

    Nomad: ESP-32 media server

  • Selfhosted @lemmy.world

    Self hosting on retro computer?

  • LocalLLaMA @sh.itjust.works

    Lumo 2.0 is out

  • Selfhosted @lemmy.world

    Do you host your own AI?

  • Selfhosted @lemmy.world

    Should AI disclosure tags [AI], [NOT AI] be mandated when sharing projects?

  • Selfhosted @lemmy.world

    No man is an island

  • LocalLLaMA @sh.itjust.works

    "The future of AI depends on the moral compass of five people."

  • Selfhosted @lemmy.world

    Best speech to text for arthritic fingers?

  • Selfhosted @lemmy.world

    Another reason to self host your own AI

  • LocalLLaMA @sh.itjust.works

    Claude? No. Cucumbers? Yes!

  • LocalLLaMA @sh.itjust.works

    "The cost of running LLMs is just too damn high"

  • LocalLLaMA @sh.itjust.works

    Token Speed visualiser

    mikeveerman.github.io /tokenspeed/