GitLab 1275 - https://about.gitlab.com/company/team/
1,483 karma · joined September 7, 2012
[ my public key: https://keybase.io/stedaniels; my proof: https://keybase.io/stedaniels/sigs/aTqjvGTx-EbsRDrgqT7BxOJiW24ao8WKISx1X8Aq6aA ]
GitLab 1275 - https://about.gitlab.com/company/team/
Cheers
Watching individual user sessions from session recordings provides more depth, but you are still missing out on great swathes of information.
Analytics and session recordings don't give anything near as much concrete data as taking the time to engage with your users. You then use analytics to confirm behaviour.
Cloudflare can explain it much better than me.
From the article:
> Accessing the Endpoint
> The endpoint, which serves a tool called spectrum analyzer, uses a websocket for communication with the graphical frontend displayed in a browser. Whereas CORS would restrict access to such an endpoint for HTTP requests, websocket is not protected by this protocol. Therefore, it is up to the server to verify the relevant request parameters added by the browser. Because these parameters are never inspected by the cable modem, the websocket will accept requests made by javascript running in the browser regardless of origin, thereby allowing attackers to reach the endpoint. It should be noted that the exploit is not limited to run in a browser. Any place where running code can reach an IP on the local network, can be used to exploit Cable Haunt.
# It's slow, each page load and column sort is 1.7+ seconds.
# It only sorts in increasing order, not decreasing, and if you'd want only one direction you'd likely want decreasing for followers and Alexa rank.
# Categories (Regions, and Platforms) should be faceted, to keep the UI tight consider the pattern employed by Excel for picking column filters.
# URL and Twitter should be sortable.
# Whole and filtered lists should be exportable to CSV.
Whilst these are all UX related, the last one for content.
# Add a "Type" column, this could differentiate between the type of site: "News", "Directory", etc.
This is all possible with a sprinkling of JS, no need for heavy server-side stuff :-)
I hope my partially unsolicited feedback is useful, have a great day.
I do have touchbar envy! I tend not to look at my keyboard too much on desktop, but when on a laptop it's definitely in my peripheral vision and would hopefully encourage me to learn it's shortcuts. There's a lot of UX work involved to make it all work perfectly though. App's especially, shouldn't just use the touchbar, they should make it easier with visual in app reminders about what's down there. They should do this with the standard FN-keys too for us non-touchbar folk. I'm a big fan of having keyboard shortcuts shown on screen UI's.
There's no denying it can do more in than Fn-keys.
I think what the touchbar brings is always active tutorial/reminder as to what's possible with the touchbar. Due to it's very nature you don't have to be taught what's on there, you can see, you then don't have to remember/rely on building up muscle memory.
I imagine it sucks for accessibility. I'd still want one before my faculties faulter, I imagine I'd get some use out of it with my IDE.