Blocking quoted posts possible? -

System Apps

Directory Help Language

Like Us Public Stream QRator Random Channel Report Bug Search

Support Hubzilla

Blocking quoted posts possible?

2025-03-10 19:23:16

Hubzilla Support Forum

adminsforum@hubzilla.org

*_jayrope wrote the following post Mon, 10 Mar 2025 19:24:29 +0100

Blocking quoted posts possible?

@!Hubzilla Support Forum If i were a person, who'd like to block quoted posts, what options do i have in Hubzilla?

I think, that - even if don't need it myself - such a feature would help certain other people to get along with Hubzilla more nicely.

@Harald Eilertsen @Mario Vavti

show all 20 comments

2025-03-10 21:21:04

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

Essentially, that'd require a channel-wide and per-contact-role permission "Can share my posts".

Ideally, it'd be compatible with the quote-post opt-in/opt-out flag that Mastodon is planning to roll out soon. Basically, if a Mastodon user has opted out of/not opted into being quote-post-able, Hubzilla should hide the "Share" button under any and all posts and comments from that user. Vice versa, Mastodon should understand the lack of permission to share posts on Hubzilla's side as quote posts being opted out of/not being opted into.

2025-03-10 21:31:17

*_jayrope

jrp@hub.kliklak.net

@Jupiter Rowland Good suggestions, though I'd prefer AP as the standard there, not Mastodon's own version (control).

2025-03-11 10:55:01

Mario Vavti

mario@hub.somaton.com

@*_jayrope are you referring to blocking your posts to be quoted or to inbound quote posts?

2025-03-11 11:47:15

*_jayrope

jrp@hub.kliklak.net

@Mario Vavti Thanks for asking, originally inbound.

2025-03-11 12:05:30

Mario Vavti

mario@hub.somaton.com

@*_jayrope for inbound traffic ?body ~= [/share] in the connections content filter should do the trick...

2025-03-11 12:46:48

*_jayrope

jrp@hub.kliklak.net

@Der Pepe (Hubzilla) ⁂ ⚝ Hey Pepe, another trick for your manual :)

2025-03-11 12:51:12

*_jayrope

jrp@hub.kliklak.net

@Mario Vavti Mario, does this work for all connections at once, when used in Settings/Channel settings/Do not import posts with this text ?

2025-03-11 13:00:20

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

@*_jayrope Great, I'll include that.

2025-03-11 13:14:20

Mario Vavti

mario@hub.somaton.com

@*_jayrope not sure actually. You can try. Be aware though that this way you will not receive any hubzilla forum posts anymore...

2025-03-11 13:32:52

*_jayrope

jrp@hub.kliklak.net

@Mario Vavti Oh, similar to ?verb == Announce i guess?
Well in that case that wasn't what i was looking for. I was wondering if one can block all quote posts at once without loosing any other functionality.

2025-03-11 13:52:22

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

@Mario Vavti @*_jayrope

Related question:

‘body ~= [/share]’ means that the string “/share” does NOT appear in the body of the message (~= is not equal to).

If I enter this at “Do not import posts with this text”, then I will NOT import any postings that do not contain the string “/share”... so practically only and exclusively shared posts.

If I were to enter it at ‘Only import posts with this text’, then ONLY posts from the contact would be imported that DO NOT contain the character string ‘/share’ in the body... so that would be the correct way if I don't want to see shared posts.

The condition ‘?verb == Announce’ is (according to the tips) usually entered with ‘Do not import posts with this text’... and that works fine. Wouldn't it be more consistent to also enter the condition for shared posts in this area and then use the comparison operator ‘==’ instead of ‘~=’... so ‘?body ~= [/share]’? Or am I making a mistake in my thinking here? Actually, both ways should lead to the goal (with different locations for the filters), right?

2025-03-11 16:27:42

Mario Vavti

mario@hub.somaton.com

@*_jayrope so you want to block quote posts without blocking quote posts

Technically Hubzilla forum posts are quote posts...

2025-03-11 16:31:51

Mario Vavti

mario@hub.somaton.com

@Der Pepe (Hubzilla) ⁂ ⚝ ~= checks if a string contains value...

2025-03-11 19:13:06

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

@Mario Vavti

In fact, I was wrong and had the ‘mathematical’ symbol at the back of my mind. My mistake!
I have now included content filters in the help section, where the comparison operators are also described.

Content filters

2025-03-11 19:25:35

*_jayrope

jrp@hub.kliklak.net

@Der Pepe (Hubzilla) ⁂ ⚝ Pepe, great page! got a question there, are we able to filter for exact matches as single terms? When i filter for LLM also allmendenetz gets filtered atm ...

2025-03-11 22:39:57

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

@*_jayrope

?body ~= /\bLLM\b/ should possibly work like this.

2025-03-12 10:39:09

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@Der Pepe (Hubzilla) ⁂ ⚝ Nope, filter syntax doesn't work with regex and vice versa.

But Hubzilla's filters seem to have more issues than Fediverse Report anyway, especially whitelisting only works under very specific lab conditions.

2025-03-12 10:47:57

Jupiter Rowland

jupiter_rowland@hub.netzgemeinde.eu

@*_jayrope Do it without filter syntax.

Just put /\bLLM\b/ onto the blacklist without the ?body ~= ahead of it.

I think blacklists let you mix filter syntax lines and lines without filter syntax. Whitelists don't because they combine non-filter syntax lines with OR and filter syntax lines with AND. Also, if the last line is filter syntax, only filter syntax lines seem to be parsed, and if the last line is without filter syntax, only non-filter syntax lines seem to be parsed.

See also my comment on your Limit scope of filtering issue as well as my own Filters with switchable operators that allow keywords and filter syntax simultaneously feature request.

2025-03-12 13:21:48

Air Cushion Finish

acf@hub.kliklak.net

@Jupiter Rowland

/\bLLM\b/

Thank you, Jupiter, I'm sorry, I am unexperienced in this. What are /\b and \b/ doing here exactly?

2025-03-12 13:34:31

Der Pepe (Hubzilla) ⁂ ⚝

pepecyb@hub.hubzilla.hu

@Air Cushion Finish

\b ensures that the character string enclosed in between fits as a whole, so there must be nothing before or after LLM. This is to exclude false positives, such as ‘allmende’, in which LLM is also contained.

The / at the beginning and end enclose the RE (standard).