JP Dillingham

Retention and pruning is likely not going to make the cut for the initial implementation. Users can delete the database (or manipulate it with a SQLite tool) if they want...

Closed by #569. I'll create a separate issue for dealing with old records.

Thanks, not sure how I lost track of this, but it is absolutely needed. This will require a new database context (and .db file) for messaging related data, to include...

@skar07 sure thing! I think the ideal solution is to make sure the suffix only appears once, so `1.38 KB/1.38 KB` would appear as `1.38/1.38 KB`. I'm not sure why...

Given that most search lookups complete in well under 1ms, this would not be beneficial in the short term. Long term I'd like to detect long-running responses (for example, responses...

Re-requesting downloads is _sort of_ blocked by #406 (resumable downloads) since anything in progress when the app is restarted would be stuck in a non deterministic state. To do this...

I hear you; I've been struggling to keep track of things since I added the ability to add a bunch of searches one after the other. I think a lot...

Starting with release [0.16.9](https://github.com/slskd/slskd/releases/tag/0.16.9) transfers (including uploads and downloads) are now stored in a SQLite database in `/app/data`. There were some bumps along the way, and as of release [0.16.17](https://github.com/slskd/slskd/releases/tag/0.16.17)...

Thanks for raising this, I agree that it is needed!

~~In case it wasn't clear, the official guidance for M1 Macs is to use the `osx-amd64` binaries until this issue is resolved.~~