15th
Content Limitation Details
I’d like to explain a few details about how content limitation works in EventBox.
Event Ownership
Each event can have multiple “owners” (folders / containers). It’s important to distinguish between ownership and aggregation. Just because you see an event in a folder / container, it doesn’t mean it’s owned by it. I’ll give a few examples to clarify the point.
If you use Google Reader, you know that content is organized in feeds. Each feed owns the feed posts that belong to it. What about any folders? Well, they don’t actually own any of the feed posts - the only reason any events are displayed is because the folders aggregate the contents of feeds.
Let’s support you use Twitter and have created a folder to keep all your searches. Each search owns the events it contains but the folder containing your searches doesn’t own a single event.
Content Limitation
It’s crucial to understand that when you right click on any container (except a few ones, see below) and adjust the content limit, you’re only adjusting the limits for any owned events. The consequence is that if you set the limit for a Google Reader / Twitter folder to 1 day and pressed “Limit Now”, nothing will happen. Why? Because the container doesn’t own any events, so there’s nothing to remove.
Exclusion
We also have the ability to exclude some containers from being limited. If you right-click on them, you will not see any options to adjust the limitation (Twitter’s Favorites and Google Reader’s Starred are prime examples).
Behavior
We’ve changed the behavior of the content limitation actions performed when you use the interface (i.e., by right-clicking). Everything above is still valid and is how things work under the hood. We’ve made the following adjustments:
- When you set the content limitation for a folder, we will automatically assume that you also want to set the same content limit for all folders below.
- When you manually limit (“Limit Now”) a folder, we also perform content limitation for the folders below.
