10:18 <beneroth> Regenaxer, I have a (+List +Link) relation, how in pilog generate/bind to the list elements? not same/3 and not member/2, but?

10:20 <beneroth> or must this done in two steps, first getting the list with (same) and than using that @Lst in member/2?

10:20 <Regenaxer> I use lst

10:21 <Regenaxer> st/3

10:21 <Regenaxer> lst/3

10:21 <beneroth> ah lst/3

10:21 <beneroth> yeah found it

10:21 <beneroth> thx :)

10:22 <Regenaxer> :)

10:28 <beneroth> using lst/3 in select/3 would mean, that if at least one value generated by lst/3 fulfills the subsequent rules, then it is a match, correct?

10:29 <Regenaxer> I would not say so. It generates things, which may or may not match later

12:31 <beneroth> Regenaxer, I mean object A has (in +List +Link relation, or +List +Joint) a list of B. select/3 is searching for A. pilog rules match B objects. A is a match if at least one linked B object matches the B filter clauses. versus A is only a match if all linked B objects match the B filter clauses.

12:32 <beneroth> according to my tests, it behaves as I would expect

12:40 <beneroth> Regenaxer, kinda (find) vs. (fully) on linked objects. of course everything depends on the specific pilog query. My point is, bindings generated by lst/3 going through additional simple filter clauses behaves like (find) not like (fully)

12:40 <beneroth> if this is somewhat understandably worded

13:00 <Regenaxer> Sorry beneroth, I was very busy

13:01 <Regenaxer> For a +List, you need in fact nothing else

13:01 <Regenaxer> same/3 etc handle that

13:03 <beneroth> yeah

13:03 <beneroth> np thanks :)

13:04 <Regenaxer> I use lst/3 for a generator, yes, but for filter rules nothig special is needed for +List :)

13:07 <beneroth> lst/3 was what I needed here

13:08 <Regenaxer> ok

15:58 <beneroth> [OT] matrix messenger security (E2E) weakness: https://matrix.org/blog/2021/09/13/vulnerability-disclosure-key-sharing german: https://www.heise.de/news/Luecken-im-Matrix-Protokoll-gefaehrden-Ende-zu-Ende-Verschluesselung-von-Messengern-6191625.html

16:27 <Regenaxer> Oh! Sh*t. Thanks beneroth!

16:27 <beneroth> not so bad

16:27 <beneroth> compared to that:

16:29 <beneroth> [OT / security] azure cloud linux VM with normally installed agent-software OMI give root access when sending HTTPS request without authentication header https://www.wiz.io/blog/secret-agent-exposes-azure-customers-to-unauthorized-code-execution

16:29 <beneroth> "In addition to Azure cloud customers, other Microsoft customers are affected since OMI can be independently installed on any Linux machine and is frequently used on-premise. For example, OMI is built in System Center for Linux, Microsoft’s server management solution. "

16:29 <Regenaxer> indeed

16:29 <beneroth> I find it funny

21:42 <beneroth> Regenaxer, a question for the morning. pilog (or) is (in itself) never short-circuiting, correct?

22:20 <beneroth> or is it? in any case, pilog variables only present within (or) seem not to be traced into prg of pilog

22:37 <beneroth> btw. I've feel now confident with combined index generator clauses and indirect object association generator clauses, got them fully grokked :)

22:37 <beneroth> (the terminology gives many scrabble points :D)

22:38 <beneroth> haven't used them yet in combination, but I guess that is just a small step