We need a public archive website for the binaries created (and willingly uploaded) by the user base. This website should support uploading binaries, searching based on predefined indexer and deleting binaries.
The binaries contain a sha-256 hash of the logged in user's userId and userHash. The binary will not contain these individual properties. While logging in, the userId and userHash properties will be saved in their user.home/.rsprox/credentials/ directory.
By entering these two properties on the website, a list of binaries associated with the account will be given. Users will be able to delete any binary that's less than 24 hours old on their own, in case some sensitive data slipped through, or they just don't wish to keep a specific binary in the archive. After 24 hours, binaries can only be deleted by manually requesting from the archive owners (myself, potentially more people in the future). We limit the deletion period to just 24 hours to avoid running into scenarios where people have a falling out between one another and suddenly decide to punish others by deleting their logs, as this is all too common in this community.
Furthermore, anyone will be able to download the full archive at any point. These archives are made once every 24 hours, and contain only binaries that are at least 24 hours old.
When searching for binaries, unless searching with the aforementioned security keys, only binaries that are at least 24 hours old will be shown to the users. This is to make the 24 hour grace period during which users can delete their binaries actually mean something - otherwise people will just scrape the logs periodically. If people wish to immediately publish some logs before the 24 hour period is up, they should have the ability to do so.
We need a public archive website for the binaries created (and willingly uploaded) by the user base. This website should support uploading binaries, searching based on predefined indexer and deleting binaries.
The binaries contain a sha-256 hash of the logged in user's
userIdanduserHash. The binary will not contain these individual properties. While logging in, theuserIdanduserHashproperties will be saved in theiruser.home/.rsprox/credentials/directory. By entering these two properties on the website, a list of binaries associated with the account will be given. Users will be able to delete any binary that's less than 24 hours old on their own, in case some sensitive data slipped through, or they just don't wish to keep a specific binary in the archive. After 24 hours, binaries can only be deleted by manually requesting from the archive owners (myself, potentially more people in the future). We limit the deletion period to just 24 hours to avoid running into scenarios where people have a falling out between one another and suddenly decide to punish others by deleting their logs, as this is all too common in this community.Furthermore, anyone will be able to download the full archive at any point. These archives are made once every 24 hours, and contain only binaries that are at least 24 hours old.
When searching for binaries, unless searching with the aforementioned security keys, only binaries that are at least 24 hours old will be shown to the users. This is to make the 24 hour grace period during which users can delete their binaries actually mean something - otherwise people will just scrape the logs periodically. If people wish to immediately publish some logs before the 24 hour period is up, they should have the ability to do so.