Finer-grained ubiquitous rules #301
Comments
|
Thanks and thumbs up! |
|
Well this adds a good chunk of overhead. For each single cell, the following pseudo code needs to run in addition to the existing code:
And a lot of cell may be visited when going up the matrix inheritance path, all the way up to the And this not counting the complication of graylisting cells, like for example user graylist a cell in local scope in order to cancel specific rule in global scope, than later remove said rule from global scope leaving the graylisted cell uselessly explicitly graylisted. Sigh... |
|
Closing as "won't fix". Sorry, the required changes are scary. On the surface all is simple and easy. Digging under the surface, it's horrible. So we will have to accept the extension can't and won't do everything that comes to mind. So back again to the same point: scopes are sandboxes, and I can't argue about this anymore. My only suggested alternative from this point forward is to fork the code, I can't implement this without compromising the sanity of the code (and mine I suppose). |

Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.

Many users have asked about "scope inheritance". Scope inheritance is not something I will undertake because I don't know how this would ever work when considering all the complications.
However given the specific examples given, what would take care of the issues is really finer-grained ubiquitous rules. This potentially will affect negatively matrix filtering performance. Need to investigate faisability though, as this would take care of many of the issues raised.
The text was updated successfully, but these errors were encountered: