aboutsummaryrefslogtreecommitdiffstats
path: root/mds/oneclientforeverything.txt
diff options
context:
space:
mode:
authorterminaldweller <devi@terminaldweller.com>2024-05-20 02:23:40 +0000
committerterminaldweller <devi@terminaldweller.com>2024-05-20 02:23:40 +0000
commitfe8f6fc5246abf4d99db034d8848c0297f9c9c1a (patch)
tree15e7f63528f8e62c91034f146027081a3407f56a /mds/oneclientforeverything.txt
parentWIP (diff)
downloadblog-fe8f6fc5246abf4d99db034d8848c0297f9c9c1a.tar.gz
blog-fe8f6fc5246abf4d99db034d8848c0297f9c9c1a.zip
new article
Diffstat (limited to 'mds/oneclientforeverything.txt')
-rw-r--r--mds/oneclientforeverything.txt96
1 files changed, 94 insertions, 2 deletions
diff --git a/mds/oneclientforeverything.txt b/mds/oneclientforeverything.txt
index 9d61a5b..dff38b7 100644
--- a/mds/oneclientforeverything.txt
+++ b/mds/oneclientforeverything.txt
@@ -244,9 +244,101 @@ volumes:
matterircddb:
----
-timestamp:1699398469
+==== SMS
+
+I have an entire post about how one can get their SMS on IRC
+link:posts/how_to_get_your_sms_on_irc[here]. You need a piece of
+software on your phone to forward the SMS to a web hook server and then
+we send the SMS over to IRC. You can find the web-hook server that I use
+https://github.com/terminaldweller/sms-webhook[here].
+
+==== where to sink all the bridges
+
+Bridges connect two things. You need to have a sink for your bridges. I
+was contemplating making a lot of invite-only channels protected by
+password on public networks then I found out about
+https://github.com/ergochat/ergo[ergo]. I’d say the main advantage of
+using ergo is, it’s easy to setup. You don’t need any other services to
+run to get basic functionality like chanserv or nickserv. You don’t even
+need a bouncer if you need to have your messages when your client
+disconnects. ergo has that functionality built-in. Here are some other
+perks:
+
+* ergo allow you to define a ``private'' IRC network. You do that by
+requiring SASL while connecting, so others can’t connect to your
+instance without having an account
+* it is under active development
+* it has good documentation
+* its one executable written in go so it’s very easy to deploy
+
+==== bots
+
+We have LLMs now. The genie is out of the box. They are useful.’ I
+needed a bunch of them to I wrote
+https://github.com/terminaldweller/milla[milla]. At the time of writing
+milla supports chatgpt, gemini and of course ollama.
+
+===== Deploying milla
-version:0.1.0
+[source,yaml]
+----
+version: "3.9"
+services:
+ milla:
+ image: milla
+ build:
+ context: .
+ deploy:
+ resources:
+ limits:
+ memory: 64M
+ logging:
+ driver: "json-file"
+ options:
+ max-size: "100m"
+ networks:
+ - millanet
+ restart: unless-stopped
+ command: ["--config", "/opt/milla/config.toml"]
+ volumes:
+ - ./config.toml:/opt/milla/config.toml
+ cap_drop:
+ - ALL
+ dns:
+ - 9.9.9.9
+ environment:
+ - SERVER_DEPLOYMENT_TYPE=deployment
+ entrypoint: ["/milla/milla"]
+networks:
+ millanet:
+----
+
+[source,toml]
+----
+ircServer = "irc.terminaldweller.com"
+ircPort = 6697
+ircNick = "mybot"
+ircSaslUser = "mybot"
+ircSaslPass = "mypass"
+ircChannel = "#mychannel"
+ollamaEndpoint = ""
+temp = 0.2
+ollamaSystem = ""
+requestTimeout = 10
+millaReconnectDelay = 60
+enableSasl = true
+model = "llama2-uncensored"
+chromaStyle = "rose-pine-moon"
+chromaFormatter = "terminal256"
+provider = "ollama" # ollama, chatgpt, gemini
+apikey = "key"
+topP = 0.9
+topK = 20
+----
+
+timestamp:1713480455
+
+version:1.0.0
https://blog.terminaldweller.com/rss/feed