-
Notifications
You must be signed in to change notification settings - Fork 1
Specification
The network must be anonymous and distributed, without any central autority. We're planning on using a DHT table and TOR.
New users join by invitation from inside users, this may happen in form of QR code or URL.
After a user has joined the network it should interleave deeply with it by downloading a list of peers. This mechanism should avoid the need of another invitation
The main purpose of the network is distributing rare pepes throughout the internet in order to make them censor resistant.
By it's nature the network reduces the rareness of the posted pepes, especially if the users decide to store them.
The rareness should be a function dependent on time and downloaded instances and it shouldn't depend on users preferences, this mechanism encourages old pepes preservation as historic artifact and encourages the creation of new rare pepes.
Old pepes may become rare again if the number of their instances goes below a threshold.
The rareness function shouldn't consider every new pepe as rare, but there should be a sweet spot of time and downloads that maximizes the rareness. This mechanism avoids the boosting of normie and cancerous pepes.
This system is not meant to be democratic, users shouldn't be able to vote the best pepes; instead they should preserve the best pepes by downloading them.
Illegal and degenerate content should be overwhelmed by rare pepes instead, a well adjusted rareness function should allow the best to suppress any cancerous content.
The user interface should be exposed as a web page provided by a local or remotely owned server. Please refrain from creating pepenet hubs which allow to access the network without hosting it. If enough users adopt this behaviour the network will eventually collapse.
Pepes should be stored in a local folder in png or jpeg, other formats may be added in the future.
Users should be able to share new pepes by simply dragging and dropping files in the folder. A filesystem hook would be ideal, but even an update-pepes command will suffice.
Users should be able to scroll the various pepes from their web browser and choose which ones they want to download.
There should be a mechanism to prevent rareness alteration by boosting the downloads.
Every pepe should have metadata:
- Timestamp
- Hash
- Downloads
- Rareness
- Dynamic tags
Spam and metadata falsification must be prevented.
The normieness of a pepe shouldn't be determined by the users, but by the system itself.
The function depends on the pepe's timestamp and number of unique downloads (pins).
To be rare the pepe must satisfy multiple conditions:
-
a < x < b: x is the number of unique downloads, it should be between a minimum (a) and maximum (b) value that should be normalized accordingly to the timestamp. -
dt > threshold: if the pepe lifetime (dt) is very little but it has the right number of downloads it is probably spam.
Cases:
-
dt < threshold && a < x: Spammed pepe -
dt > threshold && a < x < b: Rare pepe -
dt > long_time && a < x < b: Artifact pepe -
dt > threshold && x > b: Normified pepe -
dt > long_time && x > b: Pop pepe -
dt > long_time && x < a: Outdated pepe -
dt < threshold && x < a: Novel pepe
Absolute cancer < Pop < Spammed < Normified < Outdated < Novel < Artifact < Rare
The specification may be altered in the future