Comments (6)
tbvdm
commented on August 23, 2024
Could you please implement a timestamp option so that only messages and/or attachments younger than a given timestamp (either epoch or optionally human-readable) are exported? This would make cumulative backups much less cumbersome.
I agree it would be useful to have options to select a subset of messages or attachments. Selection based on time, as you propose, would be one of those options. I'll look into it.
1. Could you please make the filename resolution logic configurable when exporting attachments, so that it is also possible to either overwrite existing files or only export attachments which are not already present in the filesystem (or let the user choose interactively, as is standard for cp)? The current behaviour of exporting everything again, possibly with some digit appended to the filename, is not very useful in my opinion.
When sigtop exports an attachment, it uses the attachment's original filename, if available. However, sometimes it happens that different attachments have the same original filename. In those cases, sigtop adds a sequence number to the filename.
For this reason, skipping or overwriting existing files is not straightforward. sigtop cannot tell if an existing file is an identical attachment from a previous export or a different attachment with the same filename.
As things stand, it's best to export attachments to an empty directory.
2. Maybe it would be a good idea to optionally offer a more meaningful naming logic for exported attachments, for example by prepending the message timestamp formatted in a human-readable format (YYYY-MM-DD_HH_MM_SS). But this job is probably easier done in some post-processing script using python, Perl and the likes (of course sacrificing some speed).
If the original filename for an attachment is not available, sigtop falls back to a hexadecimal string. I think you are referring to these hexadecimal filenames. I agree it would be better to fall back to a time-based name instead. I'll look into that, too.
from sigtop.
tbvdm
commented on August 23, 2024
If the original filename for an attachment is not available, sigtop falls back to a hexadecimal string. I think you are referring to these hexadecimal filenames. I agree it would be better to fall back to a time-based name instead. I'll look into that, too.
I've just fixed this. Attachments (without original filename) now have filenames of the form "attachment-yyyy-mm-dd-hh-mm-ss.ext". Thanks.
from sigtop.
tbvdm
commented on August 23, 2024
Could you please implement a timestamp option so that only messages and/or attachments younger than a given timestamp (either epoch or optionally human-readable) are exported? This would make cumulative backups much less cumbersome.
@herrsimon I've added the -s option to the attachments and messages commands. See the manual for details. In your case, to export attachments sent at or after a given time, you'd use something like this (note the comma after the time):
sigtop attachments -s 2021-01-23T12:34:56, ~/.config/Signal
Does this work out for you?
from sigtop.
herrsimon
commented on August 23, 2024
Hi and sorry for this super late reply, I had a long-distance move, change of job and newborn kid to take care of (no joke). The -s option works like a charm, thanks a lot for implementing! One more thing to consider would be to (optionally) store or link attachments in subdirectories named after the phone number of the communication partner. This would make it much easier to find them afterwards ("where is that picture I sent to my spouse?"). This is of course not essential but would be a nice addon. Thanks again and have a nice weekend!
from sigtop.
tbvdm
commented on August 23, 2024
Hi and sorry for this super late reply, I had a long-distance move, change of job and newborn kid to take care of (no joke).
No worries. And congratulations!
The -s option works like a charm, thanks a lot for implementing!
Great!
One more thing to consider would be to (optionally) store or link attachments in subdirectories named after the phone number of the communication partner. This would make it much easier to find them afterwards ("where is that picture I sent to my spouse?"). This is of course not essential but would be a nice addon.
I see what you mean. Yes, that seems useful. I'll look into it.
from sigtop.
tbvdm
commented on August 23, 2024
One more thing to consider would be to (optionally) store or link attachments in subdirectories named after the phone number of the communication partner.
Hi. At long last, this has been implemented.
from sigtop.
Related Issues (20)
- Not enough tokens to parse JSON HOT 1
- Sigtop selective export HOT 2
- Issues with accessing exported browser file HOT 6
- Precombiled Windows app crashes immediately after opening. HOT 1
- cannot install on linux: "cannot use path@version syntax in GOPATH mode" HOT 2
- sigtop: cannot prepare statement: no such column: uuid HOT 2
- path_windows.go: sanitiseFilename is not robust HOT 10
- If I don't want to run sigtop on the production database of my signal desktop, how do I run it? HOT 1
- Export to HTML and link attachments HOT 6
- Program detected as a virus HOT 2
- "att -M" command throws error "utimes: unsupported flag" HOT 6
- Emoji in chat title HOT 8
- Bash Command not found HOT 1
- brew installation error: "go build: Error: Passed `nil` into T.must" HOT 2
- -i option for messages HOT 1
- Not a database error when running sigtop db HOT 13
- Attachments decryption HOT 2
- Feature: Include contact names in JSON message export HOT 2
- skipping attachment without path HOT 2
- cannot decrypt database key: cannot find encryption key HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sigtop.