xeyecle - product stuff

In short HTTP to HTTPS redirects aren't always configured. Solution options: Browsers should change resolving to HTTPS first, when unspecified! perhaps then attempting HTTP as a fallback. #upForDiscussion Chrome extensions that : " As a browser that has received a failed HTTP response (ERR_EMPTY_RESPONSE*), I would like myself (the browser) to resolve to try the same path with a secure path instead (HTTPS), so that my pages that don't have an apache redirect to HTTPS will work without my banging my head on the wall. " In longer Many systems today use (and should use!) HTTPS for web communication.  The browsers today, though, still try attempt HTTP first when resolving a request for, say, www.xeyecle.com...  but *sometimes* there are servers out there that don't have a REWRITE condition on their servers, nor a 301 redirect at the Nginx web server level...  and sometimes the groups that own these items are <insert legitimate, rude, or ignora...

Behold - the double preview! Solution Look for duplicate content in the og:title, og:description and prevent double posting or, simpler yet: Only create a Link Previews for the first url in a message.  More on this topic yesterday - https://www.xeyecle.com/2018/07/zoom-url-previews-in-slack-guide-to.html 

In short Companies should care about how URL previews look. Specifically Zoom should update their /{letter}/ meeting URLs to have concise 'meta og:description' properties and horizontally-rectangle 'og:image' assets, so that Slack users (or just me) are happier. before | after In longer ~319px height preview Slack has a feature that I've contemplated quite a bit, both internally with colleagues and with my own thoughts. The feature is Link Previews , which build a preview of a URL (if publicly available*) so that folks can see what they may be clicking on (or not!). Other sites do it too, like Facebook. Anyhow, while I like this feature overall, there are some companies that don't (know to) manage this for the ever expanding 8MM active daily users of Slack**.  I emphasize FOR these users, because they indeed are a powerful usergroup whose use case is important. The example that was the catalyst for my writing this is Zoom . Zoom, i...