It first has to be approved by some moderator, what is this all about? Perhaps it thinks I’m spamming? 
I approved your post already. Please check. Yes, we use third party Discourse software and it has some anti-spam systems that we don’t make/control, but we are good about checking and approving stuff as soon as possible!
Also, all your other posts were approved immediately. Discourse just didn’t like that single one.
OK I see, I just thought it was a bit weird. Strangely enough I could delete the post, but not edit it, while it was waiting for approval. 
1 Like
Yeah, we use Discourse.org for the forum and I’m pretty sure it’s just the default settings.
Weird, it happened again today, I wonder if it happens when I mention other software?
1 Like
I approved that post. Sorry for the issue @RasheedHolland!
1 Like
Sadly enough I just got another weird error.
In one of the threads I couldn’t reply because it said I first needed to wait for a reply, before I could reply to a post? It said something like ‘‘3 consecutive replies are not allowed’’ or something?
1 Like
I found this at Discourse.org: This is a default setting that prevents users from posting too many posts after each other to encourage people to edit their post and add information instead.
I won’t lie, these things are kinda annoying. I feel like it should be looking at someone’s reputation, before coming to the conclusion that someone is probably a spammer.
1 Like
Good idea. Maybe they can link it to social media accounts with followers, or Linkedin accounts, etc… If someone is more trustworthy then it trusts their posts more. You can tell them at Discourse.org, then when we get an update it will have the changes they made. I noticed they are pretty good about listening to user feedback.
I see that once again my post is awaiting approval. I think this forum should also give an option to edit my post that awaits approval, not only an option to delete it. 
Sorry for the issue, let me see what’s going on.
This issue still hasn’t been fixed? Perhaps my posts should be edited?
I think certain things could have been said in a different way, although I didn’t mean it in a harsh way. I’m just trying to figure out what the best strategy for you guys exactly is.
Yeah, I think we are a bit lost on strategy currently due to changes to Windows, but hopefully we can figure out a clear path forward. Thanks for your feedback and sorry for the issue.
To clarify, you still haven’t approved the posts, did you read them? Perhaps I should remove the post, so that I can rewrite it? And it might be just me, but seems like the quoting system is still broken. This forum software really isn’t that good, I’m afraid.
In my post I tried to explain that security tools should still be able to offer many of the requested features on Windows 11. It isn’t clear to me if you guys have tried to add protection against code injection for example.
If you block code injection/hooking, you can also block keyloggers, without keystroke encryption. I also think you guys should combine SpyShelter with AppControl, you could make a freeware and Pro version.
1 Like
Great ideas, thanks! Sorry for the issue with the posts.
Also, it would be nice if we understood how to do anti-keylogging somehow that was reliable, then we just offer a simple anti-keylogger again here. It’s what we would want most probably.
I have now deleted the posts in the other thread, but I wonder if I can still post in that topic, without constantly having to wait on approval? Why weren’t those posts approved, was it because of the content?
Basically, it has now been 2 years since SpyShelter 15 was released, and seems like you guys are not going to add more ‘‘old skool’’ protection features that most behavior blockers should offer. So if this is the case, then I will also stop asking for new features, because it’s pointless. 
No, please continue asking about new features. For us it has felt devastating because anything interesting we wanted to do with security always seemed to be things we could no longer implement with Windows in a reliable way, so always having to say “no” is a real downer. Nobody is perfect, so maybe there is something we are missing somehow, but in our own research we find a lot of the things we want to do are no longer possible with Windows 11. But things change, and maybe there will be some new way we can do anti-keylogging that’s allowed, reliable, and a way we didn’t think of before and we can just go back to making a simple anti-keylogger here which I think SpyShelter is all about. We tried to turn it into something else and still used the name “SpyShelter”, which is a famous anti-keylogger, so maybe we made a mistake.
OK so you guys have actually looked into how to add protection against code injection? As mentioned before, there are other tools out there that can block this on Win 11. So I hope you can understand why I find it odd that your developer hasn’t been able to figure this out.
So that’s why I think it’s pointless to keep asking about it after 2 years. In my view, you guys should at least protect against API based keyloggers and keyloggers who make use of hooking/injection. But it’s not going to happen, so let’s move on. 
1 Like