core: auto-delete by TTL setting

[ayoung19]

Auto-delete old entries by giving entries an expiration or after the list hits a certain number of entries.

[Ribas160]

The easiest way is to remove entries by list length. But it is possible to do both and allow the user to switch between them and change the settings (max list length, number of minutes/hours/days). It depends on your goal and the complexity you want to add to the application.

[ayoung19]

Users are requesting the option to auto-delete both ways. Here is the inspiration (first two options):

Did you want to take this on?

[Ribas160]

Yes, I would like to work on it.

[ayoung19]

Ok I'm currently working on the popup side of this (UI that lets the user configure the settings). You can work on ingesting this setting and perform the behavior on entry creation. Does that sound good to you? Let's also start with just the max number of entries auto-delete setting:

import { z } from "zod";

// DO NOT REUSE DEPRECATED FIELDS.
export const defaultSettings = {
  totalItemsBadge: true,
  // theme: "light",
  themeV2: "system",
  localItemLimit: undefined,
};

export const Settings = z
  .object({
    totalItemsBadge: z.boolean().default(defaultSettings.totalItemsBadge),
    // theme: z.string().default(defaultSettings.theme),
    themeV2: z.string().default(defaultSettings.themeV2),
    localItemLimit: z.number().optional(),
  })
  .default(defaultSettings);
export type Settings = z.infer<typeof Settings>;

The new settings field will be localItemLimit with a type of number | undefined where undefined means it's off.

[ayoung19]

Also do you have a rough timeline on when you could do this by?

[Ribas160]

Ok, it is ok for me. The timeline depends on my free time. I am going to work on it this week.

[ayoung19]

No worries, I totally understand. Also very sorry but because this is a pretty highly requested feature and I'm going to have a lot less free time soon, I went ahead and finished the first type of auto-delete earlier tonight.

We still need the auto-delete by TTL version but that one's lower on the priority list so I can leave it to you to finish it whenever you have the time. Just give me a heads up when you begin working on it. Also, feel free to ping me for questions anytime.

Do you use Discord? I might make one to make it easier to discuss features.

[Ribas160]

No problem, I can work on auto-delete by TTL version.
I have a Discord account, so, we can contact there.

[dani0332]

@ayoung19 Can you please add the third feature (don't save the text bigger than... ) as well. I've been using this extension but it wants to access my browser history so had to dump this, and installed yours.
.
Having this 3rd feature really helps in the case when I sometime copy stuff like mysql dump with 25000+ chars and it tries to save this and entire chrome gets crashed, I used to set the limit to 5000 chars

Users are requesting the option to auto-delete both ways. Here is the inspiration (first two options):

Did you want to take this on?

[ayoung19]

@dani0332 Sorry to hear about the other extension wanting access to your browsing history. now. One of the main reasons I made this new version is because there wasn't a secure and transparent alternative available.

I'll add in the new option ASAP, thanks for the feedback!

[ayoung19]

@dani0332 Hey! I think I might have figured out how to prevent the extension from crashing when copying large items but it might be machine/data dependent so if you have the time could you do me a favor and try running the latest version (v1.3.1) in development mode and copying the same sql dumps you previously copied?

You can download the latest version here: https://github.com/ayoung19/clipboard-history/releases.

It'd also be nice if you could export your clipboard history and import it into the development version when doing this test. I would love to see if this new version works on your machine with your data.

[ayoung19]

@dani0332 Just an update, I reverted the changes because there might be an issue with the recursive setTimeouts on Chrome. Will look into this more later but I think the general concept works as long as I can get the intervals to dynamically change: increase polling interval when reading the clipboard takes longer. This means it can support extremely large copies.

The size filtering option may still be nice to have even when the extension can support large items though to conserve disk space.