Mark Vacation

When:
Monday, 23 April 2018

Description:

I will be on vacation starting Monday, April 23, returning on Thursday, May 2nd. I will be monitoring the site as normal, except for a few times when I'm on planes or otherwise out of cell/Internet coverage. During those times, a friend of mine will be monitoring the site.

Replies to support emails will be delayed during this time. Also, group transfers will be delayed as well.

Meltdown/Spectre patching #downtime

When:
Thursday, 10 May 2018
5:00am to 7:00am
(GMT-07:00) America/Los Angeles

Description:

The final patching required to protect against the Meltdown and Spectre vulnerabilities will require downtime on May 10th, starting at 5AM Pacific Time. Two hours are allocated for the downtime, but hopefully it should be completed in much less time than that.

Email sent during the downtime will be queued and sent when the site is back up.

Message history table is for me the first part of stats about groups.
I like to see:

1. Number of topic by months
2. Total numbers messages or topics by year
3. Number and graph of message "+x message this week (+xx %)" " +x this yesterday (+x%)

On Sat, Apr 14, 2018 at 08:07 am, toki wrote:

On 04/14/2018 12:57 PM, Arno Martens wrote:

What if the TOS spells out that by posting anything in an IO group the
creator explicitly consents to sharing the content on a non exclusive, non
commercial basis?

GDPR requires explicit consent. Putting statements as above into Terms
and Conditions is not explicit consent.
jonathon

If users are permitted to upload Files and Photos maybe somewhere a request could be made to send a message to the group+owner, giving explicit consent to sharing the content on a non exclusive, non commercial basis, before being allowed to upload.

This would require an administrator setting, similar to he moderation permission.

Changes to the site this week:

• CHANGE: Change the URL sort for database tables to sort by title first, then URL, then description.
• INTERNAL: Upgraded to Font Awesome 5.
• NEW: For premium groups, you can now lock groups/subgroups, making them read-only.
• INTERNAL: Updated the Stripe API library.
• CHANGE: Instead of changing the Message-ID for all recipients, we now only change the Message-ID for the original sender.
• CHANGE: Formatting changes to the view event page for events with RSVPs.
• BUGFIX: We didn't recognize RSS feeds that were served to us in non UTF-8 format. We now fetch feeds and specifically convert them to UTF-8 before passing them off to the feed parser.

Have a good weekend everybody.

Mark

Mark, I think you missed one. Netzero emails contain a lot of spam at the bottom. Thanks.
--
J

 

Messages are the sole opinion of the author, especially the fishy ones.

I wish I could shut up, but I can't, and I won't. - Desmond Tutu

On Sat, Apr 14, 2018 at 06:12 am, William Finn wrote:

But you are missing the main reason this is being added .... content migrated from Yahoo is assigned to the migrator as the owner so reassignment of ownership is needed.

Is that so? If it is then why did your post which started this Topic read as follows:

It would be nice to have the ability to change ownership on files, folders and photo albums as people change roles and if the data is for a specific role in an organization then assigning a new owner would mean we wont have to open up access to all members of a group.

Please tell because you have got me a bit confused, and others might feel the same.

Chris

Maybe there should be something in the TOS similar to the restrictions for minors. To wit, people in jurisdictions where the relationship of the government to its subjects is essentially that of parent to child should be prohibited from subscribing.

Drew

On 04/14/2018 12:57 PM, Arno Martens wrote:

What if the TOS spells out that by posting anything in an IO group the creator explicitly consents to sharing the content on a non exclusive, non commercial basis?

GDPR requires explicit consent. Putting statements as above into Terms
and Conditions is not explicit consent.

jonathon

On Fri, Apr 13, 2018 at 09:42 pm, toki wrote:

GDPR doesn't prohibit sharing content, provided the creator explicitly
consented to sharing the content, and the content is correctly attributed.

I am not a lawyer. This is not legal advice.

What if the TOS spells out that by posting anything in an IO group the creator explicitly
consents to sharing the content on a non exclusive, non commercial basis?
Arno

Mark; we often come up with suggestions for changes on this forum, and it isn't always clear if those suggestions or requests are going to go on the "to do" list or not.

Can I ask that there be "Moderators Only" Hashtags showing #Pending & #Done that can be added to a topic once its merit has been assessed; this would give us clear sight of something that is now "on the list" and something that isn't. (I suppose there might also need to be a #No_Chance tag as well!)

Obviously some proposals are more important than others, some more urgent, some easy and some difficult and time - consuming, and of course others right down (say) pointless.

If this could be done we would know that action was in hand, even if a completion date might be some time into the future. It would prevent good ideas and suggestions disappearing into a sort of black hole

Regards,

Chris

(Sent in Hope...)

On 04/13/2018 11:19 PM, William Finn wrote:

You must also consider that context t stored on here are not official
versions of the documents and that they are published on here as a convince
copy of the items posted to be generally shared.

Official or not doesn't matter. Incorrect attribution is, at best, a
copyright violation. If somebody requests all content relating to them
to be deleted, and something is incorrectly attributed, resulting in it
not being deleted, you just broke both GDPR and Copyright Law.

Mark has plans to meet with his legal team to identify the effects of such regulations on groups.io.

He's got just on forty days to get Groups.IO in full compliance with
GDPR. Might be a bit late to do so.

Also if such regulations does prevent such sharing then Yahoo, Google and
every other forum, group service will have to shut down. This we know wont
happen.

GDPR doesn't prohibit sharing content, provided the creator explicitly
consented to sharing the content, and the content is correctly attributed.

I am not a lawyer. This is not legal advice.

jonathon

On 04/13/2018 10:24 PM, William Finn wrote:

How about doing it at a folder level and the rights propagate to all containing files and sub folders

_Right of Attribution_, which is part of EU law on copyright, comes into
play here. You can't arbitrarily remove the name of a creator, from
their work. The definition of "work" is intentionally broad, and vague.

As a second point, GPDR compliance requires that changes be done within
five working days (Estonia). Ireland, with thirty days to comply,
appears to be an outlier.

If done at the folder level, the only legally acceptable solution I can
see, is that an individual can only upload material into a folder they
own. Two immediate consequences are:
* No more shared folders;
* No content outside of a folder;

Both _Right of Attribution_ and GPDR apply, regardless of the format of
the content/data in question.

I am not a lawyer. This is not legal advice.

jonathon

My group just got a question mark for a photo. Not sure whether the photo was attached or included in the message. It looks like this:

This is him enjoying the sun :-) 

--
J

 

Messages are the sole opinion of the author, especially the fishy ones.

I wish I could shut up, but I can't, and I won't. - Desmond Tutu

I would have 0 members if I asked for a last name. There are many reasons this is not feasible for everyone.
Cacky