• 14 Posts
  • 606 Comments
Joined 2 years ago
cake
Cake day: January 28th, 2025

help-circle



  • Shimitar@downonthestreet.eutoAndroid@lemmy.worldaaa
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 days ago

    And yes Whatsapp telegram matrix… They all create a line of communication like a normal phone. Just shittier, all of them, in my opinion. Latency, shitty connectivity and too long line length (back and forth from their servers) make the call experience pretty bad in my own limited experience. (Ymmv, specially if you have good data / wifi coverage everywhere you are).


  • Shimitar@downonthestreet.eutoAndroid@lemmy.worldaaa
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 days ago

    First of all mandatory “BBB”.

    Now, that’s NOT VoIP. VoIP stands for voice over IP and it’s a bi-directional audio channel very much like standard telephone.

    Maybe you are NOT using VoIP or you are confused by VoIP not sending data packets if no audio is detected? On traditional analog phone lines you always get background noise. Often not the case with VoIP. Maybe it’s even configurable who knows.











  • Op want to upload a file to a web GUI and print it from there, not share printers with other computer/ devices.

    Also, scanservejs is the the sane web GUI to actually do the same with scanner.

    For scanning it make sense as there are no shared scanning solutions across platforms. For printing, it’s of little use as other pointed out you can print to cups from anything basically.

    But o get the need for a web printing page, as uploading a file and hit print button is a zero setup, and while simple even remote cups printing is not 0% extra setup, you have at the very least to select a printer or hit “share as” and select a print service (android). YMMV




  • Uptime for home users is useless. More important is recovery, reboot and resume (the 3’Rs)

    You server should reboot automatically, storage should restore itself from unsafe shutdown and your services should resume operations like nothing happened.

    This means test your reboot, ensure stuff doesn’t break, and so on.

    Failing storage after an hard reboot is the hardest.

    For network, i have two ISP connections and a an auto switch script Incase one goes down. But honestly it’s overkill and not needed for 99% of home hosters.

    Buying some kind of UPS like a battery powered power strip is also nice but keep in mind that require maintenance to replace batteries once every few years (long enough to forget) and so be useless. The ups shall only last enough to perform a controlled server shutdown using NUTS.



  • Llama CPP can run models offloading with CPU (es MoE models), you have much more control over how you run your models, and overall it’s very much actively developed.

    For starters and people without too much willingness to mess up with stuff, ollama is a great choice. Llama.cpp gives you that extra power and flexibility that is so much worth for people who like to tweak and do more.

    My personal opinion, of course. But based on having used both and ditched ollama for llama.cpp, so I am also biased, keep in mind.

    But I will hardly go back to ollama now :)