Limited Guest Viewing Pro - Boost Registrations

Limited Guest Viewing Pro - Boost Registrations [Paid] v2.1.7

No permission to buy ($40.00)
Wutime updated Limited Guest Viewing Pro - Boost Registrations with a new update entry:

v2.1.0

  • New: All-new consolidated Charts dashboard at admin.php?wutime-lgv-charts with one unified statistics experience.
  • New: Flexible date filtering with presets (including 3 days), custom start/end date selection, and one-click reset.
  • New: Highcharts-powered analytics across the page for clearer trend visibility and better long-range readability.
  • New: Conversion mix hero section with at-a-glance donut charts and KPI cards for total, earned, warned, forced, and averages.
  • New...

Read the rest of this update entry...
 
Would love the ability to replicate this, but also for users in an adblocking usergroup.

'You have adblock, you have 32 page loads...' before being unable to view any more.

It would add real teeth to the adblock detector/usergroup swap and tracker.

Just a suggestion anyway, thanks for all your hard work supporting the XF community.
 
AdBlock Tracker works like that already, but a bit opposite in order to remain invisible. After too many AdBlock visits it gimps their user access permissions, and requests they disable their AdBlocker to restore normal access permissions, in due time.

Limited Guest Viewing is just for guests, and while it sounds nice what you're proposing, it would inevitably lead to a technical user dismantling the AdBlock detection by creating multiple "filter rules" globally against your domain. Primarily becaue of the upfront and obvious nature of letting the user know they're being monitored, and the fact you're making it visible to guest accounts.
 
Also, LGV is mainly there to push visitors to sign up and register. It increases conversions by turning people who are just browsing into actual members at a much higher rate. The benefit is that a registered user is far more likely to interact with your board than someone just passing through for information. Given that goal, the add-on is already doing what it’s supposed to do.
 
Are there any plans to add a similar limiting system for guest posting, not just guest viewing?

What I have in mind is something like this:
  • Allow unregistered guests to make a limited number of posts
  • Track the limit using a persistent cookie/session, possibly with IP as an additional fallback or anti-abuse measure.
  • Once the guest reaches the limit, show a registration CTA/notice instead of allowing more posts.
  • Ideally, the limit could be configured per node or certain forums could be excluded.
  • It would also be useful to have a configurable reset period, for example X posts per 30 days.
The idea would be to let visitors participate and experience the forum before forcing registration, but still give active guests a reason to create an account instead of posting anonymously forever.

Your existing guest viewing limit / warning / force registration system already seems very close to the UX I have in mind, except the counter would be based on guest posts rather than page views.

Is something like this planned, or would you consider adding it in the future?
 
Are there any plans to add a similar limiting system for guest posting, not just guest viewing?
It's a good thought, but outside the scope of this add-on. Plus, guest posting isn't something that's really supported with xenforo because the post isn't associated with a normal XenForo member account.
 
Considering this to curb AI bots mass attacks as "guests" / unregistered users. Any thoughts?
This software is more intended to get people to register, and more importantly, convert regular members to paying subscribers.

For the "AI bot attacks" you really need to implement firewall management, bot protection, rate limiting and some server hardening. They're quite sophisticated these days so you need to spend a few hours making sure your server is provisioned properly. I'd highly recommend usiing something like the free CloudFlare plan, route traffic through CF IP's only, lock down your server, and then use their free firewall rules. It's worked wonders for me.
 
This software is more intended to get people to register, and more importantly, convert regular members to paying subscribers.

For the "AI bot attacks" you really need to implement firewall management, bot protection, rate limiting and some server hardening. They're quite sophisticated these days so you need to spend a few hours making sure your server is provisioned properly. I'd highly recommend usiing something like the free CloudFlare plan, route traffic through CF IP's only, lock down your server, and then use their free firewall rules. It's worked wonders for me.
Thanks, and yes this is all in place. Just considering complementary options. This was suggested to me as an extra layer, sending bots hit a wall. :)
 
If this is helpful for inspiration, I built a monitoring website that uses cloudflare to mostly automatically watch all my xenforo installations. I have things locked down tight for guests so that most things are on cache and most endpoints guests don't need aren't accessible. Dropped my server resource usage down by factors of 100. I even downgraded my servers to cheaper versions because I don't need as much RAM or vCPU's now that the bot traffic is completely under control.

Then, for AI bots that register and like to scrape, I have an automated system that if bots scrape pages when logged-in too quickly it'll automatically block them by IP if flagrant, or manage challenge them for 7, 15, or 30 days depending on severity. It also gives me an interface to see offenders and then I can easily see if they're real members or not, whitelist moderators etc. It's gotten to the point where what used to take hours per week to manage is now so fully automated that I rarely intervene or even pay attention.

Pretty straight forward to build using Codex or Grok Build.
 
I'm curious about how this could help with bots as I am regularly getting attacked by residential proxy swarms - they change IP's so fast they never reach guest viewing limitations. Now if I hardened the views to say 1 or even just straight to the registration page, this would presumably stop ALL the residential proxies hitting the site. However they would probably all (quite a few thousand that get past cloudflare challenges) then try and register? So am weighing up if this could affect my email account with increased bounced emails from failed registrations/fake emails. Any thoughts?
 
Back
Top Bottom