• 3 Posts
  • 534 Comments
Joined 4 years ago
cake
Cake day: January 17th, 2022

help-circle


  • Few seem to address the issue here : it does not work 100% of the time for you.

    It might work for everybody else but that doesn’t help you much. You have your setup, no theirs.

    So… you need to investigate. When it works, great, nothing to learn from. When it fails though… can you find a pattern? Does it always fail after you have use something specific? Check https://lemmy.ml/post/46800646/25494455 which gives examples of potential failure point and journalctl logs. You can then check what failed and if not you can at least know when then backtrack to others logs, e.g. dmesg.

    They key take away is that when things do not behave as expected you need to put a detective hat on and you investigate :

    • what’s your crime scene? Your laptop and it’s log files
    • what’s the crime? It didn’t suspend properly
    • where are the traces? In the logs
    • where are the logs? Using journalctl or dmesg and typically in /var/log/
    • what would a good detective do? Search for specific clues, e.g. places where fingerprints do stick, e.g metal or glass, which here would be error messages. That can be found using grep and other tools

    You also have limited times because the logs will, just like on a real crime scene, get contaminated or rotated or deleted. So… if you do encounter the problem do not rush to the next tasks at hand because you are wasting an opportunity to learn and there is vanishing window.

    TL;DR : grep logs



  • A lot of already great advice here, often clarifying that a computer that is not yours… is not yours.

    What I would still add though is that you are NOT, and I’m very confident in saying this, the only one there, in your very school, to ask that question. In fact I would argue MOST users have the exact same concerns but they might even be aware that alternatives exist.

    So… do not push back, or even just avoid, all this alone. Find others who have similar problems and solve them together.

    There might be a Linux User Group already, join them. If there isn’t one, consider making it. It might just be you for few weeks, even month, but at least you will dedicate time and space to improve YOUR situation. Chances are though that others, even if only curious at first, might check what you are up to, if they can replicate that, etc.

    Don’t feel isolate, move the needle for yourself first, in your corner, but be welcoming to others who are eager to contribute.

    It’s a challenge, but it’s a fun challenge while trying to tackle it with others.





  • IMHO the question depends on :

    • who you are (boring, rando, political dissident, journalist, etc)
    • who you talk to (family, friends, work, etc)
    • what alternatives actually exist

    So… sure Signal is not perfect but if you can’t convince your family members to move to DeltaChat it sure beats using WhatsApp, Telegram, etc.






  • utopiah@lemmy.mltoPrivacy@lemmy.mlClaude: papers please?
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    18 days ago

    IMHO LLM usage isn’t coherent with independence. That being said I wrote quite a bit on self-hosting LLMs. There are quite a few tools available, like ollama itself relying on llama.cpp that can both work locally and provide an API compatible replacement to cloud services. As you suggested though typically at home one doesn’t have the hardware, GPUs with 100+GB of VRAM, to run the state of the art. There is a middle ground though between full cloud, API key, closed source vs open source at home on low-end hardware : running STOA open models on cloud. It can be done on any cloud but it’s much easier to start with dedicated hardware and tooling, for that HuggingFace is great but there are multiples.

    TL;DR: closed cloud -> models on clouds -> self-hosted provide a better path to independence, including training.