nheko
axolotl
Our great sponsors
nheko | axolotl | |
---|---|---|
17 | 27 | |
1,740 | 5,156 | |
2.3% | 26.6% | |
9.7 | 9.8 | |
6 days ago | 4 days ago | |
C++ | Python | |
GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nheko
-
PSA: security vulnerability in qBitorrent 4.5.x webUI
Look at this, notice anything different? https://github.com/Nheko-Reborn/nheko/issues/new/choose
-
This Year in Matrix
Nheko has been around for a number of years. Never used it myself though.
-
Matrix was worth the effort to self host.
Matrix clients hit different than pretty much any other chat client I've use before. Theres multiple clients I've found like nheko, moments, element that are a pleasure to look at and smooth as hell. Even better you can have users use web services like Element Web to sign-up and chat. Its sick.
-
What flatpaks are "official" (i.e., directly from the application's developer)?
The Nheko flatpak is official. Just compare the source to the nightlies we build and upload to our nightly repo.
-
GTK4 Matrix Client
Like almost every client out there it has no support for e2ee. I was happy to find https://nheko-reborn.github.io (I'm a KDE user so Qt apps are preferred).
- Mozilla Thunderbird Beta now supports Matrix chat
-
Using Files with Browsers, in Reality
I probably wouldn't have guessed that `e.dataTransfer.items` gets cleared at the first await (since I'm not a proficient web developer), but I would've been extremely wary of this code in general. Additionally (not tied to async-await but race conditions in general), is `item.getAsFileSystemHandle()` a TOCTTOU vulnerability where the type of an item can change between folders and files and symlinks etc., while this code is running?
Rust's & vs. &mut system largely eliminates shared state hazards in both threading and asynchronity (&mut is exclusive/unaliased and can't be mutated by other threads or event loop jobs, and & is difficult and unidiomatic to mutate), though it doesn't solve async cancellation errors (https://carllerche.com/2021/06/17/six-ways-to-make-async-rus..., discussed at https://news.ycombinator.com/item?id=27542504), or filesystem TOCTTOU (https://blog.rust-lang.org/2022/01/20/cve-2022-21658.html as well as user code).
Qt event loop reentrancy is fun(tm) as well. It looks like a blocking call, but spawns a nested event loop which can do anything (but rarely enough to lull you into a false sense of complacency), resulting in segfaults like https://github.com/Nheko-Reborn/nheko/issues/656 (workaround at https://github.com/Nheko-Reborn/nheko/commit/570d00b000bd558..., I didn't look into it). And Qt lacks "easy" await syntax and a framework based on calling red functions (though I didn't look into C++20 coroutines yet, perhaps https://www.qt.io/blog/asynchronous-apis-in-qt-6 or https://github.com/mhogomchungu/tasks or https://blog.blackquill.cc/asynchronous-qtquick-uis-and-thei...?).
- Introducing Native Matrix VoIP with Element Call!
-
How a Single Line of Code Made a 24-Core Server Slower Than a Laptop
> So forcing everyone to think about ownership because maybe they are writing concurrent code (then again maybe they aren't) so that "congrats your memory management problems are solved" seems like a Pyrrhic victory--you've already blown their brain cells on the wrong problem.
https://manishearth.github.io/blog/2015/05/17/the-problem-wi... argues that "[a]liasing with mutability in a sufficiently complex, single-threaded program is effectively the same thing as accessing data shared across multiple threads without a lock". This is especially true in Qt apps which launch nested event loops, which can do anything and mutate data behind your back, and C++ turns it into use-after-free UB and crashing (https://github.com/Nheko-Reborn/nheko/issues/656, https://github.com/Nheko-Reborn/nheko/commit/570d00b000bd558...). I find Rust code easier to reason about than C++, since I know that unrelated function calls will never modify the target of a &mut T, and can only change the target of a &T if T has interior mutability.
Nonetheless the increased complexity of Rust is a definite downside for simple/CRUD application code.
On the other hand, when a programmer does write concurrent code with shared mutability (in any language), in my experience, the only way they'll write correct and understandable code is if they've either learned Rust, or were tutored by someone at the skill level of a Solaris kernel architect. And learning Rust is infinitely more scalable.
Rust taught me to make concurrency tractable in C++. In Rust, it's standard practice to designate each piece of data as single-threaded, shared but immutable, atomic, or protected by a mutex, and separate single-threaded data and shared data into separate structs. The average C++ programmer who hasn't studied Rust (eg. the developers behind FamiTracker, BambooTracker, RtAudio, and RSS Guard) will write wrong and incomprehensible threading code which mixes atomic fields, data-raced fields, and accessing fields while holding a mutex, sometimes only holding a mutex on the writer but not reader, sometimes switching back and forth between these modes ad-hoc. Sometimes it only races on integer/flag fields and works most of the time on x86 (FamiTracker, BambooTracker, RtAudio), and sometimes it crashes due to a data race on collections (https://github.com/martinrotter/rssguard/issues/362).
- Update on beta testing payments in Signal
axolotl
- LoRA from Scratch implementation for LLM finetuning
-
Dataset Creation Tools?
You can save that overall set into a json file and load it up as training data in whatever you're using. I'm using axolotl for it at the moment. Though a GUI based option is probably best for the first couple of tries until you get a feel for the options.
-
Run LLMs at home, BitTorrent‑style
80GB is enough, yeah.
I'm not sure what exact LORA/quantization settings would be ideal, but check out https://github.com/OpenAccess-AI-Collective/axolotl#config
-
Show HN: Fine-tune your own Llama 2 to replace GPT-3.5/4
There are already many hundreds of finetunes on huggingface, and many excellent UIs to run them in, like KoboldCPP and Text-gen-ui: https://huggingface.co/models?sort=modified&search=13B
There is even a crowdsourced version of the UI like artbot: https://lite.koboldai.net/#
And there are some excellent extant finetuning frameworks, like Aoxotol, that run on consumer GPUs: https://github.com/OpenAccess-AI-Collective/axolotl
IIRC Text-gen-ui had a QLORA finetuning UI too.
-
Help with QLoRA Fine Tune
Two other reference points for parameter choices: - https://github.com/OpenAccess-AI-Collective/axolotl/blob/main/examples/openllama-3b/qlora.yml - https://www.reddit.com/r/LocalLLaMA/comments/14q51cf/comment/jqm8g0i/
-
Any guide/intro to fine-tuning anywhere?
I have seen several folks using https://github.com/OpenAccess-AI-Collective/axolotl but no personal experience, please report back!
- Developer Help
-
Finetuning on multiple GPUs
Finetuning on multiple GPUs works pretty much out of the box for every finetune project I've tried. Here's the best finetune codebase I'd found that supports QLoRA: https://github.com/OpenAccess-AI-Collective/axolotl
-
I would like to try my hand at finetuning some models. What is the best way to start? I have some questions that I'd appreciate your help on.
For finetunings, I would recommend the https://github.com/OpenAccess-AI-Collective/axolotl library. It is friendly for new users since there are pre-existing example configs to adapt for different base models and datasets. Also, the maintainers are pretty quick to add new techniques. As an example, they incorporated finetuning with QLoRA landmark tokens from u/NeverEndingToast over the weekend.
What are some alternatives?
gomuks - A terminal based Matrix client written in Go.
axolotl - A Signal compatible cross plattform client written in Go, Rust and Vuejs
Signal-Android - Patches to Signal for Android removing dependencies on closed-source Google Mobile Services and Firebase libraries. In branches whose names include "-FOSS". Uses new "foss" or "gms" flavor dimension: build with "./gradlew assemblePlayFossProdRelease".
weechat-matrix - Weechat Matrix protocol script written in python
telegram-bot-api - Telegram Bot API server
gpt-llm-trainer
signal-cli - signal-cli provides an unofficial commandline, JSON-RPC and dbus interface for the Signal messenger.
org.signal.Signal
dendrotox - Python interface to Tox distributed communications
LoRA - Code for loralib, an implementation of "LoRA: Low-Rank Adaptation of Large Language Models"
Signal-Server - Server supporting the Signal Private Messenger applications on Android, Desktop, and iOS
otter - Music player for Funkwhale