Filter by visibility level #7

New issue

Closed

opened 2024-01-30 12:09:12 +00:00 by quardbreak · 3 comments

quardbreak commented

2024-01-30 12:09:12 +00:00

(Migrated from codeberg.org)

As a replacement for skip_deleting_dm ==> skip_deleting_visibility. On config setup should make a list of selected visibility levels which will be used to skip (or use) statuses which match status.get("visibility") with anything in.
~~I'm thinking to try make this as my python test task, but~~ not sure yet if you actually need this at cost of deleting skip_deleting_dm.

For reference:
https://docs.joinmastodon.org/spec/activitypub/#Mention
https://docs.joinmastodon.org/user/posting/#privacy

As a replacement for `skip_deleting_dm` ==> `skip_deleting_visibility`. On config setup should make a list of selected visibility levels which will be used to skip (or use) statuses which match status.get("visibility") with anything in. ~~I'm thinking to try make this as my python test task, but~~ not sure yet if you actually need this at cost of deleting `skip_deleting_dm`. For reference: https://docs.joinmastodon.org/spec/activitypub/#Mention https://docs.joinmastodon.org/user/posting/#privacy

marvin8 commented

2024-02-02 22:24:03 +00:00

(Migrated from codeberg.org)

Sounds like a reasonable idea. I am currently working on something else and I might take a few days / weeks until I can get to this.

However if you feel like submitting a pull request, I'd be very happy to look at that and merge as soon as I can.

Sounds like a reasonable idea. I am currently working on something else and I might take a few days / weeks until I can get to this. However if you feel like submitting a pull request, I'd be very happy to look at that and merge as soon as I can.

marvin8 commented

2024-02-24 23:10:50 +00:00

(Migrated from codeberg.org)

I have started working on this issue now. Looks like it's going to be reasonably straight forward to implement.

marvin8 commented

2024-05-09 09:48:18 +00:00

(Migrated from codeberg.org)

Sorry I forgot to mention that this has been included in release 3.1.0 and later.