cel
/
nederlandskie
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
nederlandskie/Cargo.toml

35 lines
930 B
TOML
Raw Normal View History

Initial version of things: just reads the stream of messages and prints it out and that's that
2023-08-18 20:11:49 +01:00
[package]
name = "nederlandskie"
version = "0.1.0"
edition = "2021"
Add some untested version of publishing a feed Also adjust names of different env vars, and also adjust setup instructions
2023-09-22 12:33:13 +01:00
default-run = "nederlandskie"
Initial version of things: just reads the stream of messages and prints it out and that's that
2023-08-18 20:11:49 +01:00
# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html
[dependencies]
Upgrade everything to latest versions This includes a bunch of small changes to adapt to how atrium-api has changed over time. They're not functional or interesting, just some type-level adjustments that are needed. Some more complicated logic was changed in how profile details are parsed, since atrium's way of doing things is weird and hard to understand so I just manually grab stuff from the object map instead of relying on atrium's types. This is similar to how CBOR parsing is done. Boring maintenance stuff.
2024-08-18 12:35:41 +01:00
anyhow = "1.0.86"
async-trait = "0.1.81"
atrium-api = "0.24.2"
atrium-xrpc = "0.11.3"
atrium-xrpc-client = "0.5.6"
axum = "0.7.5"
chat-gpt-lib-rs = "0.5.1"
chrono = "0.4.38"
clap = { version = "4.5.16", features = ["derive"] }
Read chatgpt and postgresql credentials from .env
2023-09-07 18:20:38 +01:00
dotenv = "0.15.0"
Upgrade everything to latest versions This includes a bunch of small changes to adapt to how atrium-api has changed over time. They're not functional or interesting, just some type-level adjustments that are needed. Some more complicated logic was changed in how profile details are parsed, since atrium's way of doing things is weird and hard to understand so I just manually grab stuff from the object map instead of relying on atrium's types. This is similar to how CBOR parsing is done. Boring maintenance stuff.
2024-08-18 12:35:41 +01:00
env_logger = "0.11.5"
http = "1.1.0"
ipld-core = "0.4.1"
Upgrade dependencies No breakage this time, nice
2023-12-22 09:43:52 +00:00
lingua = "1.6.2"
Upgrade everything to latest versions This includes a bunch of small changes to adapt to how atrium-api has changed over time. They're not functional or interesting, just some type-level adjustments that are needed. Some more complicated logic was changed in how profile details are parsed, since atrium's way of doing things is weird and hard to understand so I just manually grab stuff from the object map instead of relying on atrium's types. This is similar to how CBOR parsing is done. Boring maintenance stuff.
2024-08-18 12:35:41 +01:00
log = "0.4.22"
Upgrade dependencies No breakage this time, nice
2023-12-22 09:43:52 +00:00
once_cell = "1.19.0"
Initial version of things: just reads the stream of messages and prints it out and that's that
2023-08-18 20:11:49 +01:00
rs-car = "0.4.1"
Upgrade dependencies
2023-08-31 14:09:42 +01:00
scooby = "0.5.0"
Upgrade everything to latest versions This includes a bunch of small changes to adapt to how atrium-api has changed over time. They're not functional or interesting, just some type-level adjustments that are needed. Some more complicated logic was changed in how profile details are parsed, since atrium's way of doing things is weird and hard to understand so I just manually grab stuff from the object map instead of relying on atrium's types. This is similar to how CBOR parsing is done. Boring maintenance stuff.
2024-08-18 12:35:41 +01:00
serde = "1.0.208"
serde_ipld_dagcbor = "0.6.1"
Remove ciborium in favor of custom deserialization logic Unfortunately, looks like serde is not flexible enough to support everything CBOR does, so a lot of messages cannot be deserialized properly. Other serde-based CBOR libraries suffer from the same problem. So now we have a bunch of boring deserialization logic supported by sk-cbor
2023-09-24 19:06:20 +01:00
sk-cbor = "0.1.2"
Upgrade everything to latest versions This includes a bunch of small changes to adapt to how atrium-api has changed over time. They're not functional or interesting, just some type-level adjustments that are needed. Some more complicated logic was changed in how profile details are parsed, since atrium's way of doing things is weird and hard to understand so I just manually grab stuff from the object map instead of relying on atrium's types. This is similar to how CBOR parsing is done. Boring maintenance stuff.
2024-08-18 12:35:41 +01:00
sqlx = { version = "0.8.0", default-features = false, features = ["postgres", "runtime-tokio-native-tls", "chrono"] }
Upgrade tokio stuff Something is screwy with stack overflowing when there's many profiles to check This is my first attempt at fixing the problem
2024-11-17 18:28:27 +00:00
tokio = { version = "1.41.1", features = ["full"] }
tokio-stream = "0.1.16"
Upgrade everything to latest versions This includes a bunch of small changes to adapt to how atrium-api has changed over time. They're not functional or interesting, just some type-level adjustments that are needed. Some more complicated logic was changed in how profile details are parsed, since atrium's way of doing things is weird and hard to understand so I just manually grab stuff from the object map instead of relying on atrium's types. This is similar to how CBOR parsing is done. Boring maintenance stuff.
2024-08-18 12:35:41 +01:00
tokio-tungstenite = { version = "0.23.1", features = ["native-tls"] }