If you did it more often you'd quickly get used to it. This is one of those things that people learn the first time around. But it could benefit from some user documentation for sure. --

I remember arguing the same as Noel when the feature first came into being. I wanted people to be able to (i.e., have to) click "private" before even composing their reply. The thread is probably

Funny, I hardly ever use the web interface to send messages, but I happened to try yesterday and I could not figure out how to Reply to Sender. I didn't even notice the "Private" button, LOL. I

And not only the one from the top of Topics and Hashtags views. I was once taken to my list of topics (i.e.,in all groups), which I had not visited in recent, or even semi-recent, memory, after

Thanks, me too! In all honesty, it's not a high-priority item. More of a "it would be nice" thing, esp. since seems easy to do. -- J Messages are the sole opinion of the author, especially the

Hi Shal This is probably worth it's own separate thread, but I think it's more useful if I see how it all feels in a week. As with any interface change/IOS change/ phone change - it may be that in a

I disagree re: obscurity. I think the reply interface was updated (2016?) to the current layout for replies. We have had very few accidental group replies as a result of the layout. I think it helps

Just as a data point, I have not noticed any odd behavior. If I click on the "Your Groups" navigation tab ( second from top) on the left hand side of desktop browser view when on https://groups.io I

But unfortunately not the - presumably related - issue of the 'Your Groups' link at the top of Topics and Hashtags views, which now seems to have rather random effects as to where you go: I suspect it

For what it is worth, I had an identical error a couple of weeks ago using 1&1 SMTP (any groups.io address), occurred suddenly but now seems to have been cured while doing nothing my end. While it was

Noel, I agree that grey, which usually signifies a control that is not available (doesn't "click"), is a very poor choice for a button that is actually intended to be used. It was once that way. The

J, I find the UI design aspects interesting. The challenge (for Mark, ultimately) is to let the user ask for the result you want, within the style of the site and, hopefully, leveraging existing

Totally, which was I was flummoxed by your mentioning it. :-) -- 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

J, ♫ Because you know I'm all about that look, 'Bout that look, no coding I only worry about implementation if the suggestion seems challenging, but this one seems fairly pedestrian. Shal

Maria, Interesting idea. One possibility would be to make it the top entry in the Your Groups drop-list. That's still two clicks though. I don't think I want it below the Logo bar when visiting a

I'm late on this. I see the inconvenience mentioned by Charlie and Gina, but we were enjoying that cal-invite automatically checked on. After the default was changed to that we just adjusted by

Hi All, I have changed it back to not being checked by default. Thanks, Mark

I want to add my voice also as being unhappy with this change to set the 'Send Invite To Group' default to 'Checked'. In my case I was creating two place holder calendar entries that got sent to my

Furthermore, this group is for enhancements to groups.io. Not for support questions.

The essence of the error is contained in these sections of the message: This part is the text explanation: --1553608364-eximdsn-1711883849 Content-type: text/plain; charset=us-ascii This message was