matt/database
1
0
Fork 0
mirror of https://github.com/Dictionarry-Hub/database.git synced 2025-12-10 15:57:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

tweak: add headers to article

Browse Source
This commit is contained in:
Sam Chau
2025-01-26 01:07:12 +10:30
parent 52755fd93a
commit cb198edbe4
1 changed files with 7 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
wiki/SAE.md → wiki/RGP.md
View File

@@ -1,13 +1,13 @@
---
title: Simplification, Abstraction & Extrapolation
slug: SAE
title: Release Group Philosophy
slug: RGP
author: santiagosayshey
created: 2025-01-26
tags: [home, wiki, release_group, philosophy]
blurb: Explore Dictionarry's release group abstraction philosophy and what it actually means to simplify media automation.
---
So, how does Dictionarry _actually simplify media automation?_
## So, how does Dictionarry _actually simplify media automation?_
Well, first we need to understand that we're trying to **automate the subjective analysis of how "good" a release is**. To do that, we need to first define **what "good" even means**. To some people, it could mean how well something looks on their screen, or sounds through speakers; we define this as _quality_. To others, it means how many releases they can download while still maintaining some kind of quality standard; we define this as _efficiency_.
@@ -21,6 +21,8 @@ Release 2 (27.3 GiB): Blockbuster Movie A.1080p.WEBRip.DD+7.1.x264-group B
Looking at these two releases, you'll notice that they both have the EXACT same technical specification and would rank equally. But they're different sizes... so which is better? Using audio / video properties to measure quality / efficiency can be effective, but is largely **limited by the information that they convey**. You can't adequately answer which is better just by looking at these releases in isolation. So how do we not look at these releases in isolation? Or rather, how do we _extrapolate information that isn't already there?_
### Group Tags
Our answer lies in the little bit of information at the end of every release - it's **group tag**. Dictionarry tracks historic release group data in order to **rank groups based on their propensity to reach quantifiable levels of quality and efficiency**. We do this using two metrics:
1. Golden Popcorn Performance Index (GPPi): How many golden popcorns a release group has, as a ratio of their total number of releases
@@ -28,4 +30,6 @@ Our answer lies in the little bit of information at the end of every release - i
These metrics are **evidence based, data driven and objective**.
### TL;DR
TL;DR: Dictionarry **simplifies media automation by prioritizing release groups that achieve quantifiable levels of quality and efficiency through objective measurement**. These release group rankings are built and maintained as custom formats to be scored in their respective quality profiles. You can review these group rankings below.