Delete toots marked with a hashtag #2

New Issue

hirusi · 2021-06-15T07:35:16+02:00

hirusi commented

2021-06-15 07:35:16 +02:00

My use case is a little different. For the most part, I'm happy to keep my toots, but instead want an opt-in -- delete toots marked with this hashtag.

I think we could build it off the following:

Keep toots containing a hashtag (recent addition)

Would you have any interest in this use case?

My use case is a little different. For the most part, I'm happy to keep my toots, but instead want an opt-in -- delete toots marked with this hashtag. I think we could build it off the following: > Keep toots containing a hashtag (recent addition) Would you have any interest in this use case?

gaugendre commented

2021-06-16 08:28:34 +02:00

Thanks for your interest in cleantoots! 😊

It's been a long time since I haven't dived into this source code but if I remember correctly, cleantoots will fetch all toots from your account, protect some based on some rules then delete all the others.

In your use case, we would protect all toots, except for some conditions. That would reverse the paradigm.

It's not something I'd have a use for but it may be interesting to build it into the tool indeed.

To implement this, we would need to solve the issue of conflicting directives: what do we do if we both have for example protected tags and to-delete tags?

I see multiple possibilities:

Raise an error: the config is not OK, because some protection rules conflict with to-delete rules (in this case we need to determine which rules conflict with each other)
Make the protection override the deletion: If a toot is both protected by an explicit rule (i.e., not protected because it's not "to delete") and marked as "to delete" by an explicit rule, then it's protected. If a toot is not protected by an explicit rule and it's marked as to deleted by an explicit rule, then it's deleted.
Make the deletion override the protection: This one seems more dangerous, I don't really like it.
Make it configurable: Yet another config option, maybe too much?

We will also need to find proper wording to explain it clearly 🙂

I don't know if I'll have time to build it in the near future but I'm open to discussions and contributions, if you feel like it!

If you do, please note that I'd prefer discussing the concerns before you spend time implementing it, in order to reduce the back and forth when reviewing the code 😉

Thanks for your interest in cleantoots! 😊 It's been a long time since I haven't dived into this source code but if I remember correctly, cleantoots will fetch all toots from your account, protect some based on some rules then delete all the others. In your use case, we would protect all toots, except for some conditions. That would reverse the paradigm. It's not something I'd have a use for but it may be interesting to build it into the tool indeed. To implement this, we would need to solve the issue of conflicting directives: what do we do if we both have for example protected tags and to-delete tags? I see multiple possibilities: * Raise an error: the config is not OK, because some protection rules conflict with to-delete rules (in this case we need to determine which rules conflict with each other) * Make the protection override the deletion: If a toot is both protected by an explicit rule (i.e., not protected because it's not "to delete") and marked as "to delete" by an explicit rule, then it's protected. If a toot is not protected by an explicit rule and it's marked as to deleted by an explicit rule, then it's deleted. * Make the deletion override the protection: This one seems more dangerous, I don't really like it. * Make it configurable: Yet another config option, maybe too much? We will also need to find proper wording to explain it clearly 🙂 I don't know if I'll have time to build it in the near future but I'm open to discussions and contributions, if you feel like it! If you do, please note that I'd prefer discussing the concerns before you spend time implementing it, in order to reduce the back and forth when reviewing the code 😉

hirusi commented

2021-08-01 07:51:33 +02:00

Hi Gabriel! 😄

So I don't have the time/energy/expertise to implement this myself. I know codl's forget also has had an issue open about this for a long time now.

It looks like a fraction of people do want something like this. In the end, I might choose to revisit and contribute this somewhere sometime, maybe even my own tool, but at the moment I just can't dive in.

It would be cool to leave this issue open for anyone else coming across this discussion.

Hi Gabriel! 😄 So I don't have the time/energy/expertise to implement this myself. I know codl's forget also has had [an issue open about this](https://github.com/codl/forget/issues/43) for a long time now. It looks like a fraction of people do want something like this. In the end, I might choose to revisit and contribute this _somewhere_ _sometime_, maybe even my own tool, but at the moment I just can't dive in. It would be cool to leave this issue open for anyone else coming across this discussion.

gaugendre commented

2021-08-01 08:38:01 +02:00

Hello! 👋

So I don't have the time/energy/expertise to implement this myself.

Don't worry 😉

From what I read on the issue you linked, it's the contrary: the OP asked to preserve posts with a specific hashtag. That's something we already do, as you mentionned in your original post.

I'd be happy to review your contribution if you decide to publish one for cleantoots 😉

In the meantime let's indeed keep the issue open!

Hello! 👋 > So I don't have the time/energy/expertise to implement this myself. Don't worry 😉 From what I read on the issue you linked, it's the contrary: the OP asked to *preserve* posts with a specific hashtag. That's something we already do, as you mentionned in your original post. I'd be happy to review your contribution if you decide to publish one for cleantoots 😉 In the meantime let's indeed keep the issue open!

hirusi commented

2021-08-01 09:01:42 +02:00

Ah you're right. My bad! I had been juggling the two ideas at the time! 😅

Sign in to join this conversation.

No Label

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: gaugendre/cleantoots#2