Date   
moderated Re: GIO in the long term

Bob Bellizzi
 

You  replied to an old thread and I fail to understand what "like to be ahead on this issue" actually means to you.

--

Bob Bellizzi

moderated Re: GIO in the long term

John Wirtz SF
 

Well I am already a premium customer and though I am in favour of paying for the service as long as visible support exists, I think it would be slicker with an integrated tables facilities.

 

The main reason for our organisation to go for this kind of group is that it delivers message direct to the member’s inbox.  And all members have the option to respond for all to see.  I like this type of openness and we’ve had a group for nearly twenty years and only a very small handful of behaviour issues.  AND ONE CAN KEEP IT PRIVATE.

 

But, I have more pressing things to do than maintain my messaging system beyond the essential matters.  So, easing routine maintenance task such as member management would be very welcome.

 

Cheers

 

John Wirtz

 

 

 

From: main@beta.groups.io <main@beta.groups.io> On Behalf Of SP4149
Sent: 01 April 2020 20:19
To: main@beta.groups.io
Subject: Re: [beta] GIO in the long term

 

Last fall it was mentioned that large lists would have to upgrade to Premium, based on the number of subscribers.  Then the issue was suspended during the YG meltdown.
I have several lists considering upgrades to Premium.  I would like to be ahead on this issue, avoiding an "Oh, by the way" surprise.

ken

moderated Re: GIO in the long term

SP4149
 

Last fall it was mentioned that large lists would have to upgrade to Premium, based on the number of subscribers.  Then the issue was suspended during the YG meltdown.
I have several lists considering upgrades to Premium.  I would like to be ahead on this issue, avoiding an "Oh, by the way" surprise.

ken

Re: Markdown Support #suggestion

Bill Costa
 

I think it probably makes sense to convert those messages to HTML before sending them out to the group

Yes!

This would definitely be a niche thing...

Too true, unfortunately. So pretty low on the scale of things to do I'm sure.

I'm not sure it's even possible to force Gmail and the other web-based clients to send out just a plain text email anymore.

Still can with Gmail and Outlook. But those days may be numbered! sigh.

Markdown has become the preferred format for many geeks, particularly those still using a plain text email client. As such, perhaps this is a problem better solved locally at the email client side. That is, compose in Markdown and have your own client do the filtering into HTML before sending it out the door. But know this -- I appreciate the support already added to this platform. Thanks!

Re: Zoom integration now active #update

 

An update: it turns out I need to have Zoom approve the integration for their marketplace before it can be active (I don't need it to be in their marketplace, but whatever). I hope this will happen in the next few days; I'll keep you posted.

Thanks,
Mark

Re: Reply Composition #bug

 

On Tue, Mar 31, 2020 at 5:25 PM Duane <txpigeon@...> wrote:
On Tue, Mar 31, 2020 at 06:04 PM, Mark Fletcher wrote:
Ah, that's it. For groups that are plain text only, we only allow plain text replies.
Helps a LOT!  Thank you for checking.  Is this something that changed "recently"?  I seem to remember seeing the HTML editing buttons previously, but maybe I wasn't paying close enough attention (and I know how you've done little things to see if we're really paying attention. ;>)  Makes sense though as there'd be no need to convert it to text like an incoming email.

It's true that I do tweak things, but I try to announce them (I have done a bunch of word tweaks lately in response to tech writer Nina's suggestions that I haven't specifically called out). But this particular behavior dates back, IIRC, several years.

Mark

Re: Zoom integration now active #update

Brian Dooley
 

Thank you Mark!!!


On Tue, Mar 31, 2020, 4:31 PM Mark Fletcher <markf@corp.groups.io> wrote:
Hi All,

I've just pushed Zoom integration to production. If you've used the Zoom Chrome plugin before with GCal, it works much the same way. When you create or edit a single calendar event, there is a new button, 'Make This A Zoom Meeting'. Click that, a window will pop up to log into Zoom (first time only), and then you'll get a dialog box to set the parameters of your Zoom meeting. Once you create the Zoom meeting, it'll populate the location and description fields of your event with the relevant information and add the #zoom hashtag to the event name. You can also delete your Zoom meeting while editing your event.

This currently does not work with repeating events.

I had originally decided that this would be a premium feature, but with lots of people using Zoom to stay in touch during the pandemic, it will be available to everyone through September 1st.

Please let me know if you have any questions.

Thanks,
Mark

Re: Reply Composition #bug

Duane
 

On Tue, Mar 31, 2020 at 06:04 PM, Mark Fletcher wrote:
Ah, that's it. For groups that are plain text only, we only allow plain text replies.
Helps a LOT!  Thank you for checking.  Is this something that changed "recently"?  I seem to remember seeing the HTML editing buttons previously, but maybe I wasn't paying close enough attention (and I know how you've done little things to see if we're really paying attention. ;>)  Makes sense though as there'd be no need to convert it to text like an incoming email.

Thanks much,
Duane

Re: Reply Composition #bug

 

On Tue, Mar 31, 2020 at 3:08 PM Duane <txpigeon@...> wrote:
On Tue, Mar 31, 2020 at 03:31 PM, Mark Fletcher wrote:
My guess is that there's something causing a javascript error.
Another bit of information for those that may check, it only seems to happen on "Plain Text Only" groups.  Works fine here on beta - get the HTML window.  Other info sent to Mark.


Ah, that's it. For groups that are plain text only, we only allow plain text replies. I tested the URL you sent, and it put up the plain text editor, as expected. It wasn't the markdown editor (really the same thing as plain text except that there'd be a Preview button under it).

Hope this helps.
Mark

Re: Reply Composition #bug

Duane
 

On Tue, Mar 31, 2020 at 03:31 PM, Mark Fletcher wrote:
My guess is that there's something causing a javascript error.
Another bit of information for those that may check, it only seems to happen on "Plain Text Only" groups.  Works fine here on beta - get the HTML window.  Other info sent to Mark.

Duane

Re: Zoom integration now active #update

 

On Tue, Mar 31, 2020 at 1:47 PM Robert Kingett <kingettr@...> wrote:

When I try to create an event with my personal meeting ID I get the below error message.

Client Groups.ioAccount LevelYou cannot authorize the app This app cannot be installed outside of the developer's account. Please contact the application developer to get support with installing this application.


Gah! I clearly didn't do something right when applying for permission. Let me look into it. I'll disable it for now.

Thanks,
Mark

Re: Zoom integration now active #update

 

When I try to create an event with my personal meeting ID I get the below error message.

Client Groups.ioAccount LevelYou cannot authorize the app This app cannot be installed outside of the developer's account. Please contact the application developer to get support with installing this application.

Does it require a Zoom Premium subscription? I'm running Windows 10, 1909, using the latest FireFox.

Re: Zoom integration now active #update

Glenn Glazer
 

On 3/31/2020 13:29, Mark Fletcher wrote:
Hi All,

I've just pushed Zoom integration to production. If you've used the Zoom Chrome plugin before with GCal, it works much the same way. When you create or edit a single calendar event, there is a new button, 'Make This A Zoom Meeting'. Click that, a window will pop up to log into Zoom (first time only), and then you'll get a dialog box to set the parameters of your Zoom meeting. Once you create the Zoom meeting, it'll populate the location and description fields of your event with the relevant information and add the #zoom hashtag to the event name. You can also delete your Zoom meeting while editing your event.

This currently does not work with repeating events.

I had originally decided that this would be a premium feature, but with lots of people using Zoom to stay in touch during the pandemic, it will be available to everyone through September 1st.

Please let me know if you have any questions.

Just as a heads-up, there was a recent Zoom bug on iOS that caused Zoom to leak data to Facebook. They have since dropped the Facebook integration, so make sure you update the app before using it.

Best,

Glenn


--
PG&E Delenda Est

Virus-free. www.avast.com

Zoom integration now active #update

 

Hi All,

I've just pushed Zoom integration to production. If you've used the Zoom Chrome plugin before with GCal, it works much the same way. When you create or edit a single calendar event, there is a new button, 'Make This A Zoom Meeting'. Click that, a window will pop up to log into Zoom (first time only), and then you'll get a dialog box to set the parameters of your Zoom meeting. Once you create the Zoom meeting, it'll populate the location and description fields of your event with the relevant information and add the #zoom hashtag to the event name. You can also delete your Zoom meeting while editing your event.

This currently does not work with repeating events.

I had originally decided that this would be a premium feature, but with lots of people using Zoom to stay in touch during the pandemic, it will be available to everyone through September 1st.

Please let me know if you have any questions.

Thanks,
Mark

Re: Reply Composition #bug

 

On Tue, Mar 31, 2020 at 1:00 PM Duane <txpigeon@...> wrote:
I just attempted to make a reply on one of my groups and got the Markdown (MD) composition window.  I went to my account, changed it to plain text (though it showed HTML), and still get the MD window.  Changed it back to HTML, still showing MD window.  I'm going to leave it there, hoping Mark is playing with an idea and this will be straightened out shortly.

I'm not aware of any issues with that, and I haven't touched that code in awhile. My guess is that there's something causing a javascript error. Off-list, please send me the URL of the message you're trying to reply to and I'll investigate.

If anyone else is seeing this, please also send me the URL off-list.

Thanks,
Mark 

Reply Composition #bug

Duane
 

I just attempted to make a reply on one of my groups and got the Markdown (MD) composition window.  I went to my account, changed it to plain text (though it showed HTML), and still get the MD window.  Changed it back to HTML, still showing MD window.  I'm going to leave it there, hoping Mark is playing with an idea and this will be straightened out shortly.

Thanks,
Duane

Re: Markdown Support #suggestion

 

Hi All,

We do support markdown in email, as outlined here: https://beta.groups.io/g/main/message/1318

You'll be forgiven for not knowing about this, since it's so obscure and supported by (I believe) exactly one email client. :-)

Note that we don't do any conversions of those messages before we send them out (so all email recipients see the original markdown when viewing the message in their clients), but we do display them correctly on the website.

Conversely, if you have your Editor Preference set to Markdown and you compose a message on the website, we send that out with both HTML and plain text parts.

Like I said in the referenced message, I'm happy to add support for flagging a message as markdown if we can agree on the magic word/set of characters. If we do, I think it probably makes sense to convert those messages to HTML before sending them out to the group (ie change the current behavior). This would definitely be a niche thing, (for amongst other reasons) because I'm not sure it's even possible to force Gmail and the other web-based clients to send out just a plain text email anymore.

Thanks,
Mark


Re: Messages contain CC:group even with ReplyTo=sender and "Remove other options" #bug

 

On Thu, Mar 19, 2020 at 07:34 AM, Jim Avera wrote:

If "Reply to" in Group settings is set to "sender", and "Remove Other Reply Options" is checked, messages still contain a CC: header pointing to the group post address.   This permits users to reply to the group through email, but not on the web.  This is almost certainly not what the owner intended.  I'm guessing this is a #bug.

Well, not a bug because it's doing what it was designed to do, but I think the design was wrong. For Reply To Sender groups, we were adding a CC line pointing back to the group email address. I think I added that because of reasons explained here: https://beta.groups.io/g/main/message/2181, but on reflection that is wrong because when someone clicks the Reply All button in their email client, the client already includes the To address, which is the group. On testing with Gmail, with the CC line, and doing Reply All, you end up sending the reply to the group twice (because it used the addresses in the To and CC lines).

I have removed this CC line for Reply To Sender groups. Please let me know if it causes a problem.

Now, to what I think you're asking: is there a way to disable Reply All in email clients. I think the answer is yes, if I re-write the To line in messages so that, instead of being the group email address, the To line is the recipient of the email message. Then the group email address would not appear anywhere in the message headers and Reply All would not send the message to the group. But, I think this would make it very difficult for someone to determine if a message they received was sent to them via the group or just by someone replying to a message the person originally sent to the group. I think this would be confusing. Thoughts?

Thanks, Mark

Re: Event: Mail server upgrade #downtime - Monday, 30 March 2020 #downtime #cal-invite

Chris Aldrich
 

I didn't know about this downtime until one of my group members emailed asking about the delay in receipt of email messages that were visible on our group's page.

I first checked status.groups.io where there was nothing to indicate this downtime. Next I checked GMF (nada) and the Beta, where I found this message. I thought Bera was the place to discuss potential improvements to groups.io and I get the Beta messages in Full Digest since (I thought) there was no particular need for speed in reading them. I was surprised that it was the place that this announcement was posted. 

All of this is to say - is there a more expedient way for Group Owners and Moderators to be notified of anticipated #downtime? Is there something else I should be subscribed to?

Thanks much - we love groups.io and I just suggested it to the admin of a nearly-defunct Y group that I belong to.
Chris

Re: Markdown Support #suggestion

 

On Sun, Mar 29, 2020 at 05:00 PM, Bill Costa wrote:
Perhaps starting the body of a plain text message with a first
line of ".markdown", or something similar, to signal that the text
should be poured though the markdown filter before posting and
storage?
I just wanted to note that it seems to be a common thing that a text entry starting with "%md" (without the quotes) indicates that text should be treated as Markdown. I checked the RFCs but don't see any reference to that, so that's why I'm saying it just seems to be common practice rather than a standard. For example, starting a message with:

%md ##This message is in **Markdown**!

would cause the message to be interpreted in Markdown. That's one option.

JohnF