I am trying to figure out how, or if there is a way, to restrict only New and WWW (i.e. they meet both requirements) from being able to post in message areas until they are upgraded. I was hoping to figure out that maybe I could set the new user level for those users to a separate value than for telnet/SSH/etc. users.

I have read here before that some people don't allow WWW users to post at all even after they are not new (which I don't want to do). I currently have it set where all new users cannot post (or even see the message areas) by setting one new user level that is lower than the access level for all the areas.

Is there a way to set the new-user access level for WWW new users to a lower value than the others, or restrict their posting abilities while they are "new"?

I checked the wiki and the docs but couldn't find what I was looking for.

Thanks!

---
■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Prevent New Web users from posting
By: Dumas Walker to All on Fri Dec 30 2022 10:44 am

I am trying to figure out how, or if there is a way, to restrict only New and WWW (i.e. they meet both requirements) from being able to post in message areas until they are upgraded. I was hoping to figure out that maybe I could set the new user level for those users to a separate value than for telnet/SSH/etc. users.

Better yet, just check the protocol in the posting requirements string:
LEVEL <upgraded> OR PROT != HTTP*

Where <upgraded> is your upgraded-user level. That should do what you're wanting. "HTTP*" should match either "HTTP" or "HTTPS".

I have read here before that some people don't allow WWW users to post at all even after they are not new (which I don't want to do). I currently have it set where all new users cannot post (or even see the message areas) by setting one new user level that is lower than the access level for all the areas.

Is there a way to set the new-user access level for WWW new users to a lower value than the others, or restrict their posting abilities while they are "new"?

I checked the wiki and the docs but couldn't find what I was looking for.

https://wiki.synchro.net/access:requirements
--
digital man (rob)

Rush quote #28:
The future pre-decided, detached and subdivided in the mass production zone Norco, CA WX: 55.5°F, 86.0% humidity, 0 mph E wind, 0.00 inches rain/24hrs

I am trying to figure out how, or if there is a way, to restrict only New and WWW (i.e. they meet both requirements) from being able to post in message areas until they are upgraded. I was hoping to figure out that maybe I could set the new user level for those users to a separate value than for telnet/SSH/etc. users.

Better yet, just check the protocol in the posting requirements string:
LEVEL <upgraded> OR PROT != HTTP*

Where <upgraded> is your upgraded-user level. That should do what you're

anti

. "HTTP*" should match either "HTTP" or "HTTPS".

I don't this fixes it, unless I am misunderstanding the condition
statement.

I want to limit *only* *new* web users from being able to post until they are upgraded. I think your way would still limit everyone until they are
upgraded (first half of statement satisfied), but would never allow web users to post (second half satisfied), which is what I am trying to avoid.

I think that would require something like this:

IF PROT = HTTP*
LEVEL <upgraded WWW>
ELSE
LEVEL <that it used to be before WWW spammer problems>
END-IF

I think I can phrase that in a synchronet conditional statement like this:

LEVEL <upgraded WWW> OR (LEVEL <something lower> AND PROT != HTTP*)

From the wiki page, Nested example 2, it does look like I can nest
statements that way, and SCFG (under linux) will just BARELY let me get
that typed in. :)

Now, is there a way to set that globally for all message areas? I thought
I could set a global requirement under SCFG -> Message Options but I
don't see it there.

Thanks!


* SLMR 2.1a * Basic Flying Rule #1: Keep the pointy end forward.

---
■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Prevent New Web users fro
By: Dumas Walker to DIGITAL MAN on Sat Dec 31 2022 11:04 am

I am trying to figure out how, or if there is a way, to restrict only New and WWW (i.e. they meet both requirements) from being able to post in message areas until they are upgraded. I was hoping to figure out that maybe I could set the new user level for those users to a separate value than for telnet/SSH/etc. users.

Better yet, just check the protocol in the posting requirements string:
LEVEL <upgraded> OR PROT != HTTP*

Where <upgraded> is your upgraded-user level. That should do what you're

anti

. "HTTP*" should match either "HTTP" or "HTTPS".

I don't this fixes it, unless I am misunderstanding the condition
statement.

I want to limit *only* *new* web users from being able to post until they are upgraded. I think your way would still limit everyone until they are upgraded (first half of statement satisfied), but would never allow web users to post (second half satisfied), which is what I am trying to avoid.

That's exactly what the requirements string I provided does:

Security level must be greater than or equal to the <upgraded> level, OR
their protocol must not be HTTP*. If their protocol is not HTTP*, then the security level doesn't matter.

I think that would require something like this:

IF PROT = HTTP*
LEVEL <upgraded WWW>
ELSE
LEVEL <that it used to be before WWW spammer problems>
END-IF

Nope.

I think I can phrase that in a synchronet conditional statement like this:

LEVEL <upgraded WWW> OR (LEVEL <something lower> AND PROT != HTTP*)

From the wiki page, Nested example 2, it does look like I can nest statements that way, and SCFG (under linux) will just BARELY let me get
that typed in. :)

You don't need a nested example because there are only 2 conditions.

Now, is there a way to set that globally for all message areas?

If you're running v3.20a, doing a search/replace of the "post_ars" key values should be easy with most text editors.

I thought
I could set a global requirement under SCFG -> Message Options but I
don't see it there.

No, the closest thing is the template sub-board that you clone to the rest of the message group with a single operation in SCFG.

Also, ecWeb supports its own set of newuser values: https://wiki.synchro.net/config:webv4#new_user_values

So you could just give new users via web the 'P' restriction and then remove it when they're validated.
--
digital man (rob)

Synchronet/BBS Terminology Definition #85:
TTY = Teletype (dumb terminal)
Norco, CA WX: 56.5°F, 95.0% humidity, 0 mph E wind, 0.04 inches rain/24hrs

That's exactly what the requirements string I provided does:

Security level must be greater than or equal to the <upgraded> level, OR their protocol must not be HTTP*. If their protocol is not HTTP*, then the

ec

ity level doesn't matter.

If the default new user level is 50, and I don't want anyone under 50 to be able to post, then it does matter.

Now, is there a way to set that globally for all message areas?

If you're running v3.20a, doing a search/replace of the "post_ars" key values ould be easy with most text editors.

I am running 3.19 for now. Will keep this in mind when I upgrade. For reference, what text file would I be doing a search/replace on?


* SLMR 2.1a * The 4 major food groups: fast, frozen, junk, & spoiled.

---
■ Synchronet ■ CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP

Re: Prevent New Web users fro
By: Dumas Walker to DIGITAL MAN on Sun Jan 01 2023 10:09 am

That's exactly what the requirements string I provided does:

Security level must be greater than or equal to the <upgraded> level, OR their protocol must not be HTTP*. If their protocol is not HTTP*, then the

ec

ity level doesn't matter.

If the default new user level is 50, and I don't want anyone under 50 to be able to post, then it does matter.

If the default level is 50, and you don't want the user to post, give the user the 'P' restriction.

Now, is there a way to set that globally for all message areas?

If you're running v3.20a, doing a search/replace of the "post_ars" key values ould be easy with most text editors.

I am running 3.19 for now. Will keep this in mind when I upgrade. For reference, what text file would I be doing a search/replace on?

ctrl/msgs.ini
--
digital man (rob)

Sling Blade quote #23:
Karl: I reckon I'm gonna have to get used to looking at pretty people.
Norco, CA WX: 52.9°F, 95.0% humidity, 0 mph ENE wind, 0.12 inches rain/24hrs