

Ollama is in extra, open-webui in the AUR.
Ollama is in extra, open-webui in the AUR.
KeePassXC + KeePass2Android
It was gone?
I only do hardcore horny chats with my LLMs lol
CW be like:
Spend 7 weeks learning C# (we learned Java in Uni, it’s not that hard ffs) and implementing a proper base for a project: Nah
Let ChatGPT generate fucky code and let $me fix it over the span of 7 weeks: Hell yeah
Had I realized that it all was generated, and he didn’t have a single little clue how it works, I would’ve just rewritten it with django or something. Hell, technically the whole server part wasn’t needed, it could’ve been index.html, style.css and scripts.js and that’s it.
As I understand it, they want to train AI with AI?
Except in the 10% of times, in 30% of those you’ll have a hell of a lot of fun finding which exact line has one little variable name mismatch. But if you’re actually very careful, it’s a nice feature.
Co"worker" spent 7 weeks building a simple C# MVC app with ChatGPT
I think I don’t have to tell you how it went. Lets just say I spent more time debugging “his” code than mine.
Yes. (n)vi(m) > Emacs, and Bing >= Google. So it should be vi SearxNG
But remember, on a third device. Not the one where your KeePass DB is one fingerprint away, and your private SSH key too.
Tbh, I myself still have SSH on port 22. Firstly, because I’m lazy, and secondly … yeah that’s it. I’m honestly just lazy. But spam bots trying office/cookie123 are not a real threat, and anyone trying to actually target me will either have somehow acquired my key + password, use one of the probably many security issues that exist in the dozen services I selfhost, social engineer me into doing something (not saying I’ve given out my (old) KeePass password once, but it could be, as love makes blind (I still love her)), or just smash my kneecaps until I give out everything.
Move SSH to non-standard port, make endlessh use the default port. Only use SSH keys. Only allow correct users (so eg. your user and git/forgejo). Use fail2ban to aggressively ban (redirect to default port, so 22) and report to abuseipdb everything that fails to authenticate first try (wrong user, password instead of key), has non-compatible ciphers (generally, only allow TLS1.3 etc.), or fails in any other way. Just be sure that if you accidentally get banned yourself (eg. Ctrl+C-ing during authentication), you can use another IP (eg. force v4) for connecting.
Reminder that old games, ported correctly, run on anything. We just need the source.
I’d say that yay encourages checking the PKGBUILD or its diff more than the average “curl xy | sudo sh” instruction, but considering most people see yay just as yet another package manager, instead of an AUR helper, that’s probably true for most people
Except it automates the steps you’d have to take to inspect and edit the script, if needed. Also, PKGBUILDs are much nicer to read than just plain install scripts. And, of course, it actually builds a package, which is then installed, so it’s not only tracked but can be updated like the rest of the system.
yay <package name>
There is a 99% chance it’s in there, and there is an 80% chance it uses the latest version/git HEAD
Meanwhile my workflow of creating anything:
And then I have a native thingy working on every Arch machine I have (a server, a workstation, two DNS/DHCP servers, a PC and a laptop). And as the servers are chilling at my dad’s place … it’s not even costing me much (excluding 1000/500 fiber for like 100€/month, which is technically mine)