That’s true, sr.ht it not a drop-in-replacement, but rather a full on alternative.
That’s true, sr.ht it not a drop-in-replacement, but rather a full on alternative.
I really like radicle though.
I use sourcehut, specifically because I like their web gui!
Do you know how access rights management work on radicle?
Last time I checked I could just add commits to any open PR…
Luckily, the main repo is different, having a canonical version.
Thanks for the writeup! So far I’ve been using ollama, but I’m always open for trying out alternatives. To be honest, it seems I was oblivious to the existence of alternatives.
Your post is suggesting that the same models with the same parameters generate different result when run on different backends?
I can see how the backend would have an influence hanfling concurrent api calls, ram/vram efficiency, supported hardware/drivers and general speed.
But going as far as having different context windows and quality degrading issues is news to me.
Is there an inherent benefit for using NVLINK? Should I specifically try out Aprodite over the other recommendations when having 2x 3090 with NVLINK available?
I use sourcehut.
dd if=/dev/zero of=image.png bs=1k count=1024 conv=notrunc
Good question: https://github.com/styluslabs/Write/commits/master/LICENSE
yes: sntx.space, check out the spurce button in the bottom right corner.
I’m building/running it the homebrewed-unconventional route. That is I have just a bit of html/css and other files I want to serve, then I use nix to build that into a usable website and serve it on one of my homelab machines via nginx. That is made available through a VPS running HA-Proxy and its public IP. The Nebula overlay network (VPN) connects the two machines.
Git integration support was added three weeks ago in 0.3.3 ^^
You still have to install it manually, but it will be a default plugin in an upcoming release.
Please tell ^^
This, or slackhq/nebula
I’m suprised nobody mentioned nebula: A scalable overlay networking tool with a focus on performance, simplicity and security.
I’ve been running it for about two years on multiple machines and it worked flawlessly so far. Even connecting two hosts, both behind mullvad-vpn tunnels.
The only downside is, that you have to host your own discovery server (callled “lighthouses”). One is fine, but running at least two removes the single point of failure from the network.
It’s affected by the write-hole phenomenon. In BTRFS case that can mean that perfectly good old data might corrupt without any notice.