From 444537ad1731e8ddf5ce8efdbbfeffe27fed2767 Mon Sep 17 00:00:00 2001 From: dasPolygon <polygom+git@systemli.org> Date: Mon, 8 Jan 2024 21:56:51 +0100 Subject: [PATCH] version bump; readme --- Cargo.toml | 4 ++-- README.md | 13 ++++++++++--- 2 files changed, 12 insertions(+), 5 deletions(-) diff --git a/Cargo.toml b/Cargo.toml index 33345ab..5783bc5 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -1,6 +1,6 @@ [package] -name = "matrix_emote_upload" -version = "0.1.0" +name = "emowoji_bot" +version = "1.0.0" edition = "2021" # See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html diff --git a/README.md b/README.md index 91fd7da..92cb4fd 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,11 @@ # emowoji-bot -a not yet fully functional matrix bot that will upload image files from the emotes/ directory to a matrix homeserver and create a custom m.image_pack event to make it available as custom emoji/stickerpack. -We want to add a LARGE amount of emotes to a room, and the clients we've tried to use just all crashed, -the way we wrote this script, we get a `Failed to process emoji pack: the server returned an error: [413 / M_TOO_LARGE] M_TOO_LARGE: Message is too long` - too eepy to debug as of writing this. \ No newline at end of file +A smol (somewhat shitty) matrix bot meant to add a huuge amount of custom emotes to a room. +Usage: +* start like ./emowojÃ_bot <homeserver-url> <username> <password> +* invite the bot to a room +* type `!add <desired_image_pack_name>` +* let it to its thing + +It worked on our conduit server and nheko as a client when adding a smol amount of emotes, +but when we tried to process hundreds of megabyte's we quickly ran into spec limitations due to the max message length being 64kB or something, +so for this to work the events need to be split up in some way - from what we can see now resulting in having a bunch of image packs in the end. \ No newline at end of file -- GitLab