|
Andy,
Looks like it. TeaneckShuls had over 10,000 at the time of its move. If there's a larger it is unlisted. ?
I don't think so.
Not since Mark upgraded the servers from the 80286 based models... ;-)
It does not, except for Photos that happen to be stored in the Files section. There's a separate count of Photo + Attachment space at the top of the Albums tab in your Y!Groups Photo section. That one is usually the factor that hits groups -- it caught me off-guard in transferring my group of classmates because the total shown by Yahoo is way off - it failed to include at least one album with hundreds of direct-from-camera originals (Up to 4k x 5k resolution) that itself totaled over 1 GB. The transfer agent put my transfer "on pause" and emailed me to ask what to do about it. Setting a max upload size of 2k x 2k brought the storage under the limit without affecting the images noticeably. ?
No. But depending on how you handle things, they may not know they have access until it is done -- Groups.io's default "You've been added" message and your Groups.io group's Welcome member notice won't be sent to the copied members until the entire transfer is complete. So one possibility is to tell your members to wait until they receive those notices. The groups I've personally been involved with transferring have been much smaller, so my perception was that there was very little "window of opportunity" between when members were copied in and when the notices went out, signifying that the rest of the content was in as well. ?
Yes, message posted to the Y!Group after the transfer agent collects its messages will be orphaned on the Y!Group. I know member addresses (subscriptions)? are copied into the Groups.io group before any of the content of the group, but I don't know in what order things are gathered from the Y!Group, there could even be some parallelism involved. Whether that's a problem or not depends a bit on how your group operates. If most members read and post by email they may not notice much except the change to the addressing and footer formatting of the messages.
The automated process does retry, but it has a limit and some items may still not be copied over. ?
You, at the email address you used to sign-in when you initiated the transfer, will receive a summary email at the end of the transfer. It will have statistics about how much made it. ?
Some members here have commented about their experiences with that here. In my groups the only missing content were some database rows that had invalid content. ?
I'm not sure what you could do. Mark (er, the transfer agent) will likely get involved if the automation runs into any issues. ?
The only irreversible setting is choosing to make your group's Messages section "private" (available to members only). So that's one thing you'll want to decide upon before starting the transfer. Another thing to think about is whether your Groups.io group will want to use the Subgroup feature. If you do you probably want to create at least one before starting the transfer - that has the effect of changing the email and web address format for your group. ?
I did, but I don't really know if it was needed. That is, I invited the mods and co-owners of my Y!Group into the Groups.io group soon after I created it, and well before discussing the move with the Y!Group membership. We kicked the tires a little, but there's not really much learning curve to day-to-day group management chores. One thing that is different is how moderation for new members is handled. In Y!Groups there was only a group-level setting to cause new members to be put on moderation. In Groups.io there's that plus a count of messages and a companion state of the member's Posting Privileges. Together those implement an automation of removing members from moderation after you (a group mod) approve N consecutive posts from the member. N is a group setting that appears if you select New Member moderation. But in particular, members of your Y!Group whose Posting Privilege is currently set at "Override - Posts are moderated" will copy over with the equivalent privilege in Groups.io, which is an indefinite state. Meaning that they will not be handled by the new member automation - even though that may have been why they had that setting in the Y!Group - and if you later wish to take them off moderation you'll have to do that manually, just as you would have in the Y!Group. Shal -- Help: /static/help More Help: /g/GroupManagersForum/wiki Even More Help: Search button at the top of Messages list |
Shal Farley