Digital Rage cover logo

36 | Jeff Byer – Chrome Dev Tools, Shopify, CCPA and Tech Talk

43m · Digital Rage · 04 Nov 13:05

Today Jeff Byer (@globaljeff) talks about his experiment with workspaces in Chrome Dev Tools, the Shopify universe, upcoming project launches, real-world project issues, and tech talk.

Show Links

Chrome Dev Tools - Workspaces https://www.hongkiat.com/blog/google-chrome-workspace/ CCPA - https://oag.ca.gov/privacy/ccpa Fact Sheet, pdf

Transcript

Jeff Byer    00:06    Welcome to digital rage, the podcast about all things internet and the people that make it great. My name is Jeff Byer and I know last episode I have promised you guests but uh, that didn't happen. You know, people are busy, things are happening and uh, you know, just didn't get around to it. I did have an interview scheduled, we had our <inaudible> in our call  

Jeff Byer    00:30    and there was a misunderstanding. This a, I believe a the person involved was expecting some sort of a uh, you know, get to know ya. Uh, cause I sales call and I was expecting it to be an interview. So a little bit of a miscommunication. But um, anyway, I do have a ton of things to talk about. So this will be an episode full of stuff. I like to say stuff because some of it is crap set of, some of it's not. So let's get right into it. First thing is I was playing around and in Chrome and, and the dev tools and just futzing around and came across the workspaces in dev tools and thought, okay, this is interesting. Why would, why would they have a, you know, invite somebody to put their file structure inside of Chrome dev tools if it doesn't actually make any live, live edits as you go.  

Jeff Byer    01:41    Because as most developers know, whenever you get to a live website and you go into dev tools, you can modify all of the code you want and change the display of, of that website. You know, change the content, anything you want, run experiments, even if it's not your site but only you can see it. And as soon as you close dev tools or refresh the page, all those edits are gone. And it goes back to the way it is on the live server. And I do use that sometimes to one. If I'm trying to get a screenshot and I want to modify things for the actual screenshot, I'll go in, remove modules, remove ads and stuff like that. But on my own sites, I use it just to play around and see, you know, if there's something visually or content wise that I want to accomplish, how fast it would be to make that adjustment and just kind of play around in dev tools before I open up, uh, you know, my editor editing environment and go ahead and go through with the change.  

Jeff Byer    02:45    It also helps me to, to create estimates on what it's going to take to accomplish certain things requested by my client. So I get into this and I've read a couple of articles and I go through the Google tutorial on how to use Chrome tools and the whole time, uh, I'm going through these tutorials and obviously it says, okay, you know, it's, you'll be able to save the changes if you use it in, in your local environment and you add your local pho folder for that environment. So I was like, okay, that's fine, but it, uh, it's very limited and uh, I didn't see any way if you are going to use a SAS or any type of, of pre compiler that it just didn't have a way to really integrate those unless you had another third party script going. So the whole time I'm going through this tutorials, like who the hell would use this?  

Jeff Byer    03:47    It's just basic. If you had a basic site with no preprocessing prop, pre-processing, no minification and uh, just static something, I don't even know what, um, that's what you'd use. So I went down a rabbit hole on that and found myself completely disappointed. So moving on. Um, so today I added another team member to my Shopify partner program. Uh, another developer that's going to help me launch these two big projects that we're launching this month. And so the month of November is going to be a huge month here for us. And so we needed to bring on extra help. And the way Shopify partners, the partner system on Shopify works is that if, uh, I'm going to take on a new client that has an existing store, I go find the existing stores, my Shopify address, then I request access to that through my partner portal. And then the owner of that store is able to verify and then, uh, I get, I gain access through the partner portal.  

Jeff Byer    05:05    If the customer just puts in my email address and sends me access, even if it's the exact same address, it does not, uh, it's not available in my portal. So it's, uh, it's just a little quirky thing. I'm sure there's plenty of reasons on the back end or privacy issues or security issues or anything like that that, that takes that into account I guess. Because you know, anybody can put in anybody's email address and then you can accept and, and, but not really have access. I don't really understand the details of why it's separate, but it's separate. So, um, with adding a new team member, um, you know, I take privacy and my accounts very, very seriously, especially when hiring outsourced developers. So I create account specific for them, you know, server accounts, user accounts, things like that. And for this one, um, the developers first request was just to send me the access and what that assumes is that he wanted to log in as me through my account and take a look at everything.  

Jeff Byer    06:20    And that doesn't really sit with me very well, uh, for plenty of different reasons. Obviously security and, and you know, my, my customers who are, the admins can see my logins. And so if something happens while I'm logged in or near anything, it's just, I don't want it on me personally as, as a, you know, possible vulnerability. But the great thing is through the partner program, all of my, all of my accounts are in my partner program and when I log in, it shows that it's my company that's locked in, a representative of my company that's in there doing changes. And that's much better as far as, uh, my clients are concerned and I'm concerned. So the, the great thing was it the easy way to, there's an easy way to add people. You just add staff members to your partner portal, then each of those staff members, you can define their access but then they have access to all of your partners sites.  

Jeff Byer    07:24    And this hire today was not for for one specific type but for three of them that are in my partner portal. And so it was very convenient that I just had to get his Shopify email address, the email address that he uses for Shopify and he now has access to uh, to make changes to all of my customer accounts, which is, which is very convenient for me because it's one single point of access. He can access all of them. Now if something happens or if I don't like the worker or if I'm just moving on to a different developer, remove him and he wrote it, he doesn't have any access to them anymore and if he's going to ask them, access them currently he has to go through my partner portal. So a very cool thing. Uh, just thought that was really interesting cause it's, it's kind of backwards from how you access how you grant access to a customer's store rather than through a partner in, through my company.  

Jeff Byer    08:27    So that was fun. Um, another piece of information, uh, was regarding the, the California consumer consumer privacy act CC P a. So this is coming on January 1st and uh, I'm making sure that all of my, all of my accounts are aware of this and so that they're prepared and know that it's coming. And so digging into the fact sheet of the CCPA, the here's the requirements. So, uh, E not a lot of my customers actually require this, but for the ones that do, I'm just confirming cause I don't know the ins and outs of everything that they do. Uh, I have web stats and that's it. I don't know how the business is run specifically. I don't know revenue numbers cause they're mostly private businesses. But here are the, here's the, the requirements. So businesses are subject to the CCP. A, if one or more of the following, our true has gross Avenue S sorry, I'm having trouble speaking today.  

Jeff Byer    09:47    Let's try this again. If the following are true, has gross annual revenues in excess of $25 million, um, buys, receives or sells the personal information of 50,000 or more customers, households or devices. So that one's interesting because when I first skimmed through it and I said, Oh, buy and sells information, that's, you know, none of my customers do that. But then receives and absolutely all of my customers receive information and checking databases on that information. Is, is only part of what the law entails. This is pretty much everything. So I need to verify that with all my customers because 50,000 consumers on, you know, a site that's been 10 years old, that's a pretty easy number to hit. So, uh, even for a small business, so I'm confirming that, uh, all the information that they have

The episode 36 | Jeff Byer – Chrome Dev Tools, Shopify, CCPA and Tech Talk from the podcast Digital Rage has a duration of 43:20. It was first published 04 Nov 13:05. The cover art and the content belong to their respective owners.

More episodes from Digital Rage

38 | Jeff Byer – Using Descript, Agency Site Review, JAMStack Options

Today Jeff Byer (@globaljeff) talks about using Descript to record this episode and its impact on podcast production, he reviews a new agency website built with Nuxt.js, and he discusses more JAMstack options he is considering for his customers.

Descript podcast software https://spatzek.studio/ https://www.getpostman.com/ https://buttercms.com/ https://snipcart.com/ https://www.apple.com/macbook-pro-16/

Transcript

Digital Rage

 [00:00:00]Jeff Byer: [00:00:02] Welcome to digital rage, the podcast about all things internet and the people that make it great. My name is Jeff Byer, and today we have a special episode because I am testing a new tool. So, this will be a podcast about podcasting and, the technology that I'm using to record podcasts.

[00:00:29] So. Today, we're using D script and I am recording directly into D script. I added my intro music and did a little volume editing and envelope editing there, but, now I'm recording directly into the app. So this feels a little strange. What I'm. What I use for all the previous episodes is I have my, my hardware setup, which I described last time.

[00:00:58] Is my microphone plugged in [00:01:00] to a Scarlet to it, to USB interface. And this now is me talking into my microphone directly into the D script app to downloadable app. they have a great tutorial that teaches you how to go through and get started recording a podcast episode. And editing the text.

[00:01:23] We'll edit the audio, which is really cool. So, as I'm recording this, I don't know exactly how this is going to turn out, but we're gonna go through and, see if we can produce a whole episode within the D script app. Okay. So previously here was my production process. I would set up the microphones.

[00:01:44] So there was a digital input, which had been, internet based, mostly Skype, sometimes Hangouts, and sometimes an actual telephone call through FaceTime. Then that would record as two separate tracks [00:02:00] into logic and logic is a pro audio. A nonlinear editing system or software pro level software for Mac.

[00:02:12] And that's what I use to record a lot of music and music production, things like that. So, I'm familiar with all the pro level tools and I do a minimum amount of pro level audio editing within logic. Very little effects, anything like that. It's mostly raw. I didn't want to, I wanted to make the production of the podcast as simple and smooth as possible so that it wasn't a huge production.

[00:02:40] Time-suck which most podcasts, producers all agree is the best, the best, philosophy, which is make it simple, keep it simple and try and automate as much as you can. So the biggest benefit to D script is that it does a [00:03:00] automated transcript as you'd go. Ah, I can't see it as I'm talking, but it does process it on the backend, and then it will, provide it into this project so that I can edit, once it's all done.

[00:03:14] So back to my old process in logic, I would record both tracks. The one track would be me, the other track would be anything from external resources. So that's where my interviews would show up. And what I usually do would do is do record the intro. Break the audio, put a music over the break so that it introduces the next segment, which is the interview.

[00:03:44] And then we go into the interview. So I have music playing in the intro, music playing at the transition to the section, the new, interview section, and then a outro. Outro music with [00:04:00] my voiceover of, where to find podcasts, notes and things like that. And then I would bounce the whole thing to an MP three file and post it in Dropbox.

[00:04:13] From there. I log into WordPress and create a new episode based on, you know, our naming convention. That's now just the episode number guest, and then a highlight topics, which I, I somewhat use as keywords. And then, upload it into WordPress. WordPress automatically sends it to cast dos, which is our, audio hosting provider.

[00:04:46] Casios will then automatically do a transcription, and then I would create the post. I would put in all the, manual show notes that I had, links and mentions and things like that. [00:05:00] And then on the bottom of the page is the transcript. Now the dose transcript is also automated. And it's not very clean at all.

[00:05:12] And so, I do a little bit of editing on the transcript, but I don't go through the whole thing cause episodes are usually 30 to 45 minutes. And, it's just not efficient for me to go through and read all that text. So I basically take, for the most part, what they give me, paste it into WordPress.

[00:05:30] Set the the schedule to post on Monday morning and that's it. On Monday morning, WordPress will, we'll publish the post. The post will get published to the RSS feed and all of the podcatchers, including iTunes or Apple podcasts now would grab the new episode. From the RSS feed and feed it through their channels.

[00:06:00] [00:05:59] So it's pretty efficient, but still a kind of production heavy. So here is the advantage that I'm hoping is going to be, I'm going to make this process easier if I keep using D script. So I'm hoping that the automated transcripts are better. I'm hoping I can keep this platform as a template so that all I need to do is come in and plug in, you know, new recordings and export them.

[00:06:35] Everything gets saved to the cloud automatically. So, I don't need to worry about, you know, using resources on my computer. And don't need to worry about transferring files from my computer bouncing out to another platform. So, all that said, this is totally experimental and I don't know how this is going to go.

[00:07:00] [00:06:59] So that is that for now. That's why this episode is going to sound a little bit different. And I think next week I will give my. Full rundown on how the experience was and if it saved me any time in my podcast production. So on with the show, a today is going to be more, in real life type of, type of data, things that I've been working on this week that are interesting and hopefully the, audience can, can, speak about and comment about.

[00:07:32] So. First thing is on communication arts. they send, you know, inspiration emails and stuff, and they sent this website for a, a, a creative studio. And the, the website address is spat sec.studio. And so anytime a, a studio or an agency posts a a. A portfolio site. I like to go in [00:08:00] and take a look and see what they're doing.

[00:08:02] So they built this site on Nuxe and the first thing I did is like, okay, perfect. I can see what SEO impact that using knucks directly in, in a live environment is going to do for their SEO. And sure enough, I pull it into SEMrush and there is no organic SEO, nothing cause you can't see their content.

[00:08:27] It is all client side rendered and not server-side rendered. So they're not using a, a static site generator. So obviously Nuxe native, you know, that just confirms that that would not be a good solution for any type of Project that requires some sort of SEO or organic traffic, but that said, I believe that that's not one of their requirements because they are getting a ton of backlinks and a ton of attention from the [00:09:00] design community just based on the design and functionality of the website itself.

[00:09:05] So that's something to keep in mind. for me, since I do sell, you know, their, their agency is strictly creative and my agency is a more functional, real world SEO, building, building functional sites that accomplish business objectives. So they don't necessarily need that. So that being said, they're getting a ton of attention in the design world.

[00:09:29] So they've, you know, they're designers for designers and, and you know, their real world clients are, they look like pretty big brands that don't really need the, the big time SEO exposure. So. Just, a little interesting perspective that I had, based on this site. One other thing that I noticed about this site, it may be just because it's getting a ton of attention right now and, and it's getting a lot of simultaneous users, but it is very slow.

[00:09:59] It takes forever [00:10:00] to load. They've got humongous graphics in there, and I can tell that they did do a good bit of optimization on the images, but it's just, it's totally render blocking. Every page is blank with text that says, loading. While each page and each section is loading. It's actually a one page project.

[00:10:22] They changed the URLs and they have the content structured into different pages and sections, but it behaves as a one page site. It doesn't refresh. It loads asynchronously as you click through the project. So, yeah, that was just intro. A little interesting thing. brings up another point that, Google Chrome is going to start putting badges, speed badges on, on websites.

[00:10:50] So if it's a slow loading page, you're gonna get a little speed badge thing that it's, it typically is loading slow on your specific device. [00:11:00] I haven't seen one yet. I'm going to dig it a little bit further and see if it's actually. W you know, when it's coming out officially and, and when we'll start seeing that I do performance audits on every one of my sites.

[00:11:12]I know which specific sites that I have now that, that do need

37 | Jeff Byer – Backlinks, Memory Hacks, Tech Talk

Today Jeff Byer (@globaljeff) talks about backlinks inspired by the Search Engine Journal Show with Julie Joyce, training your brain to remember inspired by Thomas Oppong, and more tech talk.

Show Links

Julie Joyce on Paid Links, Top Tools, Cheap Link Building Ideas & More [PODCAST] How to Train Your Brain to Remember Almost Anything Rode NT-USB Versatile Studio-Quality USB Cardioid Condenser Microphone MENS GV 005 Samsung QN65Q70RAFXZA Flat 65-Inch QLED 4K Q70 Series Ultra HD Smart TV with HDR and Alexa Compatibility (2019 Model) Rode RODECaster Pro Podcast Production Studio NETGEAR Nighthawk AX12 12-Stream Wifi 6 Router (RAX200) - AX11000 Tri-Band Wireless Speed (Up to 10.8 Gbps)

Transcript

Jeff Byer 00:06 Welcome to digital rage the podcast about all things internet and the people that make it great. My name is Jeff Byer and today we do not have a guest. Again reached out to a few people, , lots of, you know, too busy to talk, couple of non responses, you know, so, , I don't have all day to do guest outreach so I apologize. But a, this'll be another, , what's going on and what am I working on type of episode. So, , what , happened this week, we hired a couple more people, a designer and a, a Shopify developer and great contrast. The designer is really slow and turning out terrible work and the Shopify developer is fast and awesome. So, , really happy with that because the Shopify good. Shopify developers are kind of like good web WordPress developers. There are a ton out there, but when you find a good one, you got to keep them. Jeff Byer 01:08 So I mean, I'm paying a premi, but he's very good. So that guy is doing great for me. He is, , is turning out stuff, you know, basically today he did a ton of stuff already, , which would have taken a week with my previous developers. So very happy with that. , the designer, not so much, , going back to my trusted designer that, , is a little slower but much more detailed and a much more on-brand. , so, and this designer, , I got this guy on Upwork and , he's, , he's a premi designer. His, his prices is, , right around $40 an hour. , which you know, is relatively not high at all if you're going to think about hiring somebody or getting a senior level designer. But my, I've, you know, I've got my, my print process designer that's doing it for $16 an hour and, , I have other offers for people that turn out some really good work at $24. Jeff Byer 02:13 So paying this guy $40 for super slow turnaround and not that great at work. , I believe I'm just going to cut them loose and go to the next person on my short list. So that's what's going on at Jeff buyer inc. , so a couple of things. , listen to a podcast this week. , Julie Joyce was the, was the guest and she owns a backlink company. And I loved what she was saying. And, , one of the things that I took away from it was that it's w that was a big truck. Sorry if you heard that. One of the things I took away from it was that she said, even though backlinks paid backlinks are against Google's guidelines, they still work. And I've heard this countless times, they still work, you know, private blogging networks, very forbidden. And if, you know, if they're obvious, they're going to get shut. Jeff Byer 03:16 You know, Google is going to be able to recognize him and penalize him. But the newer ones that are well done, that have quality content, they're working. And there's several use cases out there. I don't, I'm not suggesting that you follow these tactics. I'm not suggesting it for my clients and I'm not doing them for my clients. But it was very interesting and I wanted to talk to her about it cause she, she disclaims to every one of her backlink customers that this is against Google guidelines and they still proceed anyway. , so that's how she got into this specialty and niche of backlinks because her clients, even though she said she doesn't advise it, her clients said we want it anyway. Very interesting business to be in. So I wanted to talk to her about that. She got back to me, said she's super busy and we should reconnect in January. Jeff Byer 04:14 So then I saw a medi article titled, let me just pull it up so I can give you the title, how to train your brain to remember almost anything by Thomas APO. So Thomas, I reached out to him and he hasn't gotten back to me, but , I really found this article interesting and wanting to learn more about the process and how he came about learning all of this. , so one method that he talks about, I'm sorry, I'm having an indigestion problem. , one method he talks about is spaced repetition, which is just repeating what you, what you took in. And so, , in, in also in small chunks. But what I, I've kind of been doing that with audio books that I really love and would love to just have automatic recall for a lot of business process books and, and things like that. Jeff Byer 05:15 So I keep, I re, you know, several times a year I will re reread on audible a book that I, that is on my short list of ones that I really want to remember. So, , he says that's one of the things that you can do, but the other is a 50, 50 rule. The 50, 50 rule. Very interesting. And probably going to be where the, where my , my content process goes from here on out deciding what to write on, what to, what to talk about the time that you have dedicated to learn a new skill. 50% of the time is learning and then the other 50% of the time is teaching somebody else or explaining it to somebody else. And that's what I just did with this article because I was explaining it poorly. And then I went to the article and just said, Oh, the 50, 50 rule, learn it and then teach it. Jeff Byer 06:11 And so that is something, you know, not only is repetition a way to stimulate your memory, but being able, having to recall it and teach it, especially in a podcast or any video or especially on a, on a long form blog post, it's going to be, , going to be detailed and referenced and cited, you know, citing all of your resources and stuff. You're definitely going to take that in to your longterm memory. So explains the, the, the biology that once you listen to a audio book for instance, and you'd take the information in and it's there for a limited time. And if you don't actually do anything with it, it'll just go away. And so I can't tell you how many times I've taken, , a course on a new, on a new programming language or something. And you know, in the while I'm in the course and I'm working with it, I recall the things that I learned in previous chapters and I'm like, okay, now I'm recalling it, now I'm doing it. Jeff Byer 07:21 And by the end of it it's like, all right, got it. If I don't use it, then I go back to square one. It's like, okay, how do we start? What's the, you know, the little stuff, just like the context, like, you know, HTML was easy for me because once I learned it, I just kept hammering on it and hammering on it. And you know, back then there was no, no templates or are bootstrapping or anything like that. You had to actually type in the HTML tag in the beginning of your header or beginning of your docent to build an HTML page. So going from that level of detail, from starting out, you know, that's where I, I got my gain, my skills and in HTML. And then, , one of the first adopters for CSS, I had to learn CSS by scrap, by scratch. Jeff Byer 08:12 , you know, Java script, vanilla Java script was, was the way everybody was doing things back in the day. So, , so the, this, , the ways that he's explained in this article on how to retain information into longterm memory, they're starting to make sense to me because after reading about all of these different ways to do it, I've realized that the things that I've retained from my career in the past have been following these different guidelines and these different roles. So I thought it was a very interesting read. And as soon as I find something like this that's inspirational or, , something that, that I'd like to talk about on the podcast, I reach out to the author to see if they're willing to come on. So that's what I did. I haven't heard back, , Lily Ray just posted something on Twitter. So why don't I bring that up because that was completely relevant to what we're talking about right now. Jeff Byer 09:12 Let me go to my notifications cause she liked the comment. Okay. So she said, , Googl

36 | Jeff Byer – Chrome Dev Tools, Shopify, CCPA and Tech Talk

Today Jeff Byer (@globaljeff) talks about his experiment with workspaces in Chrome Dev Tools, the Shopify universe, upcoming project launches, real-world project issues, and tech talk.

Show Links

Chrome Dev Tools - Workspaces https://www.hongkiat.com/blog/google-chrome-workspace/ CCPA - https://oag.ca.gov/privacy/ccpa Fact Sheet, pdf

Transcript

Jeff Byer    00:06    Welcome to digital rage, the podcast about all things internet and the people that make it great. My name is Jeff Byer and I know last episode I have promised you guests but uh, that didn't happen. You know, people are busy, things are happening and uh, you know, just didn't get around to it. I did have an interview scheduled, we had our <inaudible> in our call  

Jeff Byer    00:30    and there was a misunderstanding. This a, I believe a the person involved was expecting some sort of a uh, you know, get to know ya. Uh, cause I sales call and I was expecting it to be an interview. So a little bit of a miscommunication. But um, anyway, I do have a ton of things to talk about. So this will be an episode full of stuff. I like to say stuff because some of it is crap set of, some of it's not. So let's get right into it. First thing is I was playing around and in Chrome and, and the dev tools and just futzing around and came across the workspaces in dev tools and thought, okay, this is interesting. Why would, why would they have a, you know, invite somebody to put their file structure inside of Chrome dev tools if it doesn't actually make any live, live edits as you go.  

Jeff Byer    01:41    Because as most developers know, whenever you get to a live website and you go into dev tools, you can modify all of the code you want and change the display of, of that website. You know, change the content, anything you want, run experiments, even if it's not your site but only you can see it. And as soon as you close dev tools or refresh the page, all those edits are gone. And it goes back to the way it is on the live server. And I do use that sometimes to one. If I'm trying to get a screenshot and I want to modify things for the actual screenshot, I'll go in, remove modules, remove ads and stuff like that. But on my own sites, I use it just to play around and see, you know, if there's something visually or content wise that I want to accomplish, how fast it would be to make that adjustment and just kind of play around in dev tools before I open up, uh, you know, my editor editing environment and go ahead and go through with the change.  

Jeff Byer    02:45    It also helps me to, to create estimates on what it's going to take to accomplish certain things requested by my client. So I get into this and I've read a couple of articles and I go through the Google tutorial on how to use Chrome tools and the whole time, uh, I'm going through these tutorials and obviously it says, okay, you know, it's, you'll be able to save the changes if you use it in, in your local environment and you add your local pho folder for that environment. So I was like, okay, that's fine, but it, uh, it's very limited and uh, I didn't see any way if you are going to use a SAS or any type of, of pre compiler that it just didn't have a way to really integrate those unless you had another third party script going. So the whole time I'm going through this tutorials, like who the hell would use this?  

Jeff Byer    03:47    It's just basic. If you had a basic site with no preprocessing prop, pre-processing, no minification and uh, just static something, I don't even know what, um, that's what you'd use. So I went down a rabbit hole on that and found myself completely disappointed. So moving on. Um, so today I added another team member to my Shopify partner program. Uh, another developer that's going to help me launch these two big projects that we're launching this month. And so the month of November is going to be a huge month here for us. And so we needed to bring on extra help. And the way Shopify partners, the partner system on Shopify works is that if, uh, I'm going to take on a new client that has an existing store, I go find the existing stores, my Shopify address, then I request access to that through my partner portal. And then the owner of that store is able to verify and then, uh, I get, I gain access through the partner portal.  

Jeff Byer    05:05    If the customer just puts in my email address and sends me access, even if it's the exact same address, it does not, uh, it's not available in my portal. So it's, uh, it's just a little quirky thing. I'm sure there's plenty of reasons on the back end or privacy issues or security issues or anything like that that, that takes that into account I guess. Because you know, anybody can put in anybody's email address and then you can accept and, and, but not really have access. I don't really understand the details of why it's separate, but it's separate. So, um, with adding a new team member, um, you know, I take privacy and my accounts very, very seriously, especially when hiring outsourced developers. So I create account specific for them, you know, server accounts, user accounts, things like that. And for this one, um, the developers first request was just to send me the access and what that assumes is that he wanted to log in as me through my account and take a look at everything.  

Jeff Byer    06:20    And that doesn't really sit with me very well, uh, for plenty of different reasons. Obviously security and, and you know, my, my customers who are, the admins can see my logins. And so if something happens while I'm logged in or near anything, it's just, I don't want it on me personally as, as a, you know, possible vulnerability. But the great thing is through the partner program, all of my, all of my accounts are in my partner program and when I log in, it shows that it's my company that's locked in, a representative of my company that's in there doing changes. And that's much better as far as, uh, my clients are concerned and I'm concerned. So the, the great thing was it the easy way to, there's an easy way to add people. You just add staff members to your partner portal, then each of those staff members, you can define their access but then they have access to all of your partners sites.  

Jeff Byer    07:24    And this hire today was not for for one specific type but for three of them that are in my partner portal. And so it was very convenient that I just had to get his Shopify email address, the email address that he uses for Shopify and he now has access to uh, to make changes to all of my customer accounts, which is, which is very convenient for me because it's one single point of access. He can access all of them. Now if something happens or if I don't like the worker or if I'm just moving on to a different developer, remove him and he wrote it, he doesn't have any access to them anymore and if he's going to ask them, access them currently he has to go through my partner portal. So a very cool thing. Uh, just thought that was really interesting cause it's, it's kind of backwards from how you access how you grant access to a customer's store rather than through a partner in, through my company.  

Jeff Byer    08:27    So that was fun. Um, another piece of information, uh, was regarding the, the California consumer consumer privacy act CC P a. So this is coming on January 1st and uh, I'm making sure that all of my, all of my accounts are aware of this and so that they're prepared and know that it's coming. And so digging into the fact sheet of the CCPA, the here's the requirements. So, uh, E not a lot of my customers actually require this, but for the ones that do, I'm just confirming cause I don't know the ins and outs of everything that they do. Uh, I have web stats and that's it. I don't know how the business is run specifically. I don't know revenue numbers cause they're mostly private businesses. But here are the, here's the, the requirements. So businesses are subject to the CCP. A, if one or more of the following, our true has gross Avenue S sorry, I'm having trouble speaking today.  

Jeff Byer    09:47    Let's try this again. If the following are true, has gross annual revenues in excess of $25 million, um, buys, receives or sells the personal information of 50,000 or more customers, households or devices. So that one's interesting because when I first skimmed through it and I said, Oh, buy and sells information, that's, you know, none of my customers do that. But then receives and absolutely all of my customers receive information and checking databases on that information. Is, is only part of what the law entails. This is pretty much everything. So I need to verify that with all my customers because 50,000 consumers on, you know, a site that's been 10 years old, that's a pretty easy number to hit. So, uh, even for a small business, so I'm confirming that, uh, all the information that they have

35 | Jeff Byer – Natural Language Processing and the BERT Update

Today Jeff Byer (@globaljeff) talks about the abundance of posts and information regarding Natural Language Processing and the BERT update.

About Natural Language Processing & the BERT Update

Bill Slawski @bill_slawski retweeted this article from Ibrahim Sharaf ElDen as an introduction to Natural Language Processing https://t.co/Xct8wP3BIX?amp=1

I just reread this article by @ajkohn from 1 year ago and it's quite possibly the most relevant article about BERT and #SEO on the internet right now.https://t.co/PCbCAOdQ1D

— Jon Henshaw (@henshaw) October 27, 2019

Justin Briggs@justinrbriggs article about how to write for natural language processing On-page SEO for NLP post

Kevin Indig quoting a Fortune article. I am embedding the tweet to show the comments and expose that this is not "new" as the article title might be misleading.

👀 “Language understanding is key to everything we’re doing on search,” said Pandu Nayak, Google fellow and vice president of search. “This is the single, biggest, most positive change we’ve had in last five years.”https://t.co/3LVXGjFu0e pic.twitter.com/jRzeTb7OC3

— Kevin_Indig (@Kevin_Indig) October 25, 2019 Transcript

processing...

Jeff Byer    00:08    Welcome to Digital Rage, the podcast about all things internet and the people that make it great. My name is Jeff Byer. Today's episode, I do not have a guest and I wasn't planning on recording an episode. This was going to be the first episode that I skipped since, , end of January, 2019. But, , I'm gonna call this the accidental episode because I came across so much, , tweets and posts about natural language processing and the so-called Bert update that, , I had to, , throw in my 2 cents and provide you the audience with everything that I've, I've been following and watching and learning and, and how all of this affects search moving forward. So let's get started with how this, you know, so when it comes to natural language processing and, , language itself, I look to bill Slawsky and his study on how Google has, , published their patents on language processing and Bill's breakdown of those patents and how they relate from patent to real life search results.  

Jeff Byer    01:26    So he, so bill retweeted an article from Ibraham Sharif El den as an introduction to natural language processing. And so I started digging in there and started realizing that different variations of natural language processing are taking a a sentence basically and breaking it down into its primary parts with the nouns, the adjectives and verbs and taking a, a word, a word that that is meant to be. I don't want to use the word keyword here because it's completely in different contexts. The contents here is, it's basically the root word of the sentence and how many jps from the root word backwards. Can you put the word into context and choose its actual meaning based on that. So in natural language processing and previous iterations of that, those, those jps from that, that main word in the sentence, we're, we're toward the beginning of the sentence and not many hops from the, from that word to the end of the sentence.  

Jeff Byer    02:45    And now what I understand this Bert update or Bert is supposed to do is it is supposed to take the, the words that are not on it's bi-directional means not only the w taking the context words before the main word, but after the main word and going further after the main word. So that all the, everything, all the possible data can be taken into account. So that the understanding of the context of the root word and all of the contextual words found in short jps from that root word will provide an actual context. And based on that context, you will, a search engine would then provide the appropriate response in context. So what that means for SEOs and content writers is, , a system that, , that you w a system of writing or a style of writing that if you're writing for SEO, you want those words to be relatively close to each other and provide as much context as possible for what the sentence that you are building is trying to convey.  

Jeff Byer    04:09    And if there is any, , ambiguous is there, if it's an ambiguous term, , the term can mean many different things. There's so many different ways that it can be interpreted. So your answer needs to be as clear and sustained as possible and put in all of the relevant information possible to give Google or any, , natural language processing algorithm with algorithm. The best opportunity to understand in full the context of what you're writing and what you're saying. And you know, in turn what you're basically doing is providing the, the searcher with the most informative and complete answer to a query that you could possibly offer. So, , what I've been finding in a lot of these writing guides for, , natural language processing and what the style of, of writing would be is that, , you'd need to, you know, it's, it's not as creative writing and it's not super technical.  

Jeff Byer    05:27    Writing is writing for understanding. , and so natural language processing is trying to take the natural progression of speech into account. But for people like me who find it difficult to explain technical concepts, simply, I just find it difficult to speak in general, which is why I do a podcast to become better at it. But when I've start explaining something technical and I get into details, my, my sentences tend to get longer and longer and longer, and it becomes harder for the listener to connect those dots. As an example. That sentence that I just said, the, the explanation took way too many words. And so if I was to rewrite that sentence over, I would get more to the point and say, this is, this is the problem, this is the solution. And that's it. So, , as I've been researching and digging more into it, , a tweet by Jon Henshaw, he re posted an article from AGA cone from a year ago.  

Jeff Byer    06:40    And what he tweeted was, I just re-read this article by J cone from one year ago, and it's quite possibly the most relevant article about Bert and SCO on the internet right now. And so what I did is, , I went to that original tweet and, , I'll have it in the show notes so that you can reference it and see the context of how my learning on this subject progressed. So the Bert update, , is basically, it's been used for a long time and there, and I've, we get into this later in the, in in my learnings, but it just seems like this wasn't much of an update because it's been happening for a while. And so this article came out a year ago right after the medic update and we've talked about the medic update, , in several of our past episodes. So, , if you need to catch up on that, I can put links to where we talked about it and specifically how it affected, , one of my client's sites and, and how it corrected and all linked also to a recent tweet from Kevin indig, which I'll get into in a second.  

Jeff Byer    07:56    But basically the, , here is the original tweet. , here's the quote reading article reading the article by aJ  cone one year ago about natural language processing. Burt its relation to the medic update, what went wrong with the update and how it was corrected. So this, after reading through the article in detail and it said that the medic update was actually not medic at all, but it was a, a attempt, an initial attempt at a improving the natural language processing, , for, for search and , mainly for content so that, , for search results. So this started the whole discussion, you know, as in the quality greater guidelines about, , experience authoritativeness and which is eat and SEOs now have to consider all of this because Google is now considering all of this information. And in this article he explains that the, the , medic update initially got it wrong and was, was not understanding the context of a lot of, of medical, , information and how it would relate to searchers. So a lot of medical information sites, which is how this update got the, the term medic.  

Jeff Byer    09:33    , it was basically nay natural language processing error in the update itself. And it only affected, you know, the medical, your money, your life categories. This is based on this article. So I know that the update had a lot more going on, but specifically to natural language processing, this is how the medic update was, was seen, applied and reversed. So this, the, , example in the article uses it uses a SERP analysis. I'm just looking at back up again so I can, I can tell you exactly. , so the OG in the article, it States the audit August 1st error, , that, that the new content ranking didn't match the intent of the queries. And so by October of 2018, rankings came back because there was a reversal in how the syntax was calculated in, , on pay for a natural language posts,

34 | Rachelle Golden – Accessibility Law, the Domino’s Case, and What This Case Means for the Future

Today Jeff Byer (@globaljeff) talks with Rachelle Golden about the Supreme Court's decision to not hear Domino's petition on whether its website is accessible to the disabled, and what it means for website accessibility litigation moving forward.

About Rachelle Golden

Rachelle handles labor and employment law and litigation. She defends employers before state, federal, and administrative agencies and provides counsel regarding all aspects of human resource issues and compliance to help clients avoid penalties and litigation.

  • Hatmaker Law Group
  • Rachelle T. Golden LinkedIn
Robles v. Dominos

Bloomberg Law Article by Alexis Kramer CNBC Article by Tucker Higgins Mashable Article by Siobhan Neela-Stock

Transcript

Jeff Byer   00:07    Welcome to to digital rage, the podcast about all things internet and the people that make it great. My name is Jeff Byer. Today I had a good discussion with Rachelle Golden choosing an attorney at ha maker law group and she specializes in accessibility and equal access for people with disabilities. She's, , got firsthand information about the,  

Jeff Byer    00:33    , domino Roblis vs Domino's case, which, , two weeks as you, two weeks ago as you listen to this was, , the Supreme court denied an appeal to, , they, okay. So what happened is we explained the case in the interview and how the case came about and where the case stands today. But, , what happened recently, which triggered me contacting Rochelle is the U S Supreme court's decision to not hear Domino's petition on whether its website is accessible to the disabled. So a very interesting discussion and, , it was awesome to get the details and understand the impact and how this is, this case has the, the opportunity to define website access moving forward. We also discussed that a worst case scenario is that Domino's settles the case and we don't get any resolution in the courts to decide what is an acceptable level of accessibility for websites.  

Jeff Byer    01:41    One of the main takeaways that we got from our conversation, or I get from my conversations with Rachelle, is that if you have offline access, , ADA compliance, accessibility, , guidelines to follow, then that should also be duplicated on your website. So if you sell Rochelle's example is that if you sell gift cards within your store, then you should be able to buy gift cards on your online store. And if anybody with disabilities has special access that they, they have to buy those gift cards in the store, that same access needs to be provided online. , she also said that in this wikag 2.0 AA and you know, basically WCAG 2.1 moving forward is not going to cover everybody. , disabilities have such wide ranging, , you know, symptoms and how people use assistive technologies to, , get information with their disabilities that it's never gonna cover everybody.  

Jeff Byer    02:58    And it's not gonna be possible that every single individual is going to have equal access and a digital property. All we're looking for is what is going to avoid litigation and complaints in the courts. You know, keep this, keep this not illegal issue and give us standards that we need to meet. And , and so that's what this court case could possibly do. But for now it's back to the lower courts and it's at a standstill. So that's all I got for now. I'm going on vacation. That's why I'm posting this short episode early. But this is a very important episode and lots of very quality content in here. You can reach me. I am on Twitter at global. Jeff please, if you have the opportunity and the time please rate and review us on any of your pod catchers. It really helps and I'd love to hear any feedback that you have about the show.  

Jeff Byer    03:57    And we are , there was a request online the to go into more static website hosting and and a static website rendering. We are going to get into that in the future. , right now I am working on a WordPress plugin that's going to be able to give you the fastest possible load times using WordPress as a backend. , and we're cause all of my tests using the API are taking way too long to render. So we're moving forward with the static version. So I am going to give you my recipe for static versions most likely in the next episode. So stay tuned. Thank you for listening. And here is Rochelle golden  

Jeff Byer   04:52    All right. Today we have for shell golden for shell is an attorney, a court with hatmaker law group. , Rachelle, will you briefly just explain, , you what you do and what your specialty is?  

Rachelle Golden    05:05    Yeah, sure. So, , I'm an ADA defense attorney. I represent businesses all grow up the state and state and federal courts and, , I am a proactive consultant with various businesses as well to make sure that they become compliant with the, not only construction-related access laws, but as well as the website guidelines that are produced by the worldwide web consorti. , and so I do, like I said, defense, litigation and then proactive consultant as well as employment litigation as well for various businesses.  

Jeff Byer    05:39    Excellent. So, , the topic that we're going to just discuss today, which I sent you, was the, , Supreme court's decision to not hear Domino's petition on, , the <inaudible> case. So a little bit of background. , what, how did this all start?  

Rachelle Golden    05:58    So I'm mr O bliss is a blind individual and or a sight impaired individual and he sued dominoes because he said that he was unable to access the online services to order a pizza. And at the time, , there was no banner on the website, so there was no, you know, if you're having difficulty call us or call our 24 hour hotline at such and such nber, , that, that wasn't in existence. And so he sued dominoes for at website accessibility and said that because there was no, , coding on the back end that met the out worldwide web consorti guidelines, which is the, , website content accessibility guidelines, WCA G, , he said that because it wasn't coded that way, that it was a barrier to accessibility and a violation under the Americans with disabilities act. And so that's how it started. , last year. Correct.  

Rachelle Golden    07:02    , I believe it was in 2017. Okay. I believe it was in June. I think the, I think the complaint was filed in 2017 and so that originally the district court, which was the first court to hear it, the first federal court to hear it, , dismiss the case because the, , because dominoes then after the complaint was filed, put up this banner that said, call us 24 hours for assistance. And the court said, that's sufficient. You've effectively remediated the issue because there's a 24 hour, one, 800 hotline that people could call an accident, access the same services, , for ordering pizza if you have a site in permits. Well of course Mr. Robles didn't like that decision. And so he appealed it to the ninth circuit court of appeal and the ninth circuit court of appeals said, , not only did you not comply with a website content accessibility guidelines, , that banner didn't exist at the time.  

Rachelle Golden    08:02    And so there was a right case for, , for the case to continue. And ultimately the ninth circuit court of appeals said, , setting aside the ban or issue or you know, we're not going to really focus on that. We're going to focus on whether this website needs to be coated with the would gag, the website content accessibility guidelines 2.0 AA or higher in order for it to be, , provide effective access. And the ninth circuit said yes, in order for there to be the remedy for the injunctive remedy for website accessibility is to have, , the website coated to comply with those guidelines. , and it needs to comply in order for there to be equivalent access for persons with disabilities. But the catch was, it said in order for  

Speaker 4    08:56    a website to need to be in compliance with those webs, with those website guidelines, the website must have a nexus. There must be a direct correlation between the product and services that are offered on the website to the brick and mortar of the business. And since Domino's has brick and mortar locations that somebody could walk into and go order pizza, and they also have one site prevalence, they need to ensure that they are coded properly to meet those guide

Every Podcast » Digital Rage » 36 | Jeff Byer – Chrome Dev Tools, Shopify, CCPA and Tech Talk