Then, if the problem is that indexing and data sharing are done at the same time, would it be a safe solution to share the data here using encryption and base64 and make requests from outside (e.g. matrix, telegram)?
And please understand that if the community I've re-launched sees an increase in subscribers, more posts, or more upvotes, it's not spam, but a temporary result of accepting Internet refugees.
I have confirmed. I plan to take your advice as top priority and operate accordingly. If you have any advice for me at any time, please send me a message.
To give a brief description of the existing community, it's basically in Korean and consists of chatting about piracy, sharing information like ripped.guide, and for data, you make a request (the request format is scene name and predb), someone uploads it, and it's shared via the aforementioned encryption and base64. What I would like to get is to change the whole operation and the way requests and uploads are done to be as low risk as possible, but I've already tried chatting like a matrix and it didn't work. Oh, and here's the community as it's currently built:) https://lemmy.dbzer0.com/c/highway
The fundamental reason for saying this is that I am one of the representatives of a Korean piracy community. We used to utilize shortfile hosting to share stuff like scene and 0day with link encryption + base64. But for some reason our community died and we became internet refugees and we were looking for a place on the web to create another pirate community and this is where we found it. If you welcome us or don't welcome us for some reason, please let me know why and if you don't welcome us, please let me know a decent alternative.
This is the direct link mentioned in number 1.
nodrm
joined 4 weeks ago
For example, if we choose matrix, the matrix link will be shown in announcements or introductions so that anyone can enter. A request will be made in matrix, and the requested data will be uploaded to a third-party short-term hosting by the uploader. After that, we will encrypt the link with AES256 using our own password (only Koreans can understand it, and there will be no way to know this password within dbzer0). The link encrypted with AES256 will be uploaded to the dbzer0 community.