Hi Mark,
Is this perhaps due to some code checking regarding email addresses pushed
recently?
Cheers,
Joseph

Good morning.

The question is in the subject. Again, why are we seeing our own email address next to the unsubscribe link? This is located in the footer of all emails sent to a Groups.io list. Surely we have a privacy/security vulnerability issue here. And, I don't mean to burst any bubbles here, but in the EU new laws on data protection took effect as of Friday 25 May 2018. In brief, all businesses, regardless of size, must now explicitly receive permission from their customers regarding any form of personal data. You can find out more on the General Data Protection Regulation, or GDPR, around the web.

Thank you very much. I hope Mark looks into this sooner rather than later, before something bad happens.

Kind regards Chris

So, what should the subject tag be? Should I strip it out from
incoming messages, so that it'll only appear on messages that
are special?

I would prefer [SpecialMessage], [Special], or [SpecialNotice].
[SpecialNotice] might be best, but I'm wondering if there might be
times when a message with a Special Notice type hashtag would
be sent where the hashtag would be of more importance. How
much extra work would it be to have a predefined tag, such as
[Special] that could be changed by the group owner? BTW, I'd
have this new tag placed just after the group tag.

I think stripping it would only be of importance if it were on an
unrelated message, not on replies.

I agree with Duane. If someone really needs something added because they can't do it themselves for some reason, it needs to be a marking in the header. I'm against a hashtag if it's mandatory. My groups don't use hashtags and I don't want to confuse people with them. Personally I find hashtags a clutter that makes the subject harder to understand.

When I send an Administrative message out I start the message title with =[ADMIN]=. When I need to send out a special notice, I start the title with =[Special Notice]= and select the Special Notice option. I find that an equal sign framing the brackets helps it to stand out, and titles are like advertising - you get one shot at catching their eye and it may only be three seconds.

I also strongly believe replies to a Special Notice should not be treated like a Special Notice by the system. People select 'Special Notices Only' for a reason and that should be respected. If the reader is interested, they will go to the web page or contact others for more information.

Dano

How about  #admin as well. I use that  to indicate  if I want the list to take notice especially in the middle of a thread if it starts to drift or what not.

On Mon, Jun 11, 2018 at 10:18 am, Mark Fletcher wrote:

So, what should the subject tag be? Should I strip it out from incoming messages, so that it'll only appear on messages that are special?

I would prefer [SpecialMessage], [Special], or [SpecialNotice].  [SpecialNotice] might be best, but I'm wondering if there might be times when a message with a Special Notice type hashtag would be sent where the hashtag would be of more importance.  How much extra work would it be to have a predefined tag, such as [Special] that could be changed by the group owner?  BTW, I'd have this new tag placed just after the group tag.

I think stripping it would only be of importance if it were on an unrelated message, not on replies.

Duane

On Tue, Jun 12, 2018 at 04:41 am, Linda wrote:

I use the link from the html digest when I want to hit the Like button, which saves an empty draft.
It would be better if a draft wasn't saved when the user hasn't input anything.

I prefer to highlight a section of text and then hit the reply button to quote it. This is much easier than hitting the quote bubble icon and then editing out all the fluff.

With the message composition box already open, I have to hit Discard first whether I eventually reply or not. 

It would be better if the link simply took me to the message and let me decide what to do from there. 

Bruce

Hi Mark, you wrote

Hi Mark,
Please use #specialnotice.
We're already doing it that way and having it stripped would work perfectly.
Thanks,
Linda

After the Y!G transfert I have lot of message with problem of line break.

Can I find a speed solution for format the message.

Possibility to don't add "edited" when I wrote to reason is a problem of line break?

Two suggestions that would make hashtags more user-friendly.

1) Auto-fill for #hashtags that already exist. This would be faster than scrolling down a long list to click on a hashtag that you know is already there.....

2) When I look at my group's list of hashtags, there are big text boxes with a lot of empty space inside. So my hashtags roll over onto a second page. Smaller text boxes would allow all of our hashtags to fit onto one page, which would be very nice. Or perhaps a similar list rather than the big text boxes.

Thanks!
Deb (a new manager - just learning!)

Hi John,
This digest problem prevented our move to groups.io.
Short answer to the problem: turn on the auto sig block for everyone (or if you have 10,000 users you may need to get them to, I'm not sure there is a bulk option for this), for both web _and_ email replies, and put in a standard message, e.g. "this line added for digest context quoting" or hopefully something catchier :)
This should solve all problems apart from some email systems (we had one problem with Outlook and one with the Gmail app--but not gmail on the webpage) and those who use the web interface and top post. These latter will need to quote and then post their reply below.
Hope this helps (it was some time ago I looked at this). I'd be interested in feedback as to how this works for you.
Best,
--
Paul Fraser

On Mon, Jun 11, 2018 at 06:25 am, John Russell wrote:

Now comes the big problem. The Digest users keep saying where are the 3 dots
you keep mentioning and why can't I click on 3 dots and see the included text?
Where is the context to this reply, and accusing members of not including
context. Some of the website users were reminding their fellow website users
to use the 3 dots to see the included text. The digest users were very unhappy
as they could not see the context from any of the users (whatever the delivery
method) and were confused about which reply belonged to which previous
message. I (the owner of the group) did not realise until last week (even
though we moved in February), that the Digest removed all the quoted text.
This is a big problem for our Digest users and I would like to go back to
having this text included.

Have you seen the previous messages in this thread? Groups.io does not remove *all* quoted text, it removes the quoted text under the last unindented line. All people who want the quote to stay have to do is type anything UNDER IT.

What I am thinking is that I would propose (in the Beta group) that an option
be added to the settings, so that you can have the included text trimmed or
not.

For all intents and purposes, we already have that. Like I just said. And no, I don't consider telling people to put something at the bottom of their messages to be "the tail wagging the dog". It has been proper netiquette in email and usenet for years

owners or moderators can switch off the trimming of included
text, of course, at the risk of too much being included (chains of included
emails).

I don't think it would be a big deal to implement such an option. Would there
be any objections to me making such a suggestion?

Apart from requiring some science-fiction-type artificial intelligence to be smart enough to know what to trim and what not?
Or digests becoming undigestable because people are too lazy to trim messages (or were even TAUGHT not to) ?

If it were up to me (which it isn't), autotrim would be the norm even for non-digest messages

groetjes, Ronaldo

groetjes, Ronaldo

The only thing about "Unsubscribe" versus "Leave" is that someone might think "Unsubscribe" will turn off the mail messages without leaving the group. How about both?

Unsubscribe (Leave Group): link_here

JohnF

Today I was setting up a client to join the JAWS for Windows group on Groups.io.  The various status messages that came during that process were a mixture of "groups.io" alone after the at sign in the e-mail and "jfw.groups.io."

I had set up a filter so that messages from "jfw.groups.io" would be sorted into a dedicated folder and had expected that all correspondence related to this group, e.g., the response to an e-mail addressed to help@jfw.groups.io, would come back from jfw.groups.io, but it comes back from groups.io "naked."

It would make sense to make the e-mail output for actual groups at Groups.io use the "three-part" structure after the at sign while things from Groups.io above the level of individual groups use the "naked" groups.io after the at sign.

--

Brian - Windows 10 Home, 64-Bit, Version 1803, Build 17134 
     Explanations exist; they have existed for all time; there is always a well-known solution to every human problem — neat, plausible, and wrong.

          ~ H.L. Mencken, AKA The Sage of Baltimore

Wahoo! Thanks so so much! You guys rock. Thanks for taking care of this as quickly as possible.

Well I also put the  announcement on my twitter, someone already let them know on my behalf. And such  so it worked out fine.