HelloZeroNet / HelloZeroNet/ZeroNet

On a site i signed and published manual change, but site .db was not updated automaticaly

Open
#1,840 0 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: 3744
* Operating system: Windows
* Web browser: FF

### Step 2: Describe the problem:

Hello,

on computer A (https:// 0net.io zeronet proxy) i published a video on KopyKate zeronet video streaming site. It turned the video is not playable because i think the msgpack file was not created. So on zeronet computer B i removed data.json file (from my kopykate user directory) and signed the change using my user ID private key which i found in ZeroNet/data/users.json.
Video disappeared from computer A, but was left visible for multiple days on computer B (where i signed&published the change).

After i rebuilt the KopyKate database, then video finally disappeared from the list.

Is this some bug? I think ZN should automaticaly update the DB.. and do not show outdated content?
Is this related to ZeroNet or that particular site? Can zeronet be made the way that after signing and publishing some change, the DB will be modified or rebuilt to reflect the change automaticaly?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the flow described with the site's data.json and the user's users.json signing key, then compare the local database before and after signing and publishing. Inspect the database rebuild path and determine whether stale content is expected or whether an automatic refresh is missing; done means the behavior is confirmed and covered by an appropriate test or documented explanation.

Written by the indexing model from the issue text.

Assessment

Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.