Podcasts about CPanel

Tom MacWright is a prolific contributor in the geospatial open source community. He made geojson.io, Mapbox Studio, and was the lead developer on the OpenStreetMap editor. He's currently on the team at Val Town. In 2021 he bootstrapped a solo business and created the Placemark mapping application. He acquired customers and found steady growth but after spending two years on the project he decided it was financially unsustainable. He open sourced the code and shut down the business. In this interview Tom speaks candidly about why geospatial is difficult, chasing technical rabbit holes, the mental impact of bootstrapping, and his struggles to grow a customer base. If you're interested in geospatial or the good and bad of running a solo business I think you'll enjoy this conversation with Tom. Related Links Tom's blog Placemark Play Placemark GitHub Placemark archive geojson.io Valtown Datawrapper (Visualization tool) Geospatial Companies mentioned Mapbox ArcGIS QGIS Carto -- Transcript You can help correct transcripts on GitHub. [00:00:00] Introduction Jeremy: Today I'm talking to Tom MacWright. He worked at Mapbox as a, a very early employee. He's had a lot of experience in the geospatial community, the open source community. One of his most recent projects was a mapping project called Placemark he started and ran on his own. So I wanted to talk to Tom about his experience going solo and, eventually having to, shut that down. Tom, thanks for agreeing to chat today. Tom: Yeah, thanks for having me. [00:00:32] Tools and Open Source at Mapbox Jeremy: So maybe to give everyone some context on, what your background was before you started Placemark. Um, let's talk a little bit about your experience at, at Mapbox. What did you work on there and, and what would you say are like the big things you learned from that experience? Tom: Yeah, so if you include the time that I was at Development Seed, which essentially turned into Mapbox, I kind of signed the paper to get fired from Development Seed and hired at Mapbox within the same 20 seconds. Uh, I was there for eight and a half years. so it was a lifetime in tech years. and the company really evolved from, uh, working for Human Rights Watch and Amnesty International and the World Bank and doing these small, little like micro websites to the point at which I left it. It had. Raised a lot of money, had a lot of employees. I think it was 350 or so when I left. and yeah, just expanded into a lot of different, uh, try trying to own more and more of the mapping stack. but yeah, I was kind of really focused on the creative and tooling side of it. that's kind of where I see a lot of the, the fun and programming is making these tools where, uh, they can give people the same kind of fun like interaction loop that programming has where you, you know, you do a little bit of math and you see the result and you're able to just play with, uh, what you're working on, letting people have that in other domains. so it was really cool to figure out how to get A map design tool where somebody changes the background color and it just automatically changes that in your browser. and it covered like data editing. It covered, um, map styling and we did, uh, three different versions of that tool over the years. and then Mapbox is also a company that was, it came from, kind of people who are working on the Howard Dean campaign. And so it was pretty ideological and part of the ideology was being pretty hardcore about open source. we hired a lot of people who were working on open source projects before and basically just paid them to work on the open source projects, uh, for their whole time there. And during my time there, I just tried to make as much of my work, uh, open as possible, which was, you know, at the time it was, it was pretty great. I think in the long term it's been, o open source has changed a lot. but during the time that we were there, we both kind of, helped things like leaflet and mapnik and openstreetmap, uh, but also made like some larger contributions to the open source world. yeah, that, that's kind of like the, the internal company facing side. And also like what I try to create as like a more of a, uh, enduring work. I think the open source stuff will hopefully have more of a, a long term, uh, benefit. [00:03:40] How open source has changed (value capture by large companies) Jeremy: When I was working on a project that needed offline maps, um, we couldn't use Google Maps or any of the, the other publicly available, cloud APIs. So yeah, we actually used a, a tool, called Tile Mill that I, I hadn't known that you'd worked on, but recently found out you did. So that actually let us pull in OpenStreetMap data and then use this style, uh, language called carto to, to basically let us choose what the colors would be and how the different, uh, the roads and the buildings would look. What's kind of interesting to me is that it being open source really let us, um, build something we otherwise wouldn't have been able to do. But like, at the same time, we also didn't pay Mapbox any money. (laughs) So I'm, I'm kind of curious, like, if it's changed, like what the thinking was in terms of, you know, we pay for people to build all these things. We make it open source. but then people may just not ever pay us, you know, for all these things we did. Tom: Yeah. Yeah. I think that the main thing that's changed since the era of tilemill is, the dominance of cloud platforms. Like back then, I think, uh, Mapbox was still using, we were using like a little bit of AWS but people were still just on like VPSs and, uh, configuring things in cPanel and sometimes even running their own servers. And the, the danger of people using the product for free was such a small thing for us. especially when tile Mill was also funded by the Knight Foundation, so, you know, that at least paid half of my salary for, or, well, sorry, probably, yeah, maybe half of my salary for the first year that I was there and half of three other people's salaries. but that, yeah, so like when we built Tile Mill, a few companies have really like built on those same tools. Uh, there's a company called Carto coincidentally, they had the same name as Carto CSS, and they built on a lot of the same stack they built on mapnik. Um, and it was, was... I mean, I'm not gonna say that it was all like, you know, sunshine and roses, but it was never a thing that we talked about in terms of like this being a brutal competition between us and these other startups. Mapbox eventually closed source some stuff. they made it a source available license. and eventually Mapbox Studio was a closed source product. Um, and that was actually a decision that I advocated for. And that's mostly just because at one point, Esri, Microsoft, Amazon, all had whitelisted versions of Mapbox code, which, uh, hurts a little bit on a personal level and also makes it pretty hard to think about. working almost like it. You don't want to go to your scrappy open source company and do unpaid labor for Amazon. Uh, you know, Bezos can afford to pay for the labor himself. that's just kind of my personal, uh, that I'm obviously, I haven't worked there in a long time, so I'm not speaking for the company, but that's kind of how it felt like. and it yeah, kind of changed the arithmetic of open source in this way that. It made it less fun and, more risky, um, for people I think. [00:07:11] Don't worry about the small free users Jeremy: Yeah. So it sounds like the thinking was if someone on a small team or an individual, they took the open source software and they used it for their own projects, that was fine. Like you expected that and didn't worry about it. It's more that when these really large organizations like a, a Microsoft comes in and, just like you said, white labels the software, and doesn't really contribute significantly back. That's, that's when it, the, the thinking sort of shifted. Tom: Yeah, like a lot of the people who can't pay full price in USD to use your product are great users and they're doing cool stuff. Like when I was working on Placemark and when I was like selling. The theme for my blog, I would get emails from like some kid in India and it's like, you know, you're selling this for a hundred dollars, which is a ton of money. And like, you know, why, why should I care? Why shouldn't I like, just send them the zip file for free? it's like nothing to me and a lot to them. and mapping tools are really, really expensive. So the fact that Mapbox was able to create a free alternative when, you know, ArcGIS was $500 a month sometimes, um, depending on your license, obviously. That's, that's good. You're always gonna find a way for, like, your salespeople are gonna find a way to charge the big companies a lot of money. They're great at that. Um, and that's what matters really for your, for the revenue. [00:08:44] ESRI to Google Maps with little in-between Jeremy: That's a a good point too about like the, my impression of the, the mapping space, and maybe this has changed more recently, but you had the, probably the biggest player Esri, who's selling things at enterprise prices and then there were, or there are like a few open source options. but they feel like the, the barrier to entry feels a little high. And so, and then I guess you have stuff like Google Maps, right? That's, um, that's very accessible, but it's pretty limited, so. There's this big gap, it feels like right between the, the Esri and the, the Google Maps and open source. It's, it's sort of like, there's almost like there's no sweet spot. guess May, maybe it's just because people's uses are so different, but I'm, I'm not sure, um, what makes maps so unique in that way Tom: Yeah, I have come to understand what Esri and QGIS do as like an extension of what CAD is like. And if you've used CAD software recently, it's just as crazy and as expensive and as powerful. and it's really hard to capture like the people who are motivated enough to make a map but don't want to go down the whole rabbit hole. I think that was one of the hardest things about Placemark was trying to be in the middle of those things and half of the people were mystified by the complexity and half the people wanted more complexity. Uh, and I just couldn't figure out how to get it to the right in between spot. [00:10:25] Placemark and its origins in geojson.io Jeremy: Yeah. So let's, let's talk a little bit about Placemark then, in terms of from its start. What was your, your goal with Placemark and, and what was the product itself? Tom: So the seed of the idea for Placemark, uh, is this website called geojson.io, uh, which is still around. And, Chris Fong (correction -- Whong) at, at Mapbox is still, uh, developing it. And that had become pretty useful for a lot of people who I knew in the industry who were in this position of managing geospatial data but not wanting to boot up ArcGIS uh, geojson.io is based on, I just tweeted, I was like, why? Why is there not a thing where you can edit data on a map and have a GeoJSON representation and just go Back and forth between the two really easily. and it started with that, and then it kind of grew to be a little bit more powerful. And then it was just a tool that was useful for everyone. And my theory was just that I wanted that to be more useful. And I knew just like anything else that you build and you work on for a long time, you know exactly how it could be so much better. And, uh, all the things that you would do better if you did it again. And I was, uh, you know, hoping that there was something where like if you make that more powerful and you make it something that's like so essential that somebody's using every day, then maybe there's some some value in that. And so Placemark kind of started as being like, oh, this is the thing where if you're tasking a satellite and you need a bounding box on a specific city, this is the easiest way to do that. Um, and it grew a little bit into being like a tool for collaborating because people were collaborating on it. And I thought that that would be, you know, an interesting thing to support. but yeah, I think it, it like tried to be in that middle of like, not exactly Google my Maps and certainly a lot, uh, simpler than, uh, QGIS or ArcGIS Jeremy: something I noticed, so I've actually used geojson.io as well when I was first learning how to put stuff on a map and learning that GeoJSON was a format that a lot of things were using, it was actually really helpful to, to be able to draw, uh, polygons and see, okay, this is how the JSO looks and all that stuff. And it was. Like just very simple. I think there's something like very powerful about, websites or applications like that where it, it does this one thing and when you go there, you're like, oh, okay, I, I, I know what I'm doing and it's, it's, uh, you know, it's gonna help me do the, this very specific thing I'm trying to do. [00:13:16] Placemark use cases (Farming, Transportation, Interior mapping, Satellite viewsheds) Jeremy: I think with Placemark, so, one question I would have is, you gave an example of, uh, someone, I think you said for a satellite, they're, are they drawing the, the area? What, what was the area specifically for? Tom: the area of interest, the area where they want the, uh, to point the camera. Jeremy: so yeah, with, with Placemark, I mean, were there, what were some of the specific customers or use cases you had in mind? 'cause that's, that's something about. Um, placemark as a product I noticed was it's sort of like, here's this thing where you can draw polygons put markers and there's all these like things you can do, but I think unless you already have the specific use case, it's not super clear, who uses it for what. So maybe you could give some examples of what you had in mind. Tom: I didn't have much in mind, but I can tell you what people, what some people used it for. so some of the more interesting uses of it, a bunch of, uh, farming oriented use cases, uh, especially like indoor and small scale farming. Um, there were some people who, uh, essentially had a bunch of flower farms and had polygons on the map, and they wanted to, uh, mark the ones that had mites or needed to be watered, other things that could spread in a geometric way. And so it's pretty important to have that geospatial component to it. and then a few places were using it for basically transportation planning. Um, so drawing out routes of where buses would go, uh, in Luxembourg. And, then there was also a little bit of like, kind of interesting, planning of what to buy more or less. Uh, so something of like, do we want to buy this tract of land or do we wanna buy this tract of land or do we wanna buy access to this one high speed internet cable or this other high speed internet cable? and yeah, a lot of those things were kind of like emergent use cases. Um, there's a lot of people who were doing either architecture or internal or in interior mapping essentially. Jeremy: Interior, you mean, inside of a building Tom: yeah. yeah. Jeremy: Hmm. Okay. Tom: Which I don't think it was the best tool for. Uh, but you know, people used it for that. Jeremy: Interesting. Yeah. I guess, would people normally use some kind of a CAD tool for that, or Tom: Yeah. Uh, there's CAD tools and there are a few, uh, companies that do just, there's a company that just does interior maps especially of airports, and that's their whole business model. Um, but it's, it's kind of an interesting, uh, problem because most CAD architecture work is done with like a local coordinate system, and you have like very good resolution of everything, and then you eventually place it in geo geospatial space. Uh, but if you do it all in latitude and longitude, you know, you're, you're moving a door and it's moving the 10th or 12th decimal point, and eventually you have some precision problems. Jeremy: So it's almost like if you start with latitude and longitude, it's hard to go the other way. Right? you have to start more specific and then you can move it into the, the geospatial, uh, area. Tom: Yeah. Uh, that's kind of why we have local projections for towns is that you can do a lot of work just in that local projection. And the numbers are kind of small 'cause your town's small, relatively. Jeremy: yeah, those are kind of interesting. So it sounds like just anytime somebody wants to, like you gave the example of transportation planning or you want to visually see where things are, like your crops or things like that, and that, that kind of makes sense. I mean, I think if you just think about paper maps, if somebody wants to sketch something out and, and sort of track the layout of something, this could serve the same purpose but be editable. and like you said, I think it's also. Collaborative so you can have multiple people editing the same, um, map. that makes sense. I think something that I believe I saw on your website is you said though that it was, it's like an editing tool, but it's not necessarily a visualization tool. Uh, I'm kind of curious what you, what you meant by that. [00:17:39] An editing tool that allows you to export data not a visualization tool Tom: Yeah, I, when you say a map, I think there's, people can interpret that as everything from raw data to satellite imagery and raster data. and then a lot of it is like, can I use this to make a choropleth map of the voter turnout in our, in my country? and that placemark did a little bit, but I think that it was, it was never going to be the, the thing that it did super well. and so, yeah, and also like the, the two things kind of, don't mesh all that well. Like if you have a scale point map and you have that kind of visualization of it and then you're editing the points at the same time and you're dragging around these like gigantic points because this point means a lot of population, it just doesn't really make that much sense. There are probably ways to square that circle and have different views, but, uh, I felt like for visualizations, I mean partly I just think data wrapper is kind of great and uh, I had already worked for observable at that point, which is also, which I think also does like great visualization work. Jeremy: Would that be the case of somebody could make a map inside a placemark and then they would take the GeoJSON and then import that into another visualization tool? Is that what you were kind of imagining people would do? Tom: Yeah. Yeah, exactly. Jeremy: And I could see from the customer's perspective, a lot of them, they may have that end, uh, visualization in mind. So they might look for a tool that kind of just does both. Right. Tom: Yeah. Yeah. Certain people definitely, wanted that. And yeah, it was an interesting direction to go down. I think that market was going to be a lot different than the people who wanted to manage and edit data. And also, I, one thing that I had in mind a lot, uh, was if Placemark didn't work out, how much would people be burned? and I think if I, if I built it in a way that like everyone was heavily relying on the API and embeds, people would be suffer a lot more, if I eventually had to shut it down. every API that you release is really a, a long-term commitment. And instead for me, like guilt wise, having a product where you can easily export everything that you ever did in any format that you want was like the least lock in, kind of. Jeremy: Yeah. And I imagine the, the scope of the project too, you're making it much smaller if you, if you stick to that editing experience and not try to do everything. Tom: Yeah. Yeah. I, the scope was already pretty big. as you can tell from the open source project, it's, it's bigger than I wish it was. the whole time I was really hoping that I could figure out some niche that was much more compact. there's, I forget the name, but there's somebody who has a, an application that's very similar to Placemark in. Technical terms, but is just a hundred percent focused on planning septic systems. And I'm just like, if I just did this just for septic systems, like would that be a much, would that be 10,000 lines of code instead of 40,000 lines of code? And it would be able to perfectly serve those customers. but you know, that I didn't do enough experimentation to figure that out. Um, I, that's, I think one thing that I wish I had done a lot more was, pivot and do experiments. Jeremy: that septic example, do you know if it's a, a business in and of itself where it can actually support one person or a staff of people? Or is it, is that market just too small? Tom: I think it's still a solo bootstrapped project. yeah. And it's, it's so hard to tell whether a company's doing well or not. I could ask the person over DM. [00:21:58] Built the base technology before going public Jeremy: So when you were first starting. placemark. You were, you were doing it as a solo, developer. A solo entrepreneur, reallyyou worked on it for quite a while, I think before you announced, right? Like maybe a year or so? Tom: Yeah, yeah. Almost, almost a year, I think, maybe, maybe 10 months in the dark. Jeremy: I think that there's, there was a lot of overlap between the different directions that I would eventually go in and. So just building a collaborative editor that can edit map data fairly quickly and checks all the boxes of being able to import and export things, um, that is, was a lot of work. and I mean also I, I was, uh, freelancing during part of it, so it wasn't a hundred percent of my time. Tom: But that, that core, I think even now if I were to build something similar, I would probably still use that work. because that, whether you're doing the septic planning application or you're doing a general purpose kind of map editor or some kind of social application, a lot of that stuff will be in common. Um, and so I wanted to really get, like, to figure out that problem space and get a few solutions that I could live with. Jeremy: The base. libraries or technologies you were gonna pick to get the map and have the collaborative aspect. Those are all things you wanted to get settled first. And then you figured, okay, once I have this base, then I can go find the, you know, the, the, the customers or, or find the specifics of what I'm gonna build. Tom: Yeah, exactly. Jeremy: I I think you had said that going forward when you're gonna work on another project, you would probably still start the same way. [00:23:51] Geospatial is a tough industry, no public companies Tom: if I was working on a project in the geospatial space, I would probably heavily reference the work that I already did here. but I don't know if I'll go back to, to maps again. It's a tough industry. Jeremy: Is it because of the, the customer base? Is it because like people don't really understand the market in terms of who actually needs the maps? I'm kind of curious what you feel makes it tough. Tom: I think, well there are no, there are no public mapping companies. Esri is I think one of the 10 largest private companies in the us. but it's not like any of these geospatial companies have ever been like a pure play. And I think that makes it hard. I think maps are just, they're kind of like fonts in a way in which they are this. Very deep well of complexity, which is absolutely fascinating. If you're in it, it's enough fun and engineering to spend an entire career just working on that stuff. And then once you're out of it, you talk to somebody and you're just like, oh, I work on this thing. And they're like, oh, that you Google maps. Um, or, you know, I work at a font type like a, you know, a type factory and it's like, oh, do you make, uh, you know, courier in, uh, word. It's really infrastructure, uh, that we mostly take for granted, which is, that's, that means it's good in some ways. but at the same time, I, it's hard to really find a niche in which the mapping component is that, that is that useful. A lot of the companies that are kind of mapping companies. Like, I think you could say that like Strava and Palantir are kind of geospatial companies, both of them. but Strava is a fitness company and Palantir is a military company. so if you're, uh, a mapping expert, you kind of have to figure out what, how it ties into the real world, how it ties into the business world and revenue. And then maps might be 50% of the solution or 75% of the solution, but it's probably not going to be, this is the company that makes mapping software. Jeremy: Yeah, it's more like, I have this product that I'm gonna sell and it happens to have a map as a part of it. versus I'm going to sell you, tools that, uh, you know, help you make your own map. That seems like a, a harder, harder sell. Tom: yeah. And especially pro tools like the. The idea of people being both invested in terms of paying and invested in terms of wanting to learn the tool. That's, uh, that's a lot to ask out of people. [00:26:49] Knowing the market is tough but going for it anyways Jeremy: I think the things we had just talked about, about mapping being a tough industry and about there being like the low end is taken care of by Google, the high end is taken care of by Esri with ArcGIS. Uh, I think you mentioned in a blog post that when you started Placemark you, you, you knew all this from the start. So I'm kind of curious, like, knowing that, what made you decide like, I'm gonna, I'm gonna go for it and, you know, do it anyways. Tom: uh, I, well, I think that having seen, I, like I am a co-founder of val.town now, and every company that I've worked for, I've been pretty early enough to see how the sausage is made and the sausage is made with chaos. Like every company doesn't know what it's doing and is in an impossible fight against some Goliath figure. And the product that succeeds, if it ever does succeed, is something that you did not think of two or three years in advance. so I looked at this, I looked at the odds, and I was like, oh, these are the typical odds, you know, maybe someday I'll see something where it's, uh, it's an obvious open blue water market opportunity. But I think for the, for the most part, I was expecting to grind. Uh, you know, like even, even if, uh, the odds were worse, I probably would've still done it. I think I, I learned a lot. I should have done a lot more marketing and business and, but I have, I have no regrets about, you know, taking, taking a one try at solving a very hard to solve problem. Jeremy: Yeah, that's a good point in that the, the odds, like you said, are already stacked against you. but sometimes you just gotta try it and see how it goes, Tom: Yeah. And I had the, like I was at a time where I was very aware of how my life was set up. I was like, I could do a startup right now and kind of burn money for a little while and have enough time to work on it, and I would not be abandoning an infant child or, you know, like all of the things that, all the life responsibilities that I will have in the near future. Um. So, you know, uh, the, the time was then, I guess, [00:29:23] Being a solo developer Jeremy: And comparing it to your time at Mapbox and the other startups and, and I suppose now at val.town, when you were working on Placemark, you're the sole developer, you're in charge of everything. how did that feel? Did you enjoy that experience or was it more like, I, I really wish I had other people to, you know, to kind of go through this with, Tom: Uh, around the end I started to chat with people who, like might be co-founders and I even entertained some chats with, uh, venture capital people. I am fine with the, the day to day of working on stuff alone of making a lot of decisions. That's what I have done in a lot of companies anyway. when you're building the prototype or turning a prototype into something that can be in production, I think that having, uh, having other people there, It would've been better for my mentality in terms of not feeling like it was my thing. Um, you know, like feeling detached enough from the product to really see its flaws and really be open to, taking more radical shifts in approach. whereas when it's just you, you know, it's like you and the customers and your email inbox and, uh, your conscience and your existential dread. Uh, and you know, it's not like a co-founder or, uh, somebody to work with is gonna solve all of that stuff for you, but, uh, it probably would've been maybe a little bit better. I don't know. but then again, like I've also seen those kinds of relationships blow up a lot. and I wanted to kind of figure out what I was doing before, adding more people, more complexity, more money into the situation. But maybe you, maybe doing that at the beginning is kind of the same, you know, like you, other people are down for the same kind of risk that you are. Jeremy: I'm sure it's always different trade offs. I mean, I, I think there probably is a power to being able to unilaterally say like, Hey, this is, this is what I wanna do, so I'm gonna do it. Tom: Yeah. [00:31:52] Spending too much time on multiplayer without a business case Jeremy: You mentioned how there were certain flaws or things you may not have seen because you were so in it. Looking back, what, what were some of those things? Tom: I think that, uh, probably the, I I don't think that most technical decisions are all that important, um, that it never seems like the thing that means life or death for companies. And, you know, Facebook is still on PHP, they've fought, fixed, the problem with, with money. but I think I got rabbit holed into a few things where if I had like a business co-founder, then they would've grilled me about like, why are we spending? The, the main thing that comes to mind, uh, is real time multiplayer, real time. It was a fascinating problem and I was so ready to think about that all the time and try to solve it. And I think that took up a lot of my time and energy. And in the long term, most people are not editing a map. At the same time, seeing the cursors move around is a really fun party trick, and it's great for marketing, but I think that if I were to take a real look at that, that was, that was a mistake. Especially when the trade off was things that actually mattered. Like the amount of time, the amount, the amount of data that the, that could be handled at. At the same time, I could have figured out ways to upload a one gigabyte or two gigabyte or three gigabyte shape file and for it to just work in that same time, whereas real time made it harder to solve that problem, which was a lot closer to what, Paying customers cared about and where people's expectations were? Jeremy: When you were working on this realtime collaborative functionality, was this before the product was public? Was this something you, built from the start? Tom: Yeah. I built the whole thing without it and then added it in. Not as like a rewrite, but like as a, as a big change to a lot of stuff. Jeremy: Yeah, I, I could totally see how that could happen because you are trying to envision people using this product, and you think of something like Google Docs, right? It's very powerful to be typing in a document and see the other cursors and, um, see other people typing. So, I could see how you, you would make that leap and say like, oh, the map should, should do that too. Yeah. [00:34:29] Financial pressures of bootstrapping, high COL, and healthcare Tom: Yeah. Yeah. Um, and, you know, Figma is very cool. Like the, it's, it's amazing. It's an amazing thing. But the Figma was in the dark for way longer than I was, and uh, Evan is a lot smarter than I was. Jeremy: He probably had a big bag of money too. Right. Tom: Yeah. Jeremy: I, I don't actually know the history of Figma, but I'm assuming it's, um, it's VC funded, right? Tom: Uh, yeah, they're, they're kind of famous for just having, I don't think they raised that much in the beginning, but they just didn't hire very much and it was just like the two co-founders, or two or three people and they just kept building for long time. I feel like it's like well over three years. Jeremy: Oh wow. Okay. I think like in your case, I, I saw a comment from you where you were saying, this was your sole source of income and you gotta pay for your health insurance, and so you have no outside investments. So, the pressures are, are very different I think. Tom: Yeah. Yeah. And that's really something to on, to appreciate about venture capital. It gives you the. Slack in your, in your budget to make some mistakes and not freak out about it. and sadly, the rent is not going down anytime soon in, in Brooklyn, and the health insurance is not going down anytime soon. I think it's, it's kind of brutal to like leave a job and then realize that like, you know, to, to be admitted to a hospital, you have to pay $500 a month. Jeremy: I'm, I'm sure that was like, shocking, right? The first time you had to pay for it yourself. Tom: Yeah. And it's not even good. Uh, we need to fix this like that. If there's anything that we could do to fix entrepreneurship in this country, it's just like, make it possible to do this without already being wealthy. Um, it was, it was a constant stress. [00:36:29] Growth and customers Jeremy: As you worked on it, and maybe especially as you, after you had shipped, was there a period where. You know, things were going really well in terms of customers and you felt like, okay, this is really gonna work. Tom: I was, so, like, I basically started out by dropping, I think $5,000 in the business bank account. And I was like, if I break even soon, then I'll be happy. And I broke even in the first month. And that was amazing. I mean, the costs were low and everything, but I was really happy to just be at that point and that like, it never went down. I think that probably somebody with more, uh, determination would've kept going after, after I had stopped. but yeah, like, and also The people who used Placemark, who I actually chatted with, and, uh, all that stuff, they were awesome. I wish that there were more of them. but like a lot of the customers were doing cool stuff. They were supportive. They gave me really informative feedback. Um, and that felt really good. but there was never a point at which like the, uh, the growth scale looked like, oh, we're going to hit a point at which this will be a sustainable business within a year. I think it, according to the growth when I left it, it would've been like maybe three years until I would've been, able to pay my rent and health insurance and, live a comfortable life in, in New York. Jeremy: So when you mentioned you broke even that was like the expenses into the business, but not for actually like rent and health insurance and food and all that. Okay. Okay. can you say like roughly how much was coming in or how many customers you had? Tom: Uh, yeah, the revenue initially I think was, uh, 1500 MRR, and eventually it was like 4,000 or so. Jeremy: And the growth was pretty steady. [00:38:37] Bootstrapping vs fundraising Tom: Um, so yeah, I mean, the numbers where you're just like, maybe I could have kept going. but it's, the other weird thing about VCs is just that I think I have this rich understanding of like, if you're, if you're running a business that will be stressful, but be able to pay your bills and you're in control of it, versus running a startup where you might make life changing money and then not have to run a business again. It's like the latter is kind of better. Uh, if stress affects you a lot, and if you're not really wedded to being super independent. so yeah, I don't know between the two ways of like living your life, I, I have some appreciation for, for both. doing what Placemark entailed if I was living cheaply in a, in a cheap city and it didn't stress me out all the time, would've been a pretty good deal. Um, but doing it in Brooklyn with all the stress was not it, it wasn't affecting my life in positive ways and I, I wanted to, you know, go see shows at night with my friends and not worry about the servers going down. Jeremy: Even putting the money aside, I think that's being the only person responsible for the app, right? Probably feels like you can't really take a vacation. Right. Tom: Yeah, I did take a vacation during it. Like I went to visit my partner who was in, uh, Germany at the time, and we were like on a boat, uh, between Germany, across the lake to Switzerland, and like the servers went down and I opened up my laptop and fixed the servers. It's just like, that is, it's a sacrifice that people make, but it is hard. Jeremy: There's, there's on call, but usually it's not just you 24 7. Tom: Yeah. If you don't pick up somebody else [00:40:28] Financial stress and framing money spent as an investment Jeremy: Yeah, yeah, yeah, I guess at what point, because I'm trying to think. You started in 2021 and then maybe wrapped up, was it sometime in 2024? Tom: Uh, I took a job in, uh, I, I mean I joined val.town in the early 2023 and then wrapped up in November, 2023. Jeremy: At what point did you really start feeling the, the stress? Like I, I imagine maybe when you first started out, you said you were doing consulting and stuff, so, um, probably things were okay, but once you kind of shifted away from that, is that kind of when the, the, the worries about money started coming in? Tom: Yeah. Um, I think maybe it was like six or eight months, um, in. Just that I felt like I wasn't finding, uh, like a, a way to grow the product without adding lots of complexity to it. and being a solo founder, the idea of succeeding, but having built like this hulking mess of a product felt just as bad as not succeeding. like ideally it would be something that I could really be happy maintaining for the long term. Uh, but I was just seeing like, oh, maybe I could succeed by adding every feature in QGIS and that's just not, not a, not something that I wanted to commit to. but yeah, I don't, I don't know. I've been, uh, do you know, uh, Ramit Sethie he's like a, Jeremy: I don't. Tom: an internet money guy. He's less scummy than the rest of them, but still, I. an internet money guy. Um, but he does adjust a lot of stuff about like, money psychology. And that has made me realize that a lot of what I thought at the time and even think now is kind of a rational, you know, like, I think one of the main things that I would do differently is just set a budget for Placemark. Like if I had just set away, like, you know, enough money to live on for a year and put that in, like the, this is for Placemark bucket, then it would've felt better to me then having it all be ad hoc, month to month, feeling like you're burning money instead of investing money in a thing. but yeah, nobody told me, uh, how to, how to think about it then. Uh, yeah, you only get experience by experiencing it. Jeremy: You're just seeing your, your bank account shrinking and there's this, psychological toll, right? Where you're not, you're not used to that feeling and it, it probably feels like something's wrong, Tom: Yeah, yeah. I'm, I think it, I'm really impressed by people who can say, oh, I invested, uh, you know, 50 or a hundred thousand dollars into this business and was comfortable with that risk. And like, maybe it works out, maybe it doesn't. Maybe you just like threw a lot of money down into that. and the people, I think with the healthy, productive, uh, relationship with it. Do think of it as like, oh, I, I paid for kind of a bet on a risk. and that's, that's what I was doing anyway. You know, like I was paying my rent and my health insurance and spending all my time working on the product instead of paying, uh, freelance work. but if you don't frame it that way, it doesn't feel like an investment. It feels like you're making a risky gamble. Jeremy: Yeah. And I think that makes sense to, to actually, I think, like you were saying, have a separate account or a separate thing set aside where you are like, this is, this is this money for this purpose. And like you said, look at it as an investment, which with regular investments can go down. Tom: Yeah, exactly. Yeah. Jeremy: Yeah [00:44:26] In hindsight might have raised money or tried smaller bets Jeremy: Were there, there other things, whether technical or or business wise, that, that if you were to to do it again, you would do differently? Tom: I go back and forth on whether I should have raised venture capital. there are, there's kind of a, an assumption in venture capital that once you're on it, you have to go the whole way. You have to become a billion dollar company, uh, or at least really tell people that you're going to be a billion dollar company and I am not. yeah, I, I don't know. I've seen, I've seen other companies in my space, or like our friends of my current company who are not really targeting that, or ones who were, and then they had somewhere in between the billion dollar and the very small outcome. Uh, and that's a little bit of a point in the favor of accepting a big pile of money from the venture capitalists. I'm also a little bit biased right now because val.town has one investor and he's like the, the best venture capitalist that I have ever met. Big fan. don't quote me on that. If he sacks me in like a year, we'll see. Um, but uh, yeah, there, I, I think that I understand more why people take that approach. or I've understood more why people take like the venture capital but not taking $300 million from SoftBank approach. yeah, and I don't know, I think that, trying a lot of things also seems really appealing. Uh, people who do the same kind of. of Maybe 10 months, but they build four or five different products or three different products instead of just one. I think that, that feels, feels like a good idea to me. Jeremy: And in doing that, would that be more of a, like as a solo entrepreneur or you, you're thinking you would take investment and then say, I'm gonna try all these things with, with your money. Tom: Oh, I've seen both. I, that I, yeah, one friend's company has pivoted like four times between very different ideas and yeah, it, it's one way to do it, but I think in the long term, I would want to do that as a solo developer and try to figure out, you know, something. but yeah, I, I think, uh, so much of it is mindset, that even then if I was working on like three different projects, I think I. My qualifications for something being worth, really adopting and spending all my time doing, you just have to accept, uh, a lot of hits and a lot of misses and a lot of like keeping things alive and finding out how to turn them into something. I am really inspired by my friends who like started around the same time that I did and they're not that much further in terms of revenue and they're like still, still doing it because that is what they want to do in life. and if you develop the whole ecosystem and mindset around it, I think that's somewhere that people can stay and, and be happy. just trying to find, trying to find a company that they own and control and they like. Jeremy: While, while making the the expenses work. Tom: Yeah. Yeah. that's the, that's the hard part, like freelancing on the side also. I probably could have kept that up. I liked my freelance clients. I would probably still work with them as well. but I kind of just wanted the, I wanted the focus, I wanted the motivation of, of being without a net. Jeremy: Yeah, I mean, energy wise, do you think that that would've worked? I mean, I imagine that Placemark took a lot of your time when you were working full time, so you're trying to balance, you know, clients and all your customers and everything you're doing with the software. It just feels like it might be a lot. Tom: Yeah. Yeah. Maybe with different freelance clients. I, I loved my freelance clients because I, after. leaving config. I, I wanted to work on climate change stuff and so I was working for climate change foundations and that is not the way to max out your paycheck. It's the way to feel good about your conscience. And so I still feel great about those projects, but in the future, yeah, I would probably just work for, uh, you know, a hedge fund or something. [00:49:02] Marketing to developers but not potential customers Jeremy: I think something you mentioned in one of your posts is that you maybe could have spent more time or had a different approach with marketing. Maybe you could kind of say what you did do and then what maybe worked and what didn't. Tom: Yeah. So I like my sweet spot is writing documentation and blog posts and technical stuff. And so I did a lot of that and a lot of that like worked in a way that didn't matter. I am at this point, weirdly good at writing stuff that gets on Hacker News. I've written a lot of stuff that's gotten to the top of Hacker News and unfortunately, writing about your technical approach and your geospatial project for handling errors, uh, in your JavaScript code is not really a way to get customers. and I think doing a lot of documentation was also great, but it was also, I think that the, the thing that was missing is the thing that I think Mapbox does fairly well now, in which the homepage really pushes you toward use cases immediately. and I should have been saying to each customer who had anything compelling as a use case, like, let's write an article about you and what you're doing, and here's how you use this in your industry. and that probably would've also been like a good, a good way to figure out which of those verticals was the one that was most worth spending all the time on. yeah. So it, it was, it was a lot of good marketing to nerds. and it could have been better in terms of marketing to actual customers and to people who are making the buying decisions. Jeremy: Yeah. Looking at the, the Placemark blog, I can definitely see how as a developer, a lot of the posts are appealing to me, right? It's about how you worked on a technical challenge or decisions you made, but maybe less so to somebody who they wanna. Draw a map to manage their crops. They're like, I don't care about any of this. Right. Tom: Yeah, like the Mapbox blog used to be, just all that stuff as well. We would write about designing protocol buffer layouts, and it was amazing for hiring and amazing for getting nerds in the door. But now it's just, Toyota is launching with, Mapbox Maps or something like that. And that's, that's what you, you should do if you're trying to sell a product. Jeremy: Yeah. And I think the, the sort of technical aspect, it makes sense too. If you're venture funded and you are looking to hire, right? You wanna build your team and you just want to increase like, the amount of stuff you're building and not worrying so much about, am I gonna have a paycheck next Tom: Yeah. Yeah. I, I just kind of do it because it's fun, which is not the right reason to do it, but, Yeah, I mean, I still write my blog mostly just because it's, it's a fun thing to do, but it's not the best way to, um, to run a business. Jeremy: Yeah. Well, the fun part is important too though. Tom: Yeah. Yeah. That's, that's maybe the whole thing. May, that's maybe the most important thing, but you can't do it if you don't do the, the money part. [00:52:35] Most customers came from existing audience Jeremy: Right. So the people who did find you, was it mostly word of mouth from people who did identify with the technical posts, or were there places that surprised you, that people found you? Tom: Uh, a lot of it was people who were familiar with the Mapbox ecosystem or with, with me. and then eventually, yeah, a few of the users came in through, um, through Hacker News, but it was mostly, mostly word of mouth also. The geospatial community is like fairly tight and it's, and it's not too hard to be the person who writes the article about some geospatial challenge that everyone finds. Jeremy: Hmm. Okay. Yeah, that's a good point about like being in that community, especially since you've done so much work in geospatial and in open source that you have this little, this built-in audience, I guess. Tom: yeah. Which I appreciate. It makes me nervous, but yeah. [00:53:43] Val.town marketing to developers Jeremy: Comparing that to something like val.town, how is val.town marketing? How is it finding users? 'cause from what I can tell, it's, it's getting a lot of, uh, a lot of people coming in, right? Tom: Yeah. Uh, well, right now our, our kind of target user, or the user that we think of is a hobbyist, is somebody who's, sometimes a pro developer or somebody, sometimes just somebody who's really interested in the field. And so writing these things that are just about, you know, programming, does super well. Uh, but it, we have exactly the same problem and that that is kind of being revamped as we speak. uh, we hired somebody who actually knows marketing and has a good sense for it. And so a lot of that stuff is shifting to show you what you can do with val.town because it, it suffers from the same problem as well. It's an empty text field in which you can type, type script, code, and it runs. And knowing what you can do with that or what you should do with that is, is hard if you don't have a grasp of TypeScript and web applications. so pretty soon we'll have pages which are like, here's how to connect linear and GitHub with OW Town, or, you know, two nouns connect them, for all of those companies and to do automations and all these like concrete applications. I think that's, you have to do it. You have to figure it out. Jeremy: Just briefly for someone who hasn't heard of val.town, like what, what does it do? Tom: Uh, val.town is a social website, so it has comments and likes and all of that stuff. but it's for writing these little snippets of TypeScript and JavaScript code that run. So a lot of them are websites, some of them are automations, so they receive emails or send emails or connect one service to another. And yeah, it's, it's like combining some aspects of, GitHub or like a code platform, uh, but with the assumption that every time that you save, everything's instantly deployed. Jeremy: So it's maybe a little bit like, um, like a glitch, I guess? Tom: Uh, yeah. Yeah, it takes a lot of experience, a lot of, uh, inspiration from Glitch. Jeremy: And I, I think, like you had mentioned, you enjoy writing the, the technical blog posts and the documentation. And so at least with val.town, your audience is developers versus, the geospatial community who probably largely doesn't care about, TypeScript and the, the different technical decisions there. Tom: Yeah, it, it makes it easier, that's for sure. The customer is, is me. [00:56:30] Shifting from solo to in-person teams Jeremy: Nice. Yeah. Looking at, you know, you, you worked as a, a solo developer for Placemark, and then now you've got a team of, is it like maybe five Tom: Uh, it is seven at the moment. Jeremy: Seven people. Okay. Are you all in person or is it, remote Tom: We all sit around two tables in Brooklyn. It's very nice. Jeremy: So how did that feel? Like shifting from, I'm in, I don't know if you worked from home while you were working on Placemark or if you were in coworking spaces, but you're, you're shifting from I'm like in my own head space doing everything myself to, to, I'm in a room with all these people and we're like working on this thing together. I'm kind of curious like how that felt for you. Tom: Yeah, it's been a big difference. And I think that I was just talking with, um, one, one of our, well an engineer at, at val.town about how everyone kind of had, had been working remote for obvious pandemic world reasons. And this kind of privilege of just being around the same table, if that's what you like is, a huge difference in terms of, I just remember having to. Trick myself into going on a walk around the block because I would get into such a dark mental head space of working on the same project for eight hours straight and skipping lunch. and now there's a little bit more structure. yeah, it's, it's been, it's been a overall, an improvement. Some days I wish that I could go on a run at noon 'cause that's the warmest time of the day. but, uh, overall, like it makes things so much easier. just reading the emotions in people's faces when they're telling you stuff and being able to, uh, not get into discussions that you don't need to get into because you can talk and just like understand each other very quickly. It's, it's very nice. I don't wanna force everyone to do it, you know, but it it for the people who want it, they, they, uh, really enjoy it. Jeremy: Yeah. I think if you have the right set of people, it's definitely more enjoyable. And um, if you don't, maybe not so Tom: Yeah, we haven't hired any, like, extremely loud chewers yet or anything like that, but yeah, maybe my story will change. Jeremy: No, no one microwaving fish. Tom: No, there's, uh, yeah, thankfully the microwave is outside of the office. Jeremy: Do you live close to the office? Tom: Yeah. Yeah. Like most of the team is within a 20 or 30 minute walk of the office and it's very fortunate. I think there's been something of a mass migration to New York. A lot of us didn't live in New York before four years ago, and now all of us do. it's, it's, uh, it's very comfortable to be here. Jeremy: I think that makes, uh, such a big difference. 'cause I think the majority of people, at least within the US you know, you're, you're getting in your car, you're sitting in traffic. and I know people who, during the pandemic, they actually moved further, right? Because they went, oh, like, uh, I don't need to come into the office. but yeah, if you are close enough where you can walk, yeah, I think that makes a big difference. Tom: Oh yeah. If I had to drive to work, I think my blood pressure would be so much higher. Uh, especially in New York. Oh, I feel so bad for the people who have to drive, whereas I'm just walking with, you know, a bagel in hand, enjoying listening to the birds. Jeremy: Yeah. Yeah. well now they have, what is it, the congestion pricing in Tom: Yeah. Yeah. We're all in Brooklyn, so it doesn't affect us that much, but it's supposedly, it's, it's working great. Um, yeah. I hope we can keep it. Jeremy: I've never driven in New York and I, I wouldn't want to Tom: Yeah. It's only for the brave or the crazy. [01:00:37] The value of public writing and work Jeremy: I think that's probably a good place to, to wrap up, but is there any other thoughts you had or things you wanted to mention? Tom: No, I've just, uh, thank you so much. This has been, this has been a lot of fun. You're, you're very good at this as well. I feel like it's, uh, Jeremy: Thank you Tom: It's not easy to, to steer a conversation in a way that makes awkward people sound, uh, normal. Jeremy: I wouldn't say that, but um, what's been actually pretty helpful to me is, you have such a body of work, I guess I would say, in terms of your blogging and, just the amount that you write and the long history of projects that, that there's, you know, there's a lot to talk about and I'm sure it helps, helps your thought process as well. Tom: Yeah. I, I've been lucky to have a lot of jobs where people, where companies were like, cool with publishing everything, you know? so a lot of what I've done is, uh, is public. it's, it's, uh, I'm very, very thankful for like, early on that being a big part of company culture. Jeremy: And you can definitely tell, I think for people who look at the Placemark blog posts or, or now your, your val.town blog posts, like there's, there's a clear difference when somebody like is very intentional and, um, you know, it's good at writing versus you're doing it because, um, it's your corporate responsibility or whatever, like people can tell. Yeah. Tom: Yeah. You can't fake being interested. so you gotta work on things that are interesting. Jeremy: Tom, thanks again for, for agreeing to chat. This was fun. Tom: Yeah thank you so much.

אם אתם מנהלים הרבה אתרים וזקוקים לדרך נוחה יותר לניהול השרתים שלכם, הנה טיפ שיכול לחסוך לכם זמן ואנרגיה! בסרטון הזה, אציג לכם טכניקות וכלים לניהול שרתים בצורה יעילה, שיעזרו לכם לשלוט בצורה מאורגנת על כל האתרים, לקבל התראות בזמן אמת, ולבצע עדכונים ואבטחה באופן פשוט ומהיר. נדבר על שימוש בפתרונות כמו cPanel, Plesk, וכלים לניהול מרכזי כמו ManageWP או InfiniteWP לניהול מרוכז של אתרי וורדפרס. בנוסף, אציג כלים מתקדמים לניטור ביצועים, ניהול אבטחה, גיבויים אוטומטיים וכלים שיעזרו לכם לפתור תקלות בקלות. אם אתם מנהלי אתרים או אנשי DevOps, הסרטון הזה יספק לכם כלים חשובים שיעזרו לכם לנהל את האתרים והשרתים שלכם ביעילות ובמקצועיות. אל תשכחו להירשם לערוץ וללחוץ על הפעמון כדי לקבל עדכונים על מדריכים נוספים לניהול שרתים, אתרים וכלים טכנולוגיים מתקדמים. אם הסרטון עזר לכם, תנו לייק ושתפו עם חברים! קבלו עוד טיפ שיעזור לכם לנהל את השרתים שלכם אם אתם מנהלים הרבה אתרים: איתי ורצ'יק IVBS SEO / PPC בסרטון זה תלמדו: איך לנהל שרתים מרובים וכלים לניהול אתרים באופן מרכזי. איך להשתמש ב-ManageWP ו-InfiniteWP לניהול אתרי וורדפרס. טיפים לניטור ביצועים, אבטחה, וגיבויים אוטומטיים. אל תפספסו סרטונים נוספים בערוץ: https://www.youtube.com/c/ItayVerchik?sub_confirmation=1 להרשמה למערכת לקידום אתרים: https://say-v.com/ הצטרפו עכשיו לקהילה של בוני ומקדמי האתרים הטובים בישראל בחינם: https://www.facebook.com/groups/israelwp לרכישת אלמנטור פרו, מעצב העמודים בוורדפרס הטוב בעולם:⁠⁠ https://trk.elementor.com/2500⁠⁠ אין לכם עדיין חשבון אחסון אתרים או שאתם לא מרוצים מהאחסון הקיים שלכם? קבלו הנחה לאחסון אתרים קלאודוויז 25% ל-3 חודשים ראשונים: https://platform.cloudways.com/signup?id=314159&coupon=VERCHIK תודה שצפיתם! אם יש לכם שאלות או רעיונות לנושאים נוספים שתרצו שנדבר עליהם, כתבו לי בתגובות ואני אשמח לעזור.

Hello folks, welcome to the security box, podcast 168. On this program, we'll see if we've got any morons, a service that is a phishing service, news, notes and more. The "You Stupid fuck" awards of the podcast If this isn't a moron, I don't know what is. The blog post is titled Tech CEO sentenced to IP addressing scheme which is coming from our blog. It leads to the article we spotted talking about this guy. We may have talked about Micfo LLC before, but this is probably the end of this. Problem: the JRN thinks that 5 years isn't going to be enough and isn't a harsh sentence for the crime. Please sound off if you believe that this is the case. ----------------------------- If you are prone to email scams, you might want to pay attention to this. One of my MENVI staff was smart enough to contact me to ask if they needed to do what the action in the email indicated. The bad news is that the site truly wasn't MENVI's, it looked nasty and never redirected as I thought it might. An email pretending to come from Cpanel, isn't cpanel … can you smell trouble? has the complete details of this one. Sound off if you've seen something similar to this and whether you fell for it or not. Its OK if you did. There should be no shame! ---------------------------------------------------------- Solar Winds is getting sued. Seems as though they were never as secure as they should have been, and the CEO among others are getting sued. We thought that something was wrong, seeing how we later found out about how that compromise was completely done. Whether they were compromised by Russia or not isn't the point of the lawsuit, says the article, but boy ... this is probably as bad as you get when it comes to a supply chain attack. Here is the blog post titled SEC sues Solar Winds for fraud, says they are secure and the charges are baseless for your perusal. It can't get any better than this, can it? Our topic: Phishing as a service Today, we are going to have a very interesting topic that might be known later as a threat. This comes from our friends at Phishlabs. The article is titled Threat Actor Profile: Strox Phishing-as-a-Service and it was a good one. We'll break this down, as phishing as a service now takes hold. Supporting the podcast If you'd like to support our efforts on what this podcast is doing, you can feel free to donate to the network, subscribing to the security box discussion list or sending us a note through contact information throughout the podcast. You can also find contact details on our blog page found here. Thanks so much for listening, reading and learning! We can't do this alone.

Síguenos en: ¿Qué tal la semana? Semana esther Problemas versión Plesk que bloquea actualizaciones de plugins y conexiones externas (error "Update failed: Download failed. cURL error 77:" ) Maquetación en editor bloques WP de landing HTML/CSS a medida Integración solución Correos en e-commerce a medida Semana Nahuai Follow-up, parece que los problemas de carga de los estilos de backend se solucionaron pasando una de las instalaciones de WordPress a PHP 7.4. Error 403 al intentar instalar un plugin en otro proveedor de hosting, tuve que desactivar mod_security desde cPanel. Jugando con las opciones de añadir contenidos entre bloques. Trasteando con los block hooks que llegaran en WordPress 6.4. Probando los plugins y temas de OsomPress con la versión de WordPress 6.4. Reunión del grupo de sostenibilidad de W3C. Trabajando en el tercer borrador y creando material que sea más fácil de entender y accionar. También se ha publicado la API. Si interesa el tema puedo preparar un episodio. Última reunión de Green Web Foundation. Reunión semanal del equipo de sostenibilidad de WordPress, nueva votación en marcha se comentó la opción de crear canales locales. Hoy Meetup de Terrassa donde Marc Soro hablará de diseño. Contenido Nahuai 2 nuevos tutoriales en Código Genesis de los cuales destaca: Publicado el tercer episodio de Sustain WP en que hablamos del pilar social de la sostenibilidad. Novedades Ya está disponible el guía de campo para desarrolladores de WordPress 6.4: https://make.wordpress.org/core/2023/10/23/wordpress-6-4-field-guide/ Fathom Analytics permite crear eventos: https://usefathom.com/docs/features/events y también eliminará su servicio de monitorización de webs. Tip de la semana Crear una webapp con MacOS Sonoma (opción de añadir al dock desde Safari) Menciones Jordi nos deja la siguiente pregunta: ¿Hay algún plugin que SIEMPRE instaléis junto a Wordpress? Ese plugin que no te lo piensas. Da igual si es un e-commerce, blog, web corporativa, etc. El MUST de los plugins, el imprescindible. (reto: intentad responder sin usar la palabra "depende". ¡juah!) Gracias por acompañarme en mis caminatas matutinas. Saludos Jordi (el panadero wordpresero) Catalina nos felicita por el episodio sobre la beca de Green Web Foundation.

Síguenos en: ¿Qué tal la semana? Semana esther Problemas versión Plesk que bloquea actualizaciones de plugins y conexiones externas (error "Update failed: Download failed. cURL error 77:" ) Maquetación en editor bloques WP de landing HTML/CSS a medida Integración solución Correos en e-commerce a medida Semana Nahuai Follow-up, parece que los problemas de carga de los estilos de backend se solucionaron pasando una de las instalaciones de WordPress a PHP 7.4. Error 403 al intentar instalar un plugin en otro proveedor de hosting, tuve que desactivar mod_security desde cPanel. Jugando con las opciones de añadir contenidos entre bloques. Trasteando con los block hooks que llegaran en WordPress 6.4. Probando los plugins y temas de OsomPress con la versión de WordPress 6.4. Reunión del grupo de sostenibilidad de W3C. Trabajando en el tercer borrador y creando material que sea más fácil de entender y accionar. También se ha publicado la API. Si interesa el tema puedo preparar un episodio. Última reunión de Green Web Foundation. Reunión semanal del equipo de sostenibilidad de WordPress, nueva votación en marcha se comentó la opción de crear canales locales. Hoy Meetup de Terrassa donde Marc Soro hablará de diseño. Contenido Nahuai 2 nuevos tutoriales en Código Genesis de los cuales destaca: Publicado el tercer episodio de Sustain WP en que hablamos del pilar social de la sostenibilidad. Novedades Ya está disponible el guía de campo para desarrolladores de WordPress 6.4: https://make.wordpress.org/core/2023/10/23/wordpress-6-4-field-guide/ Fathom Analytics permite crear eventos: https://usefathom.com/docs/features/events y también eliminará su servicio de monitorización de webs. Tip de la semana Crear una webapp con MacOS Sonoma (opción de añadir al dock desde Safari) Menciones Jordi nos deja la siguiente pregunta: ¿Hay algún plugin que SIEMPRE instaléis junto a Wordpress? Ese plugin que no te lo piensas. Da igual si es un e-commerce, blog, web corporativa, etc. El MUST de los plugins, el imprescindible. (reto: intentad responder sin usar la palabra "depende". ¡juah!) Gracias por acompañarme en mis caminatas matutinas. Saludos Jordi (el panadero wordpresero) Catalina nos felicita por el episodio sobre la beca de Green Web Foundation.

Kendall Miller is the Co-Founder and COO of CTO Lunches, a network of engineering leaders to get trusted advice and connections. The first half of the conversation with host Victoria Guido and special guest host, Joe Ferris, CTO of thoughtbot revolves around the use, adoption, and growth of Kubernetes within the technology industry. The discussion explores Kubernetes' history, influence, and its comparison with other platforms like Heroku and WordPress, emphasizing its adaptability and potential. The second half focuses on more practical aspects of Kubernetes, including its adoption and scalability. It centers on the appropriateness of adopting Kubernetes for different projects and how it can future-proof infrastructure. The importance of translating technical language into business speak is emphasized to influence executives and others in the decision-making process and Kendall also discuss communication and empathy in tech, particularly the skill of framing questions and understanding others' emotional states. __ CTO Lunches (http://ctolunches.com/) Follow CTO Lunches on LinkedIn (https://www.linkedin.com/company/ctolunches/) or Twitter (https://twitter.com/cto_lunches). Follow Kendall Miller on LinkedIn (https://www.linkedin.com/in/kendallamiller/). Follow thoughtbot on Twitter (https://twitter.com/thoughtbot) or LinkedIn (https://www.linkedin.com/company/150727/). Become a Sponsor (https://thoughtbot.com/sponsorship) of Giant Robots! Transcript: VICTORIA: This is the Giant Robots Smashing Into Other Giant Robots Podcast, where we explore the design, development, and business of great products. I'm your host, Victoria Guido. And with me today is Kendall Miller, Co-Founder and COO of CTO Lunches, a network of engineering leaders to get trusted advice and connections. Kendall, thank you for joining me. KENDALL: Thanks for having me. I'm excited. VICTORIA: And today, we have a special guest host, Joe Ferris, CTO of thoughtbot. Joe, thank you for joining us. JOE: Hello there. Thank you for having me. KENDALL: Hi, Joe. Thanks for being here. It's exciting. VICTORIA: Yes. It's so exciting. I think this is going to be a great episode. So, Kendall, I met you at a San Diego CTO lunch recently, and I know that's not the only thing that you do. So, you're also an advisor, a board member, and CXO. So, maybe tell us a little bit more about your background. KENDALL: Gosh, my background is complicated. I've been involved in tech for a very long time. In college, I worked for a company that started Twitter about five years too soon, and then worked in the nonprofit space in China for ten years, then came back, got back involved in tech. Today, I'm usually the business guy. So, when technical founders start technical products and want help turning them into successful technical businesses, that's when they call me. So, I have the technical background. I have never been paid to write code, which is probably a good thing. But I can hang in the technical conversations for the most part, but I'm much more interested in the business side and the people leadership side of business. So that tends to be where I play. Every organization hires me to do something different. VICTORIA: Thank you for that. And I'm just curious about the CTO Lunches. Just tell me a little bit more about that. And what's the idea behind it that led you to co-found it? KENDALL: CTO Lunches has actually been around for about eight years. And I didn't start the initial incarnation of it. It was two people that got us started, and I was trying to hire one of them; one thing led to another. Actually, originally, they did not want me to join. I think, at the time, my title was COO at a company that I was working with. About six months later, I took over engineering as VP of engineering, and then they're like, you can join the group now. We're less strict about that [laughs] now. Although it is highly focused on senior engineering leaders, it's not exclusively CTOs. But the group's been in place for a very long time, just intended as a place to network, have conversation with people who are in that senior-most technical position at technical organization. So, the CTO role is a lonely role. CTOs get fired all the time. There's not a technical person at the company that doesn't think they can do the job better than them. So, the CTO is always getting feedback. You're doing this wrong. The trade-offs you're making are wrong. This isn't going where it should be going. We should automate that. Why haven't we automated that? We should switch to this other tool. I've used it before; it's 100 times better. Joe, let me know if I'm getting any of this wrong. But that's the experience that I've had. Having a place where people can get together and, you know, half the time just complain to each other, hey, this is hard, is really why the networking group exists. So, it's a listserv. And there are local lunches that started in Boulder, Colorado. It's gotten pretty global. About a year ago, a little over a year ago, I was talking with one of the people who'd gotten it started. I've been involved in the Denver chapter for most of those eight years. And I was suggesting to him that he change a few things about it, to monetize it so that he could invest in it further. And he came back a few months later and said, "I want to take your advice and do this, but I want you to come do it with me." So, we founded the company officially...I think in December is when paperwork went into place. And we started investing in it a little bit more heavily. I was living in Europe last year, so we went and put on lunches in Paris, and Lisbon, and London, and, gosh, all over the place. I'm sure I'm missing some, Amsterdam. But there's been chapters all over the U.S. and a couple of other parts of the world for a long time. VICTORIA: That reflects my experience attending a CTO lunch. It's just very casual, like, just get together and eat food and talk about what you've worked on recently, issues you're having, just get ideas and make some friends. So, I really appreciated the group, and I'm going to personally plug the San Diego Chapter has picked up again. And we're meeting next Friday down in Del Mar. And we're going to be meeting on the last Friday of every month through October. So, I'm super excited to be a part of the group. And Joe, yeah, I'm curious about your perspective. As a CTO with thoughtbot, just what are your thoughts about that kind of thing? KENDALL: Yeah. How right am I about how lonely you are, Joe? JOE: [laughs] You know, I've been lonelier since we went remote. I used to work in the office, and I was a CTO, but also, I had lunch with people, which was nice. So, I'm lonelier. But yeah, I think everybody needs a group like that, like, senior developer therapy just to talk about your woes together, drown your sorrows. KENDALL: Well, I think years ago, I heard that CTOs are the most fired C-level executive. JOE: You're making me nervous now. KENDALL: [laughs] You've been there a long time, Joe. I know you've been there a long time. If you haven't been fired yet, you probably got a little while longer in you. This will be really awkward if it's published and you've already been fired. VICTORIA: We can always edit that out afterwards. [laughter] KENDALL: Yeah, no, I think it is a particularly lonely position. And, again, I think a lot of it is the average engineer in a technical company doesn't look at the COO or the CFO or even the CEO and think I could do that. But they're all looking at the CTO and thinking, what does that person do that I can't do? It's ridiculous because most of them would make terrible CTOs because it does require some of the business sense. Or, you know, right out of the gate, they might make terrible CTOs. It actually is quite a skill to be the most technical person and speak the business language. I mean, am I right about that, Joe? Like, was that hard for you to learn? JOE: Yeah, I definitely think...so, my background is also technical. I have a background in consulting. So, I always did a lot of metaprogramming, if you will. But making that transition to thinking about organizations that way, thinking about how all the other pieces play into it, was a pretty big step for me, even before I became a CTO as a consultant. KENDALL: Well, because you can't just chase the newest, hottest technology. You have to make business trade-offs. And not everything can be resume-driven development, right? Even if that technology over there is newer or hotter, it doesn't mean you have a business model that supports it. And it doesn't mean that migrating to it can be done, right? JOE: Yeah. I mean, even beyond choosing technologies, just choosing where to invest in your software stack, like, what needs to be reworked, what doesn't, and trying to explain those trade-offs, I think, is a rare skill. Being able to explain why something would be harder than something else when you're working with the leadership to prioritize a backlog it's a puzzle. KENDALL: Well, and I think when I'm in an executive conversation, and the CTO says, "Here's the thing that I think is the best decision technically, and I think it's the wrong decision for the business because of X, Y, or Z," I'm always super impressed, right? Like, this is the right technical solution for what we want. However, we shouldn't pursue that for business reasons right now. Maybe we can in six months, but right now, we need to prioritize this other thing. I don't know, that's always when I feel like, oh, this person knows what they're doing. JOE: There's nothing more dangerous to software than a bored developer. [laughs] One nice thing about being a consultant is that I don't have to invent problems to solve with technology at my company because sooner or later, I'll run across a company that has those problems, and I'll get to use that technology. But I think a lot of people are mostly happy...they might be happy in their role. They might be happy with our team. But they're very interested in whatever is hot right now, like machine learning, AI. And so, suddenly, that surreptitiously makes its way into the tech stack. And then, years later, it's somebody's problem to maintain. KENDALL: [laughs] Well, I have a specific memory of a firm in New York City that was, you know, this is relevant to y'all as thoughtbot is that, you know, at least historically, it was, to me, the premier Ruby on Rails consulting shop. I think that's still largely y'alls focus. Am I right about that? JOE: We still do a ton of Rails, yeah. KENDALL: Okay. Well, so this organization was all Ruby on Rails. It was a big organization. They had a very large customer base. And they hired a new CTO who came in, told everybody in the company they were stupid, laid off 70% of the engineering organization, and told the CEO he was going to completely rewrite the product from scratch in .NET, and he could do it in three weeks. And I'm pretty sure the business went under about three months later [laughs] because that was just so outrageously nuts to me. JOE: It's too bad he laid everybody off beforehand. I've been in that situation where somebody tells me, "I'm going to rewrite this. It'll be ready in three weeks." And I could fight with them and try and convince them they're wrong. But I feel like somebody who's approaching that with that attitude they're missing all of the nuance and context that would make it possible to explain to them why it's not going to work. And so, it's easier to just say, "You know, take the three weeks. I'll talk to you in three weeks." But if you've already laid off your development team, that's hard [laughs] to recover from. KENDALL: That's exactly right. VICTORIA: There's got to be a name for that kind of CTO who just wants to come in and blow everything up [laughs]. Yeah, so you spend a lot of time talking to different CTOs and doing this social networking aspect. I'm wondering if there's, like, patterns that you see. You've mentioned already one about just, like, the most often getting fired. [laughs] But what are the patterns you see, like, in challenges, and then what makes someone successful in that CTO role? KENDALL: Well, oh gosh, I have so many thoughts about this. First of all, I run into a couple of different categories of CTOs. There's a lot of people who come to CTO Lunches who are small company CTOs. I mean, it makes sense that there's a lot more small company CTOs than there are big company CTOs. But the small company CTO who maybe it's their first gig in the role or they're a serial CTO. There's the fractional CTOs that come that are doing it across several different organizations at the same time, and then there's the big company CTO who shows up. And honestly, all of their problems are very different. The thing that they have in common is even at a very large organization, in that position, they can make a decision that causes the company to go under. So, there is a significant amount of volatility in the amount of power that they wield. So, what's interesting about that is not everybody understands that. And so, first of all, there's the kind of CTO that just doesn't get that, and that doesn't matter if they're fractional, or a small company CTO, or a big company CTO. If they don't understand that, they're going to cause significant problems, right? Like the person I just mentioned who said, "I can just re-platform this in three weeks in .NET." There's that. I mean, I think, as with any senior leadership position, the comfort with volatility, the ability to know what to communicate down versus across and versus up, and then the ability to speak the business language. For everybody, the CFO's job is to communicate the financial needs alongside of the business leads, right? If the CFO's sole goal is to cut costs or make sure we're running as lean as possible, they're a bad CFO. But they're not as good of a CFO as the CFO who can say, "Hey, we're underspending right here. And I can look at the numbers and know we should invest more there. How can we invest more there and invest it well?" And it's the same thing for a technology executive to be able to look at the business context and communicate it back. And there are so many CTOs that I've worked with who they're the most technical person in the room, and they know it. And as a result, they're just a jerk to everyone around them, like, everything you did here was wrong. You know, that's where they fail. And so, if they can communicate the business needs, navigate the volatility, and support a team that's going to make decisions that aren't always the same decision they're going to make, they're going to be successful. Honestly, there's very, very few CTOs that I've met like that. People who are excited to meet you at work, excited to see you succeed, excited to see that you went and built a thing is great. I mean, the reason I was VP of engineering is the CTO that I was working with at the time...it's a terrible story. There was an engineer who had seen something that we were doing on repeat all the time and, in his spare time, spent about 40 hours outside of work, not during work hours, automating this task that we were doing regularly. And it was related to standing up a whole bunch of things in our standard infrastructure. He brings it to the CTO and says, "Look what I built." And the CTO, instead of saying, "Hey, this is incredible. Thank you. This is going to save us a bunch of time. Let's iterate on it. Here's some things I'd like to tweak. Can we bring it in this direction? Can we..." you know, whatever, said, "Why is this in Python? It should be in Ansible," something like that. I can't remember. And the engineer literally burst into tears. [laughs] JOE: Oh my God. KENDALL: [laughs] Well, I mean, yeah, it was like; literally, that's why the CTO stopped managing people that day. There's a lot of examples that I have like that. Joe, I appreciate that your response is, "Oh my God." Because I think there's a lot of people who'd be like, wait, what was wrong with that? Shouldn't it have been in Ansible? JOE: [laughs] Yeah, I've seen CTOs come into primarily two groups. One is the CTO who just tells, you know, like, they make the decisions, and they tell everybody what to do. They obviously don't have all of the information because you can't be in every room all the time. And the other is the CTO, who just wants to be one of the team members and doesn't make any decisions and tries to get people to make decisions collectively on their own without any particular guidance or structure. And finding that middle spot of, like, not just saying, "Hey, everything's in Ansible," allowing for the creativity and initiative, but also coalescing the group into a single direction, I think, is what makes a good CTO. KENDALL: Well, yeah, because the CTO does have to say no, sometimes, right? Like, the best product, people say, "No." Good CTOs say, "No." There is some amount of, hey, I need you to come to me with trade-offs about this. Why are you going to make that decision? And I'm sorry, you still didn't convince me, right? Like, I mean, those are appropriate things to say. But yeah, I'm with you on that. You said they fall into two categories. But you really mean the third and that middle ground. Is it easy for you to walk that middle ground, Joe? JOE: I wouldn't say it's easy. [laughs] KENDALL: Yeah. Well, I'm always nervous to say something. I'm doing well because I know there's a report out there that can point at every time I failed at it, right? So... MID-ROLL AD: Are you an entrepreneur or start-up founder looking to gain confidence in the way forward for your idea? At thoughtbot, we know you're tight on time and investment, which is why we've created targeted 1-hour remote workshops to help you develop a concrete plan for your product's next steps. Over four interactive sessions, we work with you on research, product design sprint, critical path, and presentation prep so that you and your team are better equipped with the skills and knowledge for success. Find out how we can help you move the needle at: tbot.io/entrepreneurs. VICTORIA: Yeah, what I'm getting from what you're saying, too, is this communication ability and not just, like, to communicate clearly but with a high level of empathy. So, if you say like, "Well, why is it in Python and not Ansible?" is different than being like, "What makes Python the best solution here?" Like, it's a different way to frame the question that could put someone on the defensive that just really requires, like, a high level of emotional intelligence. And also, if they've just worked, like, an 80-hour week, [laughs] I probably would maybe choose a different time to bring those questions up and notice that they have been burning the candle at both ends and prioritize getting them some rest. So, speaking of, like, communication and getting prioritization for [inaudible 15:34], especially on, like, infrastructure teams, maybe we could talk a little bit about Kubernetes, like, when that comes up as an appropriate solution, and how you talk about it with the business. KENDALL: My background with Kubernetes is long because a company that I still work with, Fairwinds, used to be called ReactiveOps, has been in the Kubernetes space for a very long time. I think we were one of the very first companies working with Kubernetes. It was coming up that people were running into the limits of something like Heroku, right? And I think it's Kelsey Hightower who said every company wants a PaaS. They just want the Paas that they built themselves. And that's really accurate. And I think Kubernetes isn't quite a framework for building your own PaaS or isn't quite a foundation where I think of a foundation for a house. Instead, it's more like rebar and cement and somebody saying, "Good luck, buddy." You know, you still have to know how to put the rebar and cement together to even make the foundation, but it is the building blocks that help get you to a custom-built PaaS. And it's become something that a lot of people have landed on as, you know, the broadly accepted way to build cloud-native infrastructure. The reason I've been in the Kubernetes space and the space that I see Kubernetes still filling is we need to standardize on something. We can choose a cloud provider's PaaS. We can choose a third-party PaaS, or we can standardize on something like Kubernetes. And even though we're not going to migrate from AWS to Azure, the flexibility that Kubernetes gives us as a broadly adopted pattern is going to give us some ability to be future-proofed in our infrastructure in a way that previous stacks were not, you know, it was Puppet, and it was Ansible. And it was SaltStack. And it was all Terraform all the time. I'm not saying those things don't exist anymore. I'm saying Kubernetes kind of has won that battle. Joe, since you're here and I know y'all are doing some Kubernetes work now at thoughtbot, I'm curious if you agree with that characterization. JOE: Yeah, I think that's true. I think it's the center for people to coalesce around. Like, for an effort in the industry to move forward, there needs to be some common language, some common ground. And I think Kubernetes struck the right balance of being abstract. So, you can use it in different environments but still making some decisions, so you don't have to make them all. And so, like, all of the things you had to do with containers like figuring out what your data solution is going to be, what your networking solution is going to be, Kubernetes didn't even really make those decisions. [laughs] They just made a platform where those decisions can be made in a common way. And that allowed the community and the ecosystem to grow. KENDALL: I mean, I think of it a lot like WordPress; you know, WordPress is hated by many. When WordPress came out, it was hot, right? And it was PHP, which everybody was super excited about at the time. Kubernetes is going to reach a point where it's as long in the tooth and terrible as people think WordPress is, but it has become the standard. And the advantage of the standard is you can use the not standard. You can go build a website in Jekyll instead of WordPress, and there's going to be some things that are nicer about Jekyll. But because WordPress is so broadly adopted, there's a plugin for everything. And I think that's where Kubernetes sits is because it's become so widely adopted everybody's building for it. Everybody's adapting for it. If you run into a problem, you're going to find somebody else out there who has that problem. In fact, I think of one organization that I know that was on HashiCorp's Nomad. And they said, "Actually, we think Nomad has better technology through and through. But we think we're the only company at this size and scale using Nomad. And so, when we run into a problem, we can't Google for it. There's no such thing as a plugin that exists to solve this. Nobody has ever run into this before on Nomad. But there's 100 companies dealing with the same problem in Kubernetes, and there's ten solutions." And I think that's the power that it brings. VICTORIA: So, it's not just a trend that CTOs are moving towards, you think. KENDALL: I mean, I think it's already won the battle and the hockey stick of adoption. We're still right at the very bottom of that tick-up because it takes people a long time to adapt new technology like this, especially in their infrastructure. It's a big migration, to move. So, I don't think it's the widely adopted infrastructure technology even yet. I think a lot of the biggest organizations are still running on things that predate Kubernetes. But I think it has won the battle, and it is winning the battle and is going to be the thing going forward, so yeah. JOE: I think it also has a lot of room to grow still. Like, there are other technologies that I used previously, like Docker, and they were a big step up from some of the things I was doing at the time. But you quickly hit the ceiling, or it was, like, I don't know where to go with this next. I don't know what else is going to happen. Whereas with Kubernetes, there are so many directions it can go in. Like, the serverless Kubernetes offerings that are starting to pop up are extremely interesting, where, you know, you don't actually maintain a cluster or anything. You just deploy things to this ethereal cluster that always exists. And so, that sort of combination of platform as a service, function as a service, Kubernetes, as that evolves, I think there are a lot of exciting things that have yet to come in the Kubernetes space. KENDALL: Well, so say more about that, Joe, because I've been going to KubeCon for a very long time, maybe...I don't know if it's 2016 or so when I first went. And it felt for a number of years...maybe those first four-ish years it was always the people at KubeCon were the, like, big dreamers and thinkers and, like, we're here to change the future of cloud infrastructure. And this is going places, and we're excited to be here and be a part of it. And here's what I'm going to do that changes the next thing. And I feel like now if I go to KubeCon, it's a lot of people from, you know, IBM and some big bank that are, like, deep sigh, well, I have to adopt Kubernetes. I need to know what the vendors are. What do you guys do, and how does this work? Can you please teach it to me? Because I'm being told by my boss, I have to do it. I don't see that excitement around Kubernetes anymore. The excitement I see is all around further up the stack, you know, things like Wasm, WebAssembly, or eBPF, the networking things and tracing things that are possible. Maybe that's further down the stack. I guess it depends on how you think about it, but different part of the stack. So, I'm curious, touching on the serverless components of Kubernetes; sure, I get that. And I do think, increasingly, the PaaSs of the future are all going to be Kubernetes-based, whether that's exposed or not. But where are the places that you think it's still going to go? Because I feel like it's already gotten boring, maybe in a positive way. But I don't see the excitement around it like I saw a few years back. And I'm curious what else you think is going to happen. JOE: Yeah, I mean, I don't think I disagree. I think Kubernetes itself, the core concept, is, like, it's still changing. But you're right that the excitement about Kubernetes existing has gone down because it's been there for a while. But I feel like the ecosystem is still growing pretty rapidly. Like, the things you mentioned, like Wasm and Istio, and all the tools in that ecosystem that continue to grow, is where I think the interesting things will happen. Like, it's created this new lower-level layer of abstraction that makes it possible to build concepts and technology that could not have existed before. KENDALL: Yeah, well, and I'm, you know, talking to people who are working really hard at making short-run ephemeral workloads work better on things like GPUs for the sake of AI, right? Like, I mean, there is some really interesting things happening, and people are doing this in Kubernetes. So, I get that. I agree with that. It is interesting that Kubernetes has become sort of the stable thing, and now it's about who can build the interesting add-ons. It's almost like, okay, we've built Half-Life. What is Counter-Strike going to look like? You know. That's a terrible (I'm aging myself.) example. But still. VICTORIA: I think it's interesting, I mean, to look at the size of the market for platform engineering right now. In 2022, was 4.8 billion, and it's estimated to be in 10 years $41 billion. So, there is this emerging trend of different platform engineering products, different abstractions on top of Kubernetes. And I wonder what advice you would have for a technical founder who's looking to build and solve some of these interesting issues in Kubernetes and create a business around it. KENDALL: Well, okay, let me clarify that question. Are you thinking, I'm a startup, and I need to build my infrastructure, and I'm going to choose Kubernetes. What advice do I need? Or are you thinking, I am founder, and I want to go build on the Kubernetes ecosystem. What advice do you have? VICTORIA: Now I want to know the answer to both. But my question was the second one to start. KENDALL: One of the things that is hard about the Kubernetes ecosystem is there's not a ton of companies that have made a whole bunch of money in Kubernetes because, as I said, I still think we're actually really early in the adoption curve. The kinds of companies that have adopted Kubernetes are the kinds of companies that don't spend lots and lots of money on an infrastructure. [laughs] They're the kinds of companies that are fast-moving, early adopters, or, you know, those first followers, and so they're under $100 million companies for the most part. Where the JP Morgans and Chase are running Kubernetes somewhere in their stack, but they haven't adopted it across the stack to need the biggest, best tools about it. So, the first piece of advice that I'd give is, be a little wary. It's still very early to the market. Maybe now is the time to build the thing. When ReactiveOps pivoted to Kubernetes, I think it was six months of having conversations with companies who were just, like, so excited about it, and this is definitely what we want to do. But nobody was doing it yet. You know, it was, we have, like, six solid months of just excitement and nobody actually pulling the trigger. And, you know, we were a little too early to that market. And that was just the people adopting it. So, I think there is some nervousness that cloud-native solutions the only people who are really making money in Kubernetes are named Amazon, Google, and Microsoft because it's the cloud providers that are making a ton off of it. Now, there's Rancher. There is StackPointCloud. There's a few others that have had big exits in this space. But I don't think it's actually as big of a booming economy as a lot of people think, in part because EKS is an incredibly amazing product. Like, eight years ago, the thing people paid us the most to do at ReactiveOps was just stand up Kubernetes because it was so stinking hard to just get it up and working. And now you click some buttons. Anybody can go do that. So, it's changed a lot, right? And I think be wary when you're entering that ecosystem. And then, my advice to the founder that's not building on the ecosystem but just looking to adopt a technology that's going to be a future-proofed infrastructure is just adopt one of the cloud-native platforms. And there are a whole bunch of sort of default best-in-class add-ons out there that you need to throw in. Don't adopt too many because then you have to maintain them forever. That's the easiest way to get started. You can figure out all the rest of it later. But if you go use EKS, or GKE, AKS, you can get started pretty easily and build something that is going to be future-proofed. I don't know, Joe; I'm curious if you disagree with any of that. JOE: Well, I think it's interesting to think about who's making money in Kubernetes. Like, I think there might not be as many companies who are doing only Kubernetes and Kubernetes-focused products that are massively successful. But I think because it has had a good amount of adoption and because it's easier to work with something that's standardized, it has helped companies sell things that they wanted to sell anyway. Like, all the Datadog, all the Scalas, the logging companies, they all have Kubernetes add-ons. And now everybody is paying Datadog [laughs] to have a dashboard for their Kubernetes cluster. I think they're making more money than they would have been without targeting the market. And so, I think that's really...if you want to get into the market, it's not, like, I'm going to build a Kubernetes product. It's if I'm building operations and an infrastructure product, I should definitely have it work with Kubernetes, and people will want to click and install it. KENDALL: So, to be clear, you know, one of the companies that I work with is called Axiom, and they play in the same, you know, monitoring, observability space as Datadog does. And part of what makes Kubernetes interesting in that space is in a microservice environment; there's so much happening. Where are problems being caused? We don't live in a day where I can just run my code, and it tells me that there's an unexpected semicolon on line 23, right? Like, that still happens. You're still doing those things. But this microservice talking to that microservice is where things tend to break down. Did I communicate this correctly? What was sent? What was received? Where did it break down? What was the latency? And if you were doing things in the old way back when you were standing it up with, say, Ansible, or Puppet, or something like that, and you were orchestrating all of these cloud virtual machines, you had to really work hard to instrument the tracing and logging and everything involved in order to track what was going on. Whereas that's one of the magic things about Kubernetes is with a few of the add-ons or some of the things out of the box with Kubernetes, it's a couple of clicks to get so, so much of the data and have insight into where things are going and what's going wrong. And so, I 100% agree with that. Kubernetes is generating a tremendous amount of data. And if you're a data company, it's really nice to have all that come in, and it helps them make money, helps the user of Kubernetes in that situation understand where problems are happening and breaking down. Yeah, there's definitely some network effects of what Kubernetes is doing in that. I completely agree. JOE: I think there are also some interesting companies, like, where they make...Emissary, Ambassador, and they have that sort of dual -- KENDALL: Komodor, is that -- JOE: Yeah, maybe. They have open source, but then they have a product. KENDALL: You're thinking of Ambassador Labs. JOE: Yeah. Ambassador Labs, yeah. I guess I don't really know how much money they're making. But I think that's a really interesting concept as people who make open-source things then make a well-supported product built around it. KENDALL: Sure. What's interesting is, I think in the VC world, at least right now, and it may pick up again, but post-Silicon Valley Bank nearly caving in, I think that the VC tolerance for, yeah, just go get a billion open-source adopters, and we'll figure out how to monetize later I think that the tolerance for that is a lot lower than it was even six months ago. JOE: Yeah, I think you have to have a dual model right from the beginning now. KENDALL: Yeah. Agreed. VICTORIA: You got to figure out how to make money on Kubernetes before you can. [laughs] KENDALL: You know, minor detail. That's why I think services companies in this space still have a lot going for it. Because in order to even be able to sell software to a company using Kubernetes, you half the time have to go stand up Kubernetes for them because it is still that hard for so many people to really adopt it. VICTORIA: Yeah. And maybe, like, talking more about, like, when it is the right decision to start on Kubernetes because I think the question I get sometimes is just, is it overkill? Is it too much for what we're building? Especially, like, if you're building a brand-new product, you're not even sure if it's going to get adopted that widely. KENDALL: I mean, and I'm [laughs] curious your thought on this, Joe, but there's a good argument to be made that Heroku was enough for the vast majority of founders early on. But the thing is, Kubernetes isn't as hard as it used to be. Going and clicking a couple of buttons on GKE and deploying something into Kubernetes with GKE Autopilot running it's not as easy as Heroku, but it's not wildly far off. And it does substantially future-proof you. So, when is it too early? I'm not sure it's ever too early if you have an intention of scaling if you're planning on running some kind of legacy workload, like, things that are going to be stateful. Or maybe WordPress, for example, you don't probably need to deploy your WordPress blog onto Kubernetes. You can do that in your cPanel on Bluehost. I don't actually know if Bluehost even exists anymore, but I assume it's still a thing. I don't know, what would you say, Joe? JOE: I agree with that. I think it's a hard first pill to swallow. But I think the reality is that it's very easy to underestimate the infrastructure needs of even an early product. Like, it doesn't really matter what you're building. You're still going to have things like secrets management. You're still going to have to worry about networking. They just don't go away. There's no way you have a product without them. And so, rather than slowly solving all those problems from scratch on a platform that isn't designed for it, I think it's easier to just bite the bullet and use one of the managed solutions, especially, as you said, I think it's getting easier and easier. The activation energy from going from credit card to Kubernetes cluster is just getting lower. KENDALL: And so, the role of the CTO is just getting easier and easier because they can just adopt the one technology, and it's obviously Kubernetes. And it's obviously Rust, right? [laughter] Yeah, no, I'm with you. And I think if you find somebody who knows Kubernetes inside and out, it's really not going to take them long to get started. VICTORIA: Yeah, once again, change management is the biggest challenge for any new innovation coming into adoption. So, I'm curious to talk more about the influence that you need and how you influence others to come around to these types of ideas, like, in the executive suite and with the leadership of a company, especially on these types of topics, which can feel maybe a little abstract for people. KENDALL: How you influence them specifically to use Kubernetes, or just how you talk with them about technology adoption in general? Or what are you asking? VICTORIA: Yeah, like, how do I get people to not just turn their ears off when I say the word Kubernetes? [laughs] KENDALL: Yeah, I mean, I think...so I think that's where it's the technologist's job and the role of the CTO to translate these things into business speak. And that's why I'm using words like future-proofing your infrastructure is because there are companies that...I know one company that made a conscious decision that they were going to try to re-platform every single year, and that is not a good idea or sustainable for the vast majority [laughs] of companies. In fact, I can't think of a single situation where that makes sense. But if you can say to the CFO, "Hey, it's going to cost us a little bit more right now. It's going to save us substantially in the long term because this is the thing that's winning. And if we go standardize on Heroku right now, every company does eventually have to migrate off of Heroku. They either go out of business, or they get too big for it." That's the kind of thing that needs to be communicated in order to get people to adopt it. They don't care what the word is. They don't care if you're saying Kubernetes; you know, most CFOs understand it about as well as my mom does. My mom tries to bring it up in conversation because she's heard me use it. And she thinks it makes her sound smart, which maybe it does in the right climate. VICTORIA: My partner does the same thing. He says DevOps and Kubernetes all the time. I'm like; you don't know what you're talking about. [laughter] JOE: Those words do not come up in my house. KENDALL: One of my kids asked me to explain Kubernetes. And I do a whole talk, particularly at organizations where understanding Kubernetes is essential to the salespeople's role. And I give a whole talk about the background of how we got here from deploying on some servers in our back room. And, you know, what's different about the cloud, what containerization did, et cetera. And I have this long explanation. And I remember taking a deep breath and saying to my kids, "Do you really want to hear this?" And I had one son say, "Yes, absolutely." And my wife and three of the other kids all stood up and said, "No way," and left the room. So, when somebody asks me, "What do you do?" Actually, one of the key relationships I built with some of the early people at GCP when we were partnering closely with them was a person that I met, and I asked, "What do you do for a living?" And he said, "I can tell you, but it's not going to mean anything to you." And I was like, "That's what I say to people." And it turned out he was in charge of, you know, Kubernetes partnerships for Google. I can explain to you what it means and why it's important. But you're not going to be happy that I spent that time explaining it to you. VICTORIA: [laughs] That sounds awesome, though. It sounds like you built a server rack just to demo to your children what it was. KENDALL: No, no. I just talked back through the history of...that company that I mentioned that built Twitter about five years too early; we had a, you know, we had a server rack in the...literally physically in our closet that was serving up our product at the time. VICTORIA: Probably the best demo I ever saw was at Google headquarters in Herndon, and someone had built...They had 3D-printed a little mini server rack that they had put Raspberry Pis onto, and then they had Kubernetes deployed on it. And they did an automatic failover of a node to just demo how it works and had little lights that went with it. It was pretty fun. So maybe you should get one for yourself. [laughter] It's a fun project. KENDALL: They remember the things that it enables. They don't remember what it does. And so, when I say so, and so is a client that's using this technology, then they get real excited because they're like, "My dad makes that work." And I'm like, well, okay, that's kind of a stretch, but you get the idea. VICTORIA: Yeah, you got to lean into that kind of reputation in your house. KENDALL: That's right. VICTORIA: And you're like, yes, that's correct. KENDALL: That's right. [laughs] VICTORIA: I do make Kubernetes. I make all the clouds work, yeah. KENDALL: Actually, my most common explanation is Kubernetes is the plumbing of the internet. Unless you're a plumber, you don't care about the pipes. You just want your shit to flush when you use the toilet. You want the things to load when you click your buttons. You don't actually care what's going on behind the scenes, but this is what's orchestrating it increasingly across the internet. VICTORIA: So far, we've called Kubernetes WordPress or the toilet. [laughs] KENDALL: The plumbing. [laughter] VICTORIA: You are really good at selling it. [laughter] KENDALL: Hey, if you want to build a nice, clean city, you need good plumbing. You might not care what the pipes are made of, but you need good plumbing. [laughs] VICTORIA: Works for me. On that note -- [laughs] KENDALL: Yeah. Right? Right? VICTORIA: That's [inaudible 36:41] on a high note. Is there anything else that you'd like to promote? KENDALL: With regards to CTO Lunches, we have a free listserv. There are local lunches. If there isn't a local lunch where you are, it's very lightweight to start up a chapter. We often have folks who are willing to sponsor that first lunch to get you going. We do have a paid tier of CTO Lunches. If you want a small back room Slack channel of people to discuss, I think it's $99 a month. Yeah, if you're a CTO and/or a senior engineering leader and you want a community of people to process with, be it our free tier or our paid tier, we've got something for you. We're trying to invest in this to build community around it. And it's something we enjoy doing more than almost anything. Come take part. VICTORIA: You can subscribe to the show and find notes along with a complete transcript for this episode at giantrobots.fm. If you have questions or comments, email us at hosts@giantrobots.fm. And you can find me on Twitter @victori_ousg. This podcast is brought to you by thoughtbot and produced and edited by Mandy Moore. Thanks for listening. See you next time. ANNOUNCER: This podcast is brought to you by thoughtbot, your expert strategy, design, development, and product management partner. We bring digital products from idea to success and teach you how because we care. Learn more at thoughtbot.com. Special Guest: Kendall Miller.

The Security Squawk podcast crew discusses cybersecurity, where they examine various breaches and cyber threats. They analyze recent attacks against GoDaddy, which compromised the login credentials of their hosting customers and personnel. They discuss the importance of good password hygiene, multifactor authentication, and scanning for viruses and suspicious activity. They also talk about the proposed legalization of hacking in Russia for patriotic reasons and the recent FBI cybersecurity incident. They dive into the rise of ransomware attacks against the semiconductor industry and the need for improved network security using government grants. The hosts also talk about a cybersecurity incident at Lehigh Valley Health Network, traced back to an unauthorized activity from a doctor's office. They emphasize the need for separate networks and awareness of the risks of connecting personal devices to corporate networks. The episode ended with a discussion about the use of BYOD devices in healthcare.

Show notes for the Billy Newman Photo Podcast.Communicate directly with Billy Newman at the link below.  wnp.app Make a sustaining financial donation,  Visit the Support Page here. If you're looking to discuss photography assignment work or a podcast interview, please drop me an email. Send Billy Newman an email here. If you want to see my photography, my current photo portfolio is here. If you want to read a free PDF eBook written by Billy Newman about film photography:  you can download Working With Film here.  If you get value out of the content I produce, consider making a sustainable value-for-value financial contribution, Visit the Support Page here. You can find my latest photo books on Amazon here.  View links at wnp.app Instagram  https://www.instagram.com/billynewman/ Website Billy Newman Photo https://billynewmanphoto.com/ About  https://billynewmanphoto.com/about/ YouTube  https://www.youtube.com/billynewmanphoto Facebook Page  https://www.facebook.com/billynewmanphotos/ Twitter  https://twitter.com/billynewman Communicate directly with Billy Newman at the link below.  wnp.app Make a sustaining financial donation,  Visit the Support Page here. If you're looking to discuss photography assignment work or a podcast interview, please drop me an email. Send Billy Newman an email here. If you want to see my photography, my current photo portfolio is here. If you want to read a free PDF eBook written by Billy Newman about film photography:  you can download Working With Film here.  If you get value out of the content I produce, consider making a sustainable value-for-value financial contribution, Visit the Support Page here. You can find my latest photo books on Amazon here.  View links at wnp.app Instagram  https://www.instagram.com/billynewman/ Website Billy Newman Photo https://billynewmanphoto.com/ About  https://billynewmanphoto.com/about/ YouTube  https://www.youtube.com/billynewmanphoto Facebook Page  https://www.facebook.com/billynewmanphotos/ Twitter  https://twitter.com/billynewman

0:14 Hello, and thank you very much for listening to this episode of The Billy Newman photo podcast. Today I was going to be talking about some of the ideas around VR rendering, I've been just getting into that after recording a ton of 4k, I think 5.2k video with the GoPro fusion I've just talked about a lot of that stuff on the last flash briefing, but today, I've been bringing it over onto my MacBook Pro, which is quite a modern version of the computer. I think many of the pros commented recently, it's probably the better iteration of the MacBook Pro for the last number of years. I'll get into that and some of the apple WWDC news just in a few seconds, but for some of the VR rendering that I'm doing on it without maybe a dedicated graphics card to push through it as you know, the fast clip, it takes a long time so I'm trying to export 360-degree equo rectilinear video footage in 4k mp4 file format with an H dot 264 to throw in some other term that this someone might not understand. But I've been trying to do that overnight. So I've been using, I've been using that command if you have a Macintosh, this is a good one to learn. If you go into your terminal, I think you can use the command caffeinate just the word caffeinate and then space dash D and that will force your MacBook or your iMac or you know you're your Apple computer to remain on and to not go to sleep under the normal circumstances that your settings would have precluded it to do. So it's a really cool, cool little bit, if you're just trying to make your computer stay on or force it to stay on for a longer amount of time, it leaves the screen on to you gotta you gotta do your little f one f two thing or something to turn that down but it works really well that I've been using that to leave the computer on and have it running so that it can be churning through some of these 4k rendering jobs that I have the computer set to do overnight while I'm sleeping so I put the computer out in another room and then I have you know like a queue of video set up for it to stitch together this GoPro stitching stuff for the GoPro fusion software is really intensive I know that Oh man, I get into that some of the time but man the stitching software is just I mean can you imagine what it has to do to stitch hundreds and hundreds and hundreds of frames all in like 5k or something to make it almost like you know a seamless you know make a look good and so just don't get a blurry line. So I'm amazed that it can do any of that sort of stuff at all. But it's you know, it's fascinating as it is but it takes a long time and it's interesting to get to the point where you're like Oh man, this computer can't do like a professional job like this and that's where you think you think you think You almost hit the limit of the need for computing or you know the need for a lot of the processor speed or the I don't know what it would be the specs of a computer and you think that for a lot of web-based desktop publishing stuff or phone-based mobile publishing stuff, we've really maxed out the need for the speed of a lot of the components but then you come into a position like this where you're starting to do higher level compiling or the higher level rendering of either like you know, compiling like a code base or something or trying to render out some of these higher file formats. video files, you notice like how long it takes and how much you would really have an improved job by having an improved machine and so I think that's where like a lot of stuff like the pro line of Apple hardware comes into play like the iMac pro that came out earlier this year and that's I bad I guess it's been semi well received by some of the pros there's just not a huge part where you can't upgrade it you know it's an iMac computer so it's going to be strong and 4:04 capable at video are capable at Thunderbolt expansion to whatever that would mean for you. But it doesn't have expandable slots or you know expandability within the frame of the computer. Then even really the cylinder Mac Pro didn't have the expandability that they thought it would have and I think that was also part of the graphics card architecture that they use don't end up getting updated there's a whole kind of snafu around stuff around that where that's why that computer didn't get updated in the fashion that they maybe thought it would have and that's I think why like a lot of the more modern 5k monitor IMAX are faster computers are higher spec computers have, I guess a newer generation architecture for their, their core processor than even the highest SPECT cylinder MacBook Pro At this point, I guess, given that it came out what 2013 and hasn't seen a whole update yet since then. So, or I don't know, minor update, you know, like, kind of, you know, just simple component stuff. But not it was just kind of internally within the spec, but I don't think there's been an actual rendition that's been new from that. Yep. So that kind of brings me I guess, to the last point, which is, Apple's WWDC is supposed to be coming up here real soon in just the beginning part of June. And that's when we're supposed to get some information about it, I guess it would be the developer preview for iOS 12. And some of the news a rumor oil, I guess rumors would be currently what they are, after WWDC is when we're going to get confirmation from Apple about the direction in design and feature choice, it's going to be going into iOS 12. And maybe we'll get some hints on the types of devices or the I don't know, maybe it's going to lean heavily toward the AR, maybe it's gonna lean heavily to the gesture format that we've started seeing in the iPhone x, kind of versioning of iOS 11. I don't know yet. But hopefully, we'll see some Siri improvements. Seems like that's gotten long in the tooth after a little while, especially kind of starting to see now given you know, like this, and what the echo is capable of. And well, I guess some of those Google demos that we saw a few weeks ago about artificial intelligence, parsing the verbal cues of what people are saying and trying to have that fill out a form of data. It's interesting stuff. 6:33 You can see more of my work at Billy Newman photo Comm. You can check out some of my photo books on Amazon. I think if you look at Billy Newman under the author's section there and see some of the photo books on film on the desert, on surrealism on camping, cool stuff over there. 6:56 I saw what we've been seeing I saw a helicopter, there's a thunderstorm. That was like when I was last doing a podcast right so there's like a big-time thunderstorm that was rolling through that last camp that I was at when I was podcasting and then rained a bunch after that. That was nice. stay nice and dry and pretty warm and tracking the truck canopy and stuff waited out the rain then it cleared off just like a couple of hours later is that that thunderstorm system move past us. And then yeah, cleared off and got cold. got pretty cold. I layered up and I walked out into that field now with a ton of wet grass and stuff. walked out there brought the heater like I was talking about and posted up out in that motto. To check out the stars and stuff from that you can see Scorpio almost all Scorpio it's cool when you got a strong Southern view of the sky. And from this area and Oregon, you can't quite see the dip in the tail of Scorpio as it kind of scoops down and comes back up with the stinger at the end. You just barely or you get out you can imagine how it kind of skips around but yeah, at where it is now at this time in August. I think it's it's kind of tipping over and gone. not visible in that spot. But I think I see. Was it Jupiter? You see just past Sagittarius as you're looking to the south. Then near that just a little bit further over to the east on that same ecliptic line you see Saturn. I think they are both near the position where they are in opposition. They're not as bright as they were a few years ago, you notice, but there's still really bright, really cool to see. And then if you stay up late enough, maybe around midnight or so. You'll see Mars rise over on the eastern horizon. And it looks coppery red and noticeably cool. But I think it came up right about the same or about an hour or so after the moon rose last night. So tonight it would probably rise along the same location as Mars. That's interesting. Yeah. Yeah. Would those be cool? Check out that stuff. And I was checking it out the other night after that thunderstorm out in that field. So it's kind of fun, kind of staying up and check it out some stuff but then I went to bed. And then I got up the next morning and this was what was cool. As I looked out the field I hadn't seen any animals out there. I heard a few birds like a raven and a couple of other things. I think I heard a turkey gobble. I'm not sure that but I looked out looked across the field and I saw two of the biggest birds I have ever seen. There. They are the biggest birds I've ever seen. I'm not sure what it is it looks similar to a blue herring. So I figured some kind of herring maybe it was a crane. But I would guess if it was standing up it would be almost fourth tall. It looked like a small deer or a dog in mass and size as you know kind of like the feathery body of it wasn't popped up in a big way but there are two of them. And yeah, it looked like dinosaurs out there in the middle of this field. I've never seen a bird like that it looked like a blue herring goes about twice a day I see a buck it's at two o'clock and walk into my three o'clock. 1.2 point 3.4 points it's a two or three-point buck doesn't see me That's cool. Little back cruising through. I think it's a mule deer out here. I saw a group of mule deer down in the lake bed this morning. And when I started wrestling around they all kind of started running or one of them kind of got excited and then ran off there they're probably like two or 300 yards for me. And I pulled up the binoculars as scouting and yeah, they were just bugging it across this open lake bed and then they got tired and stopped and started eating grass like almost right away so it's kind of funny how they kind of move around but yet this guy's like 11:21 I don't know what 200 feet walking around can't cool dude. These are camping with me. What was this in two giant birds? I saw these two giant birds Thunderbirds they were awesome. They were brown kind of Sandy tan colored. And they had like a beaked face like a real pointy beak face similar to blue hair and it looked like an emu or an ostrich or something out in this field. It was diet. But it looked I'd say like I've seen a lot of blue herrings they're way more slender than this had that kind of big kind of round full bodied thing and then had that cranes neck that kind of the s curved crane neck and it was just kind of on the ground walking with its buddy and they were cruising around poking at the ground trying to get grubs or whatever but yeah really cool to see him and then so I was watching them for a bit I had him the binoculars I think I got a couple of pictures but like I was explaining that last podcast smartly I have a wide-angle lens with me which is you 17 to 40 millimeter so as a way out super wide so you just so you know no telephoto my back. So didn't get the wildlife shot that would have been cool which is fine and I accept but I did get a couple of pictures of it that probably poorly show two big things out in the distance and I mean it looks like it could be dogs could be deer, or it could be birds so it was pretty awesome to see but as I walked out a little bit I exposed myself into the sunlight they got they got a side of me and then they both let out these for like maybe 30 seconds to a minute or so they both just kind of stood around and made these sort of warning or territorial. croaks these like three beat croaks that would just echo across this whole valley that or this whole metro area that I was in just carried on for acres they're probably like an acre or two away from me at that time. And yeah, they just set out these loud croaks kind of morning that these up, standing dude predator out in the distance, but yeah, then they kind of sorted it into the flight, but they just kind of wanted to back off up into the hill up into the tree line. And then I tucked back myself back up into the tree line by my truck, made another cup of coffee that morning, and then I saw the kind of popping out again and poking around that. That Meadow again, but it was cool giant birds I really would say they're like four feet tall. Body Mass section, it seemed like about two feet or so. You know, like kind of on their leg? Maybe 24 inches off the ground. Yeah, it just seemed like a really big bird. If I was standing right next to it, I'd be like, Whoa, man, this is a real critter. So it was fun. I'd never seen a bird like that out there before I heard about it. Some of those are birds like that before I remember hearing like, is like a colloquial family story. That I think a great uncle of mine had had probably similar to this area too, which is interesting. I like that. But he said that he had woken up one morning and looked out and saw these prehistoric-looking Thunderbirds he called them and I think I had an experience like a two. I think it was fun. I'm sure it's a normal animal. It probably used to be around a lake or something. You know, that's sort of what it seemed like is just like a giant Pelican or crane or something that you would see how by the ocean, but to see out here just walking around sagebrush in a field in a meadow at 730 in the morning, it's just like Wow, look at that. I thought I'd see a deer out there, but No giant birds. 15:09 You can check out more information at Billy Newman photo comm you can go to Billy Newman photo comm forward slash support. If you want to help me out and participate in the value-for-value model that we're running this podcast with. If you receive some value out of some of the stuff that I was talking about, you're welcome to help me out and send some value my way through the portal at Billy Newman photo comm forward slash support, you can also find more information there about Patreon and the way that I use it if you're interested or feel more comfortable using Patreon that's patreon.com forward slash Billy Newman photo. I bought a domain name at night sky podcast calm and so I'm trying to build a pretty simple WordPress site that can host a lot of the information about that podcast about that project as a whole. So it'll be pretty basic. And it's not supposed to be something that's, that's usually complicated by any means. But I'm interested in you know, just trying to try to make some different graphics and make some explanation of the podcast is sort of how it works just to kind of differentiate it a little bit. And so it's just like a side project and a hobby, I'm trying to put it together. But I've been trying to find out some ways to do that more easily. So I've already built about three or four pretty usable WordPress websites. And what I was hoping to do is try to try to take a lot of that, that work that I had already done, and then migrate that over to this new night sky podcast website that I'm trying to put together. Along with another site that I'm trying to put together, I'll get together. I'll probably talk about that in the next podcast. But through this nightscape podcast website, what I was hoping to do was take a lot of the way that I've customized the theme that I'm using and a lot of like the Page Layout stuff that I've already put together for let's say my Billy Newman photo website. And I want to try and find a way to migrate that over to this night sky site, and then strip out the parts that won't be the same, you know, I'll replace the graphics replace a lot of the layout stuff in a way that would be unique and bespoke to the way that I want this nightscape podcast website to go. But it's a little better than ours, it's a lot less work, and it saved me a ton of time so that I don't have to go back through and make customizations to each of the fields associated with the site in a way that would be like brand new to it. So so I'm trying to learn about that a little bit. What I've been trying to do is find out, I guess different ways to do that. And so one thing that I ran into, while I was trying to do a bunch of this troubleshooting on my site over the last couple of weeks was that I'm really in need of making backups of my WordPress sites. And so what I went through and did is a made, I'm sure there are ways within WordPress to do this, but I was using a plugin. That's and you should let me know if anybody's listening out there. And they've had experience doing backups at their WordPress site, you should let me know if it was the most effective there's, there's like the cPanel backup that I've made from the server side where I backed up the files that were associated with a website. And so hopefully that can be restored in a way that would be useful. But there are also some complications that I think I've run into with that. And it wasn't as user-friendly as I wanted it to be. And the restore points, I don't know, it didn't feel like it worked for me as well as I had hoped it would. But it did come in use, it was very useful for me to do that 18:23 when I did run into problems, and I wasn't able to access the site. So I'm glad I had those backups of the cPanel. But I do still have access to the WordPress dashboard of my website, what I'm hoping to do is use this plug-in system that I found. And I'm sure like a million other people according to what it said have found it also. But I'm using this plugin called Updraft Plus, to try and make to try and make backups of my WordPress pages. So I went through and made backups of each of the WordPress websites that I've created so far. And first, that was the Billy Newman photo.com website. And then in addition to that, there was golden hour wedding calm. So I made backups of both of those. And then there are another two websites that I'm still kind of working on. And I want to try and make those new. But I did make backups of those also. And I was able to save those on my server. But I was also able to download those to my local drive and put those on an external hard drive. And the great thing is, is that I conversion, those backups. So when I make adjustments, or when I make updates to my site, and I want to make another backup of it, it'll make I can make a backup, and then I can download that. And that'll be like the, you know, this was in January 2019. But with all these extra pieces of content and with all these extra additions to the site, this will be the backup I'm making in February 2019, something like that. I'm trying to figure out those and I think what I've discovered is that what I want to do is take a backup of my WordPress site. Let's see In this case, the Billy Newman photo comm backup. And I want to use that to clone and then migrate that over to the night sky podcast.com website. And so I think I found a way to do that even within Updraft Plus now, the Updraft Plus plugin offers a premium service where you can purchase the ability to do a database migration for I think, $30, it's not $30 per site, but I think it's $30 for the plugin, and then you get support from that plugin developer for some time, I think it's like six months on the low end. And then and then if you need support for a longer amount of time, I think it's more money than that. There are probably some caveats to it. But that is an option that I'm trying to explore right now as if I'd want to go through that process of using the Updraft Plus plugin to do a migration on my site where I can bring in a lot of the theme customization in the theme itself. And I guess the database with the updated database over to the night sky podcast website. And it could be an easy sort of one-click solution for it. But I'm also trying to look around and see if there are other ways for me to do an import for a clone of the website, and the website data so that I can bring in a lot of the information, but maybe leave out a lot of pieces that I won't need because I'm not trying to make an exact duplicate or an exact copy, I'm just trying to bring over certain elements that would be that have already been adjusted in a way that I don't want to do the work over for. So if I could just kind of bring in this draft of a website version, that's almost everything complete in the way that I want. And then delete the content that was on the blog, delete the pieces that were you know, over in this section of the site, rewrite and about page and a couple of paragraphs over here, recreate some graphics, and then I would have what would seem like a familiar site would be on brand. But it would also be, you know, a new site that would have a lot of new content on it. And it would just kind of remain the way that I wanted it to. So that's sort of the hope that I'm trying to go for. And I guess that the Updraft Plus plugin creates XML files for you to use. And 22:09 I don't know how it works. But I think if you break open the file that you've downloaded, you can go through and then, and then there's an alternate way of making an upload for that sort of stuff. But I guess the problem is, is like the database. So if you're migrating a site, it's expecting all those domain names to be what they had been in the past and not migrated or not a set of new links that have these new domain names, everything's going to link back to another site, that it's not, it's not an ad. So the database, I was just not going to make sense. And I think that's what this migration tool is supposed to help you do. So I'm looking into that. And I'm hopeful that I can kind of put that together pretty quickly. I'm also trying to be conscious of my time a little bit too so that I don't spend a huge amount of time and development trying to figure out, you know how how to go through and fix a bunch of errors that might be created if I try and do a restore of a backup or a clone of my other site and try and migrate that over to this new domain. I'm trying to figure out a way where I don't have to worry about that all that much. But I'm still going to do some more research. It's going to be an ongoing project, an ongoing project, and I will update you in this podcast on my progress. That's what I figured. So I'm going to do that with another site too. I think I mentioned yesterday that we're starting the golden hour experience podcast. And we've also started the golden hour experience.com website. And so I'm going to try and go through the same process over on that site. So I can import a bunch of the settings that I have from golden hour wedding calm and try and put it together in a way so that I get to save a bunch of time and not have to redevelop a WordPress site from scratch again. So that's it and it could work it seems like if I pay just a little bit of money, I can make it work, which might make it worth it. I figured the other news that I was gonna get to was some stuff about ebooks. I'm sure you're excited now. Thanks for listening to all this. Thanks a lot for checking out this episode of The Billy Newman photo podcast. Hope you guys check out some stuff on Billy Newman photo.com a few new things up there some stuff on the homepage, some good links to other outbound sources, some links to books, and links to some podcasts like this blog posts are pretty cool. Yeah, check it out at Billy new minnesota.com. Thanks a lot for listening to this episode and the backend.

In this week's episode, the cybersecurity experts Bryan Hornung, Reginald Andre, Randy Bryan, and Ryan O'Hara with special guest Javvad Malik at J4vv4D discuss the topic of phishing & what Javvad notices is going on with these types of attacks. Next, the team disucsses 4 tips security experts are saying will help protect thier IT employees from clicking on a link. Tune in to learn how to mitigate this human error! Then, the crew review some of the top phishing scams this week relating to Costco, Ace Hardware, PayPal, Netflix, Truist, cPanel, and Microsoft. Would you have been able to spot these scams? Lastly, the security experts discuss an article about a 65-year women who was scammed on Instagram because she was in love. Make sure to tune in! Like and Share the show! Articles used: https://unfspinnaker.com/98214/news/phishing-is-organized-crime-unf-chief-information-officer-says/ https://www.constructiondive.com/news/cybersecurity-spear-phishing-tech/634408/ https://news.trendmicro.com/2022/10/21/costco-ace-hardware-paypal-netflix-truist-cpanel-microsoft-phishing-scam/ https://gizmodo.com/astronaut-iss-instagram-1849638814

Esta semana hablaremos de como hacer una web desde 0 para todos aquellos que quieran aventurarse en la tarea de montar su propia página web, que como vais a poder ver no es tan difícil. Lo primero que hay que hacer es elegir un Hosting yo os he hablado ya de las prestaciones de los VPS de CONTABO, que para mi a dia de hoy es el mejor equilibrio prestaciones precio Una vez que tengáis contratado el hosting, que yo contrataría sin cPanel podeis acceder a el via SSH y seguir el tutorial de tecnolitas.com https://tecnolitas.com/blog/como-instalar-wordpress-en-ubuntu-20-04/ Este tutorial es sencillo, copias y pegas los comandos que aparecen en el tutorial en la consola ssh de tu servidor y cuando termines tendrás un wordpress listo y funcionando. A partir de aquí tan solo tienes que instalar un par de plugins para estar 100% operativo. Lo primero que vas a hacer es instalar el tema GeneratePress así que desde el menú de administración en Apariencia, pulsamos sobre Añadir nuevo y en la caja de busqueda escribes GeneratePress Una vez tienes el tema generatePress cargado, instala el Plugin GeneratePress Premium que puedes descargar desde este enlace de la zona de descargas de tecnolitas.com. Es un plugin que está sin licenciar, para que puedas probar su funcionalidad y puedas poner en marcha tu página hasta validar tu proyecto Le das a la opcion del menu Plugins, pulsas sobre el botón Añadir nuevo, ahora pulsamos el botón Subir Plugin y selecciones el fichero comprimido que has descargado del enlace de tecnolitas.com Una vez cargado el Plugin GeneratePress Premium, en el Menú de Apariencia aparecerá una opción que se llama GeneratePress y ahí vas a encontrar botones para activar toda la funcionalidad de la versión Premium del tema generatePress. Fondos Copyright Elementos - Desactivar Elementos Menú Plus Navegación Secundaria Biblioteca del sitio Espaciado Tipografía WooCommerce Lo que nos interesa está en Biblioteca del sitio, donde vamos a encontrar toda una serie de plantillas prefabricadas para nuestro sitio web, organizadas por categoría de negocios, Comercio electrónico o Blog Estas plantillas cargan el tema y contenido, así que es sencillo editar las páginas y sustituir el contenido por tu texto y por tus fotos. La mayoría trae páginas que sobran y algunas las puedes borrar Te quedas con lo esencial y los vas modificando Las fotografías pueden ser tuyas o puedes recurrir a sitios como pixabay, donde tienes imágenes que son libres de derechos y que puedes usar en tu web sin problema ninguno. Con relación a los textos, lo principal es que tengas una buena propuesta de valor, en la página principal, en esta zona que se llama Above the Scroll o Hero de tu cabecera, ahí tendría que ir bien especificada tu propuesta de valor. Que la gente entienda bien cual es tu oferta, tu propuesta, algo del tipo Ayudo a XXXX a XXXXX medianteXXXXXXX Ayudo a emprendedores a montar sus proyectos mediante herramientas de software libre Ayudo a personas a resolver sus dudas tecnológicas mediante asesoría y respuestas. un poco más abajo en la página principal describe tu servicio con más detalle Decide si quieres recoger correos electrónicos o no para un posterior boletín de noticias y utiliza un formulario para ello, bien un plugin o bien el formulario embebido de MailChimp o Revue Elemento de pie de pagina con algun enlace y los textos legales de la página web Buscar un sitio web de similares características y copiar los textos legales cambiando la información pertinente en cuanto a responsable de los datos direcciones y teléfonos.

Tips this week include: • How to change the day/time of backups in the free version of UpdraftPlus • Part 1 of the Keywords workshop is this Thursday • 2 updated Gutenberg Ninja tutorials and why many more are on the way • Why I'm making a major change to my site services schedule • The digital downloads and member site survey results are in, plus the action plan I'm making for us • All manner of internet goofiness is happening due to a huge uptick in cyber attacks • Issues with Cloudflare and its plugin • Ongoing issues with UpdraftPlus • What you need to know about Google deprecating Universal Analytics next year • Joost de Valk is changing his position with Yoast SEO • What the cPanel price increase means for your hosting • The difference in building community vs audience • 25 lessons learned from building a community • Why you may or may not want to run your member site from YouTube • Why I'm excited about a call for Block Pattern submissions

Shared Server Hosting hosts multiple websites on a single server, making it an affordable hosting solution for websites with less traffic and hosting resource requirements. This is why beginners, startups, and new website owners opt for Shared Hosting when first taking their business online. In today's podcast, we discuss how much traffic a Shared Hosting plan can handle and whether it's a right fit for your website or not. Check out this blog to learn how you can optimise your Shared Hosting setup through this step-by-step guide: https://blog.resellerclub.com/how-to-optimize-your-shared-hosting-setup/ With ResellerClub, you get a free cPanel, blazing-fast speed, and more reliable services with their Shared Hosting solutions. So, check out their Shared Hosting plans and choose the one that best suits your needs from: https://india.resellerclub.com/shared-hosting

Tips this week include: • ADA and UX workshop in the DIY SEO course this week • Where I'm at with making TikTok videos • Some encouragement for those just starting out with video • Why I'm returning Heartwood Art back to a hobby blog • Why I'm starting another YouTube channel or two • The DIY Site Owner Guide is live • Why I hate the new cPanel interface • My concerns with ModSecurity • What to check when using free images from Openverse • Why Meta is focusing hard on videos • What Spotify losing artists means for ushering in the Creator Economy • Will DeSo be the new decentralized social blockchain winner • How streaming bots are disrupting the music industry and what it means for NFTs

Reseller Server Hosting is the perfect way to start your own web hosting business and sell custom and unique web hosting plans and packages at competitive prices. Reseller Hosting comes with many reliable tools and features like WHMCS and white label to make your job easier as a Hosting Reseller. This podcast discusses the significance and importance of the white label service in Reseller Hosting. Learn more about becoming a good Web Hosting Reseller through this blog post: https://blog.resellerclub.com/what-it-takes-to-become-a-good-web-hosting-reseller/ ResellerClub provides reliable Reseller Hosting plans with free cPanel and WHM, on-call support, and more. So, check out their plans to start your hosting business and earn great profits: https://www.resellerclub.com/reseller-hosting

Tips this week include: • It's been a week of bumps and glitches online • Changes to my Site Audit services • Zero-day Log4J security issue update • Why you need to get your email off your hosting • What's up with hosts down and internet being slow and glitchy • cPanel's new SEO Beta testing program and why I'll be jumping in • Matt Mullenweg's State of the Word address is tonight • Update on the WP Performance Team • Tests on a new way to do Reusable Blocks and maybe even build Block Patterns • New Amazon Links exclusion for WP Fastest Cache • What's up with the bogus redirect warning email from Google Search Console

Neste vídeo, você vai entender que certos serviços que estão sendo chamados de Serverless, não podem ser considerados como pertencentes a esta categoria, visto que, o conceito de Serverless é sua aplicação rodar sem que você pague pelo provisionamento de instâncias, memória, CPUs, vCPUs e outros recursos. Vou abordar também a história e a evolução dos servidores ao longo das últimas décadas, desde o conceito do Colocation, do CPanel, Virtualização em Cloud Computing até os fundamentos dos AWS EC2 (Amazon Elastic Compute Cloud), AWS ECS (Amazon Elastic Container Service), AWS Lambda e AWS App Runner. No AWS ECS, vamos falar sobre o uso dele baseado em EC2 e a utilização dele com o AWS Fargate. Este é um vídeo completo sobre o conceito de Serverles! Fica ligado no canal, que tem conteúdos especiais sendo preparados utilizando esta tecnologia! Gostou do conteúdo deste vídeo?

อัพเดททิศทางเศรษฐกิจ รวมถึงเทรนด์การลงทุน ทั้งตลาดหุ้น ทองคำ น้ำมัน ผ่านเพจ facebook : เรียลลงทุน กับคุณปิยมิตร ยอดเมือง และคุณขวัญชนก วุฒิกุล สองผู้ดำเนินรายการด้านเศรษฐกิจและตลาดทุน ที่มีประสบการณ์กว่า 30 ปี พร้อมเชื่อมโยงข้อมูลรอบด้าน ทั้งข่าวสารจากในและต่างประเทศ ครอบคลุมทั้งข่าวจากตลาดหลักทรัพย์ฯ และ ก.ล.ต. รวมถึงบทวิเคราะห์จากหลากหลายแหล่งข้อมูล

If you're looking to discuss photography assignment work, or a podcast interview, please drop me an email. Drop Billy Newman an email here. If you want to book a wedding photography package, or a family portrait session, please visit GoldenHourWedding.com or you can email the Golden Hour Wedding booking manager here. If you want to look at my photography, my current portfolio is here. If you want to purchase stock images by Billy Newman, my current Stock photo library is here. If you want to learn more about the work Billy is doing as an Oregon outdoor travel guide, you can find resources on GoldenHourExperience.com. If you want to listen to the Archeoastronomy research podcast created by Billy Newman, you can listen to the Night Sky Podcast here. If you want to read a free PDF eBook written by Billy Newman about film photography: you can download Working With Film here. Yours free. Want to hear from me more often? Subscribe to the Billy Newman Photo Podcast on Apple Podcasts here. If you get value out of the photography content I produce, consider making a sustaining value for value financial contribution, Visit the Support Page here. You can find my latest photo books all on Amazon here. Website Billy Newman Photo https://billynewmanphoto.com/ YouTube https://www.youtube.com/billynewmanphoto Facebook Page https://www.facebook.com/billynewmanphotos/ Twitter https://twitter.com/billynewman Instagram https://www.instagram.com/billynewman/ About   https://billynewmanphoto.com/about/ 0:14 Hello, and thank you very much for listening to this episode of The Billy Newman photo podcast. Today we're gonna be talking a little bit about I think some of the 360 footers that I've been shooting at the waterfalls, some of the stuff up in the Mackenzie wilderness area, and some of it over like the three sisters wilderness area, so and then there's also cash budget stuff, we did a bunch of stuff on the coast, we did a bunch of stuff on hikes on bike rides, we had a friend with a motorcycle, drive it up a trail, that was cool. We shot over to Smith rock up to a couple of spots over in the high desert area, Eastern Oregon. Today, though, just for a minute, we're talking about some of the stuff that we did over proxy files, proxy files is a nice spot in Oregon, definitely a hiking destination that should be at the top of a lot of people's lists, especially for people that live I guess in the Willamette Valley area where you can get up on highway 126 and head out toward or if you're in the band area, and you want to come up that other way. But then you go up away up the 126, which is the main highway now. And then you take you take a little road that cuts off and that's the old road. I guess that used to be the old path that went overall you know, the mountain range there over the Cascades and then up on over to the part of Eastern Oregon, I guess we continued. But as you come up over the past there, there's a couple of cool lookouts up toward the top, but a little lower down as you're kind of, you're kind of starting your way up. There's a pull-out for proxy falls, and it's a really interesting waterfall. I think it's one of the taller waterfalls in Oregon. I think that watts and falls might be the tallest waterfall, which we also went to just a couple of days ago and I'll talk about that in the next couple of days on this. This flash briefing to the proxy false was beautiful. It was a tall waterfall, the way that it kind of cascades down and sort of blows up mist and creates kind of this mossy I guess kind of rain for his temperament. Or what would it be like oh, we're like a rain forest by him? So that sort of environment right around the place where the waterfall kind of crashes down all at one spot. But we took this 360 camera in there and recorded a bunch of footage and it has come out interesting. I love that sort of stuff. So it's really fun getting over there. 2:27 You can see more of my work at Billy Newman photo comm you can check out some of my photo books on Amazon. I think you can look at Billy Newman under the author's section there and see some of the photo books on film on the desert, on surrealism on camping, and cool stuff over there. 360-degree photo work over the last couple of weeks which has been cool and I've enjoyed it a lot. I liked doing the 360 stuff I think back in June of 2018 we had done a bunch of podcasts about some of the 360 photography stuff that we were trying to do some of the video stuff we were doing with the GoPro Fusion at the time. And that was all cool and I liked that video a lot this time I was working with a Ricoh Theta zone. And I was going around to a few locations to try and get the photographs. Specifically, I think photographs a lot in this circumstance not so many videos. But yeah, really interested in the 360 photography stuff that I was able, to edit together and to capture during that time. So that was cool. But I went out to an area in instead of Central Oregon, that was pretty cool and went up on like a hillside to do some 360 work. And it's cool out there because you can see the topography of how the Great Basin was formed at the wall I guess like during the whole era of the Pleistocene as it was for a long-standing period. Like a lake is just a big lake out there. And then as things started changing at the end of the place to see anything there were huge changes that ended the Great Basin stuff that ended a lot of the megafauna that was in the area. And that kind of changed the topography of the landscape over the last 10,000 years to be something much more of the high desert sagebrush Juniper tree exposed rock landscape that we see today and a lot less of the forested temperate kind of mountain climate that we have through the Cascades and part Oregon I'm sure it was always drier given the rain shatters the Cascade Mountains there but I think that for a long time as according to signs posted on my drives in areas where I go hiking sometimes but you know like when you go up to someplace and it says you know this area so such and such time ago had these animals in it where you see like giant beavers or you see like camels or giant sloths, I guess they added the area to there's all sorts of stuff that they had. That ended up being wiped out 100,000 years ago, 60,000 years ago, too, what, 1020 10,000 years ago, something like that. There's a lot of changes that happened throughout the Pleistocene, I guess during what they call the quarternary period, a period of glaciations that the Earth has been involved in for the last 100,000 or 200, maybe million years. I'm not sure it's last couple 100,000 years we've been going in these cycles of glaciation. So you know, we're in an ice age period. So we go into an ice age like we have ice on the Earth right now. It'll be more ice at a point and then less ice at a point. More is at a pointless I said a point, I guess it's been going on for what they say somewhere around like 200,000 years, these 30,000 year periods of glaciation to non-glaciation, where like, I think we're coming, we're like on the far end of the Glacial Maximum now. So we had the, with the Glacial Maximum about like, what, 11,000 12,000 years ago? Or is that right? No, it must have been, like, 15 20,000 years ago that we're at the maximum, then it started receding. I suppose. That's when we were able to No, that doesn't make sense. We had like the landbridge, like the Beringia stuff where people got over that was probably 15 to 20,000. sea levels were low, or they were like 400 feet squared along the coastlines that came over through the land. So that was all pretty long ago. Well, anyway, at some point, like I was there like I'm gonna figure out Wait, let me remember. Let me think back to 15,000 years ago, where was I? Yeah, I wasn't here. So I don't know what happened. But apparently, there's been some recorded evidence that I was learned about, and I think it's like Montverde down in Chile. And that's a location where I think they carbon-dated something to 15,000 years old, like human remains, the human element remains, there's, there's like a few locations here in Oregon, where they, I guess, have evidence of the Clovis people that sort of around like the 1112 13,000 year mark. And then there's other evidence of things that are I don't know within like it's time it's like anything from like 7500 years to 15,000 years ago seems to all kind of be in flux have a date, because there's not many, 7:25 not many perfect ways to date that. And if it's a cultural artifact, like a, an arrowhead, or a pot shard, or a scraper, there's some indication of how those things are going to be created or how those artifacts are going to be created and how there's going to remain like Folsom points or Clovis points are pretty distinct from each other, but they're not culturally distinct from each other. So it could be like a variation of many different tribes and languages and peoples all well unrelated to each other but related with a similar vein of technology for a few 1000 years of you know, their tool use shape was kind of similar because they're all kind of from a similar descendency but I think when you get like more than 100 miles away, your language is separate over like a couple of generations. You just got to speak different languages. But man wild stuff anyway, so I don't remember where we started with this. But I was out in Eastern Oregon, exploring the Great Basin, I went up on a hillside and public land and I was doing some 360 photography work with the Ricoh zeta Oh, Ricoh Theta zone. That's what it is. And yeah, I was capturing some stuff on a hillside really beautiful areas up there where those ridges kind of drop in and out. And so it's cool when you get like up to a higher elevation, you can kind of see the pockets of where these lakes and pools of water and kind of sat and rested for what seems like I think I was saying something about recording some 360 photographs up on some public land in the high desert, in the Lake County in Great Basin area of Eastern Oregon. beautiful spot over there. I enjoy it. And yeah, it was awesome to use the Ricoh Theta zone to be capturing some images up in that area, it's cool when you're at a higher elevation. And with a 360 camera, you can kind of it provides a little bit of a different perspective, it seems silly to see like wider, but when you re when you kind of replay those images, and you're able to sort of look around in the context of what's the left hand to the right of you, you're kind of able to put together the context of the landscape a little better, a little faster than you could if you just had a series of individual photographs that had segments of the wider landscape captured in it so it's cool at that higher elevation. You can kind of look down to areas that we had been hiking around earlier in the day through Some of the ridges and troughs that would be over in that area, and you can look down, you know, it's like 500 feet down in elevation to what we thought was kind of the mountain top pass and then pass that as another maybe 1000 foot or a couple of 100-foot drop in elevation as it goes down toward the lake basin area. So all that was pretty cool. And what was also cool about it is just sort of visualizing how populated that area had been in the past, I think, you know, before the Western expansion of the United States, and as 1000s of years passed by in this region of land in the northwest, it had been populated in that region specifically been populated by nomadic tribes that had been able to travel and subsist off of the wild game that was there, I think a lot of like antelope and deer, and it looks like bighorn sheep by some of their planning some kind of sheep, but it looks like that from some of their, their pictographs and petroglyphs information that they left then the dynamics of some of those populations of animals have changed in the time. Now given like modern-day, I don't know, I don't know if we're gonna see a lot of sheep out there in Lake County. But there's one drawn on a rock out there. So they must have been trying to look for it. There's a lot of them in the southwest. Is he moving into the I think the Mohawk tribes. For them, that's more of a 3000 to 25 2000. I don't know, it's probably bad. It was 3600 years ago, sort of a thing. But or 100 years ago I think it was like Captain jack over there Captain jack stronghold for the Murdoch Indian Reservation area. That was like in the Indian Wars of the 1850s. So they allowed us to tell them, but yeah, there's some information about some of the 11:52 pirate, the pirate Indians, I think the Northern Piute there were in that area of Southern southeastern Oregon, Nevada, then into Utah, Arizona, and New Mexico if I kind of understood, right, but I know there are some fluctuations in there. And differences and timing and stuff. But yeah, dollar, pretty cool stuff. It was really, it was awesome to get out there. It's, it's cool to get out and kind of walk around in scenarios of some public land, where we still have some access and still get out to try and do some photography stuff. Even in this period where you're supposed to stay home and there's a lockdown it was, it was cool to kind of get out and try and do some exploring and some social distance consciousness. I mean, that's fine with me, I don't, I don't have to be around a lot of people, it's better to do landscape wildlife photography worked while you're sort of in some type of isolation, I'm sure like a lot of hunters are kind of considering something like that to you know, hunters, fishermen, people like hiking or you know, a lot of those solo activities, it's cool that you know, this kind of this time, sort of is provided a little bit of a reset for probably a lot of people out there to have a bit more time to invest in some of the things that they'd want to, I suppose a lot of folks are probably stuck more in their local area but it's a great time too, to get to invest in some things that seem more important to you. So that's what I've been trying to do. I hope you guys are doing well. Thanks a lot for listening to this episode of The Billy Newman photo podcast. You can check out more at Billy Newman photo comm I've been doing a ton of updates over there. It's an airplane taking off. Sounds like prop plans about to fly over my head. It's like that scene in North by Northwest. Cary Grant starts getting run down by that biplane. That'd be scary. So that's that in the future. You can check out more information at Billy Newman photo comm you can go to Billy Newman photo.com Ford slash support. If you want to help me out and participate in the value for value model that we're running this podcast with. If you receive some value out of some of the stuff that I was talking about, you're welcome to help me out and send some value my way through the portal at Billy Newman photo comm forward-slash support, you can also find more information there about Patreon and the way that I use it if you're interested or if you're more comfortable using Patreon that's patreon.com Ford slash Billy Newman photo. 14:29 I bought a domain name nightscape podcast calm and so I'm trying to build a pretty simple WordPress site that can host a lot of the information about that podcast about that project as a whole. So it'll be pretty basic and it's not supposed to be something that's hugely complicated by any means. But I'm interested in you know, just trying to try to make some different graphics and make some explanation of the podcast and sort of how it works just to kind of differentiate it a little bit. And so it's just like a side project at all. IBM trying to put it together. But I've been trying to find out some ways to do that more easily. So I've already built about three or four pretty usable WordPress websites. And what I was hoping to do is trying to try to take a lot of that, that work that I had already done, and then migrate that over to this new nightscape podcast website that I'm trying to put together, along with another site that I'm trying to put together get together. I'll probably talk about that in the next podcast. But through this nightscape podcast website, what I was hoping to do was take a lot of the way that I've customized the theme that I'm using, and a lot of like the Page Layout stuff that I've already put together for let's see my Billy Newman photo website. And I want to try and find a way to migrate that over to this night sky site, and then strip out the parts that won't be the same, you know, I'll replace the graphics replace a lot of the layout stuff in a way that would be unique and bespoke to the way that I want this nightscape podcast website to go. But it's a little better than ours, it's a lot less work, it saved me a ton of time so that I don't have to go back through and make customizations to each of them, the fields associated with the site in a way that would be like brand new to it. So. So I'm trying to learn about that a little bit. What I've been trying to do is find out, I guess, different ways to do that. So one thing that I ran into, while I was trying to do a bunch of this troubleshooting on my site over the last couple of weeks, was that I'm really in need of making backups of my WordPress sites. And so what I went through and did is I made sure there's ways within WordPress to do this, but I was using a plugin. That's and you should let me know if anybody's listening out there. And they've had experience doing backups at their WordPress site, you should let me know it was the most effective there's, there's like the cPanel backup that I've made from the server side where I backed up the files that were associated with the website. And so hopefully that can be restored in a way that'd be useful. But there are also some complications that I think I've run into with that. And it wasn't as user-friendly as I wanted it to be. And the restore points, I don't know, it didn't feel like it worked for me as well as I had hoped it would. But it did come in use, it was very useful for me to do that when I did run into problems, and I wasn't able to access the site. So I'm glad I had those backups of the cPanel. But I do still have access to the WordPress dashboard of my website, what I'm hoping to do is use this plug-in system that I found. And I'm sure like a million other people according to what it said, I have found it also. But I'm using this plugin called Updraft Plus, to try and make to try and make backups of my WordPress pages. So I went through and made backups of each of the WordPress websites that I've created so far. And first, that was the Billy Newman photo.com website. And then in addition to that, there was golden hour wedding calm. So I made backups of both of those. And then there are another two websites that I'm still kind of working on. And I wanted to want to try and make those new. But I did make backups of those also. And I was able to save those on my server. But I was also able to download those to my local drive and put those on an external hard drive. And the great thing is, is that I can version those backups. So when I make adjustments, or when I make updates to my site, and I want to make another backup of it, it'll make I can make a backup, and then I can download that. And that'll be like the, you know, this was in January 2019. But with all these extra pieces of content, and with all these extra additions to the site, this will be the backup I make in February 2019, something like that. What I'm trying to figure out those. And I think what I've discovered is that what I want to do is make a backup of my WordPress site, let's say in this case, that Billy Newman photo comm back up, and I want to use that to clone and then migrate that over to the night sky podcast.com website. And so I think I found a way to do that even within Updraft Plus now the Updraft Plus plugin offers a premium service where you can purchase the ability to do a database migration for I think, $30, it's not $30 per site, but I think it's $30 for the plugin, and then you get support from that plugin developer for some time, I think it's like six months on the low end. And then if you need support for a longer amount of time, I think it's more money than that. There are probably some caveats to it. But that is an option that I'm trying to explore right now as if I'd want to go through that process of using the Updraft Plus plugin to do a migration on my site where I can bring in a lot of the theme customizations, the theme itself and the, I guess, the database with the updated database over to the night sky podcast website. And it could be an easy sort of one-click solution for it. But I'm also trying to look around and see if there are other ways for me to do an import for a clone of the website and the website data so that I can bring in a lot of the information but maybe leave out a lot of pieces that I won't need because I'm not trying to make an end an exact duplicate or an exact copy, I'm just trying to bring over certain elements that would be that have already been adjusted in a way that I don't want to do the work over for. So if I could just kind of bring in this draft of the website version, that's almost everything complete in the way that I want. And then delete the content that was on the blog, delete the pieces that were you know, over in this section of the site, rewrite and about page and a couple of paragraphs over here, recreate some graphics, and then I would have what would seem like a familiar site that would be on-brand. But it would also be, you know, a new site that would have a lot of new content on it, and it would just kind of remain the way that I wanted it to. So that's sort of the hope that I'm trying to go for. And I guess that the Updraft Plus plugin creates XML files for you to use. And 20:50 I don't know how it works. But I think if you break open the file that you downloaded, you can go through and then and then there's an alternate way of making an upload for that sort of stuff. But I guess the problem is, is like the database. So if you're migrating a site, it's expecting all those domain names to be what they had been in the past and not migrated, or not a set of new links that have these new domain names, everything is going to link back to another site, that it's not, it's not at so the database, I was just not going to make sense. And I think that's what this migration tool is supposed to help you do. So I'm looking into that. And I'm hopeful that I can kind of put that together pretty quickly. I'm also trying to be conscious of my time a little bit too so that I don't spend a huge amount of time and development trying to figure out you know, how to how to go through and fix a bunch of errors that might be created if I tried to do a restore of a backup or a clone of my other site and try and migrate that over to this new domain. I'm trying to figure out a way where I don't have to worry about that all that much, but I'm still gonna do some more research. It's gonna be an ongoing project, an ongoing project, and I will update you in this podcast on my progress. That's what I figured. So I'm gonna do that with another site too. I think I might have mentioned yesterday that we're starting the golden hour experience podcast. And we've also started the golden hour experience.com website. And so I'm going to try and go through the same process over on that site. So I can import a bunch of the settings that I have from golden hour wedding calm and try and put it together in a way so that I get to save a bunch of time and not have to redevelop a WordPress site from scratch again. So that's it and it could work it seems like if I pay just a little bit of money, I can make it work, which might make it worth it. I figured the other news that I was going to get to was some stuff about ebooks. I'm sure you're excited now. Thanks for listening to all this. Thanks for checking out this episode of The Billy Newman photo podcast. Hope you guys check out some stuff on Billy Newman's photo comm you knew things up there some stuff on the homepage, good links to other outbound sources. some links to books and links to some podcasts. Like these blog posts are pretty cool. Yeah, check it out at Billy numina photo calm. Thanks for listening to this episode and the back end

An SSL (Secure Socket Layer) Certificate is a security protocol that encrypts and secures the data transmission and communication between the user's browser and the website's server. This certificate ensures data protection against several hackers and online threats who wish to hack the private and sensitive customer information from your website. In today's episode, we talk about SSL Certificates and their multiple benefits for your website. Read our blog post to learn how you can install SSL Certificates in cPanel using WHM: https://blog.resellerclub.com/how-to-install-ssl-certificate-in-cpanel-using-whm/ Get ResellerClub's Comodo SSL Certificate for your website's security, credibility, and trust at a cost-efficient rate: https://www.resellerclub.com/comodo-ssl-certificate

An SSL (Secure Socket Layer) Certificate is a security protocol that encrypts and secures the data transmission and communication between the user's browser and the website's server. This certificate ensures data protection against several hackers and online threats who wish to hack the private and sensitive customer information from your website. In today's episode, we talk about SSL Certificates and their multiple benefits for your website. Read our blog post to learn how you can install SSL Certificates in cPanel using WHM: https://blog.resellerclub.com/how-to-install-ssl-certificate-in-cpanel-using-whm/ Get ResellerClub's Comodo SSL Certificate for your website's security, credibility, and trust at a cost-efficient rate: https://www.resellerclub.com/comodo-ssl-certificate

On this week's show Patrick Gray and Adam Boileau discuss recent security news, including: T-Mobile owned hard USA no fly list winds up on unsecured ElasticSearch in Bahrain… because reasons Facebook scrambles to secure Afghani accounts Hacker steals and returns $600 from de-fi platform Healthcare sector struggles with ransomware attacks A very sweet TCP-based amplification technique that will be A Problem Much, much more Evan Sultanik and Dan Guido will be joining us to talk about Fickling – a tool developed by Trail of Bits to do unnatural things to the Python Pickle files that are heavily used as a means to share machine learning models. The machine learning supply chain is really quite wobbly, and they'll be joining us later to talk about that. Links to everything that we discussed are below and you can follow Patrick or Adam on Twitter if that's your thing. Show notes T-Mobile breach climbs to over 50 million people T-Mobile: Breach Exposed SSN/DOB of 40M+ People – Krebs on Security 1.9 million records from the FBI's terrorist watchlist leaked online - The Record by Recorded Future Facebook, other platforms scramble to secure user accounts in Afghanistan This $600 Million Crypto Heist Is the Most Bizarre Hack in Recent Memory A Hacker Stole and Then Returned $600 Million Japanese crypto-exchange Liquid hacked for $94 million - The Record by Recorded Future Operator of the Helix bitcoin mixer pleads guilty to money laundering - The Record by Recorded Future Healthcare provider expected to lose $106.8 million following ransomware attack - The Record by Recorded Future Hospitals hamstrung by ransomware are turning away patients | Ars Technica US healthcare org sends data breach warning to 1.4m patients following ransomware attack | The Daily Swig The pandemic revealed the health risks of hospital ransomware attacks - The Verge Ransomware hackers could hit U.S. supply chain, experts warn Ransomware hits Lojas Renner, Brazil's largest clothing store chain - The Record by Recorded Future RansomClave project uses Intel SGX enclaves for ransomware attacks - The Record by Recorded Future Wanted: Disgruntled Employees to Deploy Ransomware – Krebs on Security Japan's Tokio Marine is the latest insurer to be victimized by ransomware Cyber insurance market encounters ‘crisis moment' as ransomware costs pile up White House to tackle cyber challenges with Apple, IBM, insurance CEOs | Reuters FBI sends its first-ever alert about a 'ransomware affiliate' - The Record by Recorded Future New LockFile ransomware gang weaponizes ProxyShell and PetitPotam attacks - The Record by Recorded Future Multiple ransomware gangs pounce on 'PrintNightmare' vulnerability Peterborough NH Cyberattack: Town Loses $2.3M in Taxpayer Money – NBC Boston Almost 2,000 Exchange servers hacked using ProxyShell exploit - The Record by Recorded Future ALTDOS hacking group wreaks havoc across Southeast Asia - The Record by Recorded Future Hackers Leak Surveillance Camera Videos Purportedly Taken From Inside Iran's Evin Prison - by Kim Zetter - Zero Day Apple reopens legal fight against security firm Corellium, raising concerns for ethical hackers Apple says researchers can vet its child safety features. But it's suing a startup that does just that. | MIT Technology Review This $500 Million Russian Cyber Mogul Planned To Take His Company Public—Then America Accused It Of Hacking For Putin's Spies Cisco: Security devices are vulnerable to SNIcat data exfiltration technique - The Record by Recorded Future SNIcat: Circumventing the guardians | mnemonic BlackBerry's popular operating system for medical devices affected by critical vulnerabilities, drawing fed warnings Realtek SDK vulnerabilities impact dozens of downstream IoT vendors | The Daily Swig Hundreds of thousands of Realtek-based devices under attack from IoT botnet - The Record by Recorded Future Accellion Kiteworks Vulnerabilities | Insomnia Security Firewalls and middleboxes can be weaponized for gigantic DDoS attacks - The Record by Recorded Future Hackers tried to exploit two zero-days in Trend Micro's Apex One EDR platform - The Record by Recorded Future Exhaustive study puts China's infamous Great Firewall under the microscope | The Daily Swig Web hosting platform cPanel & WHM is vulnerable to authenticated RCE and privilege escalation | The Daily Swig Benno on Twitter: "I will donate $50 to a charity of @riskybusiness' choice if he puts this in the show." / Twitter Never a dill moment: Exploiting machine learning pickle files PrivacyRaven: Implementing a proof of concept for model inversion GitHub - trailofbits/fickling: A Python pickling decompiler and static analyzer

Tips this week include: • More digital downloads and masterminds coming • What I'm bummed about in the Video SEO testing • An update on my effort to stop SEO agency bot crawls • Why new sites need security too • Update on UpdraftPlus not backing up for some folks • Why I'm excited that the Gutenberg Block Pattern Directory is live • The death of page builders • Automattic acquires Pocket Casts • Google finishes first phase of FLoC testing for alternative 3rd party cookies • Why to set affiliate links to nofollow AND sponsored • New list of approved Genesis child themes coming soon • What designers think of the new theme.json styles file instead of CSS • Which theme should you use? • What to do before entering the design process these days • A new look for cPanel that resembles Interworx • Why me and more of my clients are switching to Interworx control panel • Will we use YAT Emojis instead of URLs someday?

TranscriptCorey: This episode is sponsored in part by LaunchDarkly. Take a look at what it takes to get your code into production. I'm going to just guess that it's awful because it's always awful. No one loves their deployment process. What if launching new features didn't require you to do a full-on code and possibly infrastructure deploy? What if you could test on a small subset of users and then roll it back immediately if results aren't what you expect? LaunchDarkly does exactly this. To learn more, visit launchdarkly.com and tell them Corey sent you, and watch for the wince.Jesse: Hello, and welcome to AWS Morning Brief: Fridays From the Field. I'm Jesse DeRose.Amy: I'm Amy Negrette.Tim: And I'm Tim Banks.Jesse: This is the podcast within a podcast where we talk about all the ways we've seen AWS used and abused in the wild. Today, we're going to be talking about AWS, an open-source software. Now, that's kind of a broad topic, but there have been some specific, recent events I'll say, over the last year maybe or maybe even less, related to AWS and open-source software that really got us talking, and I wanted to have a deeper conversation with both of you on this topic.Tim: Well, you should probably start by going over some of the things that you're mentioning, when you say ‘some of these things,' what are those things, Jesse?Jesse: Yeah. So, I think the best place to start is what constitutes open-source software. And specifically, I think, not just what constitutes open-source software, but how does that differ from an open-source company?Tim: So, open-source software can be anything: Linux kernel, bash, anything like that, any Python functioning module. If you make a piece of software, whatever it is, and you license it with one of the various open-source licenses, or your own open-source license or whatever, it's something that the community kind of owns. So, when they get big, they have maintainers, everything like that, but at its essence, it's a piece of software that you can freely download and use, and then you're free to modify it as you need, and then it's up to the specifics of the license to whether you're required to send those modifications back, to include them, or to whatever. But the essence is that it's a piece of software that's free for me to use and free for me to modify under it's license.Jesse: And one of the other things I want to add to that is, correct me if I'm wrong here, but isn't a lot of open-source software is very community-owned, so there's a lot of focus on folks from the community that is using this software giving back not because they need to under the licensing, necessarily, but because they want to continue using this and making it better over time.Amy: I think one of the issues is that becomes a very opinionated kind of statement where there are a lot of people in the open-source community who feel that if you're going to use something and make changes to better suit what your needs are, that you should be able to submit those changes back to the community, or back to whoever owns the base of the software. But that said, it's like the community edition of MySQL before Microsoft bought it, where the assumption was that there's essentially a candidate of it that anyone can use without the expectation of submitting it back.Jesse: So, that's a broad definition of open-source software, but how does open-source software, broadly speaking, differ from an open-source company? I'm thinking specifically there is the open-source software of Elasticsearch, for example, or I should say, previously the open-source software of Elasticsearch that was owned by the open-source company, Elastic. So, what does that relationship look like? How does an open-source company like that differ from the open-source software itself?Tim: So, there are typically a couple of ways. Usually, a company that is the owner of an open-source product still has some kind of retention of the IP in their various licenses that they can do that with, but essentially—and this is in the words of one of the founders of Elastic—that they're benevolent dictators over the software. And so they allow folks to contribute, but they don't have to. And most of those open-source software companies will have a commercial version of that software that has other features that are not available, packages with support or some of the things like that, some kind of value-added thing that you're going to wind up paying for. The best way to describe—like you said—there's the company Elastic and then the product Elasticsearch.I relate back to before: there was Red Hat Linux, which was open-source, and then the company Red Hat. And I remember when they went public and everyone was shocked that a company can make profit off of something they gave away for free. But while the core of the software itself was free, the support was not free, nor was the add-on features that enterprises wanted. And so that tends to be kind of what the business model is, is that you create the software, it's open-source for a while to get a big user base, and then when it gets adopted by enterprises or people that really would pay for support or for other features, that's when the license tends to change, or there's a fork between the open-source version and then the commercial version.Jesse: And it definitely sounds like there can be benefits to an open-source company essentially charging for not just the open-source software, but these extra benefits like supports and additional features because I know I've traced multiple code bugs back to a piece of open-source software that there's a PR or an issue that has been sitting open for months, if not longer because the community just doesn't have the time to look into the issue, doesn't have the time to work on the issue, they are managing it on their own, separate as a side job, separate from their day-to-day work. Whereas if that is a bug that I'm tracing back to a feature in an open-source piece of software, or I should say software that I am paying for through an open-source company, I have a much clearer support path to a resolution to resolving that issue.Tim: And I think what the end up doing is then you see it more like a traditional core software model, like, you know, a la Oracle, or something like that where you pay for the software essentially, but it comes packaged with these things that you get because of it, and then there's a support contract on top of it, and then there's hosting or cloud, whatever it is, on top of that, now, but you would still end up paying for the software and then support as part of the same deal. But as you know, these are for-profit companies. People get paid for them; they are publicly traded; they sell this software; they sell this product, whether it's the services or the hosting, for profit. That is not open-source software. So, if company X that makes software X, goes under, they are acting like the software would then go under as if the software doesn't belong to the community.So, a business that goes after a business is always going to be fair play; I believe they call it capitalism. But when you talk about going after open-source software, you're looking at what Microsoft was doing in the '90s and early 2000s, with Linux and other open-source challenges to the Windows and the other paid commercial enterprise software market. When folks started using Linux and servers because it was free, customizable, and they could do pretty much everything they wanted to or version of it that they were using commercial Unices for, or even replacing Windows for, you didn't really see the commercial Unices going after it because that very specialized use cases; the user had specialized hardware. What folks were doing, they're buying Wintel machines and putting Linux on them, they were getting them without Windows licenses, or trial licenses, throwing Linux on it. And Microsoft really went after open-source; they really went after open-source.They were calling it insecure, they were calling it flash in the pan, saying it would never happen. They ran a good marketing campaign for a long time against open-source software so that people would not use it and would instead use their closed-source software. That is going after open-source, not going after quote-unquote, “Open-source companies.”Jesse: Yeah, I think that's ultimately what I want to dive into next, which is, there's been a lot of buzz about AWS going after open-source, being a risk to open-source software, specifically, with the release of AWS Managed Services for software like Elasticsearch, for example, Kubernetes, Prometheus vs. Other open-source packages that you can now run as a managed service in AWS. There's a lot of concern that AWS is basically a risk to all of these pieces of open-source software, but that doesn't necessarily seem to be the case, based on what we're talking about. One of the things that I want to dive into really specifically here is this licensing idea. Is it important to end-users? How would they know about what license they're using, or if the license changes?Tim: I'll let Amy dig in on it because she's probably the expert of three of them, but I will say one case in point, I remember where licensing did become very important was Java. JDK licenses, when Oracle started cornering the market on enclosing all the licenses, you had to use different types of Javas. So, you had to get, like, open JDK; you couldn't use Sun, Oracle Java, or whatever it was. And so that became a heavy lift of replacing packages and making sure all that stuff was in compliance, and while tracking packages, replacing them, doing all the necessary things because if you're running Java, you're probably running it in production. Why you would, I don't know, but there are those things that you would have to do in order to be able to just replace a package. The impact of the license, even if it doesn't cost a dime for usage, it still matters, and in real dollars and real engineering time.Amy: Even free licensing will cost you money if you do it wrong. The reason why I love talking about licensing is because I used to work for the government—Jesse: [laugh].Amy: —and if you think a large company like Amazon or Microsoft loves doing anything to rattle the cage of smaller businesses, it's not nearly as much as they love doing it to the government. So, any company that has a government-specific license, and the government is not using it, they will get sued and fined for a bunch of money, which sounds like a conflict between a super-large company and the government and who the hell cares about that, but this also translates the way they handle licensing for end-users and for smaller companies. So, for the most part for the end-user, you're going to look at what is generally sent to you to use any piece of licensing, the EULA, the End-User License Agreement, and you're just going to say, “Yeah, fine, this thing is 20 pages long; I'm not going to read this, it's fine.” And for most end-users, that is actually, you're good to go because they're not going to be coming after small, single-person users. What these licenses do is restrict the way larger organizations—be it the government or mid to larger companies—actually use their software, so that—this is a little dating—someone does not buy a single disk that does not report home, and then install that one disk on 20 computers, which is a thing that everyone has seen done if they've been in the industry long enough.Jesse: Yeah.Amy: Yeah. And it means things like licensing inventory is important, to the single you're using this license at home and you install Adobe on three computers, you would think it's not… would not hurt their value very much, but they also make it so that you can't even do that anymore. So, in purchased software, it makes a big deal for end-users; if it's just something free like being able to use some community SQL workbench just to mess around with stuff at home or on personal projects, you're usually going to be okay.Corey: This episode is sponsored in part by our friends at ChaosSearch. You could run Elasticsearch or Elastic Cloud—or OpenSearch as they're calling it now—or a self-hosted ELK stack. But why? ChaosSearch gives you the same API you've come to know and tolerate, along with unlimited data retention and no data movement. Just throw your data into S3 and proceed from there as you would expect. This is great for IT operations folks, for app performance monitoring, cybersecurity. If you're using Elasticsearch, consider not running Elasticsearch. They're also available now in the AWS marketplace if you'd prefer not to go direct and have half of whatever you pay them count towards your EDB commitment. Discover what companies like HubSpot, Klarna, Equifax, Armor Security, and Blackboard already have. To learn more, visit chaossearch.io and tell them I sent you just so you can see them facepalm, yet again.Jesse: Yeah, this is a really big issue. There's so much complexity in this space because Tim, like you said, there's some amount of capitalism here of AWS competing with open-source companies; there's business opportunities to change licensing, which can be a good thing for a company or it could be a terrible thing for a company's user base. There's lots of complexity to this issue. And I mean, in the amount of time that we've been talking, we've only really scratched the surface. I think there's so much more to this space to talk about.Tim: There really is, and there's a lot of history that we really need to cover to really paint an accurate picture. I think back when web hosting first became a thing, and everyone was running LAMP stacks and nobody was saying, “Oh, no, using cPanel is going to kill Apache.” That wasn't a thing because, yeah, it was a for-profit company that was using open-source software to make money and yet Apache still lived, and [unintelligible 00:15:00] still lived; MySQL still made it; PHP was still around. So, to say that utilizing open-source software to provide a service, to provide a paid service, is going to kill the open-source softwares, at best it's misrepresentation and omits a lot of things. So, yeah, there's a lot of stuff we can dig into, a lot of things we can cover.And the topic is broad, and so this is why it's important for us to talk about it, I think, in the context of AWS and the AWS, kind of, ecosystem is that when you see companies with big crocodile tears, saying, “Oh, yeah, AWS is trying to kill open-source,” it's like, “No, they're not trying to kill open-source.” They may be trying to go after your company, but they aren't the same.Jesse: And it feels to me like that is part of the way that the business world works. And I'm not saying that it's a great part of the way the business world works, but how can you differentiate your company in such a way that you still retain your user base if AWS releases a competing product? I'm not thrilled with the fact that AWS is releasing all these products that are competing with open-source companies, but I'm also not going to say that it's not beneficial, in some ways, for AWS customers. So, I see both sides of the coin here and I don't have a clear idea of what the best path forward is.Amy: As much as I hate the market demands it type of argument, a lot of the libraries, and open-source software, and all of these other things that AWS has successfully gone after, they've gone after ones that weren't entirely easy to use in the first place. Things like Kubernetes, and Prometheus, and MongoDB, and Elastic. These are not simple solutions to begin with, so if they didn't do it, there are a lot of other management companies that will help you deal with these very specific products. The only difference is, one of them is AWS.Jesse: [laugh]. One of them is a multibillion-dollar company.Amy: Oh, they've all got money, man.Jesse: [laugh].Amy: I mean, let's be real. At our pay grade, the difference between a multimillion-dollar and a billion-dollar company, I don't think affects you at your level at all.Jesse: No.Amy: I'm not seeing any of that difference. I am not. [laugh].Tim: Yeah, I definitely think if you all want us to dig into more of this—and we could do a lot more—let us know. If there are things you think we're wrong on, or things that you think we need to dig deeper on, yeah, we'd love to do that. Because this is a complex and nuanced topic that does have a lot of information that should be discussed so that folks can have a clear view of what the picture looks like.Jesse: Well, that'll do it for us this week, folks. If you've got questions you'd like us to answer please go to lastweekinaws.com/QA, fill out the form and we'll answer those questions on a future episode of the show.If you've enjoyed this podcast, please go to lastweekinaws.com/review and give it a five-star review on your podcast platform of choice, whereas if you hated this podcast, please go to lastweekinaws.com/review, give it a five-star rating on your podcast platform of choice and tell us your thoughts on this conversation, on AWS versus open-source software versus open-source companies.Announcer: This has been a HumblePod production. Stay humble.

Síguenos en: ¿Qué tal la semana? Semana esther Cerrando temas de clientes antes de vacaciones Seodrama de cliente Vulnerabilidad WooCommerce Semana Nahuai Reunión de Genesis Shapers en la que hablamos de headless, gestión de webs, la versión 3.3.4 de Genesis... Investigando cosas para OsomPress. Contenido Nahuai 3 nuevos tutoriales en Código Genesis de los cuales destaca: Deshabilitar el directorio de bloques del editor de WordPress Tema de la semana: Tipo de migración: Entre servidoresLocal -> ServidorServidor -> LocalCon / Sin cambio dominio Solo web o completa (email, etc…) Tipo de web: CorporativaCon registro usuarios / foro / comentarios Con pago online (ecommerce - academias) Antes de comenzar: Confirmar acceso al hosting (cPanel y FTP)Confirmar acceso al dominioRealizar una copia de seguridadDesactivar plugins de caché Pasos básicos Poner en mantenimiento (si hay registros/pagos)Crear duplicado completo (Duplicator/All in one Migration/herramienta hosting...) Episodio 7 donde hablamos de herramientas de clonado.Subir duplicado a nuevo hostingCrear registro hosts para poder apuntar IP al nuevo Comprobaciones (Better Search Replace, contenido mixto....)Migrar email (herramientas específicas o manualmente)Cambio DNSPedir que aceleren la instalación de certificado SSL  Después de la migración: Activar cachéCambio de dominio (si procede) Problemas: Peso excesivo (errores timeouts)Diferencias versiones PHP / MySql / memoria o configuración entre servidoresQue no puedas acceder a la nueva web -> limpiar caché de DNS router/ordenador o modificar el fichero hosts. Ambos los comentamos en la sección de tips del episodio 11. Novedades Automattic compra Pocket Casts. Actualización de seguridad de WooCommerce. Tip de la semana Recurso online para aprender y practicar CSS.  Menciones Muchas felicitaciones por la publicación de los temas de OsomPress en la web de StudioPress. ???? Gracias a: Este episodio está patrocinado por StudioPress, los creadores de Genesis Framework, el entorno de trabajo de temas más popular de WordPress. Ya está disponible Genesis Pro para todo el mundo, 360$ anuales que dan acceso a: Genesis FrameworkChild themes de Genesis de StudioPress1 año de hosting en WP EnginePlugin Genesis Pro (Diseños y secciones, restricción de bloques por usuarios…) y Genesis Custom Blocks Pro.

Data and website security are uncompromised and top priority of every website owner. An SSL (Security Socket Layer) certificate is a security protocol that provides data encryption and ensures the protection of confidential data on your website. It is quite essential in terms of the growth of your business and your website's SEO. An SSL certificate on your business website ensures your business's credibility to your customers. It also helps in SEO (Search Engine Optimization) and SERP (Search Engine Results Page) rankings, as Google actively pushes the website with an SSL certificate down the rank positions. In today's podcast episode, we dive deep into the SSL certificate, its need and importance, how it works, and why your website needs it. You can also read this blog post that talks about how you can install SSL using WHM in cPanel: https://blog.resellerclub.com/how-to-install-ssl-certificate-in-cpanel-using-whm/ Check out and get the Comodo SSL certificate offered by ResellerClub for your website's trust, security, and credibility from: https://india.resellerclub.com/ssl-certificates

La opción gratuita para reemplazar a cPanel es HestiaCP y en este episodio hablaremos un poco del pasado y por supuesto del presente.

La opción gratuita para reemplazar a cPanel es HestiaCP y en este episodio hablaremos un poco del pasado y por supuesto del presente.

It’s almost the default SEO plugin to add on to WordPress websites. Millions of websites are using it and it’s being developed and updated all the time. But does adding Yoast actually do anything? This is Clickstarter, the Australian digital marketing podcast. I’m Dante St James. Yoast is a plugin used on WordPress that claims to assist you to rank better on search engines by making you choose a range of key words to focus in on, then mark your blog posts and pages against those key words to see how well you have matched your content to your desire to rank on search for that topic. It then goes a bit further by adding a site map XML file to your website which Google then picks up to check on what you have on your site, and where to check next time for updates. And finally it will mark your pages and articles on how readable it is for the average page viewer and give you a list of things you can do to improve your chances of ranking better. That all seems pretty good on paper. A more readable article will be read for longer, meaning that the viewer will dwell for longer on your website. Makes sense, right? And if your titles and opening paragraphs are chock full of mentions of the things you want to be found for on Google, even better, right? The trouble with Yoast and SEO plugins The main problem with SEO plugins like Yoast, All In One SEO and SmartCrawler, is that they tend only look at one slice of the Search Engine Optimisation pie. And that is what we call On Page SEO. This is also probably the easiest part of SEO to address on a website, because you don’t really need any technical knowledge, server access or even CPanel access to make it happen. Search Engine Optimisation as a discipline involves technical changes, mobile optimisation, efficient code use, popularity of your website, and a strange term called Domain Authority which Google denies is a thing, but everyone kinda assumes is a thing because more trusted websites seem to rank better in search. Yoast doesn’t really address any of this. The biggest factors of SEO are Trust and Popularity, followed then by Backlinks, which are the number of relevant places online that are linking back to your page, article or website address. Yoast can’t do anything about any of these things. So plugins like it can lull you into a false sense of comfort that you have “done your SEO.” You’ve ticked that box, so now you can move on. What Yoast does well I’ll give Yoast and these other similar plugins some credit. They actually do the On Page SEO stuff pretty well. The readability scores and recommendations on how to use your target keywords better in your titles and paragraphs does help you to become a better writer for humans, which in turn helps to make you’re a better writer for search engines. It puts all this at the bottom of your page or posts backend view so you can see a live look at how your changes are helping you get a better score. The trouble is that none of this will help you if your website is slow to load, full of half a dozen different kinds of tracking code, full of large images that take a while to load or full of dishonest information that doesn’t match what your Yoast settings are saying that your page contains. Yoast does perhaps make you a better writer, but it won’t make you a better Google Search Ranker. And doing some work on your pages and posts with Yoast doesn’t mean that you web developer has “done your SEO.” I’m Dante St James. You can learn more about digital marketing the Australian way at clickstarter.com.au, and give your business all the tools it needs to get known, get found and stay known.

There’s an easier way to build Splunk dashboards, and Service Delivery Manager Chuck Brown is here to help! This week on the podcast Michael and Hutch walk through Chucks latest demo and learn how the new cPanel feature can help optimize your Splunk environment. Things Mentioned:·      https://www.bloomberg.com/news/articles/2021-04-14/nba-s-houston-rockets-face-cyber-attack-by-ransomware-group·      https://www.tripwire.com/state-of-security/featured/white-house-plan-protect-critical-infrastructure-against-cyber-attacks/·      https://www.justice.gov/usao-sdtx/pr/justice-department-announces-court-authorized-effort-disrupt-exploitation-microsoft·      https://krebsonsecurity.com/2021/04/did-someone-at-the-commerce-dept-find-a-solarwinds-backdoor-in-aug-2020/·      Raise Demo https://youtu.be/goC3xdG8rj4Do you have questions for the hosts? Reach out to us on our website at https://www.setsolutions.com/contact/Hosts: Michael Farnum and Justin HutchensProduced by: Set SolutionsEdited by: Lauren LynchMusic Credit: Inspired by Kevin MacLeodLink: https://incompetech.filmmusic.io/song/3918-inspiredLicense: http://creativecommons.org/licenses/by/4.0/

If you are looking at hosting a WordPress website, I suggest you use a cPanel.  At first, a cPanel may seem intimidating but once you learn the basic, hosting a WordPress website is so much easier.  Another benefit is you have control over everything and you don't have to wait for support to help you out.   Welcome back to Casey's SEO for today i just wanted to discuss um something i was doing over the past weekend and i was i was just trying to deploy a couple more websites, um and i was trying to use some different hosting services. I will say that it did not go very well now. I have tried this in the past, but for some reason i always pick cpanels, and i did not do that this time. Well, i guess i really didn't look to see if they offered a cpanel, and that was my mistake. So what i have found is once you get used to a certain way of doing things. It becomes very, very easy like, for example, if you're going to host a a WordPress website on a cpanel to me is very, very simple: all you do. Is you log into the cpanel? You add your domain depending on where your domain is registered. You may be using the name servers from that cpanel or your server there or you just take the ip and you're going to point it to that hosting provider. Very very simple, then you're going to go like all the way down on the page you're going to click. You know one click install for WordPress choose your domain hit the button fill out your username and password and boom you are done. It is that simple, but with some of these other hosting providers, where they don't offer a cpanel, i just find it very, very difficult to do, and i spend 10 times as long trying to figure out how to even point my domain over there or put put My domain onto their hosting and then try to match them up and deploy a wordpress site. It's just it's very, very challenging, then sometimes they're they either have email service or they don't and then, when they do, you have to go to like nine different other pages. To find it, i don't recommend it for me if you want something that you have more control over and you want to deploy, you know, maybe multiple websites, whatever it is, i would definitely choose a cpanel like i said, all you have to do is go to A hosting provider sign up, it will deploy your cpanel for you. You click on that button. You go in. You can add your website, you can scroll down. You can then add your WordPress if you're going to use WordPress, there's folders or icons in there for email. All you do is click on them, add your name and what domain you're going to put it on, and then you have everything right there, plus the other benefit for me of using a cpanel is, let's just say you upload a plugin or you have a plugin That kind of crashed and your back end is not working or you can't get into it. You can go back into that. Cpanel go to your file manager. Click in your contents, folder find your plugins find out what plugin it may be and, let's just say you just uploaded a plugin and it doesn't work. So you know exactly what plugin plugin it is. Go there change the name, go back see if it works. If it works, you know you have a problem with that. Then you can go ahead and troubleshoot with that plugin to see what is going on and it's very simple with some of the other hosting providers, or maybe it's just a WordPress hosting you don't have that option. You have to go back in contact. Customer support figure out the issue, but it's going to be on their time, so you may get your website back up in 30 minutes an hour who knows, but for me i can go back in. If i already know what plug-in it is, i can go back in and it will take me five minutes and then i can start over, but i have that control to go ahead and do that. But that is just it for today wanted to fill you guys in on some hosting a couple different options and which one i prefer, if you have something that is not cpanel, that is very, very easy to load up a WordPress website. Please let me know - and i will definitely check that out so that is it for today and I'll be back soon with another episode. 

Inledning Jocke använder Markdown, det är störigt med saker som försöker formattera ens inklistrade text Jocke e-postar med John Gruber, Microsoft menar allvar med Vista Christian kan hantera barntema. Det har hänt mycket med Wordpress, och det är inte odelat bra Påsken närmar sig, har alla plockat fram sina dymlar? Sveriges bästa kebab Pandemianpassning. Citigroup inför Zoomfria fredagar. Fredrik och Christian lämnar sin backlog bakom sig, funderar över hur distansmöten hackar upp dagen, och börja på ny ticket Uppföljning Intel vill bygga fler kretsar åt Apple, om de får Ämnen Microsoft erbjuder upp till 30 000 dollar för den som hittar buggar (säkerhetshål) i Teams Robotdammsugare - vad är bäst och vad ska man köpa? Pratar de med Homekit? Ljudlimpa eller liknade snygg diskret ljudlösning med Apple TV 4K - vad är bäst och vad ska man köpa? Ett fort av Homepod? Kabel och kaffe - följtips på Instagram Fredrik skriver 17 rader kod, fröjdas över datorers kraft OS X-retrospekt? Nog var Panther tidernas bästa version? Voltswagen - ett otroligt dåligt hanterat aprilskämt. Vid inspelning hade de inte erkänt att det var ett skämt än Länkar Markdown Notion Windows Vista Building a better dinosaur Windows Vista means business Preview-bilder med Jekyll - texten som felsöktes i sändning Kramdown Dymmelonsdag Kebaben i Årsta Sveriges bästa kebab ska finnas i Jönköping Kebabsåsreceptet i Jönköpingsposten Zoomfria fredagar på Citigroup Intel vill ändå gärna bygga kretsar åt Apple Microsoft betalar för att hitta säkerhetshål i Teams Sonos ljudlimpor - Arc och Beam Sonos sub Kabel och kaffe Teknikveckan intervjuar Kabel och kaffe-Erik En podd om teknik om hemautomatisering Cpanel Phpmyadmin CUPS Slå på Cups i Macos Alla John Siracusas Mac OS-recensioner Spotlight Isight-kamerorna Filevault Snow leopard Mac OS X server Ical Xiaomi mi laptop pro Oroligt i FeeBSD-land Xiaomi-klockor Voltswagen - ett extremt misslyckat aprilskämt Fredrik Björeman, Joacim Melin och Christian Åhs. Fullständig avsnittsinformation finns här: https://www.bjoremanmelin.se/podcast/avsnitt-252-stangt-i-hela-jira.html.

L'inclusività passa anche attraverso l'utilizzo delle parole giuste per raccontarla e per metterla in atto. È un vero e proprio processo di cui ripercorriamo le tappe in questo nuovo episodio in compagnia di Alice Orrù, copywriter e traduttrice tecnica con il pallino per il linguaggio inclusivo e per i siti WordPress. Alice mi racconta il suo percorso professionale, dalla laurea in economia al marketing digitale, passando successivamente all'applicazione dello studio delle lingue per il supporto clienti di una clinica di riproduzione assistita spagnola e poi a livello tecnico per una startup che sviluppa plugin. Una storia lavorativa varia ma con un fil rouge che l'ha predisposta all'ascolto, al confronto e all'importanza dell'empatia, provando a immaginare sempre che cosa sentono le persone quando approcciano una determinata situazione, che sia un'esperienza o un prodotto. Nell'episodio 10 della seconda stagione capiremo insieme come scrivere e descrivere, come applicare la culturalizzazione, come abbattere le etichette e i nostri bias internalizzati, chiarendo cosa evitare per rendere il nostro linguaggio finalmente “rispettoso”. Buon ascolto con “Siamo inclusivi solo a parole?” cPanel – È uno strumento di controllo grafico per la gestione e l'amministrazione di siti internet e web hosting. Culturalizzazione – Unire il contenuto al contesto per estendere il più possibile il numero di persone da raggiungere. Il libro consigliato da Alice – “Cross cultural design” di Senongo Akpem, edito da A Book Apart. Senongo Akpem - Sito personale Inclusive Design – Microsoft Fabrizio Acanfora - Sito personale Chimamanda Adichie - Ted Talk Parlare civile - Il sito "Da vicino nessuno è normale" - Cit. Franco Basaglia --- Send in a voice message: https://anchor.fm/nois3/message

WHM or WHMCS stands for Web Host Manager Complete Solution. Although cPanel is the most-widely used website management tool, WHMCS is a tool explicitly designed for reseller hosting businesses to manage their entire business. WHMCS allows to add/remove customers, assign plans to customers, upgrade or downgrade the resources for your customers, allocate discounts and much more. Apart from this, it can automatically send accurate invoices to your customers, accept payments, send reminders and more. In this episode, you'll get to know what is WHM in detail. Also, refer this blog post to understand more about managing your Web Host Manager: https://blog.resellerclub.com/what-is-web-host-manager-and-how-to-manage-it/ Buy cPanel Reseller Hosting plans with 24x7 customer support at affordable price only at https://www.resellerclub.com/reseller-hosting

WHM or WHMCS stands for Web Host Manager Complete Solution. Although cPanel is the most-widely used website management tool, WHMCS is a tool explicitly designed for reseller hosting businesses to manage their entire business. WHMCS allows to add/remove customers, assign plans to customers, upgrade or downgrade the resources for your customers, allocate discounts and much more. Apart from this, it can automatically send accurate invoices to your customers, accept payments, send reminders and more. In this episode, you'll get to know what is WHM in detail. Also, refer this blog post to understand more about managing your Web Host Manager: https://blog.resellerclub.com/what-is-web-host-manager-and-how-to-manage-it/ Buy cPanel Reseller Hosting plans with 24x7 customer support at affordable price only at https://www.resellerclub.com/reseller-hosting

This is an audio extract from my larger, full video course which is now complete and can be accessed from here: https://bit.ly/3bdPwJL Join the Ask Instructor Facebook Group: https://www.facebook.com/groups/askinstructor Follow me on Twitter: https://twitter.com/askinstructor

Tips this week include: • No checkbox to turn off auto updates in WP 5.6 • State of the Word address this week on Dec 17 • Why you need to check your Grow Social Pro license • Why I’m so happy with the new GTMetrix tester • Why Google PageSpeed Insights is not an accurate tester • Where Google gets its speed data about your site • Update on Genesis Full Site Editing • BlogAid holiday schedule • Update on meeting with my video SEO clients for more testing • What to do if you can’t see edits in preview • A final word on getting errors when saving UpdraftPlus settings • Why not to run end around your host security settings • Why hosts are removing the WordPress Toolkit app in cPanel and what you need to check for

Si tenés un hosting más o menos bueno es probable que tengas CPanel y si tenés CPanel es probable que tengas softaculous y si tenés softaculous probablemente tengas instalador de WordPress. Si tenés todo lo anterior y además diseñás webs ya tenés un entorno de pruebas para testear tus sitios.

On this week’s Technado, the team was joined by Microsoft Cloud Solutions Architect Jeff Mitchell. After learning about his career path, Jeff shared some cool innovations with Azure enterprise-scale landing zones for cloud migrations. In the news, the crew covered a prolonged AWS outage, Microsoft’s Pluton security chip, Linus Torvalds’ thoughts on the Apple M1 hardware, a 2FA bypass flaw in cPanel, and a hacker selling credentials for C-level executives.

On this week’s Technado, the team was joined by Microsoft Cloud Solutions Architect Jeff Mitchell. After learning about his career path, Jeff shared some cool innovations with Azure enterprise-scale landing zones for cloud migrations. In the news, the crew covered a prolonged AWS outage, Microsoft’s Pluton security chip, Linus Torvalds’ thoughts on the Apple M1 hardware, a 2FA bypass flaw in cPanel, and a hacker selling credentials for C-level executives.

On this week’s Technado, the team was joined by Microsoft Cloud Solutions Architect Jeff Mitchell. After learning about his career path, Jeff shared some cool innovations with Azure enterprise-scale landing zones for cloud migrations. In the news, the crew covered a prolonged AWS outage, Microsoft’s Pluton security chip, Linus Torvalds’ thoughts on the Apple M1 hardware, a 2FA bypass flaw in cPanel, and a hacker selling credentials for C-level executives.

On this week’s Technado, the team was joined by Microsoft Cloud Solutions Architect Jeff Mitchell. After learning about his career path, Jeff shared some cool innovations with Azure enterprise-scale landing zones for cloud migrations. In the news, the crew covered a prolonged AWS outage, Microsoft’s Pluton security chip, Linus Torvalds’ thoughts on the Apple M1 hardware, a 2FA bypass flaw in cPanel, and a hacker selling credentials for C-level executives.

On this week’s Technado, the team was joined by Microsoft Cloud Solutions Architect Jeff Mitchell. After learning about his career path, Jeff shared some cool innovations with Azure enterprise-scale landing zones for cloud migrations. In the news, the crew covered a prolonged AWS outage, Microsoft’s Pluton security chip, Linus Torvalds’ thoughts on the Apple M1 hardware, a 2FA bypass flaw in cPanel, and a hacker selling credentials for C-level executives.

WP Builds Newsletter #27 - ClassicPress fork, multisite media library and cPanel acquired

WP Builds Newsletter #27 - ClassicPress fork, multisite media library and cPanel acquired

[block id="424" title="Podcast Links"] Episode 19 has landed where I talk about SSL certificates, switching to a new web host and things I look for in cPanel dashboards. Thanks for tuning in and visit pixelswim.com for all my links, articles and other general info. Episode Links Moto G6 Specs comparison on the three different versions of the G6 Dolby Atmos test on the G6 Hosting Providers Mentioned Stable Host A Small Orange Hostgator SSL Links Google on HTTPS in Chrome Let's Encrypt SSL overview (good, simple breakdown) cPanel What is cPanel?

En este podcast analizamos que debemos de tener en cuenta antes de preparar un VPS desde cero. Veremos cuándo es mejor utilizar algún panel tipo cPanel y cuando es mejor no utilizarlos, también veremos, cómo instalar LAMP o cómo configurar el email en nuestro VPS. La entrada 069. Preparar un VPS desde cero aparece primero en Luis Peris.

En el podcast de hoy hablaremos sobre un tema que interesa a muchos oyentes y se trata de los programas que podemos utilizar (normalmente por el navegador) para administrar nuestro servidor. Software para administrar servidores Para que nadie se pierda, nos tendremos que preguntar ¿Qué son exactamente y qué nos van a permitir? A la primera pregunta (¿Qué son?), se podría decir que el software para administrar servidores, es todo aquel programa que nos facilita la gestión y administración de nuestros servidores para que no tengamos que ejecutar todo el rato comandos por la terminal. La finalidad es crear una capa de abstracción, donde de manera sencilla y con cuatro clicks podamos configurar nuestro servidor. En cuanto a que nos permite, dependerá que software instalemos, no obstante, una gran mayoría de estos programas están enfocados al mundo web, es decir, que nos permitirán configurar Apache, PHP, bases de datos, etc. No obstante, también nos permitirá crear nuevos usuarios, hacer copias de seguridad, etc. Para que podamos comprender mejor las opciones de estos programas, podríamos (generalizando) crear la siguiente lista: Gestión desde el navegador Muchos de estos programas están pensando para que no tengamos que volvernos a conectar a la terminal mediante SSH. Por ello nos permitirán gestionar nuestro servidor con cuatro clicks, desde un navegador. Gestión de los programas Un buen software para administrar servidores nos debe de permitir gestionar los programas que tenemos instalado en nuestro sistema operativo, además de poder instalar otros programas de manera sencilla. Gestión de ficheros Estos programas, también nos deberían de permitir acceder y modificar los ficheros de nuestro servidor de una forma sencilla. Gestión de Backups Los backups son importantes, por ello estos programas deberán de tener un módulo para realizar diferentes tipos de backups, ya sean para bases de datos, para carpetas, etc. Configuración web En muchas ocasiones usaremos nuestro servidor para tener páginas web, por ello, estos programas nos deben de permitir modificar la configuración de PHP mediante el fichero php.ini y de Apache mediante el fichero httpd.conf Acceso al log Nuestros servidores no deberían de tener problemas, no obstante, es mejor tener acceso al log de errores de una manera sencilla. Estos programas nos la deberían de facilitar. Programar tareas (cron job) En algunas ocasiones necesitaremos programar tareas, por ejemplo, que algo se ejecute a una hora determinada, esto lo podremos hacer de manera sencilla si nuestro software de gestión de servidores trae un apartado para los “cron jobs”. Firewall La seguridad es importantísima, por ello el programa que escojamos para gestionar nuestros servidor debería de incluir un módulo para configurar un Firewall. Bien es cierto que muchas veces, no tendrán un módulo propio sino que podrás añadir uno externo, por ejemplo ConfigServer Services. Veamos los principales programas que hay. Gestor de servidores: cPanel cPanel es uno de los programas de pago mas famosos que hay, está presente en la mayoría de hostings de todo el planeta y sin duda tiene una gran potencia. Sus principales características son: Muy enfocado al mundo hosting (incluso a la venta). Totalmente enfocado a la creación de webs. De los más completos para hostins. Está programado en PHP y Perl. Es modular, puedes añadir módulos o crear el tuyo propio. Sin duda, si lo que buscamos es un software para montar un hosting, cPanel es una de las soluciones más famosas. No obstante, tiene dos desventajas, la primera es que al ser tan grande, es necesario muchos recursos, por ejemplo, ellos recomiendan 1GB de Ram y 40GB de HDD, cuando muchos VPS tienen unicamente 10GB de HDD. Por otra parte, está el precio, cierto es que es famoso y potente, pero las licencias pueden costarnos más que el servidor si unicamente lo vamos a utilizar para uso personal. Gestor de servidores: DirectAdmin Sin duda uno mis programas de pago preferido es DirectAdmin. Está también muy enfocado al mundo web (creación de cuentas, etc.), veamos sus características: Escrito unicamente en PHP. Es muy rápido, no requiere de muchos recursos. No se ejecuta en oculto (cuando no estas haciendo nada). Es extremadamente fácil y sencillo de utilizar. La licencia te permite tener dominios ilimitados. De todos los utilizados, tengo que reconocer que DirectAdmin es muy poco potente y en ocasiones puede que acabes instalando otro para las opciones que DirectAdmin no tenga. No obstante, aunque está muy enfocado a la web y poco al servidor, hay que reconocer que es tan sencillo que a diferencia del cPanel, no te puede dar errores, se centra en una cosa (creación de cuentas, webs, base de datos, FTP, etc.) y lo hace más que bien, por lo que, si no buscas tener un gran control de tu VPS y quieres enfocarlo más a la web de una manera simple, este software puede ser perfecto para ti. Por otra parte, a diferencia del cPanel, todas las licencias de webmin incluyen dominios ilimitados, es decir, que podrás añadir 1000 páginas web a tu servidor sin problemas de licencia. Gestor de servidores: Webmin Sin duda es mi preferido (y el que más utilizo), es totalmente gratuito y es por mucho, el más potente de todos. Eso sí, webmin no está enfocado al mundo web aunque te permitirá crear tantas webs como quieras. Para empezar, veamos sus ventajas: Es uno de los más potentes (miles de posibilidades). Te permite gestionar todo tu VPS, cada parte, cada opción. Liviano, es muy rápido. Te avis si hay actualizaciones de cualquier programa instalado. Es modular, puedes instalar o crear tus propios programas. Casi no tiene capa de abstracción. Cuando haces un click se ejecuta directamente en la terminal. Es totalmente gratuito. Y ahora veamos algunas de sus desventajas: Es poco intuitivo y tiene una interfaz muy de los años 90. Puede ser muy técnico para algunas personas. En definitiva, el webmin es uno de esos programas que los amas, o los odias, pero que no te dejan indiferente. Gestor de servidores: VirtualMin Virtualmin es gratuito, pero en si mismo no es un programa, sino un módulo enorme para webmin, este módulo está muy pensado para gestionar páginas web y te da las principales opciones que tienes con cPanel o DirectAdmin. Veamos algunas de sus características: Basado para el mundo web. Totalmente gratuito. Al instalarlo se te instala todo lo necesario (te ahorras problemas). Muy intuitivo. Quizás, dependiendo la RAM, un poco lento. Este módulo es genial si queremos algo más sencillo para administrar nuestras web que el panel webmin. La entrada 055. Software para administrar servidores aparece primero en Luis Peris.

Hosting Webempresa para WordPress  En el podcast Emprendedores Digitales entrevisto a Gerard Martínez, responsable de marketing de la empresa de hosting Webempresa, que nos hablará de todo lo que necesitamos saber a la hora de escoger un buen Hosting para nuestro WordPress. Sabemos que un alojamiento para nuestra página web o blog es fundamental si queremos ir en serio en nuestro proyecto en internet, pero a veces se nos pasa por alto la seguridad en WordPress, un tema que trataremos en profundidad para tener nuestra web/blog lo más segura posible. El mejor Hosting para WordPress Webempresa es una de las empresas de Hosting español que se toman en serio y con mucha profesionalidad su trabajo. En mi opinión es una elección acertada y uno de los mejores sino el mejor hosting para WordPress. Webempresa además es especialista en Joomla! y PrestaShop, pero hoy en día lo más demandado es el alojamiento en WordPress. Esta misma página web donde lees este artículo está alojada en sus servidores, con eso te lo digo todo. Cada día hacen mejoras en seguridad y aportan nuevos servicios gratuitos al cliente, como pueden ser:  Optimizador de imágenes: Si lo solicitas te bajan el peso de las imágenes sin pérdida de calidad, con lo que optimizas el espacio en disco y mejoras a la vez el SEO.  WP Doctor: Una herramienta muy buena para chequear tu web, WP Doctor te dará una valoración y te dirá los puntos que debes de corregir para aumentar tu seguridad en WordPress. Stephan: Es un auditor virtual que revisará tu web automáticamente y entre muchas cosas más te protegerá de intentos de sesión no autorizados y te dirá también las mejoras a implementar en tu sitio web. Pero me estoy enrollando demasiado y lo interesante es que lo escuches tú mismo en el podcast y verás todo lo que te puede aportar un buen Hosting para WordPress. Si estás interesado en la contratación del hosting en Webempresa tendrás un descuento del 20% con el cupón "GRACIAS20", sin comillas, y además tienes el nombre de dominio el primer año de forma gratuita. Si necesitas ayuda para darte de alta aquí te dejo un videotutorial de cómo tienes que hacerlo. Temas tratados en el podcast ¿Quién es Gerard Martínez y la empresa de hosting Webempresa? Cuando utilizar blogs con alojamientos gratuitos como WordPress.com o blogger.com ¿Qué problemas nos podemos encontrar si decidimos migrar de un hosting gratuito a un hosting propio? ¿Por debajo de qué precio mensual en un hosting compartido deberíamos de dudar de la calidad? ¿Cuánto cuesta un hosting compartido en Webempresa para los que comienzan y qué incluye? En servicios con espacio ilimitado y ancho de banda ilimitada ¿Con qué problemas te puedes encontrar cuando aumente tu tráfico web? ¿Cuáles serían los puntos más interesantes a tener en cuenta en la elección de un buen hosting? ¿Cómo funciona vuestro sistema de copias de seguridad por si ocurre alguna desgracia a alguno de vuestros clientes? ¿Qué reglas de seguridad utiliza el Hosting Webempresa para mantener protegidas de ataques en internet las páginas de los clientes? ¿Qué medidas tenemos que utilizar nosotros mismos para protegernos de ataques? ¿Cómo funciona Stephan y en que nos puede ayudar en nuestro alojamiento? La importancia de analizar nuestra web con WP Doctor, herramienta de chequeo para mejorar nuestra seguridad en WordPress. Han salido unas nuevas vulnerabilidades graves en cPanel. ¿Que protección tenemos? ¿Cuáles son los mejores plugins para WordPress de seguridad actualmente? ¿Es recomendable un plugin de caché para acelerar la carga de la página web? ¿Cuál es el mejor hoy día? Si ya tienes un blog y lo quieres trasladar al hosting de Webempresa, ¿vosotros ofrecéis este servicio? ¿Cuáles son los proyectos próximos de Webempresa?  

Your website hosting company’s cPanel is a powerful tool. Learn how I use the cPanel to make developing websites a breeze.