Date   

moderated confirm or change language in 14-day expiration of pending subscription #suggestion #fixed

 

The Pending Subscription Notification currently reads:
"If you do not take action within that time, the pending subscription will be automatically rejected."

If the subscription request is simply deleted (rather than rejected), I would change "rejected" to "deleted." Only if "rejected" includes the sending of any active rejection notice would I keep the word "rejected." 
--
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: Banned not in Banned list #bug

 

On Fri, Jan 24, 2020 at 10:44 AM, Mark Fletcher wrote:
Now, banning by entering an email address behaves the same way as the other banning: we keep their member notes, messages to moderators, join date, etc. Previously we did not.
Mark,

1. Bad news: this is still not working. I just banned someone using their email address, and their notes are gone in the banned list.

2. There is a further remaining mismatch: the banned list contains the banned member's email delivery history, but their "history" shown in the past members list does not. (This is not a biggie, but the mismatch is still disconcerting.)

3. While I'm at it, a suggestion: the banned list provides checkboxes and actions, but the past members list does not. It would be helpful to add actions to the past members list. For example, you might remove someone and decide only later to ban them. But currently, you can't ban someone from the past members list; the only way to ban a past member (who was not banned at the time of removal) is to use their email address. 
--
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 forcing digests

ro-esp
 

From: Mark Fletcher <markf@corp.groups.io>
Date: Wed, 29 Jan 2020 23:01:54 CET
I currently force digests every night (with the caveat > that if someone had recently gotten a digest, a new one > doesn't go out).
Does "recent" have a definition?

I always assumed that digests were sent out whenever the oldest message in waiting had been there for 24 hours...or as soon as there were 12 messages in the queue

But otherwise digests can go out at any time,
depending on messages sent to a group. And I've been > contemplating changing the forcing of digests so that > it would work more like summaries do, so that a digest > would be forced at 6am based on a user's timezone, instead of everyone getting forced at 10:30pm pacific time.
If we're going down that road, maybe make it a subscribers' option, something like: "send me a digest with remaining messages at [preferred time UTC] every day"

BTW 22.30 pacific means 29.30 or 30.30 UTC, which is 06.30 where I live. So for me the change would be moot


groetjes, Ronaldo


moderated Re: suggested change to use hashtag to control sending megs #suggestion

ro-esp
 

On Wed, Jan 29, 2020 at 11:05 PM, Ken Kloeber wrote:


  the message would be turned around
what does that mean?
It means that your email to a group doesn't get delivered directly to members. 
then why send it?

GIO is an email bounce service
I don't think so. If I send a message to a group, I want it to be forwarded, not bounced back

-- A very busy Nome inside reads
your message and types it out onto another piece of paper and mails it to
members (opposed to reading the message on the website GUI.)
Do you mean gnome?

My suggestion is that a #TAG in the email subject could be used to set
(determine) which members the message is sent to.
So any subscriber would have to visit a list of allowed hashtags and pick which ones to (not) follow?
Sounds like it makes sense. I have no experience with hashtags, and don't know how they are used in groups.io now

groetjes/ĝis, Ronaldo


moderated Re: section links #suggestion

bchesneau@...
 

mmm no I mean header in github wiki like “# Header” when exported to html has an anchor added to it :  <h1>< a href=“#Header” />Header</h1> So you can link them easily

Benoît

On 29 Jan 2020, at 23:33, Christos G. Psarras <christos@...> wrote:

Could you explain what you mean exactly?  After all, you can have links (of pretty-much any kind) in Wiki, do you really mean have the ability to hover over a link and turn it into a "preview" link?

Cheers,
Christos


moderated Re: section links #suggestion

Bill Hazel
 

I too noticed this when looking at https://help.github.com/en/github content.

That is one reason I promote the idea of using a Table of Contents (ToC) for longer pages.

The page you reference uses similar functionality, it even has it's own "ToC" at the top although it is in a different format. Not sure how it differs in the underlying code but if you are looking for the functionality, the ToC works like a charm.

Bill


moderated Re: Problem with sorting in Emailed Photos folder #bug #fixed

 

On Fri, Jan 24, 2020 at 12:10 PM, Bruce Bowman wrote:

Mark -- If you sort the Emailed Photos folder by anything other than Posting Date, the thumbnails are sorted correctly but the underlying links are not. This leads to confusion when you subsequently click on a thumbnail and a different image loads.

This should be fixed now.

Thanks, Mark


moderated Re: Deleting attachments when out of space #update

Bruce Bowman
 

On Wed, Jan 29, 2020 at 05:01 PM, Mark Fletcher wrote:
Are you envisioning a group that is continually running up against its storage limit not because of attachments, but because of files/photos? And so the enforcer process would end up deleting all attachments in the group each time it runs?
Yes, that's the kind of scenario that I was thinking about.

And given that, there'd be a timing issue with digests going out? 
Perhaps. I'm mildly concerned that the enforcer [insert "hasta la vista, baby" voice here] -- if run before the daily digest compiler/sender -- then some attachments may never make it to the digests containing their corresponding messages. I hope that made sense.

Assuming I understand the request, I guess that's a possibility, but I'm not sure there's anything I can do about it. I currently force digests every night (with the caveat that if someone had recently gotten a digest, a new one doesn't go out). But otherwise digests can go out at any time, depending on messages sent to a group.
This should not be a problem for "intermediate" digests because the nightly enforcer [ditto] presumably hasn't run yet.

Of course, this all assumes that the attachment purge and digest compilation activities share some sort of time-space with respect to system maintenance...see below...

And I've been contemplating changing the forcing of digests so that it would work more like summaries do, so that a digest would be forced at 6am based on a user's timezone, instead of everyone getting forced at 10:30pm pacific time.
Yep...it would be nice for everyone to get up in the morning and find their daily digest available at that time, regardless of their time zone. That said, they might not be so happy if it meant that some attachments that were supposed to come over with that digest didn't make it.

I have no inclination to micromanage on this end...just please give some thought to this, lest it become the source of a bug report somewhere down the line.

Thanks,
Bruce


moderated Re: section links #suggestion

 

Could you explain what you mean exactly?  After all, you can have links (of pretty-much any kind) in Wiki, do you really mean have the ability to hover over a link and turn it into a "preview" link?

Cheers,
Christos


moderated Re: suggested change to use hashtag to control sending megs #suggestion

KWKloeber
 

 
>>>On Tue Jan 28, 2020 10:25 AM; ro-esp wrote:
Subject: Private: Re: [beta] suggested change to use hashtag to control sending megs #suggestion
 
>  the message would be turned around 
what does that mean? (please answer on-list)
                         groetjes, Ronaldo<<<
Ronaldo,
It means that your email to a group doesn't get delivered directly to members.  GIO is an email bounce service -- A very busy Nome inside reads your message and types it out onto another piece of paper and mails it to members (opposed to reading the message on the website GUI.)

My suggestion is that a #TAG in the email subject could be used to set (determine) which members the message is sent (turned around) to. 
(excuse the preposition.)


moderated section links #suggestion

bchesneau@...
 

WHile the wiki is said to use the github markdown flavour it's not possible yet to have section links. Would be very useful to have it...


moderated Re: Deleting attachments when out of space #update

 

On Wed, Jan 29, 2020 at 12:49 PM Bruce Bowman <bruce.bowman@...> wrote:

If I may, please ensure that the nightly attachment trim is the last function performed in whatever nightly maintenance is scheduled by groups.io. It would be unfortunate if an unexpected bolus of incoming attachments on a given day resulted in some of them being purged before they went out in the daily digest.


First, as a word nerd, I need to say that I really appreciate the use of the word bolus.

I haven't yet set up the time for when the enforcer process will run, but I'm not sure I understand your request. Are you envisioning a group that is continually running up against its storage limit not because of attachments, but because of files/photos? And so the enforcer process would end up deleting all attachments in the group each time it runs? And given that, there'd be a timing issue with digests going out? 

Assuming I understand the request, I guess that's a possibility, but I'm not sure there's anything I can do about it. I currently force digests every night (with the caveat that if someone had recently gotten a digest, a new one doesn't go out). But otherwise digests can go out at any time, depending on messages sent to a group. And I've been contemplating changing the forcing of digests so that it would work more like summaries do, so that a digest would be forced at 6am based on a user's timezone, instead of everyone getting forced at 10:30pm pacific time.

Thanks,
Mark


moderated Re: Deleting attachments when out of space #update

Bruce Bowman
 

Thanks for the update, Mark. As you might imagine, we're getting some follow-up inquiries in GMF.

If I may, please ensure that the nightly attachment trim is the last function performed in whatever nightly maintenance is scheduled by groups.io. It would be unfortunate if an unexpected bolus of incoming attachments on a given day resulted in some of them being purged before they went out in the daily digest.

Thanks again,
Bruce


moderated Re: Banned not in Banned list #bug

Duane
 

On Sat, Jan 25, 2020 at 01:44 PM, John Pearce wrote:
What is the aol weirdness you speak of?
See https://beta.groups.io/g/main/topic/70062502

Duane


moderated Re: Deleting attachments when out of space #update

 

On Sat, Jan 18, 2020 at 04:33 PM, Bruce Bowman wrote:

Mark -- The previously stated, two-week timeline for the auto-deletion of attachments is fast becoming imminent; so I thought it would be a good idea to revisit this now.

I just sent out the two week warning messages.

-- On what date/time is the "great attachment purge" actually scheduled to occur (~Jan 21)?

It will start two weeks from tomorrow.

-- What was the final decision regarding the resulting entry[s] in the Activity Log?

I will change it so that there will be one log entry per "purge", and it'll list the high water mark message number.

Thanks, Mark


moderated Re: suggested change to use hashtag to control sending megs #suggestion

KWKloeber
 

>>>. But how will you deal with the message list?<<<



J - unsure what you’re asking. Clarify?


On Jan 27, 2020, at 9:13 PM, Ken Kloeber via Groups.Io <KWKloeber@...> wrote:

Replying to wasn't the focus, but of course, options could be "to sender"  or "no replies" or to the "sent-to group" only.
subgroups seem too clunky/restrictive to simply send msgs to admins or the like.

For example, for whatever reason say a group has 4 lists (sometimes members changing), admins, renters, buyers, tire-kickers. 
A SG for each is not useful because it involved subscribing/unsubscribing, and there could be cross-listing (there could be two (but not the same) admins on each list, or there could be plain old members on 2 out of the 4 lists, and 2 on another list, and so on.

thx
K

On Mon, Jan 27, 2020 at 11:37 PM, J_Catlady wrote:
Not clear how this would work. What would happen when one of those people replies to the message?
Suggest using a subgroup instead.
--
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 Calendar ICS file changes #update

 

Hi All,

I just pushed a big revamp of how we generate calendar ICS files, something I've been working on for the past week. ICS files are the attachments in #cal-invite and #cal-reminder messages and are also what's sent out when you subscribe to a Groups.io calendar (with your Outlook/Gmail/Yahoo/etc calendar). They describe calendar events and are what allow you to easily add events from your Groups.io calendar to your Gmail/Outlook/Yahoo/etc calendar.

<NerdTalk> The changes affect how we described repeating events in the ICS files. The way we did it before was to just describe the individual events that happen; now we describe the repeating event criteria instead (ie happens every Monday at 10am). </NerdTalk>

The end result is that, in your Google calendar for example, it will know a specific event is part of a repeating event, so that you can delete all of them at once. Also, importantly, cancel event notices should behave much better.

These changes should not affect how your calendar behaves on Groups.io. These are just changes to ICS files. Mostly, you should not notice any changes. If you do, please let me know off list. Calendar changes are notoriously difficult to test, because of all the different calendars out there and also, to me, the ICS spec is difficult to implement correctly.

Thanks,
Mark
(also I added a new #update hashtag for these kinds of announcements)


moderated Re: auto-acknowledgement from support is back (yay) but missing original message #bug

 

Yep, Duane, has totally forgotten that. Which is ironic, since making MF a group option (in general, not specifically for beta) was actually my suggestion. 😊


On Jan 28, 2020, at 10:29 AM, Duane <txpigeon@...> wrote:

On Tue, Jan 28, 2020 at 11:26 AM, J_Catlady wrote:
That message took roughly 10 minutes to appear either online or in email.
Not that bad considering that all new topics are now moderated per https://beta.groups.io/g/main/message/23814

Duane

--
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: auto-acknowledgement from support is back (yay) but missing original message #bug

 

Correction: there’s no delay issue. I’d forgotten that the group is now MF. Also missed Mark’s note that he changed the tag to “bug”. 

I need to go off that decaf I started this morning...


On Jan 28, 2020, at 9:26 AM, J_Catlady via Groups.Io <j.olivia.catlady@...> wrote:

That message took roughly 10 minutes to appear either online or in email. Maybe the message delay problem is back.


On Jan 28, 2020, at 9:12 AM, J_Catlady via Groups.Io <j.olivia.catlady@...> wrote:

Mark,

This morning I sent an email to the support address, about a logged-in location in the Subscription Approval Notice not matching the member's location as stated in her questionnaire response. (I wanted to know what was going on, it was possibly not a bug, and it was inappropriate to post here as a bug since I had to send you the member's detailed information.) I was pleasantly surprised to see that the auto-acknowledgement is back. However, the acknowledgement didn't contain the text of the originally sent message, as it used to. That could make it difficult to locate these emails later, since now there is only the title to search on. Calling this "misc" since it's either a bug (if unintentional) or a suggestion (if intentional).

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

[Mod Note: Changed hashtag to #bug]


--
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: auto-acknowledgement from support is back (yay) but missing original message #bug

Duane
 

On Tue, Jan 28, 2020 at 11:26 AM, J_Catlady wrote:
That message took roughly 10 minutes to appear either online or in email.
Not that bad considering that all new topics are now moderated per https://beta.groups.io/g/main/message/23814

Duane

5901 - 5920 of 29666