From 27b88a475d4a0112b0821c460489510697a460e7 Mon Sep 17 00:00:00 2001
From: Volkor <me@volkor.me>
Date: Sun, 2 Feb 2025 02:04:30 +1100
Subject: [PATCH] update changelog and readme
---
CHANGELOG.md | 14 +++++++++++++-
README.md | 2 +-
2 files changed, 14 insertions(+), 2 deletions(-)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 1710fcf..bd1e26d 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,4 +1,16 @@
+# 0.1.0 (2025-02-02)
+
+- Added distance calculation to the UI
+- Added meshpacket logging (although I might want to remake it for logging telemetry / messages / other stuff better)
+
+
+# 0.1.0 (2025-01-30)
+
+- Added historical logging of data
+- Added a really bad egui for testing
+
+
# 0.1.0 (2025-01-12)
- You can connect to a network connected node.
-- Packets are logged to a database.
\ No newline at end of file
+- Nodes are logged to a database.
\ No newline at end of file
diff --git a/README.md b/README.md
index 5faa14c..4b0d5ca 100644
--- a/README.md
+++ b/README.md
@@ -24,6 +24,7 @@ This project serves as all that + a full historical backend of a meshtastic netw
- Logs meshtastic packets
- Saves them to a database
- Shows nodes in a ugly egui frontend
+ - Shows distance to the connected node
## What it doesn't (currently)
Rough order of how much I want to add support.
@@ -44,7 +45,6 @@ Rough order of how much I want to add support.
- [ ] Can we show the potential nodes that don't have GPS?
- [ ] Can we use heard traceroutes to map out neighbours in the mesh?
- Can we send out some traceroutes every few hours to map it if we don't? (some people don't like meshsense for this reason)
-- [ ] calculate distance to 'collector node'
- [ ] Generates a nice public dashboard (static http, once every hour?)
- Supports anything other than TCP Connection.
- [ ] Bluetooth (how? wtf? i hate bluetooth!)
--
GitLab