Robert, support just told me how to fix this bypass by switching the site from "Hard paywall" to "Hard paywall with encryption." https://help.bloxcms.com/knowledge-base/applications/community/subscription/misc/article_a177722c-2be5-11e5-8d8a-534ce2eca693.html

Checkout Christine's reply in this topic: https://community.townnews.com/communities/1/topics/604-set-broadcast-time-separate-from-start-datetime

It looks like it might solve this issue, but she hasn't confirmed it.

I've never seen private mode get around the paywall, it is what I use to test how things look to non subscribers.

But as Robert mentioned, the Outline.com method is dead simple for anyone to use, and that tip is now making the rounds in public here as well.

In my opinion any method that allows access past the paywall needs to be fixed.

Wow, that is pretty dang simple for anyone to use.

https://status.io/pages/incident/580a2a0e38015eaf1900122b/5c5de1f868c2f604a4cf07cd

Thanks Christine, can you confirm if it will fix this issue specifically: https://community.townnews.com/communities/1/topics/1095-totalcms-social-broadcast-limitations

Ouch. Somewhat on topic, we had to put a "Real Name" policy in place back in 2015 when comments started getting out of hand, it really helped: https://www.galvnews.com/realname/

This is a good idea. We typically don't let people know a comment was denied though and we rarely get questioned about it because I think for the most part they know why already.

Sorry I missed this. Yes that is what we've done in the past. I guess I need to test it and make sure nothing has changed as far as the user experience.

That looks very promising, thanks for the update Christine.

Will one of the scheduling options be "at the asset Start Date/Time" for when the person creating the notification doesn't know if an editor will move it later? If so it sounds like that will mitigate the problem from my other post today (Ticket 644051).

Also I assume that if someone schedules a notification for prior to the Start Date/Time the system will be smart enough to hold it until then and not broadcast something that results in a 404 page?