just a reminder --- there are changes in it you don't want by Ratany · Pull Request #2 · LiruMouse/SingularityViewer

Ratany · 2013-09-24T17:35:04Z

No description provided.

create whitelist and blacklist headers also when the Enable Defaults button for xantispam is used

allows to blacklist all online notifications and allowing only those that are whitelisted fixed creating whitelist and blacklist headers when pressing the xantispam default settings button

from getting autoresponses sent to them

xantispam_transparentlookup() only once, after that use cache lookups only

+ save and load to and from files + saving and loading supports base64 encoding so non-text files can be interchanged via notecards

when appling a diff

annoying warnings

for the internal text editor

+ allowing xantispam rules to use arbitrary strings in the "from" part + format of whitelist and blacklist changed in the process (they are emacs org-mode tables now) + limit of simultaneously open queries removed, avoiding duplicate queries + now blocking by default when an identical query is issued again before an open one hasn't been answered + some minor fixes to notifications created by the media filter + added new rule types: &-DomainHandleMediaURLs &-GRLogDontSave PlayFromMediaURL * mouse wheel scrolling accelerated experimentally

be against the Linden TOS added context menu entry for the internal editor to start an external editor fixed working directory setting in the xantispam process launcher adjusted xantispam list header creation to new format of black-/whitelist

into work --- initial merge after forking from https://github.com/Lirusaito/SingularityViewer adjusted to use LLLogChat::makeLogFileName() to solve conflicts Conflicts: indra/newview/llimpanel.cpp

offers distinctly by origin and type; involves new rules "&-InventoryHandleDistinctly" and "AcceptInventory?[type]"

chat history into the external editor

disables xantispam distinct inventory accept features which will be put back with next commit

…f "ALL"

configured for it. Otherwise inventory handling rules can be overridden by other rules, especially when non-relaxed mode is enabled.

"&-ConfigInverseOrderForSilent" which can change the order from 'deny, allow' to 'allow when not denied' for friend online status notifications which allows whitelisting such notifications only for those friends you want to see them for rather than having to blacklist all the ones you don't want to see when not in relaxed mode

…ia were set

it's possible that they have been prefilled on demand already through transparent lookups

not available, or when a decision-making logic is disabled

... now is a seperate function, and disables (i. e. skips) speed rezzing when enabled because there's no point to do speed rezzing when adda is used. (Adda does a much better job anyway, and it does it all the time.) Fixes: do not fall below the minimum draw distance, and set the minimum number of frames to average to the allowed minimum if it's lower. Perhaps the compiler optimizes better when adda is in its own function, and it may be easier to solve merge conflicts.

great ...

…arityViewer

complements making the inventory invisible on teleport

…arityViewer Conflicts: indra/newview/llglsandbox.cpp as upstream

I'm still getting an assertion when opening the radar floater after the inventory was opened, so be warned (minimize it instead of closing it). ASFAICT, this was introduced by upstream. I haven't had time to look into it yet.

I won't call it a fix because now the radar floater may remain underneath other floaters when closing and re-opening it. However, it's much better than crashing after the assertion comes up.

group-messages by message content This is now being tested. I might end up running the messages through spamassassin, or at least some perl script I'll write ...

You can specify regular expressions with xantispam rules now. Each rule comes with an integer which is the score to add to a total for the message which is being checked. The score of each matching rule adds to the total score until the total score goes over a threshold. When the total score is over the threshold, the message is considered spam. The message is replaced with "[blocked spam from]", and the sender gets a message "[spam message blocked by recipients client]". You'll be notified about this by getting an IM sent to yourself. The original message as was sent will be logged unaltered if you have logging enabled. The 'from' part of the xantispam rule gives the regular expression. For example: | come.*http | &-RxScore!6 Since the pipe sign is used as a column seperator, you currently cannot use it to specify regular expressions. I'll have to see what I can do about that. In the meantime, just use multiple rules when you need an OR. Same goes for the colon. Since it's used as a wildcard, you currently cannot use it within regular expressions. Two new settings accompany this: AntiSpamXtendedRxMinLength The default is 85 characters (UTF-8). When a message is shorter, it won't be checked. AntiSpamXtendedRxScoreThreshold This is the threshold mentioned above. The default is 5. You'll find those among the debug settings. As to the regular expression syntax: The boost library provides 'regex_search()', which is used for the matching, so you can always look it up if in doubt (seems pretty much like what perl uses). If you have not specified any '&-RxScore!' rules, processing will not find any matches, and no messages will be classified as spam. You might want to set the threshold very high in that case because that saves the lookups of the rules. Only the rules currently in the cache (i. e. in memory) are being checked. This is unlikely to change because resorting to the rules stored in the blacklist seems a bit unreasonable here performance-wise. I'm still a long way away from overflowing the rule caches (wich hold up to 64k rules). Be careful not to omit the score from a '&-RxScore!' rule, and especially don't put anything but an integer after the exclamation mark. When the rule is too short, i. e. doesn't have anything after the exclamation mark, it will be ignored. Put something else than an integer, and unexpected things might happen.

This calls for an /i flag like perl has. We'll see ...

e0009fe

the conversation

webkit failed

…arityViewer

seems to lead to performance problems

This should fix it. I don't trust it yet, so some debugging info is left in which will be removed later.

Ratany · 2013-09-24T17:35:04Z

No description provided.

create whitelist and blacklist headers also when the Enable Defaults button for xantispam is used

allows to blacklist all online notifications and allowing only those that are whitelisted fixed creating whitelist and blacklist headers when pressing the xantispam default settings button

from getting autoresponses sent to them

xantispam_transparentlookup() only once, after that use cache lookups only

+ save and load to and from files + saving and loading supports base64 encoding so non-text files can be interchanged via notecards

when appling a diff

annoying warnings

for the internal text editor

+ allowing xantispam rules to use arbitrary strings in the "from" part + format of whitelist and blacklist changed in the process (they are emacs org-mode tables now) + limit of simultaneously open queries removed, avoiding duplicate queries + now blocking by default when an identical query is issued again before an open one hasn't been answered + some minor fixes to notifications created by the media filter + added new rule types: &-DomainHandleMediaURLs &-GRLogDontSave PlayFromMediaURL * mouse wheel scrolling accelerated experimentally

be against the Linden TOS added context menu entry for the internal editor to start an external editor fixed working directory setting in the xantispam process launcher adjusted xantispam list header creation to new format of black-/whitelist

into work --- initial merge after forking from https://github.com/Lirusaito/SingularityViewer adjusted to use LLLogChat::makeLogFileName() to solve conflicts Conflicts: indra/newview/llimpanel.cpp

offers distinctly by origin and type; involves new rules "&-InventoryHandleDistinctly" and "AcceptInventory?[type]"

chat history into the external editor

disables xantispam distinct inventory accept features which will be put back with next commit

…f "ALL"

configured for it. Otherwise inventory handling rules can be overridden by other rules, especially when non-relaxed mode is enabled.

"&-ConfigInverseOrderForSilent" which can change the order from 'deny, allow' to 'allow when not denied' for friend online status notifications which allows whitelisting such notifications only for those friends you want to see them for rather than having to blacklist all the ones you don't want to see when not in relaxed mode

…ia were set

it's possible that they have been prefilled on demand already through transparent lookups

not available, or when a decision-making logic is disabled

... now is a seperate function, and disables (i. e. skips) speed rezzing when enabled because there's no point to do speed rezzing when adda is used. (Adda does a much better job anyway, and it does it all the time.) Fixes: do not fall below the minimum draw distance, and set the minimum number of frames to average to the allowed minimum if it's lower. Perhaps the compiler optimizes better when adda is in its own function, and it may be easier to solve merge conflicts.

great ...

…arityViewer

complements making the inventory invisible on teleport

…arityViewer Conflicts: indra/newview/llglsandbox.cpp as upstream

I'm still getting an assertion when opening the radar floater after the inventory was opened, so be warned (minimize it instead of closing it). ASFAICT, this was introduced by upstream. I haven't had time to look into it yet.

I won't call it a fix because now the radar floater may remain underneath other floaters when closing and re-opening it. However, it's much better than crashing after the assertion comes up.

group-messages by message content This is now being tested. I might end up running the messages through spamassassin, or at least some perl script I'll write ...

You can specify regular expressions with xantispam rules now. Each rule comes with an integer which is the score to add to a total for the message which is being checked. The score of each matching rule adds to the total score until the total score goes over a threshold. When the total score is over the threshold, the message is considered spam. The message is replaced with "[blocked spam from]", and the sender gets a message "[spam message blocked by recipients client]". You'll be notified about this by getting an IM sent to yourself. The original message as was sent will be logged unaltered if you have logging enabled. The 'from' part of the xantispam rule gives the regular expression. For example: | come.*http | &-RxScore!6 Since the pipe sign is used as a column seperator, you currently cannot use it to specify regular expressions. I'll have to see what I can do about that. In the meantime, just use multiple rules when you need an OR. Same goes for the colon. Since it's used as a wildcard, you currently cannot use it within regular expressions. Two new settings accompany this: AntiSpamXtendedRxMinLength The default is 85 characters (UTF-8). When a message is shorter, it won't be checked. AntiSpamXtendedRxScoreThreshold This is the threshold mentioned above. The default is 5. You'll find those among the debug settings. As to the regular expression syntax: The boost library provides 'regex_search()', which is used for the matching, so you can always look it up if in doubt (seems pretty much like what perl uses). If you have not specified any '&-RxScore!' rules, processing will not find any matches, and no messages will be classified as spam. You might want to set the threshold very high in that case because that saves the lookups of the rules. Only the rules currently in the cache (i. e. in memory) are being checked. This is unlikely to change because resorting to the rules stored in the blacklist seems a bit unreasonable here performance-wise. I'm still a long way away from overflowing the rule caches (wich hold up to 64k rules). Be careful not to omit the score from a '&-RxScore!' rule, and especially don't put anything but an integer after the exclamation mark. When the rule is too short, i. e. doesn't have anything after the exclamation mark, it will be ignored. Put something else than an integer, and unexpected things might happen.

This calls for an /i flag like perl has. We'll see ...

e0009fe

the conversation

webkit failed

…arityViewer

seems to lead to performance problems

This should fix it. I don't trust it yet, so some debugging info is left in which will be removed later.

Ratany · 2013-09-24T17:35:04Z

No description provided.

create whitelist and blacklist headers also when the Enable Defaults button for xantispam is used

allows to blacklist all online notifications and allowing only those that are whitelisted fixed creating whitelist and blacklist headers when pressing the xantispam default settings button

from getting autoresponses sent to them

xantispam_transparentlookup() only once, after that use cache lookups only

+ save and load to and from files + saving and loading supports base64 encoding so non-text files can be interchanged via notecards

when appling a diff

annoying warnings

for the internal text editor

+ allowing xantispam rules to use arbitrary strings in the "from" part + format of whitelist and blacklist changed in the process (they are emacs org-mode tables now) + limit of simultaneously open queries removed, avoiding duplicate queries + now blocking by default when an identical query is issued again before an open one hasn't been answered + some minor fixes to notifications created by the media filter + added new rule types: &-DomainHandleMediaURLs &-GRLogDontSave PlayFromMediaURL * mouse wheel scrolling accelerated experimentally

be against the Linden TOS added context menu entry for the internal editor to start an external editor fixed working directory setting in the xantispam process launcher adjusted xantispam list header creation to new format of black-/whitelist

into work --- initial merge after forking from https://github.com/Lirusaito/SingularityViewer adjusted to use LLLogChat::makeLogFileName() to solve conflicts Conflicts: indra/newview/llimpanel.cpp

offers distinctly by origin and type; involves new rules "&-InventoryHandleDistinctly" and "AcceptInventory?[type]"

chat history into the external editor

disables xantispam distinct inventory accept features which will be put back with next commit

…f "ALL"

configured for it. Otherwise inventory handling rules can be overridden by other rules, especially when non-relaxed mode is enabled.

"&-ConfigInverseOrderForSilent" which can change the order from 'deny, allow' to 'allow when not denied' for friend online status notifications which allows whitelisting such notifications only for those friends you want to see them for rather than having to blacklist all the ones you don't want to see when not in relaxed mode

…ia were set

it's possible that they have been prefilled on demand already through transparent lookups

not available, or when a decision-making logic is disabled

... now is a seperate function, and disables (i. e. skips) speed rezzing when enabled because there's no point to do speed rezzing when adda is used. (Adda does a much better job anyway, and it does it all the time.) Fixes: do not fall below the minimum draw distance, and set the minimum number of frames to average to the allowed minimum if it's lower. Perhaps the compiler optimizes better when adda is in its own function, and it may be easier to solve merge conflicts.

great ...

…arityViewer

complements making the inventory invisible on teleport

…arityViewer Conflicts: indra/newview/llglsandbox.cpp as upstream

I'm still getting an assertion when opening the radar floater after the inventory was opened, so be warned (minimize it instead of closing it). ASFAICT, this was introduced by upstream. I haven't had time to look into it yet.

I won't call it a fix because now the radar floater may remain underneath other floaters when closing and re-opening it. However, it's much better than crashing after the assertion comes up.

group-messages by message content This is now being tested. I might end up running the messages through spamassassin, or at least some perl script I'll write ...

You can specify regular expressions with xantispam rules now. Each rule comes with an integer which is the score to add to a total for the message which is being checked. The score of each matching rule adds to the total score until the total score goes over a threshold. When the total score is over the threshold, the message is considered spam. The message is replaced with "[blocked spam from]", and the sender gets a message "[spam message blocked by recipients client]". You'll be notified about this by getting an IM sent to yourself. The original message as was sent will be logged unaltered if you have logging enabled. The 'from' part of the xantispam rule gives the regular expression. For example: | come.*http | &-RxScore!6 Since the pipe sign is used as a column seperator, you currently cannot use it to specify regular expressions. I'll have to see what I can do about that. In the meantime, just use multiple rules when you need an OR. Same goes for the colon. Since it's used as a wildcard, you currently cannot use it within regular expressions. Two new settings accompany this: AntiSpamXtendedRxMinLength The default is 85 characters (UTF-8). When a message is shorter, it won't be checked. AntiSpamXtendedRxScoreThreshold This is the threshold mentioned above. The default is 5. You'll find those among the debug settings. As to the regular expression syntax: The boost library provides 'regex_search()', which is used for the matching, so you can always look it up if in doubt (seems pretty much like what perl uses). If you have not specified any '&-RxScore!' rules, processing will not find any matches, and no messages will be classified as spam. You might want to set the threshold very high in that case because that saves the lookups of the rules. Only the rules currently in the cache (i. e. in memory) are being checked. This is unlikely to change because resorting to the rules stored in the blacklist seems a bit unreasonable here performance-wise. I'm still a long way away from overflowing the rule caches (wich hold up to 64k rules). Be careful not to omit the score from a '&-RxScore!' rule, and especially don't put anything but an integer after the exclamation mark. When the rule is too short, i. e. doesn't have anything after the exclamation mark, it will be ignored. Put something else than an integer, and unexpected things might happen.

This calls for an /i flag like perl has. We'll see ...

e0009fe

the conversation

webkit failed

…arityViewer

seems to lead to performance problems

This should fix it. I don't trust it yet, so some debugging info is left in which will be removed later.

Ratany · 2013-09-24T17:35:04Z

No description provided.

create whitelist and blacklist headers also when the Enable Defaults button for xantispam is used

allows to blacklist all online notifications and allowing only those that are whitelisted fixed creating whitelist and blacklist headers when pressing the xantispam default settings button

from getting autoresponses sent to them

xantispam_transparentlookup() only once, after that use cache lookups only

+ save and load to and from files + saving and loading supports base64 encoding so non-text files can be interchanged via notecards

when appling a diff

annoying warnings

for the internal text editor

+ allowing xantispam rules to use arbitrary strings in the "from" part + format of whitelist and blacklist changed in the process (they are emacs org-mode tables now) + limit of simultaneously open queries removed, avoiding duplicate queries + now blocking by default when an identical query is issued again before an open one hasn't been answered + some minor fixes to notifications created by the media filter + added new rule types: &-DomainHandleMediaURLs &-GRLogDontSave PlayFromMediaURL * mouse wheel scrolling accelerated experimentally

be against the Linden TOS added context menu entry for the internal editor to start an external editor fixed working directory setting in the xantispam process launcher adjusted xantispam list header creation to new format of black-/whitelist

into work --- initial merge after forking from https://github.com/Lirusaito/SingularityViewer adjusted to use LLLogChat::makeLogFileName() to solve conflicts Conflicts: indra/newview/llimpanel.cpp

offers distinctly by origin and type; involves new rules "&-InventoryHandleDistinctly" and "AcceptInventory?[type]"

chat history into the external editor

disables xantispam distinct inventory accept features which will be put back with next commit

…f "ALL"

configured for it. Otherwise inventory handling rules can be overridden by other rules, especially when non-relaxed mode is enabled.

"&-ConfigInverseOrderForSilent" which can change the order from 'deny, allow' to 'allow when not denied' for friend online status notifications which allows whitelisting such notifications only for those friends you want to see them for rather than having to blacklist all the ones you don't want to see when not in relaxed mode

…ia were set

it's possible that they have been prefilled on demand already through transparent lookups

not available, or when a decision-making logic is disabled

... now is a seperate function, and disables (i. e. skips) speed rezzing when enabled because there's no point to do speed rezzing when adda is used. (Adda does a much better job anyway, and it does it all the time.) Fixes: do not fall below the minimum draw distance, and set the minimum number of frames to average to the allowed minimum if it's lower. Perhaps the compiler optimizes better when adda is in its own function, and it may be easier to solve merge conflicts.

great ...

…arityViewer

complements making the inventory invisible on teleport

…arityViewer Conflicts: indra/newview/llglsandbox.cpp as upstream

I'm still getting an assertion when opening the radar floater after the inventory was opened, so be warned (minimize it instead of closing it). ASFAICT, this was introduced by upstream. I haven't had time to look into it yet.

I won't call it a fix because now the radar floater may remain underneath other floaters when closing and re-opening it. However, it's much better than crashing after the assertion comes up.

group-messages by message content This is now being tested. I might end up running the messages through spamassassin, or at least some perl script I'll write ...

You can specify regular expressions with xantispam rules now. Each rule comes with an integer which is the score to add to a total for the message which is being checked. The score of each matching rule adds to the total score until the total score goes over a threshold. When the total score is over the threshold, the message is considered spam. The message is replaced with "[blocked spam from]", and the sender gets a message "[spam message blocked by recipients client]". You'll be notified about this by getting an IM sent to yourself. The original message as was sent will be logged unaltered if you have logging enabled. The 'from' part of the xantispam rule gives the regular expression. For example: | come.*http | &-RxScore!6 Since the pipe sign is used as a column seperator, you currently cannot use it to specify regular expressions. I'll have to see what I can do about that. In the meantime, just use multiple rules when you need an OR. Same goes for the colon. Since it's used as a wildcard, you currently cannot use it within regular expressions. Two new settings accompany this: AntiSpamXtendedRxMinLength The default is 85 characters (UTF-8). When a message is shorter, it won't be checked. AntiSpamXtendedRxScoreThreshold This is the threshold mentioned above. The default is 5. You'll find those among the debug settings. As to the regular expression syntax: The boost library provides 'regex_search()', which is used for the matching, so you can always look it up if in doubt (seems pretty much like what perl uses). If you have not specified any '&-RxScore!' rules, processing will not find any matches, and no messages will be classified as spam. You might want to set the threshold very high in that case because that saves the lookups of the rules. Only the rules currently in the cache (i. e. in memory) are being checked. This is unlikely to change because resorting to the rules stored in the blacklist seems a bit unreasonable here performance-wise. I'm still a long way away from overflowing the rule caches (wich hold up to 64k rules). Be careful not to omit the score from a '&-RxScore!' rule, and especially don't put anything but an integer after the exclamation mark. When the rule is too short, i. e. doesn't have anything after the exclamation mark, it will be ignored. Put something else than an integer, and unexpected things might happen.

This calls for an /i flag like perl has. We'll see ...

e0009fe

the conversation

webkit failed

…arityViewer

seems to lead to performance problems

This should fix it. I don't trust it yet, so some debugging info is left in which will be removed later.

Ratany · 2013-09-24T17:35:04Z

No description provided.

create whitelist and blacklist headers also when the Enable Defaults button for xantispam is used

allows to blacklist all online notifications and allowing only those that are whitelisted fixed creating whitelist and blacklist headers when pressing the xantispam default settings button

from getting autoresponses sent to them

xantispam_transparentlookup() only once, after that use cache lookups only

+ save and load to and from files + saving and loading supports base64 encoding so non-text files can be interchanged via notecards

when appling a diff

annoying warnings

for the internal text editor

+ allowing xantispam rules to use arbitrary strings in the "from" part + format of whitelist and blacklist changed in the process (they are emacs org-mode tables now) + limit of simultaneously open queries removed, avoiding duplicate queries + now blocking by default when an identical query is issued again before an open one hasn't been answered + some minor fixes to notifications created by the media filter + added new rule types: &-DomainHandleMediaURLs &-GRLogDontSave PlayFromMediaURL * mouse wheel scrolling accelerated experimentally

be against the Linden TOS added context menu entry for the internal editor to start an external editor fixed working directory setting in the xantispam process launcher adjusted xantispam list header creation to new format of black-/whitelist

into work --- initial merge after forking from https://github.com/Lirusaito/SingularityViewer adjusted to use LLLogChat::makeLogFileName() to solve conflicts Conflicts: indra/newview/llimpanel.cpp

offers distinctly by origin and type; involves new rules "&-InventoryHandleDistinctly" and "AcceptInventory?[type]"

chat history into the external editor

disables xantispam distinct inventory accept features which will be put back with next commit

…f "ALL"

configured for it. Otherwise inventory handling rules can be overridden by other rules, especially when non-relaxed mode is enabled.

"&-ConfigInverseOrderForSilent" which can change the order from 'deny, allow' to 'allow when not denied' for friend online status notifications which allows whitelisting such notifications only for those friends you want to see them for rather than having to blacklist all the ones you don't want to see when not in relaxed mode

…ia were set

it's possible that they have been prefilled on demand already through transparent lookups

not available, or when a decision-making logic is disabled

... now is a seperate function, and disables (i. e. skips) speed rezzing when enabled because there's no point to do speed rezzing when adda is used. (Adda does a much better job anyway, and it does it all the time.) Fixes: do not fall below the minimum draw distance, and set the minimum number of frames to average to the allowed minimum if it's lower. Perhaps the compiler optimizes better when adda is in its own function, and it may be easier to solve merge conflicts.

great ...

…arityViewer

complements making the inventory invisible on teleport

…arityViewer Conflicts: indra/newview/llglsandbox.cpp as upstream

I'm still getting an assertion when opening the radar floater after the inventory was opened, so be warned (minimize it instead of closing it). ASFAICT, this was introduced by upstream. I haven't had time to look into it yet.

I won't call it a fix because now the radar floater may remain underneath other floaters when closing and re-opening it. However, it's much better than crashing after the assertion comes up.

group-messages by message content This is now being tested. I might end up running the messages through spamassassin, or at least some perl script I'll write ...

You can specify regular expressions with xantispam rules now. Each rule comes with an integer which is the score to add to a total for the message which is being checked. The score of each matching rule adds to the total score until the total score goes over a threshold. When the total score is over the threshold, the message is considered spam. The message is replaced with "[blocked spam from]", and the sender gets a message "[spam message blocked by recipients client]". You'll be notified about this by getting an IM sent to yourself. The original message as was sent will be logged unaltered if you have logging enabled. The 'from' part of the xantispam rule gives the regular expression. For example: | come.*http | &-RxScore!6 Since the pipe sign is used as a column seperator, you currently cannot use it to specify regular expressions. I'll have to see what I can do about that. In the meantime, just use multiple rules when you need an OR. Same goes for the colon. Since it's used as a wildcard, you currently cannot use it within regular expressions. Two new settings accompany this: AntiSpamXtendedRxMinLength The default is 85 characters (UTF-8). When a message is shorter, it won't be checked. AntiSpamXtendedRxScoreThreshold This is the threshold mentioned above. The default is 5. You'll find those among the debug settings. As to the regular expression syntax: The boost library provides 'regex_search()', which is used for the matching, so you can always look it up if in doubt (seems pretty much like what perl uses). If you have not specified any '&-RxScore!' rules, processing will not find any matches, and no messages will be classified as spam. You might want to set the threshold very high in that case because that saves the lookups of the rules. Only the rules currently in the cache (i. e. in memory) are being checked. This is unlikely to change because resorting to the rules stored in the blacklist seems a bit unreasonable here performance-wise. I'm still a long way away from overflowing the rule caches (wich hold up to 64k rules). Be careful not to omit the score from a '&-RxScore!' rule, and especially don't put anything but an integer after the exclamation mark. When the rule is too short, i. e. doesn't have anything after the exclamation mark, it will be ignored. Put something else than an integer, and unexpected things might happen.

This calls for an /i flag like perl has. We'll see ...

e0009fe

the conversation

webkit failed

…arityViewer

seems to lead to performance problems

This should fix it. I don't trust it yet, so some debugging info is left in which will be removed later.

Ratany · 2013-09-24T17:35:04Z

No description provided.

create whitelist and blacklist headers also when the Enable Defaults button for xantispam is used

allows to blacklist all online notifications and allowing only those that are whitelisted fixed creating whitelist and blacklist headers when pressing the xantispam default settings button

from getting autoresponses sent to them

xantispam_transparentlookup() only once, after that use cache lookups only

+ save and load to and from files + saving and loading supports base64 encoding so non-text files can be interchanged via notecards

when appling a diff

annoying warnings

for the internal text editor

+ allowing xantispam rules to use arbitrary strings in the "from" part + format of whitelist and blacklist changed in the process (they are emacs org-mode tables now) + limit of simultaneously open queries removed, avoiding duplicate queries + now blocking by default when an identical query is issued again before an open one hasn't been answered + some minor fixes to notifications created by the media filter + added new rule types: &-DomainHandleMediaURLs &-GRLogDontSave PlayFromMediaURL * mouse wheel scrolling accelerated experimentally

be against the Linden TOS added context menu entry for the internal editor to start an external editor fixed working directory setting in the xantispam process launcher adjusted xantispam list header creation to new format of black-/whitelist

into work --- initial merge after forking from https://github.com/Lirusaito/SingularityViewer adjusted to use LLLogChat::makeLogFileName() to solve conflicts Conflicts: indra/newview/llimpanel.cpp

offers distinctly by origin and type; involves new rules "&-InventoryHandleDistinctly" and "AcceptInventory?[type]"

chat history into the external editor

disables xantispam distinct inventory accept features which will be put back with next commit

…f "ALL"

configured for it. Otherwise inventory handling rules can be overridden by other rules, especially when non-relaxed mode is enabled.

"&-ConfigInverseOrderForSilent" which can change the order from 'deny, allow' to 'allow when not denied' for friend online status notifications which allows whitelisting such notifications only for those friends you want to see them for rather than having to blacklist all the ones you don't want to see when not in relaxed mode

…ia were set

it's possible that they have been prefilled on demand already through transparent lookups

not available, or when a decision-making logic is disabled

... now is a seperate function, and disables (i. e. skips) speed rezzing when enabled because there's no point to do speed rezzing when adda is used. (Adda does a much better job anyway, and it does it all the time.) Fixes: do not fall below the minimum draw distance, and set the minimum number of frames to average to the allowed minimum if it's lower. Perhaps the compiler optimizes better when adda is in its own function, and it may be easier to solve merge conflicts.

great ...

…arityViewer

complements making the inventory invisible on teleport

…arityViewer Conflicts: indra/newview/llglsandbox.cpp as upstream

I'm still getting an assertion when opening the radar floater after the inventory was opened, so be warned (minimize it instead of closing it). ASFAICT, this was introduced by upstream. I haven't had time to look into it yet.

I won't call it a fix because now the radar floater may remain underneath other floaters when closing and re-opening it. However, it's much better than crashing after the assertion comes up.

group-messages by message content This is now being tested. I might end up running the messages through spamassassin, or at least some perl script I'll write ...

You can specify regular expressions with xantispam rules now. Each rule comes with an integer which is the score to add to a total for the message which is being checked. The score of each matching rule adds to the total score until the total score goes over a threshold. When the total score is over the threshold, the message is considered spam. The message is replaced with "[blocked spam from]", and the sender gets a message "[spam message blocked by recipients client]". You'll be notified about this by getting an IM sent to yourself. The original message as was sent will be logged unaltered if you have logging enabled. The 'from' part of the xantispam rule gives the regular expression. For example: | come.*http | &-RxScore!6 Since the pipe sign is used as a column seperator, you currently cannot use it to specify regular expressions. I'll have to see what I can do about that. In the meantime, just use multiple rules when you need an OR. Same goes for the colon. Since it's used as a wildcard, you currently cannot use it within regular expressions. Two new settings accompany this: AntiSpamXtendedRxMinLength The default is 85 characters (UTF-8). When a message is shorter, it won't be checked. AntiSpamXtendedRxScoreThreshold This is the threshold mentioned above. The default is 5. You'll find those among the debug settings. As to the regular expression syntax: The boost library provides 'regex_search()', which is used for the matching, so you can always look it up if in doubt (seems pretty much like what perl uses). If you have not specified any '&-RxScore!' rules, processing will not find any matches, and no messages will be classified as spam. You might want to set the threshold very high in that case because that saves the lookups of the rules. Only the rules currently in the cache (i. e. in memory) are being checked. This is unlikely to change because resorting to the rules stored in the blacklist seems a bit unreasonable here performance-wise. I'm still a long way away from overflowing the rule caches (wich hold up to 64k rules). Be careful not to omit the score from a '&-RxScore!' rule, and especially don't put anything but an integer after the exclamation mark. When the rule is too short, i. e. doesn't have anything after the exclamation mark, it will be ignored. Put something else than an integer, and unexpected things might happen.

This calls for an /i flag like perl has. We'll see ...

e0009fe

the conversation

webkit failed

…arityViewer

seems to lead to performance problems

This should fix it. I don't trust it yet, so some debugging info is left in which will be removed later.

Ratany · 2013-09-24T17:35:04Z

No description provided.

create whitelist and blacklist headers also when the Enable Defaults button for xantispam is used

allows to blacklist all online notifications and allowing only those that are whitelisted fixed creating whitelist and blacklist headers when pressing the xantispam default settings button

from getting autoresponses sent to them

xantispam_transparentlookup() only once, after that use cache lookups only

+ save and load to and from files + saving and loading supports base64 encoding so non-text files can be interchanged via notecards

when appling a diff

annoying warnings

for the internal text editor

+ allowing xantispam rules to use arbitrary strings in the "from" part + format of whitelist and blacklist changed in the process (they are emacs org-mode tables now) + limit of simultaneously open queries removed, avoiding duplicate queries + now blocking by default when an identical query is issued again before an open one hasn't been answered + some minor fixes to notifications created by the media filter + added new rule types: &-DomainHandleMediaURLs &-GRLogDontSave PlayFromMediaURL * mouse wheel scrolling accelerated experimentally

be against the Linden TOS added context menu entry for the internal editor to start an external editor fixed working directory setting in the xantispam process launcher adjusted xantispam list header creation to new format of black-/whitelist

into work --- initial merge after forking from https://github.com/Lirusaito/SingularityViewer adjusted to use LLLogChat::makeLogFileName() to solve conflicts Conflicts: indra/newview/llimpanel.cpp

offers distinctly by origin and type; involves new rules "&-InventoryHandleDistinctly" and "AcceptInventory?[type]"

chat history into the external editor

disables xantispam distinct inventory accept features which will be put back with next commit

…f "ALL"

configured for it. Otherwise inventory handling rules can be overridden by other rules, especially when non-relaxed mode is enabled.

"&-ConfigInverseOrderForSilent" which can change the order from 'deny, allow' to 'allow when not denied' for friend online status notifications which allows whitelisting such notifications only for those friends you want to see them for rather than having to blacklist all the ones you don't want to see when not in relaxed mode

…ia were set

it's possible that they have been prefilled on demand already through transparent lookups

not available, or when a decision-making logic is disabled

... now is a seperate function, and disables (i. e. skips) speed rezzing when enabled because there's no point to do speed rezzing when adda is used. (Adda does a much better job anyway, and it does it all the time.) Fixes: do not fall below the minimum draw distance, and set the minimum number of frames to average to the allowed minimum if it's lower. Perhaps the compiler optimizes better when adda is in its own function, and it may be easier to solve merge conflicts.

great ...

…arityViewer

complements making the inventory invisible on teleport

…arityViewer Conflicts: indra/newview/llglsandbox.cpp as upstream

I'm still getting an assertion when opening the radar floater after the inventory was opened, so be warned (minimize it instead of closing it). ASFAICT, this was introduced by upstream. I haven't had time to look into it yet.

I won't call it a fix because now the radar floater may remain underneath other floaters when closing and re-opening it. However, it's much better than crashing after the assertion comes up.

group-messages by message content This is now being tested. I might end up running the messages through spamassassin, or at least some perl script I'll write ...

You can specify regular expressions with xantispam rules now. Each rule comes with an integer which is the score to add to a total for the message which is being checked. The score of each matching rule adds to the total score until the total score goes over a threshold. When the total score is over the threshold, the message is considered spam. The message is replaced with "[blocked spam from]", and the sender gets a message "[spam message blocked by recipients client]". You'll be notified about this by getting an IM sent to yourself. The original message as was sent will be logged unaltered if you have logging enabled. The 'from' part of the xantispam rule gives the regular expression. For example: | come.*http | &-RxScore!6 Since the pipe sign is used as a column seperator, you currently cannot use it to specify regular expressions. I'll have to see what I can do about that. In the meantime, just use multiple rules when you need an OR. Same goes for the colon. Since it's used as a wildcard, you currently cannot use it within regular expressions. Two new settings accompany this: AntiSpamXtendedRxMinLength The default is 85 characters (UTF-8). When a message is shorter, it won't be checked. AntiSpamXtendedRxScoreThreshold This is the threshold mentioned above. The default is 5. You'll find those among the debug settings. As to the regular expression syntax: The boost library provides 'regex_search()', which is used for the matching, so you can always look it up if in doubt (seems pretty much like what perl uses). If you have not specified any '&-RxScore!' rules, processing will not find any matches, and no messages will be classified as spam. You might want to set the threshold very high in that case because that saves the lookups of the rules. Only the rules currently in the cache (i. e. in memory) are being checked. This is unlikely to change because resorting to the rules stored in the blacklist seems a bit unreasonable here performance-wise. I'm still a long way away from overflowing the rule caches (wich hold up to 64k rules). Be careful not to omit the score from a '&-RxScore!' rule, and especially don't put anything but an integer after the exclamation mark. When the rule is too short, i. e. doesn't have anything after the exclamation mark, it will be ignored. Put something else than an integer, and unexpected things might happen.

This calls for an /i flag like perl has. We'll see ...

e0009fe

the conversation

webkit failed

…arityViewer

seems to lead to performance problems

This should fix it. I don't trust it yet, so some debugging info is left in which will be removed later.

Ratany · 2013-09-24T17:35:04Z

No description provided.

create whitelist and blacklist headers also when the Enable Defaults button for xantispam is used

allows to blacklist all online notifications and allowing only those that are whitelisted fixed creating whitelist and blacklist headers when pressing the xantispam default settings button

from getting autoresponses sent to them

xantispam_transparentlookup() only once, after that use cache lookups only

+ save and load to and from files + saving and loading supports base64 encoding so non-text files can be interchanged via notecards

when appling a diff

annoying warnings

for the internal text editor

+ allowing xantispam rules to use arbitrary strings in the "from" part + format of whitelist and blacklist changed in the process (they are emacs org-mode tables now) + limit of simultaneously open queries removed, avoiding duplicate queries + now blocking by default when an identical query is issued again before an open one hasn't been answered + some minor fixes to notifications created by the media filter + added new rule types: &-DomainHandleMediaURLs &-GRLogDontSave PlayFromMediaURL * mouse wheel scrolling accelerated experimentally

be against the Linden TOS added context menu entry for the internal editor to start an external editor fixed working directory setting in the xantispam process launcher adjusted xantispam list header creation to new format of black-/whitelist

into work --- initial merge after forking from https://github.com/Lirusaito/SingularityViewer adjusted to use LLLogChat::makeLogFileName() to solve conflicts Conflicts: indra/newview/llimpanel.cpp

offers distinctly by origin and type; involves new rules "&-InventoryHandleDistinctly" and "AcceptInventory?[type]"

chat history into the external editor

disables xantispam distinct inventory accept features which will be put back with next commit

…f "ALL"

configured for it. Otherwise inventory handling rules can be overridden by other rules, especially when non-relaxed mode is enabled.

"&-ConfigInverseOrderForSilent" which can change the order from 'deny, allow' to 'allow when not denied' for friend online status notifications which allows whitelisting such notifications only for those friends you want to see them for rather than having to blacklist all the ones you don't want to see when not in relaxed mode

…ia were set

it's possible that they have been prefilled on demand already through transparent lookups

not available, or when a decision-making logic is disabled

... now is a seperate function, and disables (i. e. skips) speed rezzing when enabled because there's no point to do speed rezzing when adda is used. (Adda does a much better job anyway, and it does it all the time.) Fixes: do not fall below the minimum draw distance, and set the minimum number of frames to average to the allowed minimum if it's lower. Perhaps the compiler optimizes better when adda is in its own function, and it may be easier to solve merge conflicts.

great ...

…arityViewer

complements making the inventory invisible on teleport

…arityViewer Conflicts: indra/newview/llglsandbox.cpp as upstream

I'm still getting an assertion when opening the radar floater after the inventory was opened, so be warned (minimize it instead of closing it). ASFAICT, this was introduced by upstream. I haven't had time to look into it yet.

I won't call it a fix because now the radar floater may remain underneath other floaters when closing and re-opening it. However, it's much better than crashing after the assertion comes up.

group-messages by message content This is now being tested. I might end up running the messages through spamassassin, or at least some perl script I'll write ...

You can specify regular expressions with xantispam rules now. Each rule comes with an integer which is the score to add to a total for the message which is being checked. The score of each matching rule adds to the total score until the total score goes over a threshold. When the total score is over the threshold, the message is considered spam. The message is replaced with "[blocked spam from]", and the sender gets a message "[spam message blocked by recipients client]". You'll be notified about this by getting an IM sent to yourself. The original message as was sent will be logged unaltered if you have logging enabled. The 'from' part of the xantispam rule gives the regular expression. For example: | come.*http | &-RxScore!6 Since the pipe sign is used as a column seperator, you currently cannot use it to specify regular expressions. I'll have to see what I can do about that. In the meantime, just use multiple rules when you need an OR. Same goes for the colon. Since it's used as a wildcard, you currently cannot use it within regular expressions. Two new settings accompany this: AntiSpamXtendedRxMinLength The default is 85 characters (UTF-8). When a message is shorter, it won't be checked. AntiSpamXtendedRxScoreThreshold This is the threshold mentioned above. The default is 5. You'll find those among the debug settings. As to the regular expression syntax: The boost library provides 'regex_search()', which is used for the matching, so you can always look it up if in doubt (seems pretty much like what perl uses). If you have not specified any '&-RxScore!' rules, processing will not find any matches, and no messages will be classified as spam. You might want to set the threshold very high in that case because that saves the lookups of the rules. Only the rules currently in the cache (i. e. in memory) are being checked. This is unlikely to change because resorting to the rules stored in the blacklist seems a bit unreasonable here performance-wise. I'm still a long way away from overflowing the rule caches (wich hold up to 64k rules). Be careful not to omit the score from a '&-RxScore!' rule, and especially don't put anything but an integer after the exclamation mark. When the rule is too short, i. e. doesn't have anything after the exclamation mark, it will be ignored. Put something else than an integer, and unexpected things might happen.

This calls for an /i flag like perl has. We'll see ...

e0009fe

the conversation

webkit failed

…arityViewer

seems to lead to performance problems

This should fix it. I don't trust it yet, so some debugging info is left in which will be removed later.

lee- added 30 commits August 16, 2013 23:19

set cache size fixed to MAX_CACHE_SIZE
2b6c0b9

added example to description of AntiSpamXtendedAllowedExecutables
a7714d7
create whitelist and blacklist headers also when the Enable Defaults button for xantispam is used

added &-StatusFriendIsOnline and &-StatusFriendIsOffline rules -- this
e8062af
allows to blacklist all online notifications and allowing only those that are whitelisted fixed creating whitelist and blacklist headers when pressing the xantispam default settings button

added &-IMSendNoAutoresponses: allow to excempt particular residents
c63edfb
from getting autoresponses sent to them

do file lookups from xantispam_backgnd() through
7f75ec3
xantispam_transparentlookup() only once, after that use cache lookups only

added some functionality to the interal text editor:
399c48d
+ save and load to and from files + saving and loading supports base64 encoding so non-text files can be interchanged via notecards

forgot to remove some #includes I put in which are no longer needed
42a2d96

removed a space in front of an indentation that triggered a warning
fe9e8b0
when appling a diff

added -Wno-strict-aliasing to compile options to get rid of the
0adee3a
annoying warnings

testing compilation options
f6b28c1

transparent compression and uncompression with base64 encoded files
f4c2a09
for the internal text editor

playing with compile options
629a6c9

simplified some logic in the media filter and fixed the loopback problem
000efec

removed xantispam notification that has become obsolete
2a35b33

minor fix to xantispam list header creation
fbcc79e

Merge branch 'master' ofhttps://github.com/Ratany/SingularityViewer
9afe2d5
into work --- initial merge after forking from https://github.com/Lirusaito/SingularityViewer adjusted to use LLLogChat::makeLogFileName() to solve conflicts Conflicts: indra/newview/llimpanel.cpp

xantispam: basic implementation of optionally accpting inventory
c65b12d
offers distinctly by origin and type; involves new rules "&-InventoryHandleDistinctly" and "AcceptInventory?[type]"

xantispam: fixed return value of xantispam_backgnd() when loading the
d17d56f
chat history into the external editor

code cleanup of inventory_offer_handler() to simplify logic ---
5bf3d69
disables xantispam distinct inventory accept features which will be put back with next commit

xantispam distinct inventory accept put back in after cleanup
7d59808

xantispam: changed wildcard for inventory wildcard to "ANY" instead o…
77b9bf1
…f "ALL"

xantispam: Go by intentory handling rules when any origins are
861c6cd
configured for it. Otherwise inventory handling rules can be overridden by other rules, especially when non-relaxed mode is enabled.

bugfix: media filtering not working when no xantispam rules about med…
3bb7e7a
…ia were set

part one of cleaning up comments
bbdd228

xantispam_lookup_selectively(): clear caches before prefilling because
23a9c39
it's possible that they have been prefilled on demand already through transparent lookups

part two (last one) of cleaning up comments
5510f59

xantispam policy: requests pass when rules and queries are disabled or
e481458
not available, or when a decision-making logic is disabled

lee- added 22 commits July 26, 2015 02:58

cached controls --- lookups for every frame are probably not exactly
9cb9003
great ...

Merge branch 'master' ofhttps://github.com/singularity-viewer/Singul…
647d4bb
…arityViewer

abuse the "Get Key" button on the radar to toggle inventory visibility
b539a99
complements making the inventory invisible on teleport

Merge branch 'master' ofhttps://github.com/singularity-viewer/Singul…
10e884c
…arityViewer Conflicts: indra/newview/llglsandbox.cpp as upstream

apparently upstream missed this one ...
24121b0

adjusting to upstream changes
b9a0f5d
I'm still getting an assertion when opening the radar floater after the inventory was opened, so be warned (minimize it instead of closing it). ASFAICT, this was introduced by upstream. I haven't had time to look into it yet.

workaround for the assertion with the radar floater
e0009fe
I won't call it a fix because now the radar floater may remain underneath other floaters when closing and re-opening it. However, it's much better than crashing after the assertion comes up.

first commit, i. e. very early release, of spam-filtering
de8ecb4
group-messages by message content This is now being tested. I might end up running the messages through spamassassin, or at least some perl script I'll write ...

regex matching for spam filtering is now case insensitive
1e9f775
This calls for an /i flag like perl has. We'll see ...

never show typing info when this is disabled, including local chat
60eca18

what have I been thinking with commit
626e65d
e0009fe

show the actual recipient of a spam response rather than the label of
4e26c0b
the conversation

just testing, committing to be able to pull
7917eba

added README about compiling info after finally finding out why the
f32534d
webkit failed

Merge branch 'master' ofhttps://github.com/singularity-viewer/Singul…
8922459
…arityViewer

forgot to save a file before making626e65d
6ac51f5

removed some commented-out code that had been used for debugging
5f22c84

optimization of toggling the radar floater
33c420a

disabling bandwidth throttling altogether seems a bad idea because it
adb07cf
seems to lead to performance problems

reading files backwards really sucks ...
95dd679
This should fix it. I don't trust it yet, so some debugging info is left in which will be removed later.

LiruMouse force-pushed the master branch from 3d46baa to 9508ed2Compare October 26, 2015 19:45

Update README
c80d80c

LiruMouse force-pushed the master branch 4 times, most recently from 2a96699 to 3b5a98eCompare June 9, 2016 20:50

LiruMouse force-pushed the master branch from b305e67 to f1e6092Compare May 2, 2018 23:35

LiruMouse pushed a commit that referenced this pull request Mar 18, 2019
Intermediary commit#2.
3a78568