Best Blackhat Forum

Full Version: [UPDATE] How-To-DO Link(s) Protection,Attachment(s) Protection,Content(s) Protection
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2 3 4 5 6 7 8
What is this PROTECTION System?
This is a term we implemented in
HIDING or
LOCKING the following:

1) URL / Download link
2) Attachment
3) Single Content/ Whole Content of the post(s)


How to implement this?
Simply enclosed it with LOCK TAGS.
The html format for this is
[Image: hidey.png]

or

Simply click the LOCK icon
[Image: lockcn.png] on the editor.
[Image: addprotect.png]


When to USE this?
This was been created purposely
in order to protect FAST deleted shares.
Especially shares that are being monitor constantly that causes the download links to be deleted.
So with this kind of system, we can atleast MINIMIZE links being taken down or being deleted.


Atleast we can save the UPLOADERS effortof uploading it or
reupping it.


DO NOT ABUSE THIS SYSTEM.
I had this feeling that this system maybe abuse by some spammers or scammers.
If in case you see this system being abuse by anyone.
Please do NOT hesitate to
press the
[Image: postbit_report.gif] REPORT button.

Thanks for reading
and have a blessed Sunday to everyone.



Press [Image: postbit_thx.gif]
thanks button
if you like this new system. Wink

UPDATE:
>> Old thanks data was been converted to likes data.
>> New thanks system is been created that doesnt force users to post reply in order to unlock hidden content
>> Member can just press thank button WITHOUT the need for the reply.


How to implement this?
Simply enclosed it with LOCK TAGS.
The html format for this is
[Image: hidey.png]

or

Simply click the LOCK icon
[Image: lockcn.png] on the editor.
[Image: addprotect.png]

IMPORTANT Note:
After clicking or pressing the THANK You button.
Please REFRESH your browser so that hidden content or protected link will appear or show. Thanks.
sounds like a plan .. also I was in bht earlier and a friend posted a sneaky way to code the download links (i mean really code them good)

ok tell me what you think this is:

Code:
34653661363733333465343436333330346537613431376135393534346136643464366435393333​34653761363333333465376136333739356135343539373834653661353133333464366135393335​34653761353933323465353434613663346536613464333235613661356136623464366435393333​34643434363333313465366134393332353937613539333534653661346437393235333034313561​36613531333434653437343533323561353436333331346537613431333234643661346136633465​3661363733333465343435613662346536643464373735393531323533333434323533333434

just looks like a bunch of random numbers does it not?

well its actually a link thats coded

here is how you un-code it:

go to this link:

Code:
http://www.bigprism.com/online-tools/base64-hex-ascii-encoder-decoder.html

and then you have to post the code into the box

and then you have to:

enter the Sequence (Click decode for each method in order):

Hex
Hex
Url
Base64
Hex

PRESTO!

it reveals the live link :)

I thought it was a neat trick and would slow them down if anything from deleting shares that we all post ~
xXstackXx what you mentioned on post#2 is also a good way of protecting it. But the problem with this is if a CERTAIN DESPERATE owner monitoring his product. He will register on every forum(s), monitor the download links, report the download link then link(s) die soon. I am pretty sure he will really decode and decode it until he got the correct download link(s) then reported it again for link removal.
But with this system. We can make sure and pretty obvious for us who is monitoring the certain thread(s). Its pretty obvious that new registered user(s) will it be the culprit or quite be our main suspects but atleast we can see desperate move(s) and if ever we are sure about this then we can issue an IP(s) ban. Then if ever he will come back again as New Registered user. He had to thank and post again (Atleast we made the owner thanks/post on his own leaked product) LOL!. Atleast we can clearly see some suspicious user who only monitor certain products. Quite obvious for us. Then if in certain case, or extremely case that its really burden in protecting the download link(s) then do the initiative on doing the "pm" system as what "Direct Download" is doing on fast deleted shares.
Hi. I loved the new locking system. Thank you.
I am already implementing it. :)

Mirrorman will continue to look and provide more mirrors / split mirrors for bestblackhatforum.com EXCLUSIVELY becaused i loved and proud to be part of this forum.

Sincerely,
Mirrorman
By the way
Guys, Really sorry for the pm's that was been ignored.
or I havent replied yet. I am currently busy with this another 2 NEW/FRESH upcoming ripped.

http://bestblackhatforum.com/forumdisplay.php?fid=785
and this one
http://bestblackhatforum.com/forumdisplay.php?fid=802

Unlock this when i'm done.
Please be patience. Thanks.


Back to BUSY MODE.
Again thanks for reading and take care everyone.
Enjoy your stay :)
Thanks admin for the new protection mode :)
This is great for everyone! Will be implementing asap!

ALOHA!
Hi,

I know you've said only on 50MB+...
But, I'm adding it on stuff I've nulled for BBHF also..

Let me know it it's a problem?

Thanks,
Si
I like this idea, but there is one problem I see with this.
That is any thread using this is going to be filled with posts that do not add anything to thread.
Most of the posts will now consist of any number of ways of saying "thank you", "I want this", "let me see", " where is the link", "let me try", "I want to test", etc.
I have already seen some members just copy and paste another members reply in the same thread.
Saying thanks is great, but all that other stuff just looks like spam to me.
What I have seen a couple of other forums do is just to hit the thanks button to unlock the content, so the thread is not filled up with all those non essential posts. All they do is hit thanks and refresh the page and it is unlocked. That way you still can see who accessed the content by seeing who clicked on the thanks button.
So you are saying only use this locking system for files that are 50Megs and larger? why not do it for any share regardless of size? Maybe I am missing somehthing here?
Pages: 1 2 3 4 5 6 7 8
Reference URL's