[Addka72424]

@adelardsyah I also forgot to clarify one thing. You do not need to send reports to threads that don't contain hidden content or if they are already in other leaks.
Although maybe it's time to reform this.

[adelardsyah]

@adelardsyah I also forgot to clarify one thing. You do not need to send reports to threads that don't contain hidden content or if they are already in other leaks.
Although maybe it's time to reform this.

Alright! But what do you mean by "or if they're already in other leaks"?

---

i totally agree with standards and samples on databases
you can say that some infos are the bare minimum, but
users can increment it the way they want

adding to the infos @tail said, i would love to see the size
of the leak in mb/gb/tb before downloading. it is frustrating to see a
interesting leak asking 8 credits for less than 1kb

so in my opinion it would be:

Source/Website | Count/Size (lines and mb, gb, tb uncompressed) | Type/Format | Date/Year

and users would organize their thread the way they want, as long as this info
is available

Thanks for contributing to this discussion! You're right. The file size and information, like those in the official database section, are great addition to this too.

[Addka72424]

@adelardsyah I also forgot to clarify one thing. You do not need to send reports to threads that don't contain hidden content or if they are already in other leaks.
Although maybe it's time to reform this.

Alright! But what do you mean by "or if they're already in other leaks"?

---

i totally agree with standards and samples on databases
you can say that some infos are the bare minimum, but
users can increment it the way they want

adding to the infos @tail said, i would love to see the size
of the leak in mb/gb/tb before downloading. it is frustrating to see a
interesting leak asking 8 credits for less than 1kb

so in my opinion it would be:

Source/Website | Count/Size (lines and mb, gb, tb uncompressed) | Type/Format | Date/Year

and users would organize their thread the way they want, as long as this info
is available

Thanks for contributing to this discussion! You're right. The file size and information, like those in the official database section, are great addition to this too.

Other leaks section.

[adelardsyah]

@adelardsyah I also forgot to clarify one thing. You do not need to send reports to threads that don't contain hidden content or if they are already in other leaks.
Although maybe it's time to reform this.

Alright! But what do you mean by "or if they're already in other leaks"?

---

i totally agree with standards and samples on databases
you can say that some infos are the bare minimum, but
users can increment it the way they want

adding to the infos @tail said, i would love to see the size
of the leak in mb/gb/tb before downloading. it is frustrating to see a
interesting leak asking 8 credits for less than 1kb

so in my opinion it would be:

Source/Website | Count/Size (lines and mb, gb, tb uncompressed) | Type/Format | Date/Year

and users would organize their thread the way they want, as long as this info
is available

Thanks for contributing to this discussion! You're right. The file size and information, like those in the official database section, are great addition to this too.

Other leaks section.

Hey, i'm so sorry but i might be lost in this, do you mean that i don't have to report threads that don't contain any sample if they're in other leaks? Doesn't other leaks section also require a thread to provide a sample?