Date   

moderated Re: NC Status Clarification #bug

 

On Mon, May 11, 2020 at 07:14 PM, Shal Farley wrote:
I think that's it: easier to create the account on the spot so that the user can go ahead with filling in their options & profile while they wait for the confirmation to arrive.
I think that it is more literally because it's a placeholder in the sense that creating the account a priori prevents anyone else from signing up with the same email address while it's in process.

It behaves like it is perfectly real
That's a matter of definition. There are things it does do and things it doesn't do. I think the word "real" is meaningless.
 
--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu


moderated Re: NC Status Clarification #bug

 

J,

I would think of these NC “accounts” as placeholders.
That's a reasonable view.

It’s probably just easier for Mark to create an “account” before the
dust has settled, but it’s not a “real” account yet.
I think that's it: easier to create the account on the spot so that the user can go ahead with filling in their options & profile while they wait for the confirmation to arrive.

It behaves like it is perfectly real, in much the same way that a Bouncing (or Bounced) account is still real, but can't receive group postings by email until the NC status is cleared.

Shal


moderated Re: NC Status Clarification #bug

 

John,

It shows that an account with an incorrect email address is created
and changed without being admitted to the group or being confirmed.
It's still in NC and pending emails to both addresses bounced.
That's because NC only refers to whether the user has confirmed the email address that they typed into the Sign-up page. It has nothing to do with their activity on the web.*

Shal
*Perhaps except as later clarified by Mark concerning group creation.


moderated Re: Email only footer for users without http/s access #suggestion

Bruce Bowman
 

On Mon, May 11, 2020 at 08:50 PM, Peter Mott wrote:
The group is already set to Plain Text Only in the message formatting block, but message footers still contain clickable hyperlinks to http pages.
By definition, the plain text messages sent by groups.io cannot contain hyperlinks. If recipient's email client sees a link address and converts it to a hyperlink, that's another matter...but that behavior is not in groups.io's control.

Regards,
Bruce


moderated Re: Email only footer for users without http/s access #suggestion

Peter Mott <peter@...>
 

Hi Bruce,

The group is already set to Plain Text Only in the message formatting block, but message footers still contain clickable hyperlinks to http pages.

regards

Peter


moderated "Subscriber was removed for marking a message as spam" notification #suggestion

Bruce Bowman
 

It would be useful of the notification sent to the +owner address when someone is unsubbed for this reason contained the same "resume subscription" link that was originally sent to the affected member. That way, if he panicked and deleted the resume message, I could forward him the notification I received and help get him back into the group that way.

More generally, we need some way that a group Owner can resend that link to the [ex-]member. Seven days of expiration does not help if the one and only message sent to him is irretrievably lost.

Thanks for your consideration,
Bruce


moderated Re: NC Status Clarification #bug

Duane
 

On Mon, May 11, 2020 at 02:39 PM, Mark Fletcher wrote:
I've changed the text from 'Logged in:' to 'They accessed the web from:'.
Typo sneaked in, forgot the 'y' in They (or a bug ate it?).

Thanks much,
Duane


moderated Re: NC Status Clarification #bug

 

On Sun, May 10, 2020 at 6:42 PM J_Catlady <j.olivia.catlady@...> wrote:
I think the problem is semantics. The language used for NC members is that they "don't yet have an account." That should read "don't yet have a confirmed account." I don't know all the places that language exists, but it floats around here and there and should probably be clarified.


If you see any instances of this on the web or in notifications, please let me know and I'll clarify.

Thanks,
Mark 


moderated Re: NC Status Clarification #bug

 

On Mon, May 11, 2020 at 4:14 AM Duane <txpigeon@...> wrote:

It should more correctly be labeled something like "Accessing the web from". 

I've changed the text from 'Logged in:' to 'They accessed the web from:'.

Thanks,
Mark 


moderated Re: NC Status Clarification #bug

 

On Mon, May 11, 2020 at 1:38 AM Andy Wedge <andy_wedge@...> wrote:

So, an account that Groups.io has not received confirmation from is allowed to create groups?  Interesting. I'm not sure I see the logic of allowing that.

Not true. Only confirmed users can create groups.

Thanks,
Mark 


moderated Re: Redirect on Google login omits subdomain #bug #fixed

RFS
 

Confirmed...working now.

Thanks!


moderated Re: Redirect on Google login omits subdomain #bug #fixed

 

On Sun, May 10, 2020 at 7:56 PM RFS <rschend@...> wrote:
My 2 yr old group has a single subdomain, which was added last year. I don't know if the start of this issue coincides with that or not.

When trying to navigate directly to a message thread (like clicking on the View/Reply Online footer link in a message email notification), if I'm not already logged in, it works fine. But if I'm not already logged in, I'm prompted to do so. Upon logging in via Google, Groups redirects back to the message, but drops the subdomain from the URL, resulting in the "Sorry, but that group does not exist" error.

This should be fixed now.

Thanks,
Mark 


moderated Re: NC Status Clarification #bug

 

I would think of these NC “accounts” as placeholders. It’s probably just easier for Mark to create an “account” before the dust has settled, but it’s not a “real” account yet.


On May 11, 2020, at 9:11 AM, John Pearce <jponsalt@...> wrote:

Funny this application for membership happened just today.  It shows that an account with an incorrect email address is created and changed without being admitted to the group or being confirmed.  It's still in NC and pending emails to both addresses bounced.

Message
Pending subscription notice: Pending Subscription
Attempted
9:06am
Response
MX lookup returned: lookup gtempaccount.com on 173.255.241.5:53: no such host

--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu


moderated Re: NC Status Clarification #bug

John Pearce
 

Funny this application for membership happened just today.  It shows that an account with an incorrect email address is created and changed without being admitted to the group or being confirmed.  It's still in NC and pending emails to both addresses bounced.

Message
Pending subscription notice: Pending Subscription
Attempted
9:06am
Response
MX lookup returned: lookup gtempaccount.com on 173.255.241.5:53: no such host


moderated Re: Redirect on Google login omits subdomain #bug #fixed

RFS
 

Small typo above...

When trying to navigate directly to a message thread ... if I AM already logged in, it works fine. 

Thanks.


moderated Re: NC Status Clarification #bug

 

Yes, agree with Duane, I just replied before seeing this. It’s nothing to do with their “account” being logged into groups.io as an account.


On May 11, 2020, at 4:14 AM, Duane <txpigeon@...> wrote:

On Mon, May 11, 2020 at 05:56 AM, Chris Jones wrote:
what purpose is served by "Logged in" appearing in any membership application? It would seem to be (at best) irrelevant.
It should more correctly be labeled something like "Accessing the web from".  It was this information, a couple of months ago, that allowed group owners to determine that there were unscrupulous characters attempting to join a large number of groups.  When a group is mainly for local people, it makes no sense when someone from Timbuktu, Mali attempts to join a group in Aberdeen, Scotland.  This bit of information is a tool that group owners can use in their arsenal against the 'bad guys'.  It's not perfect since it only applies to those that are online when applying for membership, but every little bit helps.

Duane

--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu


moderated Re: NC Status Clarification #bug

 

I think the term “logged in” might be somewhat loose as well. I think (of course Mark would have to confirm - no double entendre intended) that the notification text is really just talking about where and how they’re accessing the site, “logged in” or not. I still suspect it’s really just talking about how they’re logged into the internet.


On May 11, 2020, at 3:56 AM, Chris Jones via groups.io <chrisjones12@...> wrote:

On Mon, May 11, 2020 at 02:42 AM, J_Catlady wrote:
I think the problem is semantics.
You might well be right! :)


The language used for NC members is that they "don't yet have an account." That should read "don't yet have a confirmed account."
That makes sense. However, what purpose is served by "Logged in" appearing in any membership application? It would seem to be (at best) irrelevant.

Chris

--
J

Messages are the sole opinion of the author, especially the fishy ones.
My humanity is bound up in yours, for we can only be human together. - Desmond Tutu


moderated Re: Email only footer for users without http/s access #suggestion

Bruce Bowman
 

On Tue, May 5, 2020 at 11:00 PM, Peter Mott wrote:
Please consider adding an optional system footer that does not contain any http/s links for members who are connected to the Internet over slow speed HF radio or satellite links and are only able to send and receive email.
Peter -- Set your group to Plain Text Only (Message Formatting block) and no clickable hyperlinks will be sent.

Regards,
Bruce


moderated Re: NC Status Clarification #bug

Duane
 

On Mon, May 11, 2020 at 05:56 AM, Chris Jones wrote:
what purpose is served by "Logged in" appearing in any membership application? It would seem to be (at best) irrelevant.
It should more correctly be labeled something like "Accessing the web from".  It was this information, a couple of months ago, that allowed group owners to determine that there were unscrupulous characters attempting to join a large number of groups.  When a group is mainly for local people, it makes no sense when someone from Timbuktu, Mali attempts to join a group in Aberdeen, Scotland.  This bit of information is a tool that group owners can use in their arsenal against the 'bad guys'.  It's not perfect since it only applies to those that are online when applying for membership, but every little bit helps.

Duane


moderated Re: NC Status Clarification #bug

Chris Jones
 

On Mon, May 11, 2020 at 02:42 AM, J_Catlady wrote:
I think the problem is semantics.
You might well be right! :)


The language used for NC members is that they "don't yet have an account." That should read "don't yet have a confirmed account."
That makes sense. However, what purpose is served by "Logged in" appearing in any membership application? It would seem to be (at best) irrelevant.

Chris