That 30-day expiration is unnecessarily inconvenient.
The ¡®login link¡¯ is nothing but a temporary password - it expires.
One way to think of this expiration is that it is similar to a motion detector (or garage door opener) light - it only lasts for a pre-determined amount of time. Groups.io has chosen 30 days (or when you delete its cookie) whichever occurs first.
If you think it should be for a different amount of time, make the suggestion on the beta group email List.
Why not create a (permanent) Password, it takes less effort than getting a ¡®login link¡¯ twice.
Once you log in with a ¡®login link¡¯, go the additional step to create a (permanent) Password.
I also recommend allowing your devise to remember it, along with writing it down.
Of course you can still always request a new ¡®login link¡¯ every time you forget it.
I totally get that most of my users don¡¯t want to ¡®risk¡¯ going to the website - they don¡¯t understand it and are afraid of doing ¡®something wrong¡¯ and screwing it and/or their computer up. However as Group Owners we need to experience and understand the web side of Groups.io to at least be able to help our Subscribers (email only users) and Members (email and web users) with the basics and features our groups use.
I purposely have restricted use of a number of features because they are unclear, confusing, or cause other features to change, appear and/or perform differently; namely: Subgroups, Polls, and Hashtags. I do use the Calendar and have enabled the Directory even though they need improvements. Databases and Wiki also seem to have functionally quirks. I¡¯m not a Chat fan as I¡¯ve experienced it elsewhere (Company and Utility websites) so we have not used Chats either.
Groups.io is a young, still developing service which functions better than YahooGroups has for years, and we can use it free. I believe it can and will improve, Management (Mark) follows the beta groups discussions and is actively working on fixing, improving, and adding functions - announcing changes at least once a week and asking for feedback.
Michael Pavan