Date   

moderated Re: "Was removed via email" versus "reported ... via email and was removed" #suggestion

KWKloeber
 

I’m confused.  How else would a message be reported as being spam?  Other than an email having been deleted from a spam folder?
Why is “via email” in there at all, no less needing to be parsed differently?


moderated Re: #bug Italics and other rich text formatting don't transfer to or from text files #bug

Kamaloo <k_amaloo@...>
 

Hello again!

I checked with pasting directly into the web interface from a Wordpad .rtf file, but the formatting was not preserved.


moderated Re: Unable to set web notifications in Firefox mobile #bug

Andy Wedge
 

On Thu, Jan 21, 2021 at 05:21 PM, Andy Wedge wrote:
I can no longer set notifications on Firefox mobile on my Android phone.
Trying to give this a nudge. I cannot set notifications on Chrome mobile either now.

Thanks
Andy


moderated Re: #bug Italics and other rich text formatting don't transfer to or from text files #bug

Kamaloo <k_amaloo@...>
 

Thank you for your fast reply!

I'll admit I haven't tried this extensively with Word - I mainly use Wordpad RTF files. I did check under Admin->Settings->Message Formatting that plain text hasn't been forced, but it hasn't.

On further thought, it may be that pasting directly to the web interface works - I'll have to test it again (I often use reply from email, in which case the email must be the problem then). But copying the formatting from the web interface to a Wordpad file, which is what I always do to prepare my replies, still doesn't copy the formatting. Could this be an issue of compatibility with Wordpad, somehow? Rich text shouldn't be a problem, should it?

Thanks!


moderated Re: #bug Italics and other rich text formatting don't transfer to or from text files #bug

 

But the post is about text docs, not Word docs.
--
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: #bug Italics and other rich text formatting don't transfer to or from text files #bug

 

I am constantly advising my group members not to copy/paste Word docs. The most noticeable problem is the extra line spaces that are added.
--
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: #bug Italics and other rich text formatting don't transfer to or from text files #bug

Andy
 

It works when I did a copy-and-paste.  The formatting was preserved, when copying from a Word document into a Groups.io post written in its web interface.  There are many variations possible, maybe you need to be more specific?  An example:

This is plain text.

This is italicized.

This is bold.  This is bold underlined.

This is a bulleted list:

·         Item 1

·         Item 2

·         Item 3


OK, so the bulleted list did not copy correctly.  But italics and bold and underlining did.  I wonder if the group you tried this with enforces plain-text only?

Andy


moderated Re: "Was removed via email" versus "reported ... via email and was removed" #suggestion

 

And of course, the same goes for “via web.”


On Apr 17, 2021, at 2:12 PM, J_Catlady via groups.io <j.olivia.catlady@...> wrote:

The “via email” thing is the same problem with every single action in the logs. I’m used to it. One solution might be to simply add a dash before “via email” in every case. Not beautiful parsing but at least separates “via email” from the rest. Another solution would be to put the “via email” with a colon (or something) BEFORE the rest of it. A third solution is to just get used to it. It stopped bothering me long ago. My brain now adds the separator.


On Apr 17, 2021, at 1:19 PM, Andy <AI.egrps+io@...> wrote:

When someone reports a message as spam and they are removed from a group for that reason, the entry in the Activity log says:

<email address> reported a message as spam and was removed via email
or
<email address> reported message #128643 as spam and was removed via email

Shouldn't it say that the individual reported the message as spam via email, and was removed?  As far as I know, they were not removed via email.

Thanks,
Andy

--
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


--
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: "Was removed via email" versus "reported ... via email and was removed" #suggestion

 

The “via email” thing is the same problem with every single action in the logs. I’m used to it. One solution might be to simply add a dash before “via email” in every case. Not beautiful parsing but at least separates “via email” from the rest. Another solution would be to put the “via email” with a colon (or something) BEFORE the rest of it. A third solution is to just get used to it. It stopped bothering me long ago. My brain now adds the separator.


On Apr 17, 2021, at 1:19 PM, Andy <AI.egrps+io@...> wrote:

When someone reports a message as spam and they are removed from a group for that reason, the entry in the Activity log says:

<email address> reported a message as spam and was removed via email
or
<email address> reported message #128643 as spam and was removed via email

Shouldn't it say that the individual reported the message as spam via email, and was removed?  As far as I know, they were not removed via email.

Thanks,
Andy

--
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 "Was removed via email" versus "reported ... via email and was removed" #suggestion

Andy
 

When someone reports a message as spam and they are removed from a group for that reason, the entry in the Activity log says:

<email address> reported a message as spam and was removed via email
or
<email address> reported message #128643 as spam and was removed via email

Shouldn't it say that the individual reported the message as spam via email, and was removed?  As far as I know, they were not removed via email.

Thanks,
Andy


moderated #bug Italics and other rich text formatting don't transfer to or from text files #bug

Kamaloo <k_amaloo@...>
 

Hello!

I have a minor request/bug report - would it be possible for rich text formatting such as bolding, italics and similar to be transferable when you select and copy text, or when you paste it in a post when it has been copied from a document? I know it's possible, because Yahoo Groups did it, but I haven't been able to replicate it on my groups. It's a bit tedious to go through pasted text to find and re-insert the formatting, so I hope it can be implemented in groups.io.

This is the main way I use the groups, so I hope something can be done!

TLDR; - text copied from a post on groups.io to a RTF or Word document doesn't retain the formatting information. Text copied from a RTF or Word document to a post on groups.io doesn't retain the formatting information. Is it possible to fix this?

Thanks!
 - Kamaloo


moderated Re: Site updates #changelog

Donald Hellen
 

Mark . . .

On Fri, 16 Apr 2021 21:18:32 -0700, "Mark Fletcher"
<markf@corp.groups.io> wrote:

CHANGE: Changed invite link expiry to 14 days.

Thanks for making it 14 days. I should think most people check their
email at least once a week. :-)


Donald


----------------------------------------------------
Some ham radio groups you may be interested in:
https://groups.io/g/ICOM https://groups.io/g/Ham-Antennas
https://groups.io/g/HamRadioHelp https://groups.io/g/Baofeng
https://groups.io/g/CHIRP https://rf-amplifiers.groups.io/g/main


moderated Site updates #changelog

 

Changes to the site this week:

April 16, 2021:

  • DOCS: Updates from Nina.
  • NEW: We now support Single Sign On from YourMembership, for Enterprise groups.
  • CHANGE: Changed invite link expiry to 14 days.
  • INTERNAL: Upgraded the kernel on the other replica database machine to see if it helped reduce the unexplained freezes we're seeing.

April 15, 2021:

  • CHANGE: Invite links now expire after 24 hours. We no longer delete old invitations after 14 days.
  • INTERNAL: Converted the add event page to quicktemplate.
  • INTERNAL: Improvements to the admin dashboard involving spammer detection.

April 13, 2021:

  • NEW: Delete invites that haven't been accepted that are older than 14 days (rolled back on the 15th).
  • CHANGE: If you click on an invite link and are logged in under a different account, we now display an error message instead of automatically logging you out.
  • BUGFIX: In Full Digests, we would display the Attachments line under a message even if all the attachments were inline images.
  • BUGFIX: In some instances, hashtag footers were not showing up in digests.
  • INTERNAL: Upgraded the kernel on one of the replica database machines to see if it helped reduce the unexplained freezes we're seeing.

April 12, 2021:

  • BUGFIX: When converting plain text emails to HTML that contain links with query parameters, we were only linkifying the part of the URL up until the second query parameter.

Take care everyone.

Mark


moderated Re: Cannot remove member #bug

Bruce Bowman
 

On Fri, Apr 16, 2021 at 06:14 PM, Mark Fletcher wrote:
That member is the sole owner of the `thisone` subgroup. Removing them from the parent group would remove them from all subgroups.
 
Yep, that error message should be improved.
Hm. On further thought: 

Should this even be an error? In the absence of a subgroup Owner, can't the Owner of the main group promote someone?

Regards,
Bruce


moderated Re: Cannot remove member #bug

Bruce Bowman
 

On Fri, Apr 16, 2021 at 06:14 PM, Mark Fletcher wrote:
That member is the sole owner of the `thisone` subgroup. Removing them from the parent group would remove them from all subgroups.
Ah. I forgot it even had a subgroup.

We had a similar inquiry in GMF a few months back. Filing this one away for future reference!

Thanks,
Bruce


moderated Re: Cannot remove member #bug

 

On Fri, Apr 16, 2021 at 2:49 PM Bruce Bowman <bruce.bowman@...> wrote:
Mark -- The system is keeping me from removing a Member because they are the "sole Owner of the group" (even though they aren't). See screenshots.

That member is the sole owner of the `thisone` subgroup. Removing them from the parent group would remove them from all subgroups.

Yep, that error message should be improved.

Thanks,
Mark


moderated Cannot remove member #bug

Bruce Bowman
 

Mark -- The system is keeping me from removing a Member because they are the "sole Owner of the group" (even though they aren't). See screenshots.

I don't think it's an artifact of the new member filter. If I open that first member record and click the Remove button, the same thing happens. The fact that there's only two total people in this group may be a factor.

FYI,
Bruce




moderated Re: Expire invitations after 14 days #suggestion

 

I fully agree Jeremy. In this case I also cannot see what the security problem
is which is supposed to be being solved. Only the invitee receives it, and even
if they ask for trouble by forwarding it to someone else, responding to it only
results in acceptance of the invitation by the original invitee. I don't see
how it can give access to his/her account or to the system to anyone else. It
isn't like a login link, which could do that.

Jim Fisher

On 16 Apr 2021 at 5:19, Jeremy H via groups.io wrote:

While having invites last, unexpired, for ever is not desirable, having them
expire after only 24 hours goes far too far to the other extreme. As others have
said, many people - not just the less tech inclined - do not look at, or respond
to e-mails every day - and it is unreasonable to expect them to do so. Nor is an
invitation to join a group the sort of thing necessarily calling for an instant
response.

So I would regard 14 days as a minimum, before they expire. And when they do, I
would suggest that their status be changed to expired (or something like it).

Nor I do not think there should any subsequent automatic deletion (or at lest,
not for years); rather they should stay (and able to be resent) until manually
cleaned up (and a deletion tool to assist this, based on status and time, would
be very useful),

Jeremy

On Thu, Apr 15, 2021 at 09:53 PM, Mark Fletcher wrote:


Hi All,

I've made the following changes:

- We no longer will delete invites after 14 days.
- Invite links will expire 24 hours after the invite has been sent. That
means clicking the link or replying to the invite email will no longer
work, and you'll get an error message instead.

Please let me know if you have any questions.

Thanks,
Mark















moderated Re: Expire invitations after 14 days #suggestion

Ginger Iorizzo
 

Thank you!  
Could I ask that the list of sent invitations remains with some sort of indication that the invitation is expired?
That way, if an owner wants to resend after the 14 days, all the info is still there. 
Thanks for all you do!
Ginger


On Apr 16, 2021, at 1:35 PM, Mark Fletcher <markf@corp.groups.io> wrote:


Hi All,

I've changed the invite link expiry to 14 days.

Cheers,
Mark


moderated Re: Expire invitations after 14 days #suggestion

 

Hi All,

I've changed the invite link expiry to 14 days.

Cheers,
Mark

1181 - 1200 of 30082