You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the 5 out of 5 Oxen storage servers I investigated, I found some long-term leftover messages. These messages are rare, usually less than 10 per day, but seems to exist on every server. They have timestamps starting from July 31, 2023, and have very recent expiry dates, for example, April 5, 2024.
To Reproduce
Execute the following queries to count messages or public keys by date.
SELECT
DATE(timestamp / 1000, 'unixepoch') AS date,
COUNT(*) AS message_count
FROM
owned_messages
WHERE
namespace = 0
GROUP BY
DATE(timestamp / 1000, 'unixepoch');
SELECT
DATE(timestamp / 1000, 'unixepoch') AS date,
COUNT(DISTINCT pubkey) AS pubkey_count
FROM
owned_messages
WHERE
namespace = 0
GROUP BY
DATE(timestamp / 1000, 'unixepoch');
At the time of writing, all messages prior to February 8, 2024, should have already been deleted, in theory. I'm not sure if these leftover messages have anything to do with users complaining about seeing unexpected messages reappear, or if they are the result of a legacy bug that miscategorized configuration messages into namespace 0.
Screenshot
The text was updated successfully, but these errors were encountered:
Describe the Bug
On the 5 out of 5 Oxen storage servers I investigated, I found some long-term leftover messages. These messages are rare, usually less than 10 per day, but seems to exist on every server. They have timestamps starting from July 31, 2023, and have very recent expiry dates, for example, April 5, 2024.
To Reproduce
Execute the following queries to count messages or public keys by date.
At the time of writing, all messages prior to February 8, 2024, should have already been deleted, in theory. I'm not sure if these leftover messages have anything to do with users complaining about seeing unexpected messages reappear, or if they are the result of a legacy bug that miscategorized configuration messages into namespace 0.
Screenshot
The text was updated successfully, but these errors were encountered: