Consider this a bump
Topic: LoyceV's notification bot (7 days retroactive) - page 2. (Read 3345 times)
I noticed some missing topic titles in my own notifications. I think this was caused by the last month's DDOS downtime. I'm currently scraping all missing titles (and many of those don't exist anymore because the topic was deleted). This will take about 3-4 days to complete.
Consider this a bump
Consider this a bump
Although it doesn't work for me either
Ninjastic's whitelist worked before mine. You should see this again (in a few minutes). 
Will quote to test your notification.
It also doesn't work for me, even though I started getting notifications on Telegram
It works, but updates are every 6 minutes. You were a tad too fast.
I believe the bot is down ?
Not updating since July 8 (or my forum friends all forgot about me
)
Let's test: it should work again, theymos whitelisted my scraper from Cloudflare's hickups.Not updating since July 8 (or my forum friends all forgot about me
)Still not working for me.
https://loyce.club/notifications/1554927.html
Edit: it works.
I believe the bot is down ?
Not updating since July 8 (or my forum friends all forgot about me)
Let's test: it should work again, theymos whitelisted my scraper from Cloudflare's hickups. Not updating since July 8 (or my forum friends all forgot about me
)
I believe the bot is down ?
Not updating since July 8 (or my forum friends all forgot about me)
Not updating since July 8 (or my forum friends all forgot about me
) Is LoyceV a collective? 
Good to hear you have some helping hands.
It's not a secret the server is sponsored, that's where the help came from. Good to hear you have some helping hands.Quote
Litespeed should still be able to filter out bad traffic, or rate limit traffic. I could be wrong but I have seen it used to mitigate both basic and advanced attacks before. It just depends on configuration.
I don't want to challenge any trolls, but the current solution should suffice. I'm amazed at the tricks AWS can pull Quote
Is there no possibility to build a function that could "rescan" from a set date, e.g from first attack til now?
Not really: I'd have to check all recent topics for activity, which would be more work than it's worth. The tool is working as of this post but yes, there are some struggles to properly connect consistently.
At the moment, I can't reach the server at all anymore. We're working on it.Is LoyceV a collective?
Good to hear you have some helping hands.Quote
I wonder what motive someone would have to attack your tools? They only really benefit the community and don't really pose a downside to anyone. Unless this is the case with some other tools on the server?
I'm the only one using the server's IP address. Why can't they just leave fake negative feedback, and complain on the Reputation board, like normal internet trolls? Haha! Sophisticated (for the worse) trolls.
Quote
Have you tried adopting litespeed over/in conjunction with apache? It's a good, cheap solution to filter most bad traffic without going to the extent of adopting an expensive/intrusive method like cloudflare.
The attack was on port 443, so this won't matter.Litespeed should still be able to filter out bad traffic, or rate limit traffic. I could be wrong but I have seen it used to mitigate both basic and advanced attacks before. It just depends on configuration.
What about running a Tor server? I've got the following address you could have 
:
None of that works as long as the current server is unreachable :The plan is to work some AWS magic and be back online after that. I was unprepared to setup a second scraper to prevent losing posts, so posts archive is going to be less complete. I still see LoyceBot online once in a while, it may still be able to scrape some posts.
Update: It works again. I missed about 5000 posts in total
Quote
loyceorg5d7vcl4sj5kufns5xwaoi2k3rivjqpodjzww4ijzvzdpueyd.onion
Not bad Nice to hear!
Is there no possibility to build a function that could "rescan" from a set date, e.g from first attack til now?
What about running a Tor server? I've got the following address you could have :
None of that works as long as the current server is unreachable :The plan is to work some AWS magic and be back online after that. I was unprepared to setup a second scraper to prevent losing posts, so posts archive is going to be less complete. I still see LoyceBot online once in a while, it may still be able to scrape some posts.
Update: It works again. I missed about 5000 posts in total
Quote
loyceorg5d7vcl4sj5kufns5xwaoi2k3rivjqpodjzww4ijzvzdpueyd.onion
Not bad
What about running a Tor server? I've got the following address you could have :
loyceorg5d7vcl4sj5kufns5xwaoi2k3rivjqpodjzww4ijzvzdpueyd.onion
:loyceorg5d7vcl4sj5kufns5xwaoi2k3rivjqpodjzww4ijzvzdpueyd.onion
The tool is working as of this post but yes, there are some struggles to properly connect consistently.
At the moment, I can't reach the server at all anymore. We're working on it.Quote
I wonder what motive someone would have to attack your tools? They only really benefit the community and don't really pose a downside to anyone. Unless this is the case with some other tools on the server?
I'm the only one using the server's IP address. Why can't they just leave fake negative feedback, and complain on the Reputation board, like normal internet trolls? Quote
Have you tried adopting litespeed over/in conjunction with apache? It's a good, cheap solution to filter most bad traffic without going to the extent of adopting an expensive/intrusive method like cloudflare.
The attack was on port 443, so this won't matter. 
Notifications: http://loyce.club/notifications/2739748.html
Code:
ignoreuser:2739748
fullquotesorjustlinks:fullquotes
order:newestfirst
alias:Galt
Hey, great tool! I've only been using it for a couple of days and already I'm finding great value from it. Nice work (as always) Loyce
Well, I'll have to disappoint you: for the first time since I created it, it was really down:It looks like there's a DDOS going on, which started yesterday. I started DROPping ports, but I forgot to exclude Bitcointalk (it was quite late), so I broke my scraper.
For 7 hours and 2 minutes, I didn't download any posts between posts 62480523 and 62481467. That's 944 missing posts, which also mean my notifications failed for those.
I hope to keep it working from now on, but the DDOS is ongoing. For 7 hours and 2 minutes, I didn't download any posts between posts 62480523 and 62481467. That's 944 missing posts, which also mean my notifications failed for those.
Let me try this
Notifications: http://loyce.club/notifications/314792.html
Notifications: http://loyce.club/notifications/314792.html
Code:
ignoreuser:314792
fullquotesorjustlinks:fullquotes
order:newestfirst
Notifications: http://loyce.club/notifications/404695.html
Code:
ignoreuser:404695
fullquotesorjustlinks:justlinks
order:newestfirst
Notifications: http://loyce.club/notifications/885256.html
Code:
ignoreuser:885256
fullquotesorjustlinks:justlinks
order:newestfirst
9
I've added it. Try this:
It took me a while to fix this, so it's still experimental. Adding the feature was easy, but triggering it at the right moment (to reduce server load) didn't really fit my current setup. Let me know if anything fails.
It's not working yet. Feel free to add an alias already, I'll test it later.
I tested it again, andit looks okay. Try it, and keep me posted
I think I got it now
I will try.
Is this correct?
Notifications: http://loyce.club/notifications/1554927.html
Thank you
I would like to be notified, in the same link, when someone mentions bitcoindata.science
This has been on my TODO for years:TODO:
-custom aliases
-custom aliases
I've added it. Try this:
Preference: show notification for other keywords:
alias:nickname (only letters and numbers, you can add more than one alias, use a new line for each)
alias:nickname (only letters and numbers, you can add more than one alias, use a new line for each)
It took me a while to fix this, so it's still experimental. Adding the feature was easy, but triggering it at the right moment (to reduce server load) didn't really fit my current setup. Let me know if anything fails.
I tested it again, and
I think I got it now
I will try.
Is this correct?
Notifications: http://loyce.club/notifications/1554927.html
Code:
ignoreuser:1554927
ignoreuser:3601165
fullquotesorjustlinks:fullquotes
order:newestfirst
stillusingthis:yes
alias:bitcoindata
alias:FeeBuddy
Thank you
I would like to be notified, in the same link, when someone mentions bitcoindata.science
This has been on my TODO for years:TODO:
-custom aliases
-custom aliases
I've added it. Try this:
Preference: show notification for other keywords:
alias:nickname (only letters and numbers, you can add more than one alias, use a new line for each)
alias:nickname (only letters and numbers, you can add more than one alias, use a new line for each)
It took me a while to fix this, so it's still experimental. Adding the feature was easy, but triggering it at the right moment (to reduce server load) didn't really fit my current setup. Let me know if anything fails.
I tested it again, and
I think I got it now
you only need your phone number during registration (for that you can use those disposable fakes from the internet). after registration, you can completely remove the phone number and it will be completely invisible to everyone who contacts you.
Although slightly off-topic here: what happens to your account if someone else registers the same phone number on Telegram later? Jump to: