On Fri, Jan 17, 2020 at 10:36 PM, Laurence Marks wrote:

A favicon is a 16x16 pixel icon, sometimes packed with a 32x32 pixel icon (and rarely a 48x48 pixel or larger icon) into a file customarily named favicon.ico. Browsers display this icon on tabs open to their website. See the date-on-shield on a Google Calendar tab, or the rainbow-colored suitcase on eBay's tab.

There are dozens of online free favicon generators that pack the multiple images into an appropriate file, easily enough for a novice to use.

Has any thought been given to accommodating user-provided favicons? 
--
Larry Marks

Larry,

I am curious as to how this would be used.

As far as I can tell, GIO pages already have a favicon. For example, I bookmarked the page with your post. Here is how it shows up as in my bookmark manager in Chrome.



If you don't like that icon, you can change it. For example, there is an extension for the Chrome bookmark manager to change the icon. I've also used this feature in other browsers.

https://beebom.com/how-change-bookmark-icons-chrome/
 
--
Gerald

>>>
Is is possible that you can adjust the column widths used on the Members List to provide more space for the email address and status flags? "Delivery" and/or Applied" are far wider than they need to be.
<<<

I also would like this to be implemented, I've run into similar display issues when doing member maintenance.

As an FYI, Rick also asked for the same thing in another thread, https://beta.groups.io/g/main/message/23641
in case we may want them to be merged.

Cheers,
Christos

Changes to the site this week:

• BUGFIX: Fixed a deadlock issue in some cases during confirmation via email.
• INTERNAL: Addressed some technical debt around the calendar code, and in the process fixed two timezone conversion bugs in ICS feeds.
• API: The message object now has an attachments array.
• BUGFIX: The your subscription is not yet approved banner was appearing one page refresh too late.
• BUGFIX: Edit buttons were missing from the Hashtags page.
• API: The docs for /createhashtag incorrectly stated that description was required.
• BUGFIX: Fix crash when sorting a database by a column that no longer exists.
• BUGFIX: The user was not being displayed in Message rejected from not confirmed member activity log lines.
• API: /downloadarchives now supports start_msg_num parameter.
• NEW: When downloading archives either through the API or through the export group function, each message now has a X-Groupsio-MsgNum header with the message number of the message.
• API: /newdraft now supports draft_type_dm.
• NEW: Include descriptions in the list of hashtags on the New Topic page.
• APP: Created new App subgroup and got approval from Apple for the first test version of the app.
• BUGFIX: If a pending member was rejected on the group member screen, they were marked as Removed in the Past Members page, when they should be marked as Rejected.
• BUGFIX: The API call /directadd wasn't returning full member_info object information.
• CHANGE: Increased concurrency of the process responsible for handling email delivery status updates because it was bottlenecking email delivery due to our ever increasing email delivery numbers.
• BUGFIX: We were not handling emails with header lines that weren't properly capitalized correctly.
• BUGFIX: Editing a malformed message imported from Yahoo that was missing a body didn't work.
• CHANGE: Removed Facebook Integration from the group Integrations page.
• NEW: Added additional checks for our DNS servers to ensure that we catch any DNS issues.
• NEW: Added new Messages that start new topics are moderated group moderation option.

Have a good weekend everyone.

Mark

On Jan 17, 2020, at 9:36 PM, Laurence Marks <marks@bellsouth.net> wrote:

A favicon is a 16x16 pixel icon, sometimes packed with a 32x32 pixel icon (and rarely a 48x48 pixel or larger icon) into a file customarily named favicon.ico. Browsers display this icon on tabs open to their website. See the date-on-shield on a Google Calendar tab, or the rainbow-colored suitcase on eBay's tab.

There are dozens of online free favicon generators that pack the multiple images into an appropriate file, easily enough for a novice to use.

Has any thought been given to accommodating user-provided favicons?

Do we really trust or want these...


"Due to the need to always check for it in a fixed location, the favicon can lead to artificially slow page-load time and unnecessary 404 entries in the server log if it is nonexistent.[6]

The W3C did not standardize the rel-attribute, so there are other keywords such as shortcut icon that are also accepted by the user agent.

Favicons are often manipulated as part of phishing or eavesdropping attacks against HTTPS webpages."
https://en.wikipedia.org/wiki/Favicon#Limitations_and_criticism

A favicon is a 16x16 pixel icon, sometimes packed with a 32x32 pixel icon (and rarely a 48x48 pixel or larger icon) into a file customarily named favicon.ico. Browsers display this icon on tabs open to their website. See the date-on-shield on a Google Calendar tab, or the rainbow-colored suitcase on eBay's tab.

There are dozens of online free favicon generators that pack the multiple images into an appropriate file, easily enough for a novice to use.

Has any thought been given to accommodating user-provided favicons? 
--
Larry Marks

Michael,

I am not in disagreement, I just thought I would try to "herd" the requirements into a summary. It seems that a lot of the topics go back and forth. I like to see the process ending up in a convergence.

-- 
Gerald

On Jan 17, 2020, at 4:15 PM, J_Catlady <j.olivia.catlady@gmail.com> wrote:

On Fri, Jan 17, 2020 at 01:10 PM, Michael Pavan wrote:

unless it is a Restricted Membership group with an active Pending Subscription Member Notice, then it should say:
"Your request to join this group may expire in 14 days if you do not reply to the <Pending Subscription Member Notice's name>"
Good idea in theory, but I would not add that, even if there is an active pending notice, because even if there is one, it may not require a response. It's conceivable that some groups simply send a pending notice informing the member that they are acting on the application in some way, shape, or form, possibly giving out some interim info, etc. Their membership decision may or may not include responses from an emailed questionnaire.

Good point, as there currently is not a good feature to require answers for applicants.
The current Pending Member feature is used by some as an "Additional Information to join required" while others use to provide "Additional Information to applicants"

This reaffirms that there needs to be an additional Member Notice type created so that the 'opposite' uses are no longer commingled, which would support the additional clarity needed in the 'confirmation-request', and a better applicant screening process than current cumbersome workarounds.

On Fri, Jan 17, 2020 at 11:27 AM, Bill Hazel wrote:

Each choice should be adequately defined since not everyone is a nerd.

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

Whoops. Didn't mean to send that blank reply to Bob's message (I completely agree with everything he said).

Mark

On Fri, Jan 17, 2020 at 01:10 PM, Michael Pavan wrote:

unless it is a Restricted Membership group with an active Pending Subscription Member Notice, then it should say:
"Your request to join this group may expire in 14 days if you do not reply to the <Pending Subscription Member Notice's name>"

Good idea in theory, but I would not add that, even if there is an active pending notice, because even if there is one, it may not require a response. It's conceivable that some groups simply send a pending notice informing the member that they are acting on the application in some way, shape, or form, possibly giving out some interim info, etc. Their membership decision may or may not include responses from an emailed questionnaire. 
 
--
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

Gerald,

On Jan 17, 2020, at 12:33 PM, Gerald Boutin <groupsio@infinichron.com> wrote:

Perhaps there should also be two other pieces of info:

1. Timeout: Specify how long before this expires

Yes, but will would-be subscribers understand:
"Your request to join this group will expire in 14 days, unless you request has been claimed by a group Moderator or Owner"...

I'd like to see it say:
"Your request to join this group may expire in 14 days"
"Please address any questions to: <GROUPNAME+owner@groups.io>"

unless it is a Restricted Membership group with an active Pending Subscription Member Notice, then it should say:
"Your request to join this group may expire in 14 days if you do not reply to the <Pending Subscription Member Notice's name>"
"Please address any questions to: <GROUPNAME+owner@groups.io>"

*I'm not sure if "Please address any questions to: <GROUPNAME+owner@groups.io>" is already included - I didn't create a new (unknown to Groups.io) email address to test this.

2. Not you: What to do if you didn't want this (eg - ignore)

Already happens, it says something like:
"If you are not interested, or if <yourname@yourdomain> is not your email address, please ignore this email."

Michael

On Fri, Jan 17, 2020 at 01:27 PM, Bill Hazel wrote:

(No default selected)
If no choice was made, when saving the settings, the default would be opt out.

That doesn't make sense to me.  If there's no default, the default becomes opt-out?

Duane

What I hear is that we all would like not only a system for inputting change requests but a method of tracking them and, when they are complete, a simple way to know they are completed.

That's all good but what's missing from it from my perspective are some other steps;

• Each issue/bug  that Mark accepts could have the subject modified with a Hashtag of "Bug"  followed by a number that is a unique ID, e.g. "#Bug 5385", that indicates Mark has decided to  work on it.  That would give us simple way to keep track of what's in process and what's not.
• When Mark considers the Bug/Change/Whatchamacallit complete, one or more authors of the request would be informed by Mark and allowed to perform Testing which would include a review summary of the proposed (changed) documentation
• When complete the testers would issue a final Signoff reply, adding a #Complete or #Reject reply message.  (or whatever is decided for hashtags)

Documentation of how the change/feature works is desirable and a link to that documentation should become part of the information provided when the item is signed off by the testers.  
This doesn't preclude hashtag use for each  step but assigning a number makes searching/tracking progress much easier.

l'm sure Mark tests his changes but no one person or group can possibly cover every variation.
--

Bob Bellizzi

Our group requires someone to tell us something about why they are interested in our group before we approve.  Member notices are active and edited appropriately and are sent to them explaining what we want to know, and to explain that they must reply to the email as this part of the process is automated.  All notices are working as verified by my testing.   However with the folks who request to join via the web days go by before people respond if at all.  Many just age out after 14 days.  I have a test ID that I use to subscribe and unsubscribe to see what happens as well as testing what users see with various email options.  I used that to subscribe via the web and the response page from groups.io does NOT mention that they should check their email as some groups require a response via email before they can join.  Could that be added to the response page?  It appears that many people don't use email much and rely on the web interface to read messages.  It might also be helpful to move them to a page where they could fill out their response immediately but at least a notice to check their email.

I agree that a member search function is needed.

As far as the opt in/opt out debate, I would think that would be a group's decision.

The way I would handle it is to make the Owner/Administrator choose between an empty radio button choice. (No default selected)
If no choice was made, when saving the settings, the default would be opt out.
The reason I say empty would, I think, subconsciously make the Owner/Administrator at least think about it.

Each choice should be adequately defined since not everyone is a nerd.

>>>On Fri, Jan 17, 2020 at 02:17 PM, J_Catlady wrote:

On Fri, Jan 17, 2020 at 11:14 AM, Ken Kloeber wrote:

NO, C's method does not create a tag on the individual message.  And the 1st line above doesn't make logical sense anyway.  One cannot tag an individual message by creating a new message. 

If effectively does this by creating a new thread out of the single message, as I explicitly said.
. <<<

As I've lamented before - left coast reasoning.  LOL.   G explicitly stated (and I believe that J and C are missing that point) -- NOT add a tag to a Topic.

On Fri, Jan 17, 2020 at 11:20 AM, Ken Kloeber wrote:

no one cannot currently add a tag to a msg body.

Of course not, which is the point I've been trying to make from square one. You are adding special symbols to imitate or effectively create a tag. I'm giving you kudos for the creativity. Don't put it down.
 
--
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

>>>On Fri, Jan 17, 2020 at 03:57 AM, J_Catlady wrote:

Of course you can add tags to message bodies<<<

PS - no one cannot currently add a tag to a msg body.  One can add or edit some text into it that could later be searched on, but that is not adding a hashtag from a defined set, using a function (pull down, or radio button, or whatever feature/function would be added to gio to accomplish this.)  By that reasoning, one does not need any gio function that adds hashtags to a Topic, one could always instead add some text string that could be searched on later. 

On Fri, Jan 17, 2020 at 11:14 AM, Ken Kloeber wrote:

NO, C's method does not create a tag on the individual message.  And the 1st line above doesn't make logical sense anyway.  One cannot tag an individual message by creating a new message. 

If effectively does this by creating a new thread out of the single message, as I explicitly said.
Your method of inserting special symbols into an individual message may be useful but I think falls short of Susan's original request. That's for her to say. 
 
--
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