> 1. It mangles GGUF files so other apps can't use them, and you can't access them either without a bunch of work on your end (had to script a way to unmangle these long sha-hashed file names)
This is what pushed me away from Ollama. All I wanted was to scp a model from one machine to another so I didn't have to re-download it and waste bandwidth. But Ollama makes it annoying, so I switched to llama.cpp. I did also find slightly better performance on CPU vs Ollama, likely due to compiling with -march=native.
> (they don't have to technically thanks to MIT)
Minor nit: I'm not aware of any license that requires improvements to be upstreamed. Even GPL just requires that you publish derivative source code under the GPL.
> That said, the need to compile it yourself is still a pretty big barrier for most people.
My distro (NixOS) has binary packages though...
And there's packages in the AUR (Arch), GURU (Gentoo), and even Debian Unstable. Now, these might be a little behind, but if you care that much you can download binaries from GitHub directly.
mu4e in Emacs works well, or Notmuch, or even Gnus with a local Maildir. Or Mutt if you're more into that. None of these applications can be that much harder than flying the capsule can they?
> I think Emacs today with the jitted Elisp interpreter it's able to do far more stuff than depending on external tools such as GNU coreutils, findutils and non-GNU Gnuplot.
The problem with doing everything in Elisp is the lack of threading. GNU Find can search down multiple directories in parallel, and an Elisp implementation of Grep would block the Emacs UI while searching. Until Elisp gets threading it will fundamentally be limited to either short bursts of computation or frustrating UX because of blocking (see also frustrations with Gnus).
I can't tell if you're being sarcastic, but assuming you're not: Tailscale makes security easier because networks are private by default. To achieve a similar effect with Yggdrasil you'd have to use a firewall to whitelist the Yggdrasil IPs of all your devices. So it's more work to set up.
Huh? I thought one of the appeals of Tailscale is that security is done at the network level; plus that your network is private, so you don't get randos knocking at your ports.
The novelty is that routing is based on cryptographic identity. Yggdrasil's IPv6 addresses are actually truncated representations of public keys. You configure the Yggdrasil software with a list of peers which it connects to over normal internet, but then when you route a Yggdrasil address your device talks to all its peers, who talk to their peers and so on until they find your destination. As I understand it, they optimize it by caching the routing information and using bloom filters to find the appropriate peer.
I actually don't have firewalls set up on my devices that run Yggdrasil yet (please don't crack me). I haven't noticed any brute-force attacks on my SSH servers yet. Though I really should set up firewalls.
As for routing, I run my own node on a VPS, so all my edge devices are peered with that machine so routing is fine. Though when my machines are on the same network they automatically peer with each other directly.
This is what pushed me away from Ollama. All I wanted was to scp a model from one machine to another so I didn't have to re-download it and waste bandwidth. But Ollama makes it annoying, so I switched to llama.cpp. I did also find slightly better performance on CPU vs Ollama, likely due to compiling with -march=native.
> (they don't have to technically thanks to MIT)
Minor nit: I'm not aware of any license that requires improvements to be upstreamed. Even GPL just requires that you publish derivative source code under the GPL.
reply