HelloZeroNet / HelloZeroNet/ZeroNet

How works to PIN or not to PIN an optional bigfile video when streamed?

Open
#1,484 6 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
18.8k
Forks
2.3k
PR merge metrics
No merged PRs in 30d

Description

### Step 1: Please describe your environment

* ZeroNet version: 0.6.3 rev3502
* Operating system: W10
* Web browser: FFbeta
* Tor status: available
* Opened port: no

### Step 2: Describe the problem:

Hello, it seems that on a zeronet based media streaming site the optional bigfile was PINned (making it undeletable by the "garbage collector") just because it was a few seconds played. The size on drive appears to be several hundred of megabytes even it was watched several seconds and closed as not worth to be watched/shared. Though the file is PINned :-/ [Here are](http://127.0.0.1:43110/Talk.ZeroNetwork.bit/?Topic:1530097903_1NZftAz9VSawGF5JgMYGFv4ByoKEaQbNZu#comment_168_1NZftAz9VSawGF5JgMYGFv4ByoKEaQbNZu) more details. Is there anything that can be done so potentialy unwanted bigfiles are not automaticaly PINned and do not use large amount of data on HDD even minority of the file was downloaded?

Contributor guide

No contributing guide indexed for this repository

Research direction

No source file or test is named. Start by reproducing the partial video playback in the reported ZeroNet 0.6.3 environment and trace how streamed optional bigfiles become PINned. Done means an unwanted partially watched bigfile is not retained permanently and remains eligible for garbage collection.

Written by the indexing model from the issue text.

Assessment

Domain
distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.