Hello Andy,

On 02/12/2022 20:18, Andy Wedge wrote:

Hmm. I thought 07:00 was late in the day and I always tried to get that out to my members ASAP after it arrived.  The time it normally arrived was 07:00 but a couple of times a year it would be 06:00 due to the different dates when the US & UK changed their clocks.  If the permanent DST legislation is signed into law in the US and the job to create the cal-summary message is based on Pacific time, that means roughly half the year it will arrive at 09:00 and the other half at 08:00.  I think expanding the flexibility around when the cal-summary message is created, perhaps by specifying a time & timezone, would be a help.

And here we again come to the problem of localization (or localisation). Why should people, who perhaps have never seen the Pacific ocean, bother themselves about things like Pacific Time and how is it different from GMT, UTC and BST. Localisation must be tailored to everyday live of a local community of customers... Which is my own opinion, of course...


Regards,

Gregory

On Fri, Nov 4, 2022 at 09:39 PM, Mark Fletcher wrote:

CHANGE: Send the two-week advanced billing notice to all moderators, not just the person set to pay the invoice.

A question/complaint came up about this on GMF.  For clarification, is it ALL moderators or only those with Billing permission?

Thanks,
Duane

On Fri, Dec 2, 2022 at 03:28 PM, Mark Fletcher wrote:

It arrived at 09:00 rather than the normal 07:00. A scheduling change?

Yes, previously they went out at 11:00pm pacific time the night
before, which caused the off-by-one error you saw last week. Now they
go out the same day (pacific time).

Hmm. I thought 07:00 was late in the day and I always tried to get that out to my members ASAP after it arrived.  The time it normally arrived was 07:00 but a couple of times a year it would be 06:00 due to the different dates when the US & UK changed their clocks.  If the permanent DST legislation is signed into law in the US and the job to create the cal-summary message is based on Pacific time, that means roughly half the year it will arrive at 09:00 and the other half at 08:00.  I think expanding the flexibility around when the cal-summary message is created, perhaps by specifying a time & timezone, would be a help.

Regards
Andy

On Fri, Dec 2, 2022 at 1:36 AM Andy Wedge <andy_wedge@...> wrote:

On Fri, Dec 2, 2022 at 07:18 AM, Andy Wedge wrote:

Our #cal-summary message has not been received again this morning.

It arrived at 09:00 rather than the normal 07:00. A scheduling change?

Yes, previously they went out at 11:00pm pacific time the night
before, which caused the off-by-one error you saw last week. Now they
go out the same day (pacific time).

Thanks,
Mark

On Fri, Dec 2, 2022 at 07:18 AM, Andy Wedge wrote:

Our #cal-summary message has not been received again this morning.

It arrived at 09:00 rather than the normal 07:00. A scheduling change?

Regards
Andy

Hi Mark,

Oh Mark - please just rest up and get better. Thankfully the vaccines and boosters help tremendously to lessen the course,  but they aren't bullet proof vests. letting your body recover is the most important thing now.
Ginny
--
Ginny T.  gttemari21@...
========
TemariKai.com

On Thu, Dec 1, 2022 at 03:27 PM, Grigorii Semenov wrote:

No doubt, the old principle "don't use it if you don't like it" still has a value these days. But we are here to find technical means to expand usage of GIO as much as possible. The products that we all like!

I don't disagree

In 2016, the EU adopted the General Data Protection Regulation, which came into force in 2018. Among other things, this Act in Article 17 stipulates that "The data subject shall have the right to obtain from the controller the erasure of personal data concerning him or her without undue delay and the controller shall have the obligation to erase personal data without undue delay ".

Ah yes, Article 17 (1) of GDPR (the so called 'right to be forgotten'). Being in the UK, I am fully aware of this. I hear this mentioned now and then and what most people fail to mention is the conditions under which article 17 (1) applies. And then of course, we have Article 17 (3) which lists exceptions to Article 17 (1).  The only thing you can guarantee about this is that the people that make money from it will be the lawyers, but then who do you think wrote it.

Given that we are using a system that emails messages to multiple people, some or all of whom maybe unknown and we have no control over what they do with those emails, your chances of being truly 'forgotten' are slim to none existent.

Regards
Andy

We're all with you. Drink plenty of liquids; it's easy to forget when you are sick. Get well soon. Best, Marv

Hi Andy,

When you start using Groups.io you agree to the Terms of Service. If they are not legally acceptable to you in your location, then perhaps an alternative platform that meets your requirements would be best at this time.

No doubt, the old principle "don't use it if you don't like it" still has a value these days. But we are here to find technical means to expand usage of GIO as much as possible. The products that we all like!

If a member unsubscribes from a group, they will still have a Groups.io account, they just won't receive emails from that group any more. If you have a Premium or Enterprise group, details of past members are retained on the Past member list and you can see when and why they left, so those details are not 'totally removed' from the group. Some details will also appear in the group's Activity Log too.

In 2016, the EU adopted the General Data Protection Regulation, which came into force in 2018. Among other things, this Act in Article 17 stipulates that "The data subject shall have the right to obtain from the controller the erasure of personal data concerning him or her without undue delay and the controller shall have the obligation to erase personal data without undue delay ".

GIO's Terms and Conditions say the same things.

Are there any technical tools in GIO that past subscriber can easily use to do so?

Regards,

Gregory

Get well soon.

The beta group welcomes your participation. When you post messages to the group, please observe these guidelines:

• Hashtags are required for new topics. Members of this group can apply these hashtags:
  
  
  • #bug (for describing a bug in the Groups.io service)
  • #meta (for suggestions about this group)
  • #misc (for topics that do not fit another hashtag)
  • #suggestion (for suggestions of improvements to the Groups.io service)
    

    
    If you’re not sure which hashtag to use, apply #misc. (The descriptions are on the group’s Hashtags page as well as in the list of hashtags when you create a new topic on the group’s website. Be aware the Hashtags page lists additional hashtags that are restricted to moderator use only.)

• All new topics are moderated. Therefore, if your message creates a new topic, expect a delay before it is posted to the group.
  
  
• When posting bug reports (#bug hashtag), include as much detail as possible to aid Support in reproducing the issue.
  
  
• When posting new feature requests (#suggestion hashtag), include as much detail as possible that explains why you think the feature is needed or what problem it would solve.
  
  
• Replies to feature requests should be:
  
  
  • Polite, helpful responses pointing out existing features that already do what was requested (the original poster might not know there are other ways to accomplish what they’re asking for)
    or
  • Polite, constructive suggestions for improvements to the original feature request
    or
  • Polite, descriptive arguments against the feature that explain how it could actually have a negative effect
    
    Avoid posting negative replies such as “I wouldn’t use this” or “I don’t see how that’d be useful” or “That would cause a mess,” etc., which are not helpful to anyone. Disagreement is fine, but please keep it (a) polite and (b) focused on improving feature suggestions. Don’t just shoot down ideas. Keep in mind that everyone just wants to make the service better.
    
    
• When replying to a particular topic, take your time: try to consolidate your thoughts in one message, and proofread the message before posting it. Please do your best to avoid sending multiple individual replies in rapid succession to include additional thoughts or to correct typos.
  
  
• Above all (to quote noted philosopher Bill S. Preston, Esquire): "Be excellent to each other."

On Wed, Nov 30, 2022 at 05:52 PM, Grigorii Semenov wrote:

localisation of subscribe process is vital due to legal requirements, not just because of comfort and convenience.

When you start using Groups.io you agree to the Terms of Service. If they are not legally acceptable to you in your location, then perhaps an alternative platform that meets your requirements would be best at this time.

Same applies to unsubscribe: former customer must be explained that they are leaving the group, now further messages will be delivered to him/her and the address will be totally removed from the group's database.

If a member unsubscribes from a group, they will still have a Groups.io account, they just won't receive emails from that group any more. If you have a Premium or Enterprise group, details of past members are retained on the Past member list and you can see when and why they left, so those details are not 'totally removed' from the group. Some details will also appear in the group's Activity Log too.

Regards
Andy

 

Hi Mark,

Take it easy and please get well soon.

Cheers,
Christos

Mark . . .

On Wed, 30 Nov 2022 09:51:28 -0800, "Mark Fletcher" <markf@corp.groups.io>
wrote:

The cold I've been fighting since Monday has turned into covid. I made it almost 3 years before getting it.

Whatever you do, don't overwork yourself, and take care of yourself while you
fight it off.

Both of us have avoided it so far, fortunately.

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

Mark -
Thank you for slowing down and dealing with this. From personal experience I will warn you to watch out for atypical symptoms. For what it's worth, I understand vitamin D3 and zinc help slow replication of viruses. It's worked for me, but Your Mileage May Vary.

I pray that your family avoids it and you don't have any severe or lasting symptoms. Take good care of yourself!

Dano

Mark,

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

Hi All,

The cold I've been fighting since Monday has turned into covid. I made it almost 3 years before getting it. I'm vaxxed and boosted, and it's not bad so far. But I'm going to take it easy while I recover. Expect email responses to be slower than normal, and the next #changelog will now be posted on Friday, December 9th.

Thanks,
Mark

Get well soon!

Best,

Glenn

Hello everyone,
As a resident of a non-English speaking country in Eastern Europe, I'd like to make my contribution about language localization of GIO. In my opinion, localization should begin with subscribe/unsubscribe processes. Let me illustrate this with my own example.

I am running (well, actually, just starting!) a group for a local condominium. Laws about Internet privacy in my country are famous for the broad wording and uncertain, ambiguous definitions. In essence, any new subscriber must be explained in their native language what exactly they are doing. They are giving their personal email address to someone and this someone will start using this address to send something to subscriber. Any misunderstanding may result in subscriber's frustration, telling that he/she was fooled by a foreign language text and is now being spammed.

When  someone tries to subscribe to any GIO group from an email, completely unknown to GIO, they will receive the standard message in English, asking them to reply and confirm subscription. This mechanism and this message is hard-wired into GIO platform and can not be edited or replaced by owner/moderator.

After receiving some help from GroupManagersForum (thanks, Duane!) I implemented a bypass: made the group Restricted and created Pending Membership message in my own language. But this is a poor solution: angry subscriber may clam that they have already supplied their address in exchange of an uncertain explanation in the language, they don't really understand... You know how severe may be punishment for breaking privacy laws...

Sorry for the long story, but I wrote this to explain that localisation of subscribe process is vital due to legal requirements, not just because of comfort and convenience. Same applies to unsubscribe: former customer must be explained that they are leaving the group, now further messages will be delivered to him/her and the address will be totally removed from the group's database.

Will be grateful for any thoughts on this topic!

Regards,
Gregory