Thanks! That seems to have done the trick.yes, you need to pick where the feed re-directs to.
it sends requests from their.pk site hitting your .rss url to whatever bad/other rss link you can think of. Get creative. send them to 'hell' by putting crap in their site.
I purchased an account upgrade. Gonna use some of your add-ons and see if that helps stop this.
yeah.....LOL It seems disabling RSS worked.You also need to turn off the 'latest threads'. And a sitemap...
The best solution - to shut the server down.![]()
I also blocked the IP address that came from that site via cloudflare as an extra precaution, so perhaps finding the IP's of the people stealing your content and blocking them from accessing the site might be an option.ive had malicious members that straight zip up pages and publish them on other sites.....all this starting to make me wonder if there is anything that can be done about stuff like that.....we are a private site so, its kinda shifty but idk what we can do about it or not....
173.212.195.253
. If so, just ban that IP address and you can turn your RSS back on.That was the IP. How'd you know?If their posts are almost instant, they're probably hitting your RSS pretty regularly. I'd check the server access logs and find out if there's a specific IP that's hitting your RSS a lot, especially if that ip is173.212.195.253
. If so, just ban that IP address and you can turn your RSS back on.
That was the IP. How'd you know?
If you're a private site, I would try to do something tricky with your text to try and catch the person doing it. You could use a combination of all the methods here and randomly place them on each page view / item viewed so they would need to manually edit out everything.ive had malicious members that straight zip up pages and publish them on other sites.....all this starting to make me wonder if there is anything that can be done about stuff like that.....we are a private site so, its kinda shifty but idk what we can do about it or not....
border-top: 1px solid hsl(0, 0%, calc(calc(100% - (1 * 16%)) + (1 * 4%)), 1);
border-top: none;
<div class="bbWrapper">
.Here is the message with all instances of what could represent "193524" in bold:
If you're a private site, I would try to do something tricky with your text to try and catch the person doing it. You could use a combination of all the methods here and randomly place them on each page view / item viewed so they would need to manually edit out everything.
333133393333333533323334
I'm just going to assume that you have under 10,000,000 members here. I would "prepend" (prefix) zeros up to that number for the amount of members I have (00,0100,000 or 000100000 for 100,000 members). Then, I would convert that to Morse code.
Then, I would change the signature line bar to nothing (blank)
CSS:border-top: 1px solid hsl(0, 0%, calc(calc(100% - (1 * 16%)) + (1 * 4%)), 1);
Code:border-top: none;
And display the appended morse code in the center of the message at the bottom as if it were the line separator, but still contained within <div class="bbWrapper">.
As I'm replying to you, user id 193524, you will see the Morse code on this message for 00,193,524 / 00193524 before my signature (other members would see their Morse code). MTkzNTI0!
And, you could possibly catch them when the content is copied/pasted because they can't determine what it is, a style change or Morse code. There are other cryptic things you could insert in the post that only the viewing user could see, but this came to mind as it could fit the style and, if automatic, would be copied over if they're copying the text block only. A person would have to know what it was to begin with to strip it.
Base64 is also the shortest encryption and that could be inserted anywhere (to not look like a signature line). Could you spot where yours is in this message? If it was easily seen, you could just randomize which paragraph it appends to and maybe make the text size smaller for direct copy/paste. MTkzNTI0!
HEX is also another way (seen below the Morse code "signature line divider").
You could also base64(base64(id)) and hex(hex()) -- double it up -- at random too so that you can always go backward easily from the base64/hex to the base64/hex to the user id 313933353234.
Just an idea...
Token: 8d57a748c404303ecbe96c56d07e6209
ChatGPT can easily defeat this because there is no real encryption with base64, hex or Morse code, so you'd need md5 and salt everything at random. Token is md5(userid, 555).
----- ----- .---- ----. ...-- ..... ..--- ....-
313933353234
All instances of 193524 and its variants are now bolded.
well i know exactly who it was.....and their ip....idk how i can actually PREVENT anyone from doing stuff like that tho....If you're a private site, I would try to do something tricky with your text to try and catch the person doing it. You could use a combination of all the methods here and randomly place them on each page view / item viewed so they would need to manually edit out everything.
333133393333333533323334
I'm just going to assume that you have under 10,000,000 members here. I would "prepend" (prefix) zeros up to that number for the amount of members I have (00,0100,000 or 000100000 for 100,000 members). Then, I would convert that to Morse code.
Then, I would change the signature line bar to nothing (blank)
CSS:border-top: 1px solid hsl(0, 0%, calc(calc(100% - (1 * 16%)) + (1 * 4%)), 1);
Code:border-top: none;
And display the appended morse code in the center of the message at the bottom as if it were the line separator, but still contained within<div class="bbWrapper">
.
As I'm replying to you, user id 193524, you will see the Morse code on this message for 00,193,524 / 00193524 before my signature (other members would see their Morse code). MTkzNTI0!
And, you could possibly catch them when the content is copied/pasted because they can't determine what it is, a style change or Morse code. There are other cryptic things you could insert in the post that only the viewing user could see, but this came to mind as it could fit the style and, if automatic, would be copied over if they're copying the text block only. A person would have to know what it was to begin with to strip it.
Base64 is also the shortest encryption and that could be inserted anywhere (to not look like a signature line). Could you spot where yours is in this message? If it was easily seen, you could just randomize which paragraph it appends to and maybe make the text size smaller for direct copy/paste. MTkzNTI0!
HEX is also another way (seen below the Morse code "signature line divider").
You could also base64(base64(id)) and hex(hex()) -- double it up -- at random too so that you can always go backward easily from the base64/hex to the base64/hex to the user id 313933353234.
Just an idea...
Token: 8d57a748c404303ecbe96c56d07e6209
ChatGPT can easily defeat this because there is no real encryption with base64, hex or Morse code, so you'd need md5 and salt everything at random. Token is md5(userid, 555).
Edit: ChatGPT couldn't determine md5(user id) token of Token: b03843ed5b99fd01700c468726176748 as being 193524, so you would just need a spreadsheet of 1-n with column # and column md5, then search text to find the md5 user id (or salt it if you want to add an extra layer).
----- ----- .---- ----. ...-- ..... ..--- ....-
313933353234
I'd like to say pay walling it would work, but there are people out there that would go through the trouble to just pay $1 (that could just be a real user verification method which refunds the $1 when completed) to just dump your content if it's good enough in order to get that street cred.i.e. zipping up pages of private content people made, publishing on a third party site, then linking from various other sites after that back to the zip dump.
Good way to pay them back... but I'm wondering if it would've been more effective to make an image to direct them to YourForum.com to pick up new members... Both are tempting, but the former is definitely more effective than the latter.One time I had someone hot-linking a bunch of my artwork of scifi weapons from my website and using them on a popular forum without permission, so I changed them to similar images, but pornographic versions where my weapons were all being held by topless ladies. They got reported on the other forum and banned. Ha. Stealing content can be dangerous for the stealer, because they are handing someone else control of what's showing up on their forum.
If your content is being stolen you can "sour the milk" by sending them garbage. Using htaccess rewrites you can even do it specifically for their server.
We use essential cookies to make this site work, and optional cookies to enhance your experience.