Date   

moderated Include owner emails and notifications in moderators' email delivery history #suggestion

 

This morning I wanted to check whether one of my mods received notification that someone had joined the group, so naturally, I checked their email delivery history, only to discover that these notifications, even though they are emails delivered, are not logged as such. I think they should be.
--
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 Subscriptions to Gio Calendars No Longer Syncing #bug

Kenny Paul
 

ISSUE: Subscriptions from Gio calendars from both G-cal and Confluence have suddenly stopped working for some of our lists and the events have disappeared from people's calendars.  

TIMING: The reports of failures from community members started coming in shourtly after the Jan 31 update. https://groups.io/g/updates/message/118 

DEBUGGING INFO:
- These were all existing subscriptions that have been syncing correctly for more than a year.  I have verified that the meetings still exist on the Gio calendar and are unchanged.

- Attempts to remove the old subscriptions and resubscribe using the link generated by Gio have not worked.  Confluence produces the error "Specified calendar does not seem like iCalendar." when the link produced by Gio is pasted into the subscription url.

- Subscription  attempts from newly created Gio calendars produce the same error.

- I found a link describing the error, in the context of a Confluence subscription to a G-cal. I don't have the necessarry perms to attempt the debugging suggested. -
https://confluence.atlassian.com/confkb/unable-to-subscribe-to-google-calendar-with-error-specified-calendar-does-not-seem-like-icalendar-722145638.html 

--
Kenny Paul, Technical Program Manager for ONAP
The Linux Foundation
Pacific Time Zone


moderated Unsubscribing a Member via Membership List #suggestion

Leeni
 

Right now when you unsubscribe a member using the membership list and after you click on remove, you get a verifying pop up asking you if you want to unsub that member. Would it be possible if the member's user name or email can be added to that verification pop up so you know you are removing the correct member from the group. Thanks Leeni
 
   
 
 


moderated Re: Site updates #changelog

Benoît Dumeaux
 

On Sat, Feb 29, 2020 at 04:35 AM, Mark Fletcher wrote:
BUGFIX: When deleting attachments to make space, we were not taking into account space used by files and photos, so we ended up deleting fewer attachments than we should have.

I don't sure I understand can you more explain please :-D


moderated Site updates #changelog

 

Changes to the site this week:

  • CHANGE: Previously, we would force a digest to be created at 10:30pm Pacific Time nightly, if one had not been generated in the previous 6 hours and messages had been sent to the group since the last digest. Now, we force a digest to be created at 6AM local time for each subscriber, based on their timezone, if a digest had not been generated in the previous 6 hours and messages had been sent to the group since the last digest.
  • CHANGE: When creating a new group or changing the name of an existing group, change the error message when the group name is already taken to That address is not available..
  • CHANGE: Hardcode some IP addresses associated with chinamobile.com because reverse DNS lookups on them fail randomly.
  • BUGFIX: The command to update whether a topic was locked/moderated/etc in the search index was failing because the syntax changed between Elasticsearch versions. Fixed the command and re-indexed the message archive.
  • BUGFIX: When joining a new group, the membership parameters could not be modified from that page.
  • INTERNAL: Upgraded to Go 1.14 compiler.
  • NEW: Database columns now have a Default Hidden checkbox.
  • NEW: Database tables now have ID Default Hidden and Updated Default Hidden checkboxes.
  • API: Added default_hidden field to the Database Column object.
  • API: Added id_default_hidden and updated_default_hidden fields to the Database Table object.
  • BUGFIX: Wrong logo used for Google Drive.
  • API: Removed the invalid posterid error from /searcharchives to allow people to search for messages from people who are no longer members of the group.
  • API: Added body field to message_search_result object.
  • NEW: Member Directory Search.
  • API: Added /searchmemberdirectory endpoint.
  • BUGFIX: When deleting attachments to make space, we were not taking into account space used by files and photos, so we ended up deleting fewer attachments than we should have.
  • BUGFIX: Fixed pagination when searching on members.
  • SYSADMIN: Added an additional hot standby instance of the main database server.
  • CHANGE: In the UI, changed hash tags to hashtags for consistency.

Have a good weekend everyone.

Mark


moderated Re: Search member directory #suggestion #done

Charles Roberts
 

Still no search button in Landscape mode.  Note the SEARCH feature works fine in MEMBERS LIST.
Chuck


moderated Re: Search member directory #suggestion #done

Duane
 

On Fri, Feb 28, 2020 at 06:33 PM, Charles Roberts wrote:
SEARCH button does not appear on DIRECTORY screen on either one.
If the display is too narrow, the Search button disappears.  At the same time, the "member boxes" will only be one wide.  (I do believe this is a mistake.)  As long as the screen is at least 2 boxes wide, the Search is there.  Have you tried landscape mode?  Might still be too narrow, but I haven't checked.

Duane


moderated Re: Search member directory #suggestion #done

Charles Roberts
 

Have tried two different Android phones.....SEARCH button does not appear on DIRECTORY screen on either one.
Chuck


moderated Re: Digest change #update

Ann Wild
 

Thanks, Mark.  This is great change to 6 AM local time.  We had previously been getting the digest at 3:40 AM EST, which didn't fit with the fact that you sent it out at 10:30 PM PST.  The new time will fix any difficulties with overflow messages if we have a digest during the day. No temptation to post at midnight or later :-).


moderated Re: Ability to send later from web interface #suggestion

 

That's a great idea, but I use the calendar to announce, and remind, people of in person speaking engagements and book signings and otherwise. Plus, I'd like the ability to time a quick update without the email subject filled with, well, calendar prefixes and hashtags.


moderated Re: Ability to send later from web interface #suggestion

Joseph Hudson
 

Hi Robert, why not use the calendar for this purpose. That way it goes out right when you want to. You can specify the date and time in the calendar I do believe.

On Feb 28, 2020, at 2:21 PM, Robert Kingett <@blindjourno> wrote:

I would like the ability to write new topics now, but schedule them for posting at a certain date and time. I know this can be done using email services, but I use the website a lot because the composer allows for markdown.


moderated Ability to send later from web interface #suggestion

 

I would like the ability to write new topics now, but schedule them for posting at a certain date and time. I know this can be done using email services, but I use the website a lot because the composer allows for markdown.


moderated Re: Missing Digest #bug

Bruce Bowman
 

On Fri, Feb 28, 2020 at 12:31 PM, Ann Wild wrote:
If we had a digest during the day because we were active, we always got an early morning digest with the remaining messages of the previous day.  It has always worked that way since we moved to groups.io in October---with the exception of the other day.
My guess is that there simply were no messages remaining to be sent. If nothing has been posted to the group in the interval between the previous 12-message digest and when the nightly job runs, groups.io does not generate and send an empty digest.

Bruce


moderated Re: Missing Digest #bug

 

On Thu, Feb 27, 2020 at 3:48 PM Ann Wild via Groups.Io <annlwild=aol.com@groups.io> wrote:
Yesterday (Wednesday) we got an early digest because we were busy at 8:36 PM EST, but we never received the 3 AM digest on Thursday morning.  We always get that early AM digest.  Instead, just now we got a digest at 6:07 PM EST, which included the messages that should have been sent out early this morning.  This is the first time this has happened.  I hope it won't be repeated because it delays the posting of messages.

My guess is that there was less than 6 hours between the 8:36pm EST digest and when we started the 10:30pm PST forcing digest run.

Please also see the message I just posted about digest changes.

Thanks,
Mark


moderated Digest change #update

 

Hi All,

Digests are generated for every 12 messages sent to a group. That has not changed. Digests were also generated at 10:30pm Pacific Time nightly, if one had not been generated in the previous 6 hours and messages had been sent to the group since the last digest. I've just changed that to behave more like summary emails. Now, we force a digest to be created at 6am local time for each subscriber, based on their timezone, if a digest had not been generated in the previous 6 hours and messages had been sent to the group since the last digest.

Please let me know if you have any questions.

Thanks, Mark


moderated Re: Missing Digest #bug

Ann Wild
 

Sorry for my mistake.  I know each digest has 12 messages, not 20.  But my question remains.


moderated Re: Missing Digest #bug

Ann Wild
 

I don't understand your reply and searched the wiki to see if I have missed something.  The digest options for our group are two: full featured digest and summary.  The digest bundles topics (the list shows the topics and the number of messages on each topic in parentheses), and when the total number of messages reaches 20, we get a digest immediately that shows all 20 messages.  If we had a digest during the day because we were active, we always got an early morning digest with the remaining messages of the previous day.  It has always worked that way since we moved to groups.io in October---with the exception of the other day.  The summary is a list of messages posted once a day.  I don't see the various options for the digest that you mention.


moderated Re: Default database view #done #suggestion

Duane
 

On Fri, Feb 28, 2020 at 09:28 AM, Peter Rawbone wrote:
However, when hiding, say, the ID column only the ID’s on the current page are hidden.  If you select another page, the ID’s show until they’re hidden and so on with each page.
Peter,

I'm not seeing that.  The hidden columns stay hidden on all pages, whether I hide them by default or while looking at the table.  Of course they come back the next time I open it unless I've changed the table properties.

Duane


moderated Re: Default database view #done #suggestion

Peter Rawbone
 

I do like the ability to hide!
However, when hiding, say, the ID column only the ID’s on the current page are hidden.  If you select another page, the ID’s show until they’re hidden and so on with each page.  It would be nice if the column selected to be hidden applied to all pages.  We have in excess of 14 pages - so far!

Mark - any ideas??!!
--
Peter


moderated Re: Missing Digest #bug

Duane
 

On Thu, Feb 27, 2020 at 05:48 PM, Ann Wild wrote:
Yesterday (Wednesday) we got an early digest because we were busy at 8:36 PM EST, but we never received the 3 AM digest on Thursday morning.  We always get that early AM digest.  Instead, just now we got a digest at 6:07 PM EST, which included the messages that should have been sent out early this morning.  This is the first time this has happened.
Probably by design.  It sounds to me like you may not understand how the digests work.  Not everyone will get a digest at the same time.  It all depends on which messages they choose to receive in it (first, following, etc.)  Someone that chooses to only get the first message of each topic may only get the 'forced' digest.  Someone that chooses to receive all messages may get 2 or 3 digests in the same time frame.  It's also been stated that there's a timing function so that if someone has received a digest recently, another one won't be sent at the (current) 10:30 pm PST job (though 'recently' hasn't been defined as far as I know.)  The only way to be sure you get all messages at some known time is to receive all individual messages.  Then you should receive them shortly after they are posted.  Mark has mentioned previously that he may change the 'force' time, but hasn't so far.  Even that won't change the fact that you may not get a digest at a specific time.

Duane