Podcasts about Google Reader

Ed Zitron joins us fresh from CES to talk about how Ai is bullshit and who killed Google Reader.

It's Halloween this week, and we've got an appropriately spooky episode for you. We're looking back at a random selection of some of our favourite dead and/or zombified companies, platforms and products of the past couple of decades. From instant delivery and Google Reader to Adobe Flash and the Microsoft Zune, prepare to be utterly terrified by these terrifying spirits from tech's past.See omnystudio.com/listener for privacy information.

【本期嘉宾】阑夕、张宁、王俊煜阑夕（知名IT人）张宁（Platform Thinking 主理人、前知乎COO）王俊煜（「阅览室」创始人、豌豆荚和轻芒创始人）主播：潘乱（「乱翻书」主理人）【时间线】01:02 2024年了，为什么还在使用这么“原始”的RSS阅读？03:54 为什么不继续写独立博客了？05:39 豆瓣九点【图】豆瓣的RSS阅读工具：九点（已于2015年12月10日永久关闭）07:27「订阅如山倒，阅读如抽丝。」未读：999+【图】Google reader界面08:54 为什么会去做Newsletter？11:48 「RSS跟Newsletter刚好走向了两个极端」15:52 Newsletter的冷分发机制16:41 八卦一则：「天下文章一大抄」，“美国版”公众号——Substack【图】Substack的联合创始人Chris Best，也是通讯软件Kik Messenger的联合创始人【图】Kik Messenger的早期界面截图，和微信风格极其相似18:59 目前只有一款阅读器能抓取微信公众号文章——微信读书20:39「早期的即刻，也是RSS技术的应用场景。」22:37 文章推荐《RSS二十年》（作者：kyth ）【图】即刻 1.0 与 2.023:30「RSS碰到Twitter的那一天，此消彼长开始了！」24:19 FriendFeed【图】FriendFeed界面（已于2015年4月9日正式关闭）25:17 Google reader 关停时的产品数据【图】2013年7月1日，Google reader 正式关闭25:33 「我每天往网吧跑，就是为了把Google Reader的未读都点掉。」26:27 「800万个RSS源，但其中2/3的RSS源只有1个订阅者！」28:35 文章推荐《RSS不死，只是凋零——感谢拥有Google Reader的岁月》（By：阑夕）29:50 Google Reader关闭后，张一鸣和张小龙对此的看法：《为佩奇关闭Google Reader的魄力叫好！》（By：张一鸣）《微信背后的产品观》（By：张小龙）30:56「订阅模式对用户要求太高！」31:48 一码难求的Follow，未来可期！33:30 「我希望有一个独立的阅读空间能够留给我自己。」36:53 RSS3不是RSS×Web3，而是RSS 3.039:12 散是满天星的Google+40:52 「我对Google reader中文版有一点点微小的贡献」41:20 Google reader团队，一开始并不想做阅读器。44:19 平台需要解决的问题：内容的来源、分发和目的地49:35 「微信是一个 push中心！」50:11 创作者激励这件事53:20 《资本化信息分发》（By：Joshua）55:00 「RSS短短几年里完成了从先进到“反动”的角色转变！」58:21 「虽然说大家可能很讨厌资本，但资本还是很有用处的！」59:52 产权与效率65:03 AI产品出现，应该被界定在哪个环节？77:17 「谷歌关掉那么多产品，被舆论攻击最猛的就是Google reader！」78:48 「播客（Podcast）在RSS的废墟上繁荣起来了！」81:10 《为什么一说中文播客，你就能联想到小宇宙？》（By：Enzo）82:38 RSS对于播客创作者来说，可以降低分发成本。85:49 内容创作、分发、消费大一统的平台，会留下缝隙和缺口吗？88:31 「RSS产品的消亡是一种必然！」89:18 未读的焦虑——「万物皆可折叠」，包括微信服务号。92:29 去多巴胺阅读，未来预期会是怎么样？93:45 RSS+播客/博客，创作者更喜欢这样自由的创作方式98:08 「深度阅读在今天是小众群体」98:28 「图文的繁荣，其实是德不配位的一段历史。」101:13 内容创作者试着从平台手里夺回主权，是这样吗？【开场&结尾音乐】开场音乐：李小龙 - 好久不见（电视剧《武林外传》片头曲）结尾音乐：虞霞/李小龙 - 侠客行（电视剧《武林外传》片尾曲TV Verison）【相关推荐】1、阑夕对本次直播的总结（全文约5千字，原文见链接）：2、《RSS二十年》｜kyth3、《Whokilled Google Reader?》｜David Pierce4、《聊聊RSS这个「古董」》｜乱槽之巅5、《资本化信息分发（Capitalizing InformationDistribution）》｜Joshua6、《RSS不死，只是凋零——感谢拥有GoogleReader的岁月》｜阑夕【图】Google Reader 关闭十周年纪念文章插图（Illustration by Hugo Herrera for TheVerge）【关于「乱翻书」】「乱翻书」是一档关注商业、科技和互联网的圆桌对话节目。关心How和Why，以及少有人注意到的What。内容主要方向是科技考古、行业观察和前沿思考，研究公司的兴衰循环，希望能够为你带来信息增量。「乱翻书」主理人是潘乱，代表作品有《腾讯没有梦想》、字节跳动/快手早期关键节点的系列特写。【关于主播】即刻/视频号/B站/抖音：潘乱公众号/播客：乱翻书【图】直播截图微信公众号：乱翻书视频号：潘乱商业合作：联系微信 tongxing717本期编辑：怀杭

Thu, 12 Sep 2024 12:45:00 GMT http://relay.fm/tc/116 http://relay.fm/tc/116 Dan Provost, Tom Gerhardt, and Myke Hurley Today's guest is Jason Shellen, an entrepreneur and the founding product manager of Google Reader. His object is the Patagonia Refugio 28L backpack. Today's guest is Jason Shellen, an entrepreneur and the founding product manager of Google Reader. His object is the Patagonia Refugio 28L backpack. clean 3612 Today's guest is Jason Shellen, an entrepreneur and the founding product manager of Google Reader. His object is the Patagonia Refugio 28L backpack. Guest Starring: Jason Shellen Links and Show Notes: On The Last Detail, Tom and Dan invite a guest on to chat about an object that is meaningful to them. They dive deep into that object, discussing the design, the manufacturing process, the good, and bad, and everything in-between. Support Thoroughly Considered with a Relay FM Membership Patagonia Refugio 28 Daypack | REI Co-op Patagonia Refugio 28L Pack | REI Co-op Patagonia Refugio Daypack Video - YouTube Patagonia Refugio Pack 28L - YouTube THE BROWN BUFFALO® – The Brown Buffalo Timbuk2 Bags: Backpacks, Messenger Bags, Custom Bags

Thu, 12 Sep 2024 12:45:00 GMT http://relay.fm/tc/116 http://relay.fm/tc/116 The Last Detail with Jason Shellen 116 Dan Provost, Tom Gerhardt, and Myke Hurley Today's guest is Jason Shellen, an entrepreneur and the founding product manager of Google Reader. His object is the Patagonia Refugio 28L backpack. Today's guest is Jason Shellen, an entrepreneur and the founding product manager of Google Reader. His object is the Patagonia Refugio 28L backpack. clean 3612 Today's guest is Jason Shellen, an entrepreneur and the founding product manager of Google Reader. His object is the Patagonia Refugio 28L backpack. Guest Starring: Jason Shellen Links and Show Notes: On The Last Detail, Tom and Dan invite a guest on to chat about an object that is meaningful to them. They dive deep into that object, discussing the design, the manufacturing process, the good, and bad, and everything in-between. Support Thoroughly Considered with a Relay FM Membership Patagonia Refugio 28 Daypack | REI Co-op Patagonia Refugio 28L Pack | REI Co-op Patagonia Refugio Daypack Video - YouTube Patagonia Refugio Pack 28L - YouTube THE BROWN BUFFALO® – The Brown Buffalo Timbuk2 Bags: Backpacks, Messenger Bags, Custom Bags

Anchor, Plágio de Palworld, advogado Kirby, clássico King Kong vs. Donkey Kong, Fifa 14, Pokémon Company, Voltaire, viúvo do Google Reader, o fim do Dois Analógicos, Spotify, banho de loja da Rare, Nintendo surrupiando, videogames são arte?, Umurangi Generation, RSS do podcast, são alguns dos assuntos da conversa infinita de videogame de Marcos Kyioto, João R, João Varella, Thomas Kehl e Alexandre Sato. --- Send in a voice message: https://podcasters.spotify.com/pod/show/2analogicos/message

Pablos: People are pissed off about social media all the time. They think that Facebook is making people vote for the wrong person. It's still very difficult to find somebody who thinks they voted for the wrong person because of Facebook, but they think everyone else did. Never mind that, there's this kind of, uh, very popular sensibility, which is to blame Facebook for all the problems in the world. They're doing fake news, they're doing, disinformation they're doing , every possible thing that could be wrong. Everybody wants to blame Facebook for getting wrong or Twitter or, any of the other social platforms. So if you think about it, in one sense, , yeah, Facebook got everybody together. I'm just going to use them as the example, we can extrapolate. They got everybody together. They, ended up getting too much content. you and your friends are posting too much shit. Nobody has time to see all of it. So you need the magical algorithm, which you should do like triple air quotes every time I say algorithm. They're like, the algorithm is supposed to figure out, okay, of all the shit that's supposed to be showing up on your feed, what's the coolest, or what's the stuff that you're gonna like the most? That's the job of the algorithm. And of course, we all believe the algorithm is tainted. And so, it's not really trying to find the things I care about the most or like the most. It's just gonna find the things that piss me off the most so that I get my, outrage, dopamine hit and keep coming back. So, which may all be true. We don't know. But, the point is, there's a fundamental problem, which is you cannot see everything that gets posted from all the people you follow. So, there does have to be some ranking. And then the second, thing is that you want that ranking to be tuned for you. And I think the thing that people, are missing about this is that you've got to have, a situation where it is very personalized because, not everybody's the same. Even if you and I followed the same thousand people, it doesn't mean we have identical interests. There are other factors that need to play into determining like what I want to see and what you want to see. And then I think that there's a whole bunch of things that, are classified as societal evils, that Facebook has to decide are not okay for anybody to follow. So if you have posts about Hitler, nobody should get to see those. Even if you're a World War II historian, nope, you don't get to see it. So there's a kind of, problem here, which is that all of this flies in the face of actual diversity, actual multiculturalism, we have 190 countries in the world. We have a lot of different peoples, different cultures, you and I just had a huge conversation about, different cultures and how they drive, we don't agree about these things. We have different ideas in different places in the world, even whole societies have different ideas about what's okay, and what's not okay, and that is the definition of Culture that is the definition of multiculturalism is valuing that that exists and letting everybody have their own ideas And and make let these different people operate in the way that suits them And when you travel, you get beaten over the head with that because, I can appreciate that people drive like this in Bangkok. That's not how I want to do it , that's kind of the fundamental point here. So anyway, what I'm trying to get at is you cannot create one set of rules for the entire world. That is not okay. Ash: 100% Pablos: And so what Facebook has chosen to do is try to create one set of rules for the entire world, at least the two billion people that are on Facebook. Ash: But then you become the government of Facebook. Pablos: You become the government of Facebook. And it's and we're all pissed off because they keep choosing rules that some people don't like or whatever. And so I think this is untenable and I don't think there's a solution there. I think it is a fool's errand and what I believe is, has gone wrong is that Facebook made the wrong choice long ago and they chose to control the knobs and dials and now they're living with the flack that comes with, every choice they make about where to set those knobs and dials. And what they should have done is given the user the knobs and dials. They should let me have buried six pages deep in the settings, have control over. What do you want more of? What do you want less of? Ash: More or less rant. Pablos: Yeah, They try to placate you with the like button and unfollow and all that, but it's not really control. So, contrast that with, the other fork in history that we didn't take, go back to like 2006, in the years before Facebook, We had this beautiful moment on the internet, with RSS. So RSS, which stands for Really Simple Syndication, that hardly matters, RSS was an open standard that allowed any website to publish the content in the form of posts in a kind of machine readable way. And then you could have an RSS reader that could subscribe to any website. So we didn't have the walled garden of Facebook, but, you remember all this, of course, but I'm just trying to break it down here. What we had was, this kind of open standard. , anybody in the world could publish on RSS using their website, all the blog software did this out of the box. WordPress does it out of the box. In fact, most websites, would support RSS. And then you had a reader app, that could be any reader app. This is again, open standards so get any reader you want. And if you just subscribe to any website in the world, you are following them directly. When they publish a post, it show up in your feed. And when you followed too many people, you could start making filters. So I've been making filters. I still do RSS. So by the way, all this machinery still works 15 years later. The machinery still works almost any website if you just put /RSS or / feed on the domain name you'll see an RSS feed and you can subscribe to that so it goes into my reader app And then I've been building filters over the years. So I have filters like -Trump because I got sick and tired of all this bullshit about Trump regardless what you think about Trump I just wanted to think about other things and it was painful to have a feed filled with Trump during the election So I have also -Biden, I have -Kanye, I have -Disney, I have minus all kinds of shit that I don't want to see, I still follow the publishers, but it's weeding out articles that are about those things. And so I get this feed that's pretty curated for me and my interests, and I get more of the stuff I like and less of the stuff I don't like, but I'm responsible for the knobs and dials, I'm controlling the settings, and I get to have my own autonomy about what I think is cool and not cool. And if I don't want Hitler, I can easily just -Hitler. And what we did instead is we kind of signed up for this sort of, babysitter culture of having Facebook make those choices for us. And people not, taking responsibility for their own choices has put us in this situation where we just have an internet full of people want to blame somebody else for everything that they think is going wrong. What we need to do is, figure out a way to, shift the world back to RSS. And out of the walled garden. So that's my, that's where I'm at, and I have ideas about that. Ash: And it's interesting, go back to Delphi, So Delphi internet... Pablos: One of the first, before, before internet, this was like an ISP, like a, like AOL. Centralized ISP. Ash: Right. So, so Delphi was sold to Murdoch, to News Corp and, and then the founder, Dan Burns brought that back. He purchased it, he re acquired the company and then invited a couple of ragtag individuals, myself and, and Palle again, and Rusty Williams. Chip Matthes, and we had like, you know, a room with a VAX in the back. I was doing a lot of the stuff, but we were running forums. Dan had this crazy idea. It was like, Hey, what if you could just make your own forum? And this would be like way pre Facebook, it's like 97, 98. And 98, we started supplying that ability to websites. And the first one we did was a guy named Gil . And like we said to him, it's like, Hey Gil, like you guys really should have some forums, like, yeah, we totally should be. Wait, so how do we do that? And we wrote like a little contract, right? like the first, I think, business development contract that you could probably make. He was head of, , business development, eBay. Right. So he did that. I mean, he's very well known sort of angel kind of lead syndicate guy. Now I like an angel is for like for, for ages. Pablos: Oh, Penchina. I know who you're talking about. Yeah. Ash: We still have like the first document, you will do this. I will do this. I will give you a forum. You will use it for people to talk about, I don't know, the, the, their beanie baby or whatever they were selling back then. And the, the reality was that that took off and then we started supplying this technology, which we then enabled, we RSS enabled it, by the way, of course, at some point, right. When it was, when the, when the XML feeds were like ready to go, we upgraded from XML And then we, we, we took that and we said, all right, let's go, let's go for it. And at some point we're doing 30 million a month, 30 million people a month. Unique. We're like on this thing and we never governed. You could, you could go hidden, right? Kind of like your locked Instagram page versus not, but we didn't govern anything. Forums had moderators, they were self appointed moderators of that domain of, of madness. So if you didn't like that person's moderation, You know, like, all right, screw this guy. You know, like, I don't, I don't want to listen to you. You're crazy. And what we found, and this was the piece of data that I think that was the wildest. Servers are expensive back then. You actually have to have servers. Or in our case we were beating everyone else. Cause we had a VAX that was locked in a, Halon secure room. No, because it came when we repurchased it for a dollar. Like the VAX was still there and Lachlan Murdoch's, office became our like conference room. No, I'm not kidding. It was, it was really crazy. There was a, it was just a VAX sitting there and, Hey, look, you could run UNIX on it. We were good. We didn't care. It loved threads and it was good. And it could do many, many, many, many threads. So we were running this, this thing highly efficiently. There's six people in a company doing that much. That was the company, literally six. I look today and how many people we hire and I'm like, there were six of us. It was wild, the iceberg effect took place. So what ended up happening is the percent, and this is where I think Facebook can't do or doesn't want to do, is how do you advertise below the waterline? And when we were sitting there with the traffic, we're like, dude, why is there so much traffic, but we can't see it, right? It looked like we only had 20, 000 forums or something, and there was like all this mad traffic going on. And. It was something like the 80, 20 rule the other way. It was like 20 percent was indexable that you could see that you could join a forum. And it was 80 percent were, were insane things like Misty's fun house. That by the way, is a legitimate. Forum at one point, right? It was Misty's fun house. So I'm just saying, cause we're trying to figure out what was going on. Where were the people chatting and talking? And that's what we did. We let them bury themselves deeper and deeper and deeper. Usenet did that. If you just go back in time, what do you think BBSs were? It's the same. Pablos: Exactly. Ash: We always love talking. Pablos: Yeah. People love talking. Ash: You just figure out which one you want to dial into. Pablos: Nobody's pissed off about who they're talking to really. Usually they're pissed off about who other people are talking. They're pissed off about some conversation they're not really a part of. Or a conversation they can be a spectator on, but doesn't match their culture. That's one of the big problems with Twitter it's like BBSs, and it's BBS culture. Elon was the winner of the Twitter game long before he bought Twitter, because, that's just BBS culture that he had in his mind, IRC or whatever. All kinds of people who are not part of that culture, are observing it and think that it's a horrible state, of society that people could be trolling each other and shit. And that's just part of the fun. You have this problem when you try to cram too many cultures into one place, it takes a lot of struggle to work that out if you're in, Jamaica, Queens, then you're gonna, you're gonna work it out over time, with a lot of struggle, you're going to work it out and the cultures are going to learn to get along. But in, but on Twitter, there's no incentive. Ash: That's why we still have states. The EU still has, like, how many languages? That's why we have Jersey for New Yorkers. Pablos: The EU in their way has figured out how these cultures can get along. I think there's a real simple fix to this. The big death blow to RSS in some sense was that the winning reader app was Google Reader. And so the vast majority, of the world that was using RSS was using Google Reader. And then I don't totally have insight on how this happened, but, Google chose to shut down Google Reader. And I don't know if they were trying to steer people into their, Facebook knockoff products or whatever at the time. in a lot of ways I think what it did is it just handed the internet over to Facebook. Because anybody who was being satisfied by that, and just ended up getting, into their Facebook news feed instead. So it just kind of ran into a walled garden. I don't really blame Facebook for this, the way a lot of people want to. I blame the users. You've got to take some responsibility, make your own choice, choose something that's good for you, and most people are not willing to do that. But, I think to make it easier for them, and there is a case to be made that , people got better things to do than architect their own rSS reader process, but we could kind of do it for them. And so I think there's one, one big kingpin missing, which is you could make a reader app that would be like an iPhone app now. And you could think of it as like open source Instagram. It's just an Instagram knockoff, but instead of following, other people on a centralized platform by Instagram, it just follows RSS. And then it only picks up RSS posts that have at least one picture, right? So any RSS post that has one picture and then the first time you post it automatically makes a WordPress blog for you, that's free. And then, posts your shit as RSS compliant blog posts, but the reader experience is still just very Instagramesque. So now it's completely decentralized in the sense that like you own your blog, yeah, WordPress is hosting it, but that's all open source. You could download it, move it to Guam if you want, whatever you want to do. So now all publishers have their own direct feeds. All users are publishers, which is kind of the main thing that Facebook solved. Ash: Content is no longer handed over to someone, right? That's the other big thing. Pablos: Exactly. The content is yours and then your followers are yours, right? When they follow you, they follow you at your URL. And so you can take them with you wherever you go. And then to make this thing more compelling, you just add a few tabs. You add the Twitteresque tab. You add the TikTokesque tab for videos. And, add, the podcast tab. So now, posts are just automatically sorted into the tab for the format that matches them. Because people have different modalities for, for consuming this shit. So, depending on what you're in the mood for, you might want to just look at pictures because you're on a conference call. Fine. Instagram. Or, you know, you might want to watch videos because you're on a flight. Who knows? So, the point being, all of this is easy to do. You and I could build that in a weekend. And then the reason that this works, the reason this will win is because you can win over the creators, right? Because the sales pitch to a creator, and those are the people who drive the following anyway, you see TikTok and everybody else kissing the ass of creators because that's who attracts the following. The creators win because they're not giving anything up to the platform. Because they make money off advertising. So fine. We make an advertising business and we still, take some cut of what the creators push out. But if they don't like us, there's a market for that, right? The market is I'm just pushing ads out along with my content to my followers. Some of them watch the ads. Some of them don't. I have this much of an impact. And so now you get the platforms out of the way. Ash: If you do it right, Google has ad networks that they drop everywhere. Pablos: Everybody has ad networks already for websites. You could just use that. Amazon has one. So you can sign up for that if you want. Or the thing that creators want to do, which is go do collabs, go do direct deals with brands. Now you're getting 100 percent of that income. You pump it out to your fans. And there's no ad network in the middle. Nobody's taking a cut. Alright, if you could cut your own deals, then great, but you're in control and you can't be shadow banned, you can't be deprioritized in the feed, because that's the game that's happening. These platforms, they figure out you're selling something, you immediately get deprioritized. And so the creators are all pissed off anyway. So I think we can win them over easily enough. And then the last piece of it is, there's one thing that doesn't exist, which is you still need to prioritize your feed. You still need an advanced algorithm to do it. You don't want to be twiddling knobs and dials all day. You might put in -Hitler if you want. But what should happen is you should also be able to subscribe to feed ranking services. So that could be, the ACLU, or the EFF, or the KKK, whoever you think should be ranking your feed. Ash: Well, I was actually thinking you could subscribe to a persona. So people could create their own recipes. So this is the world according to Ash, right? Here you go. Like, I've got my own thing. I've done my dials, my tuning, my tweaks, my stuff. And you want to see how I see the world. Here we go. The class I teach, that's the first day I tell people, take Google news and sit down and start tuning it. And everyone's like, well, let me just start to just add, put ups and downs, ups and downs, add Al Jazeera, do whatever you want. Just do everything that you want, just make them fight and put all of that in and then go down the rabbit hole. But there's no way to export that. When we start class, I always talk about viewpoints And how all content needs a filter because we are filter. But if I want to watch the world as Pablos, I can't, there's no, you can't give me your lens. So if we look at the lens concept, today you can tune Google News, there is a little subscribe capability, but you could tune it and poke it a little bit, and it will start giving you info. It's not the same, quite the same as RSS, but it's giving you all the news feeds from different places, right? Could get Breitbart, you could get, Al Jazeera, you could get all the stuff that you want. And if you go back in time to, to when I was working with the government, that was actually my sort of superpower, writing these little filters and getting, Afghani conversations in real time translated. And then find the same village, in the same way. So then I would have two viewpoints at the same time. The good thing was that when you did that what I haven't seen, and I would love, love this take place, is for someone to build a, Pablos filter,? And I could be like, "all right, let me, let me go see the world the way he sees it." his -Hitler, his minus, minus, -election, - Trump, -Biden, that's fine. And then, and now I have a little Pablos recipe. I can like click my glasses, and then, then suddenly I see the world, meaning I filter the world through Pablos's. Pablos: Yeah, I think that, I think we're saying a similar thing because then what you could do is you could, subscribe to that. You could subscribe to the Pablos filter. You could subscribe to the... Ash: exactly, I'm taking your ACLU thing one step further. I think ACLU is like narrow, but you could go into like personality. Pablos: You could even just reverse engineer the filter by watching what I read. My reader could figure out my filter by seeing the choices that I make. Ash: Yeah, if it's stored it right, if we had another format, but let's just say that we had an RSS feed filter format. 'cause it's there. It's really the parameters of your RSS anyway. But if you could somehow save that, config file, go back thousand years, right? If you could save the config.ini, that's what you want? And I could be like, Hey, Pablo, so I can hand that over. Let's share that with me. And now what's interesting is works really well. And it also helps because each person owning their own content, the, the beauty of that becomes, you never, you never filtered, you never blocked you, you, you're self filtering. Pablos: That's right. Ash: We're self subscribing to each other's filters. Pablos: Publishers become the masters of their domain. If you've got a problem with a publisher, you've got to go talk to them, not some intermediary. The problem is on a large scale, control is being exercised by these intermediaries. And they have their own ideas and agendas and things. The job here is to disintermediate - which was the whole point of the internet in the first place - communication between people. Ash: Then the metadata of that becomes pretty cool, by the way. If I figured out that, okay, now it looks like 85 percent of the population has, has gone -Biden, -Trump. Let's think about that. Suddenly you've got other info, right? Suddenly you're like, Oh, wait a minute. and if you're an advertiser or you're a product creator, or you're a, like just sitting there trying to figure out how can I get into the world, that becomes really valuable, right? Because you could. Go in and say, people just don't give a shit about this stuff, guys. I don't know what you're talking about. Whereas when you have one algorithmic machine somewhere in Meta/Facebook, whatever we want to call it, pushing things up, it could be pushing sand uphill, right? It could be like stimulating things that you don't necessarily know you want. The structure that you just described flips that on its head because it says, Hey, I just don't want to listen to this shit, guys. Like, I just could not give a crap about what you're saying. Pablos: Right. Ash: And if enough people happen to do that, then the content creators also have some, some idea of what's going on. We try to decode lenses all day long,? We spend our life, like you said, in meetings or in collaborations or business development. What do you think we do? We sit there, we're trying to figure out the other person's view. We're trying to understand if you're a salesperson, "Hey, can I walk a mile in that guy's shoes" or speak like that person, I've never heard of anyone sort of selling me, lending me, letting me borrow their RSS, like, their filter. That would be phenomenal, that'd be great. And I bet you, if you did it right, you might even solve a lot of problems in the world because then you could see what they see, you know, I don't want to touch the topics that we know are just absolute powder kegs, but every time we get to these topics, I always tell the person, can you show me what you, what are you reading? Pablos: Yeah. Ash: Like, where did you get? Pablos: Yeah. Ash: You ever, you ever asked someone like, "where did you get that?" and then they show you, they show you kind of their, feed. And you're just like, what is going on? Like, if you, if you go to someone, whether they're pro or anti vax, it doesn't matter where it is. And just look at their feed, look at what they're listening to, because it's not the same thing I'm listening to, because the mothership has, has decreed which, which one we each get. But you look at it and then you're like, okay, maybe the facts that they were presented with were either incomplete and maybe not maliciously? I get it in the beginning of this, you started like, okay, is it malicious and didn't do it would get changed. But if you just cut out, I don't know, let's just say there's like 10 pieces of news, but I only give you five and I give the other person the other five. And they're not synchronous, you're going to start a fight. There's no question. What we don't have is the ability to say, Hey, like, let me, let me be Pablos for a second before I start screaming, let me see what he sees. that will probably change that could change a lot. Pablos: Think it could. That and certainly there's a cognitive bias that feels comfortable in an echo chamber. This is one of the issues that we're really experiencing is that, the process of civilization, literally means "to become civil" to do that. It's sort of the long history of humans figuring out how to control obsolete biological instincts. We've been evolved to want to steal each other's food and girlfriends. That's not specifically valuable or relevant at this point. We've had to learn how to get along with more people, we've had to learn to become less violent, we've had to learn to, play the long game socially, those things. And, there's work to do on that as far as like how we consume all this, this information, all the media. You're using the wrong part of your brain to tune your feed right now. You're using the lazy Netflix part of your brain to tune your news, and that's not really , how are you going to get good results. There's work to do to evolve the tools and work to do to evolve the sensibilities around these things. And so, you know, what I'm suggesting is like, we're not going to get there by handing it over to the big wall garden. You got to get there through this, again, sort of. Darwinian process of trying a lot of things and so you've described some really cool things that we'd want to be able to try that are impractical to try because things are architected wrong and using Facebook is the central switchboard of these conversations or Twitter or whatever and so you know what we need is a more open platform where like you know we can all take a stab at figuring out how to design cool filters that express our point of view and share them. And that's not possible in the current architecture. I think the last thing is, there are certainly other frustrations and attempts to go solve some class of these, some subset of these problems. You've got Mastodon, of course, and the Fediverse, and you've got Blue Sky trying in their way to make a sort of open Twitter thing. And then you've got, these other attempts, but a lot of them are pretty heavy handed architecturally. As far as I can tell, most of them end up just being some suburb of people who are pissed off about one thing or another that they get its adoption, right? So, Mastodon is basically a place for people who are, backlashing against Twitter. As far as I can tell. Ash: Yeah, and we even worked on one, right? Called Ourglass. Pablos: I don't know that one. Ash: It was coming out and we actually did an entire session on it. I actually worked on some of the product thought design on, on how that works. , it was like, it's all on chain. Part of the, the thing that, we did was very similar to what you're talking about. You wanted the knobs and the controls, and you wanted people to rant in their space. I know it gets pretty dark when you say, okay, but what are they allowed to talk about in in the dark depths of that sort of internet and and I say, "well, they already talk about it, guys" Whether they get into a smoky back room or, there's somewhere else that if they don't say it, I feel we get more frustrated. Pablos: The fundamental difference here is between centralized services. That's certainly Facebook and Twitter, but it's also Delphi and AOL, versus open, decentralized protocols and the protocols in time win over the services like TCP/IP won over AOL, AOL was centralized service, TCP/IP, decentralized protocol. At the beginning it was a worse user experience, harder to use, but It's egalitarian and it won and I think that that's kind of the moment we're in right now with with the social media. We're still on centralized service mode and it needs to be architected as decentralized protocol and we had a chance to do that before Facebook and we lost and so now there's just like the next battle is like how do we get back on the track of decentralized protocol, and I think if we just define them... That's why I think RSS won because it's called Really Simple Syndication for a reason. Because it's really simple. It was easy for any developer to integrate. Everybody could do it. And so it just became ubiquitous almost overnight. You could design something cooler with the blockchain and whatnot. But it's probably over engineered for the job. And the job right now is just like, get adoption. Ash: We started going down that path. So Delphi's sort of twin. Was, called Prospero. So Prospero was, little Tempest reference, was designed. As a way that you could just adopt it. That was that, that first eBay deal. And then we did about.com and most of the stuff. And right now you see Discuss. It's at the bottom of, of some comments. It's a supported service where, you had one party taking care of all of the threads and handles and display methods and posts and logins. And, you were seamlessly logged into the other sites. MD5 sort of hash and we did the first single sign on type nonsense, and we used to build gateways between the two, you're going to go from one to another, but the whole idea was that you provide, the communication tool, As a, as an open or available service. And you could charge for for storing it. And then what happens is you don't do the moderation as a tool. That's your problem. You strip it back to "look, I'm going to provide you the car and I don't care how you drive it." Go back to our story, whether you're in Vietnam or Riyadh or whatever you're doing, we're going to, we're not there to tell you which lane to go into, but that's, that's your problem. I think that one of the challenges with like RSS, cause we were RSS compliant, by the way. I'm pretty sure Prospero and I'm sure it's still around because it went XML to RSS. And I remember the fact that you could subscribe to any forum that was Prospero powered. You could subscribe to it a lot, like directly through your RSS reader. And I remember what was great about it is that people were like, "we don't want, your viewer." Just like we didn't want your AOL view of like, "you've got mail." I want my own POP server and then IMAP or whatever it is. I think there does need to be, like you said, someone putting together a little toolkit that's super easy. They don't need to know it's got RSS. They don't need to know anything. But it's like, "own your post." it can be like an Own Your Post service. And then the Own Your Post service happens to publish RSS and everything else, and it's compliant. Pablos: I think you just make an iPhone app and when you set up the app it just automatically makes you a WordPress blog and if you want you can go move it later. Ash: You got it. All that other stuff is just automated. Pablos: You don't even have to know it's WordPress. It's behind the scenes. Ash: If you were going to do this, what you would do is you'd launch and I would launch it like three different companies. Like three different tools. I've got a, "keep your content" tool and the keep your content guys are something compliant, RSS. You keep bringing it back. It's published, it's out there and then some new company, Meta Two, Son of Meta, creates a reader. Anyone that's got a RSS tag on it, we're a reader for it. So anyone using Keep Your Content or, whatever. the idea being that now you're showing that there's some adoption. You almost don't have to rig it. There is a way to do this because no one wants to download a reader if there aren't sources. Pablos: The thing can bootstrap off of existing sources because there's so much RSS compliant content. You could imagine like day one. If you downloaded this reader today. You could follow Wall Street Journal and just everything online. And some of it you have to charge for it. Like Substack has RSS. I follow Substacks. You could just follow those things in the app Substack has a reader, but it only does Substacks, and probably Medium has one that only does Medium. But we have one that does both, plus New York Times and everything else. So now, like any other thing, you just follow a bunch of stuff. And then, there's a button that's like post. Sure, post. Boom. Now that fires up your own WordPress blog. Now you're posting. All your content's being saved. You control it. You got some followers or if you have this many followers, here's how much you can make in ad revenue. Boom, sign up for ad network. Now you're pushing ads out. All This could be done with existing stuff, just glued together, I think, and with the possible exception of the filter thing, which, needs to be more advanced probably worth revisiting. Ash: I think what You could do is maybe the very first thing you do, create the filter company, like your RSS glasses. So instead of having to do that heavy lift, curate Pablos's, I would love to get your RSS feed list. How do you give it to me? How could you give me your RSS configured viewer? Pablos: A lot of RSS readers make it really easy to like republish your own feed. So like all the things I subscribe to, then go into feed... Ash: But then, that's blended, right? Pablos: Oh, it's blended. Yeah, for sure. Ash: Is blended, right? So now it becomes your feed. I'm saying, can I get your configuration? Pablos: I don't know if there's a standard for that. Ash: I'm saying that's maybe the thing you create a meta, Meta. Pablos: Honestly, I think these days what you would do is just have a process that looks at everything I read, feeds it into an LLM, and tries to figure out like how do you define what Pablos is interested in that way. You probably would get a lot more nuance. Ash: That's to find out what you're interested in. Pablos: It's almost like you want your feed filtered through my lens. Ash: That's exactly what I want. I want to read the same newspaper you're reading, so to speak. So if you assume that that feed that you get is a collection of stories. That's your newspaper, the Pablos newspaper, right? That's what it is, Times of Pablos and you have a collection of stories that land on your page, right? It's been edited. Like you're the editor, you're the editor in chief of your little newspaper. If you think of all your RSS feeds ripped down your, your own newspaper, I'd like to read that newspaper. How do I do that? That doesn't exist. I don't think that's easy to do. And if I can do that, that'd be great. Pablos: If you're looking on Twitter and people are reposting, if I go look at your Twitter feed and all you do is repost stuff and then occasionally make a snarky comment, that's kind of what I'm getting. I'm getting the all the stuff you thought was interesting enough to repost and I think that's a big part of like why reposting merits having a button in Twitter because that's the signal you're getting out of it. I don't love it because it's part of what I don't like about Twitter is I'm not seeing a lot of unique thought from the people I follow. I'm just seeing shit they repost. And so my Twitter feed is kind of this amalgamation of all the things that were reposted by all the people I follow and and to me, that's what I don't want. I would rather just see the original post by those people. Twitter doesn't let me do that, so I'm scrolling a lot just to get to the, first person content. I think it is a way of substantiating what you're saying, though, which is "There's a value in being able to see the world through someone else's eyes." Repost might just be kind of a budget version of that. Ash: The reason I say that it's valuable, it's like the old days you'd sit on train and maybe even today and you had a physical copy of the New York Times, and everyone, and you could see who reads the New York Times and who reads the Journal. Right. And who reads The Post and The Daily News, that's what you can tell. And those people had their lenses, you go to the UK and everyone, this is the guardian, the independent, whatever. And you were like, Oh, that's a time, Times reader. That's a Guardian reader or someone looking at page three of the sun. I have no idea what they're doing, but, you knew immediately where they were. Pablos: It's the editorial layer. Ash: You got it. Pablos: it's what's missing in today's context. What's missing now is you got publishers, and you got the readers. but the editor is gone. Ash: Well, it's not gone, that's the problem, right? So what we did is , in the, in the world of press, there was a printing press and an editorial group took stories and they shoved them through the printing press. And then, the next minute, another editorial group came in and ran it through the printing press. so if you went out , and you were making your sort of manifestos, the printing press probably didn't care, right? The guy at like quickie print or whatever it was didn't care. Today, Facebook claims it's the place to publish, but it's not. Because it's editorial and publish so that so what they're doing is they're taking your IP They're taking a content and then there's putting their editorial layer on it. Even if it's a light touch or heavy touch, whatever it is. But it's sort of like if the guy that was the printing press like "I don't really like your font." " Dude, that's how I designed it." I want the font. Like I like Minion, Minion Pro is my thing, right? That's what I'm going to do. But, but if they just decided to change it, you'd be really pissed off. Now, Facebook claims to be an agnostic platform, but they're not an ISP. They're not a, an open architecture. like we would have had in the past where like you host what you wanted to host. There, you host what you want to host, but they're going to down promote you. They're going to boost you. They're going to unboost you. So wait a minute, hold on a second. You're, you're not really an open platform. And I think that's what you're getting at, which is, either you're a tool to publish or you're the editorial, the minute you're both. You're an editorial. You're actually no longer a tool. Pablos: That's exactly right. I think, that's the key thing, we've got to separate those things. Ash: That's the element. And I think that that tells you a lot about why we get frustrated. If Twitter was just a fast way to shove 140 characters across multiple SMS, which we didn't have, because we're in the U.S. We were silly and we didn't have GSM. That's what Twitter was, right? Twitter was kind of like the first version of like a unified messaging platform. Cause it was like, you could broadcast 140 characters and it would work on the lowest common denominator, which was your StarTAC flip phone. So the point was that Twitter was a not unmoderated open tool. Then it got editorial. And now it's then it's no longer. And I think that's the problem, right? It used to be, you had a wall on Facebook and you did whatever the hell you wanted to. And then Facebook said I need to make money and it became the publisher, became the editorial board. Pablos: Okay, so we have a lightweight plan to save the internet. Let's see if we can find somebody to go build this stuff. Ash: If you could build that last thing, I think it's not a, it's not a complicated one, but they, I think they just need to sit down and, grab your feed. Or someone can come up with a collection of, Mixtapes, let's call it. Pablos: Yeah, cool. Mixtapes, I like that. Ash: Internet Mixtapes. There you go.

This week Mary and Nat talk about how the dystopia is not even being well executed, the golden age of RSS, cancel culture in comedy, and more. Follow us on Instagram: @nfstrongarm | @marygreenhahaha | @BlowingItPod This podcast was recorded in on the unceded territory of the Wolastoqiyik people and we should give them their land back. New Brunswick 2SLGBTQIA causes that need your support: AIDS New Brunswick Chroma NB Clinic 554 Imprint Youth steel.transplants qtfattiesnb Further reading/viewing: Anglophone East council votes to sue N.B. over school gender-identity policy (CBC) Opposition calls for reinstatement of rent cap as N.B. rents rose 9% over last year (Global) Meta ban has been rough, but Google ban would be worse, say small news outlets, analysts (CBC) There Is No One to Cheer for in the Clash Between Tech Titans and Canada's News Media (Jacobin) Who killed Google Reader? (The Verge) In stunning pre-dawn raids, Toronto police ‘terrorize' Palestine activists (The Breach) CTV reports on Gaza with anti-Palestinian double standard, data shows (The Breach) Ex-officer Derek Chauvin, convicted in George Floyd's killing, was stabbed in prison, AP source says (AP) Good Omens | Official Trailer | Amazon Original (YouTube) Fargo | Installment 5 Teaser - There's a New Cowboy in Town (Jon Hamm) | FX (YouTube) Matt Rife Wants You to Think He's Edgier Than He Actually Is (Rolling Stone) Kliph Nesteroff (Twitter) Episode 1278 - "Canceled Comedy" w/ Kliph Nesteroff and David Bianculli (WTF with Marc Maron) Mike Birbiglia: The Old Man & The Pool | Official Trailer | Netflix (YouTube) PETE HOLMES - I AM NOT FOR EVERYONE - NETFLIX COMEDY SPECIAL (YouTube) Bullseye with Jesse Thorn (Maximum Fun)

Los creadores originales de Instagran siguen mejorando su aplicación de noticias. Lo último que han implementado nos trae muchos recuerdos a Google Reader porque pretende generar una comunidad de información dentro de la app. Os lo cuento porque es muy interesante.

-- Finches Diversify in Decades, Opals Form in Months,  Man's Genetic Diversity in 200 Generations, C-14 Everywhere: Real Science Radio hosts Bob Enyart and Fred Williams present their classic program that led to the audience-favorites rsr.org/list-shows! See below and hear on today's radio program our list of Not So Old and Not So Slow Things! From opals forming in months to man's genetic diversity in 200 generations, and with carbon 14 everywhere it's not supposed to be (including in diamonds and dinosaur bones!), scientific observations fill the guys' most traditional list challenging those who claim that the earth is billions of years old. Many of these scientific finds demand a re-evaluation of supposed million and billion-year ages. * Finches Adapt in 17 Years, Not 2.3 Million: Charles Darwin's finches are claimed to have taken 2,300,000 years to diversify from an initial species blown onto the Galapagos Islands. Yet individuals from a single finch species on a U.S. Bird Reservation in the Pacific were introduced to a group of small islands 300 miles away and in at most 17 years, like Darwin's finches, they had diversified their beaks, related muscles, and behavior to fill various ecological niches. Hear about this also at rsr.org/spetner. * Opals Can Form in "A Few Months" And Don't Need 100,000 Years: A leading authority on opals, Allan W. Eckert, observed that, "scientific papers and textbooks have told that the process of opal formation requires tens of thousands of years, perhaps hundreds of thousands... Not true." A 2011 peer-reviewed paper in a geology journal from Australia, where almost all the world's opal is found, reported on the: "new timetable for opal formation involving weeks to a few months and not the hundreds of thousands of years envisaged by the conventional weathering model." (And apparently, per a 2019 report from Entomology Today, opals can even form around insects!) More knowledgeable scientists resist the uncritical, group-think insistence on false super-slow formation rates (as also for manganese nodules, gold veins, stone, petroleum, canyons and gullies, and even guts, all below). Regarding opals, Darwinian bias led geologists to long ignore possible quick action, as from microbes, as a possible explanation for these mineraloids. For both in nature and in the lab, opals form rapidly, not even in 10,000 years, but in weeks. See this also from creationists by a geologist, a paleobiochemist, and a nuclear chemist. * Finches Speciate in Two Generations vs Two Million Years for Darwin's Birds?  Darwin's finches on the Galapagos Islands are said to have diversified into 14 species over a period of two million years. But in 2017 the journal Science reported a newcomer to the Island which within two generations spawned a reproductively isolated new species. In another instance as documented by Lee Spetner, a hundred birds of the same finch species introduced to an island cluster a 1,000 kilometers from Galapagos diversified into species with the typical variations in beak sizes, etc. "If this diversification occurred in less than seventeen years," Dr. Spetner asks, "why did Darwin's Galapagos finches [as claimed by evolutionists] have to take two million years?" * Blue Eyes Originated Not So Long Ago: Not a million years ago, nor a hundred thousand years ago, but based on a peer-reviewed paper in Human Genetics, a press release at Science Daily reports that, "research shows that people with blue eyes have a single, common ancestor. A team at the University of Copenhagen have tracked down a genetic mutation which took place 6-10,000 years ago and is the cause of the eye colour of all blue-eyed humans alive on the planet today." * Adding the Entire Universe to our List of Not So Old Things? Based on March 2019 findings from Hubble, Nobel laureate Adam Riess of the Space Telescope Science Institute and his co-authors in the Astrophysical Journal estimate that the universe is about a billion years younger than previously thought! Then in September 2019 in the journal Science, the age dropped precipitiously to as low as 11.4 billion years! Of course, these measurements also further squeeze the canonical story of the big bang chronology with its many already existing problems including the insufficient time to "evolve" distant mature galaxies, galaxy clusters, superclusters, enormous black holes, filaments, bubbles, walls, and other superstructures. So, even though the latest estimates are still absurdly too old (Google: big bang predictions, and click on the #1 ranked article, or just go on over there to rsr.org/bb), regardless, we thought we'd plop the whole universe down on our List of Not So Old Things!   * After the Soft Tissue Discoveries, NOW Dino DNA: When a North Carolina State University paleontologist took the Tyrannosaurus Rex photos to the right of original biological material, that led to the 2016 discovery of dinosaur DNA, So far researchers have also recovered dinosaur blood vessels, collagen, osteocytes, hemoglobin, red blood cells, and various proteins. As of May 2018, twenty-six scientific journals, including Nature, Science, PNAS, PLoS One, Bone, and Journal of Vertebrate Paleontology, have confirmed the discovery of biomaterial fossils from many dinosaurs! Organisms including T. Rex, hadrosaur, titanosaur, triceratops, Lufengosaur, mosasaur, and Archaeopteryx, and many others dated, allegedly, even hundreds of millions of years old, have yielded their endogenous, still-soft biological material. See the web's most complete listing of 100+ journal papers (screenshot, left) announcing these discoveries at bflist.rsr.org and see it in layman's terms at rsr.org/soft. * Rapid Stalactites, Stalagmites, Etc.: A construction worker in 1954 left a lemonade bottle in one of Australia's famous Jenolan Caves. By 2011 it had been naturally transformed into a stalagmite (below, right). Increasing scientific knowledge is arguing for rapid cave formation (see below, Nat'l Park Service shrinks Carlsbad Caverns formation estimates from 260M years, to 10M, to 2M, to it "depends"). Likewise, examples are growing of rapid formations with typical chemical make-up (see bottle, left) of classic stalactites and stalagmites including:- in Nat'l Geo the Carlsbad Caverns stalagmite that rapidly covered a bat - the tunnel stalagmites at Tennessee's Raccoon Mountain - hundreds of stalactites beneath the Lincoln Memorial - those near Gladfelter Hall at Philadelphia's Temple University (send photos to Bob@rsr.org) - hundreds of stalactites at Australia's zinc mine at Mt. Isa.   - and those beneath Melbourne's Shrine of Remembrance. * Most Human Mutations Arose in 200 Generations: From Adam until Real Science Radio, in only 200 generations! The journal Nature reports The Recent Origin of Most Human Protein-coding Variants. As summarized by geneticist co-author Joshua Akey, "Most of the mutations that we found arose in the last 200 generations or so" (the same number previously published by biblical creationists). Another 2012 paper, in the American Journal of Physical Anthropology (Eugenie Scott's own field) on High mitochondrial mutation rates, shows that one mitochondrial DNA mutation occurs every other generation, which, as creationists point out, indicates that mtEve would have lived about 200 generations ago. That's not so old! * National Geographic's Not-So-Old Hard-Rock Canyon at Mount St. Helens: As our List of Not So Old Things (this web page) reveals, by a kneejerk reaction evolutionary scientists assign ages of tens or hundreds of thousands of years (or at least just long enough to contradict Moses' chronology in Genesis.) However, with closer study, routinely, more and more old ages get revised downward to fit the world's growing scientific knowledge. So the trend is not that more information lengthens ages, but rather, as data replaces guesswork, ages tend to shrink until they are consistent with the young-earth biblical timeframe. Consistent with this observation, the May 2000 issue of National Geographic quotes the U.S. Forest Service's scientist at Mount St. Helens, Peter Frenzen, describing the canyon on the north side of the volcano. "You'd expect a hard-rock canyon to be thousands, even hundreds of thousands of years old. But this was cut in less than a decade." And as for the volcano itself, while again, the kneejerk reaction of old-earthers would be to claim that most geologic features are hundreds of thousands or millions of years old, the atheistic National Geographic magazine acknowledges from the evidence that Mount St. Helens, the volcanic mount, is only about 4,000 years old! See below and more at rsr.org/mount-st-helens. * Mount St. Helens Dome Ten Years Old not 1.7 Million: Geochron Laboratories of Cambridge, Mass., using potassium-argon and other radiometric techniques claims the rock sample they dated, from the volcano's dome, solidified somewhere between 340,000 and 2.8 million years ago. However photographic evidence and historical reports document the dome's formation during the 1980s, just ten years prior to the samples being collected. With the age of this rock known, radiometric dating therefore gets the age 99.99999% wrong. * Devils Hole Pupfish Isolated Not for 13,000 Years But for 100: Secular scientists default to knee-jerk, older-than-Bible-age dates. However, a tiny Mojave desert fish is having none of it. Rather than having been genetically isolated from other fish for 13,000 years (which would make this small school of fish older than the Earth itself), according to a paper in the journal Nature, actual measurements of mutation rates indicate that the genetic diversity of these Pupfish could have been generated in about 100 years, give or take a few. * Polystrates like Spines and Rare Schools of Fossilized Jellyfish: Previously, seven sedimentary layers in Wisconsin had been described as taking a million years to form. And because jellyfish have no skeleton, as Charles Darwin pointed out, it is rare to find them among fossils. But now, reported in the journal Geology, a school of jellyfish fossils have been found throughout those same seven layers. So, polystrate fossils that condense the time of strata deposition from eons to hours or months, include: - Jellyfish in central Wisconsin were not deposited and fossilized over a million years but during a single event quick enough to trap a whole school. (This fossil school, therefore, taken as a unit forms a polystrate fossil.) Examples are everywhere that falsify the claims of strata deposition over millions of years. - Countless trilobites buried in astounding three dimensionality around the world are meticulously recovered from limestone, much of which is claimed to have been deposited very slowly. Contrariwise, because these specimens were buried rapidly in quickly laid down sediments, they show no evidence of greater erosion on their upper parts as compared to their lower parts.- The delicacy of radiating spine polystrates, like tadpole and jellyfish fossils, especially clearly demonstrate the rapidity of such strata deposition. - A second school of jellyfish, even though they rarely fossilized, exists in another locale with jellyfish fossils in multiple layers, in Australia's Brockman Iron Formation, constraining there too the rate of strata deposition. By the way, jellyfish are an example of evolution's big squeeze. Like galaxies evolving too quickly, galaxy clusters, and even human feet (which, like Mummy DNA, challenge the Out of Africa paradigm), jellyfish have gotten into the act squeezing evolution's timeline, here by 200 million years when they were found in strata allegedly a half-a-billion years old. Other examples, ironically referred to as Medusoid Problematica, are even found in pre-Cambrian strata. - 171 tadpoles of the same species buried in diatoms. - Leaves buried vertically through single-celled diatoms powerfully refute the claimed super-slow deposition of diatomaceous rock. - Many fossils, including a Mesosaur, have been buried in multiple "varve" layers, which are claimed to be annual depositions, yet they show no erosional patterns that would indicate gradual burial (as they claim, absurdly, over even thousands of years). - A single whale skeleton preserved in California in dozens of layers of diatom deposits thus forming a polystrate fossil. - 40 whales buried in the desert in Chile. "What's really interesting is that this didn't just happen once," said Smithsonian evolutionist Dr. Nick Pyenson. It happened four times." Why's that? Because "the fossil site has at least four layers", to which Real Science Radio's Bob Enyart replies: "Ha ha ha ha ha ha ha ha ha ha ha", with RSR co-host Fred Williams thoughtfully adding, "Ha ha!" * Polystrate Trees: Examples abound around the world of polystrate trees:  - Yellowstone's petrified polystrate forest (with the NPS exhibit sign removed; see below) with successive layers of rootless trees demonstrating the rapid deposition of fifty layers of strata. - A similarly formed polystrate fossil forest in France demonstrating the rapid deposition of a dozen strata. - In a thousand locations including famously the Fossil Cliffs of Joggins, Nova Scotia, polystrate fossils such as trees span many strata. - These trees lack erosion: Not only should such fossils, generally speaking, not even exist, but polystrates including trees typically show no evidence of erosion increasing with height. All of this powerfully disproves the claim that the layers were deposited slowly over thousands or millions of years. In the experience of your RSR radio hosts, evolutionists commonly respond to this hard evidence with mocking. See CRSQ June 2006, ICR Impact #316, and RSR 8-11-06 at KGOV.com. * Yellowstone Petrified Trees Sign Removed: The National Park Service removed their incorrect sign (see left and more). The NPS had claimed that in dozens of different strata over a 40-square mile area, many petrified trees were still standing where they had grown. The NPS eventually removed the sign partly because those petrified trees had no root systems, which they would have had if they had grown there. Instead, the trees of this "fossil forest" have roots that are abruptly broken off two or three feet from their trunks. If these mature trees actually had been remnants of sequential forests that had grown up in strata layer on top of strata layer, 27 times on Specimen Ridge (and 50 times at Specimen Creek), such a natural history implies passage of more time than permitted by biblical chronology. So, don't trust the National Park Service on historical science because they're wrong on the age of the Earth. * Wood Petrifies Quickly: Not surprisingly, by the common evolutionary knee-jerk claim of deep time, "several researchers believe that several millions of years are necessary for the complete formation of silicified wood". Our List of Not So Old and Not So Slow Things includes the work of five Japanese scientists who proved creationist research and published their results in the peer-reviewed journal Sedimentary Geology showing that wood can and does petrify rapidly. Modern wood significantly petrified in 36 years these researchers concluded that wood buried in strata could have been petrified in "a fairly short period of time, in the order of several tens to hundreds of years." * The Scablands: The primary surface features of the Scablands, which cover thousands of square miles of eastern Washington, were long believed to have formed gradually. Yet, against the determined claims of uniformitarian geologists, there is now overwhelming evidence as presented even in a NOVA TV program that the primary features of the Scablands formed rapidly from a catastrophic breach of Lake Missoula causing a massive regional flood. Of course evolutionary geologists still argue that the landscape was formed over tens of thousands of years, now by claiming there must have been a hundred Missoula floods. However, the evidence that there was Only One Lake Missoula Flood has been powerfully reinforced by a University of Colorado Ph.D. thesis. So the Scablands itself is no longer available to old-earthers as de facto evidence for the passage of millions of years. * The Heart Mountain Detachment: in Wyoming just east of Yellowstone, this mountain did not break apart slowly by uniformitarian processes but in only about half-an-hour as widely reported including in the evolutionist LiveScience.com, "Land Speed Record: Mountain Moves 62 Miles in 30 Minutes." The evidence indicates that this mountain of rock covering 425 square miles rapidly broke into 50 pieces and slid apart over an area of more than 1,300 square miles in a biblical, not a "geological," timeframe.  * "150 Million" year-old Squid Ink Not Decomposed: This still-writable ink had dehydrated but had not decomposed! The British Geological Survey's Dr. Phil Wilby, who excavated the fossil, said, "It is difficult to imagine how you can have something as soft and sloppy as an ink sac fossilised in three dimensions, still black, and inside a rock that is 150 million years old." And the Daily Mail states that, "the black ink was of exactly the same structure as that of today's version", just desiccated. And Wilby added, "Normally you would find only the hard parts like the shell and bones fossilised but... these creatures... can be dissected as if they are living animals, you can see the muscle fibres and cells. It is difficult to imagine... The structure is similar to ink from a modern squid so we can write with it..." Why is this difficult for evolutionists to imagine? Because as Dr. Carl Wieland writes, "Chemical structures 'fall apart' all by themselves over time due to the randomizing effects of molecular motion."Decades ago Bob Enyart broadcast a geology program about Mount St. Helens' catastrophic destruction of forests and the hydraulic transportation and upright deposition of trees. Later, Bob met the chief ranger from Haleakala National Park on Hawaii's island of Maui, Mark Tanaka-Sanders. The ranger agreed to correspond with his colleague at Yellowstone to urge him to have the sign removed. Thankfully, it was then removed. (See also AIG, CMI, and all the original Yellowstone exhibit photos.) Groundbreaking research conducted by creation geologist Dr. Steve Austin in Spirit Lake after Mount St. Helens eruption provided a modern-day analog to the formation of Yellowstone fossil forest. A steam blast from that volcano blew over tens of thousands of trees leaving them without attached roots. Many thousands of those trees were floating upright in Spirit Lake, and began sinking at varying rates into rapidly and sporadically deposited sediments. Once Yellowstone's successive forest interpretation was falsified (though like with junk DNA, it's too big to fail, so many atheists and others still cling to it), the erroneous sign was removed. * Asiatic vs. European Honeybees: These two populations of bees have been separated supposedly for seven million years. A researcher decided to put the two together to see what would happen. What we should have here is a failure to communicate that would have resulted after their "language" evolved over millions of years. However, European and Asiatic honeybees are still able to communicate, putting into doubt the evolutionary claim that they were separated over "geologic periods." For more, see the Public Library of Science, Asiatic Honeybees Can Understand Dance Language of European Honeybees. (Oh yeah, and why don't fossils of poorly-formed honeycombs exist, from the millions of years before the bees and natural selection finally got the design right? Ha! Because they don't exist! :) Nautiloid proves rapid limestone formation. * Remember the Nautiloids: In the Grand Canyon there is a limestone layer averaging seven feet thick that runs the 277 miles of the canyon (and beyond) that covers hundreds of square miles and contains an average of one nautiloid fossil per square meter. Along with many other dead creatures in this one particular layer, 15% of these nautiloids were killed and then fossilized standing on their heads. Yes, vertically. They were caught in such an intense and rapid catastrophic flow that gravity was not able to cause all of their dead carcasses to fall over on their sides. Famed Mount St. Helens geologist Steve Austin is also the world's leading expert on nautiloid fossils and has worked in the canyon and presented his findings to the park's rangers at the invitation of National Park Service officials. Austin points out, as is true of many of the world's mass fossil graveyards, that this enormous nautiloid deposition provides indisputable proof of the extremely rapid formation of a significant layer of limestone near the bottom of the canyon, a layer like the others we've been told about, that allegedly formed at the bottom of a calm and placid sea with slow and gradual sedimentation. But a million nautiloids, standing on their heads, literally, would beg to differ. At our sister stie, RSR provides the relevant Geologic Society of America abstract, links, and video. *  Now It's Allegedly Two Million Year-Old Leaves: "When we started pulling leaves out of the soil, that was surreal, to know that it's millions of years old..." sur-re-al: adjective: a bizarre mix of fact and fantasy. In this case, the leaves are the facts. Earth scientists from Ohio State and the University of Minnesota say that wood and leaves they found in the Canadian Arctic are at least two million years old, and perhaps more than ten million years old, even though the leaves are just dry and crumbly and the wood still burns! * Gold Precipitates in Veins in Less than a Second: After geologists submitted for decades to the assumption that each layer of gold would deposit at the alleged super slow rates of geologic process, the journal Nature Geoscience reports that each layer of deposition can occur within a few tenths of a second. Meanwhile, at the Lihir gold deposit in Papua New Guinea, evolutionists assumed the more than 20 million ounces of gold in the Lihir reserve took millions of years to deposit, but as reported in the journal Science, geologists can now demonstrate that the deposit could have formed in thousands of years, or far more quickly! Iceland's not-so-old Surtsey Island looks ancient. * Surtsey Island, Iceland: Of the volcanic island that formed in 1963, New Scientist reported in 2007 about Surtsey that "geographers... marvel that canyons, gullies and other land features that typically take tens of thousands or millions of years to form were created in less than a decade." Yes. And Sigurdur Thorarinsson, Iceland's chief  geologist, wrote in the months after Surtsey formed, "that the time scale," he had been trained "to attach to geological developments is misleading." [For what is said to] take thousands of years... the same development may take a few weeks or even days here [including to form] a landscape... so varied and mature that it was almost beyond belief... wide sandy beaches and precipitous crags... gravel banks and lagoons, impressive cliffs… hollows, glens and soft undulating land... fractures and faultscarps, channels and screes… confounded by what met your eye... boulders worn by the surf, some of which were almost round... -Iceland's chief geologist * The Palouse River Gorge: In the southeast of Washington State, the Palouse River Gorge is one of many features formed rapidly by 500 cubic miles of water catastrophically released with the breaching of a natural dam in the Lake Missoula Flood (which gouged out the Scablands as described above). So, hard rock can be breached and eroded rapidly. * Leaf Shapes Identical for 190 Million Years?  From Berkley.edu, "Ginkgo biloba... dates back to... about 190 million years ago... fossilized leaf material from the Tertiary species Ginkgo adiantoides is considered similar or even identical to that produced by modern Ginkgo biloba trees... virtually indistinguishable..." The literature describes leaf shapes as "spectacularly diverse" sometimes within a species but especially across the plant kingdom. Because all kinds of plants survive with all kinds of different leaf shapes, the conservation of a species retaining a single shape over alleged deep time is a telling issue. Darwin's theory is undermined by the unchanging shape over millions of years of a species' leaf shape. This lack of change, stasis in what should be an easily morphable plant trait, supports the broader conclusion that chimp-like creatures did not become human beings and all the other ambitious evolutionary creation of new kinds are simply imagined. (Ginkgo adiantoides and biloba are actually the same species. Wikipedia states, "It is doubtful whether the Northern Hemisphere fossil species of Ginkgo can be reliably distinguished." For oftentimes, as documented by Dr. Carl Werner in his Evolution: The Grand Experiment series, paleontogists falsely speciate identical specimens, giving different species names, even different genus names, to the fossil and living animals that appear identical.) * Box Canyon, Idaho: Geologists now think Box Canyon in Idaho, USA, was carved by a catastrophic flood and not slowly over millions of years with 1) huge plunge pools formed by waterfalls; 2) the almost complete removal of large basalt boulders from the canyon; 3) an eroded notch on the plateau at the top of the canyon; and 4) water scour marks on the basalt plateau leading to the canyon. Scientists calculate that the flood was so large that it could have eroded the whole canyon in as little as 35 days. See the journal Science, Formation of Box Canyon, Idaho, by Megaflood, and the Journal of Creation, and Creation Magazine. * Manganese Nodules Rapid Formation: Allegedly, as claimed at the Wikipedia entry from 2005 through 2021: "Nodule growth is one of the slowest of all geological phenomena – in the order of a centimeter over several million years." Wow, that would be slow! And a Texas A&M Marine Sciences technical slide presentation says, “They grow very slowly (mm/million years) and can be tens of millions of years old", with RWU's oceanography textbook also putting it at "0.001 mm per thousand years." But according to a World Almanac documentary they have formed "around beer cans," said marine geologist Dr. John Yates in the 1997 video Universe Beneath the Sea: The Next Frontier. There are also reports of manganese nodules forming around ships sunk in the First World War. See more at at youngearth.com, at TOL, in the print edition of the Journal of Creation, and in this typical forum discussion with atheists (at the Chicago Cubs forum no less :). * "6,000 year-old" Mitochondrial Eve: As the Bible calls "Eve... the mother of all living" (Gen. 3:20), genetic researchers have named the one woman from whom all humans have descended "Mitochondrial Eve." But in a scientific attempt to date her existence, they openly admit that they included chimpanzee DNA in their analysis in order to get what they viewed as a reasonably old date of 200,000 years ago (which is still surprisingly recent from their perspective, but old enough not to strain Darwinian theory too much). But then as widely reported including by Science magazine, when they dropped the chimp data and used only actual human mutation rates, that process determined that Eve lived only six thousand years ago! In Ann Gibbon's Science article, "Calibrating the Mitochondrial Clock," rather than again using circular reasoning by assuming their conclusion (that humans evolved from ape-like creatures), they performed their calculations using actual measured mutation rates. This peer-reviewed journal then reported that if these rates have been constant, "mitochondrial Eve… would be a mere 6000 years old." See also the journal Nature and creation.com's "A shrinking date for Eve," and Walt Brown's assessment. Expectedly though, evolutionists have found a way to reject their own unbiased finding (the conclusion contrary to their self-interest) by returning to their original method of using circular reasoning, as reported in the American Journal of Human Genetics, "calibrating against recent evidence for the divergence time of humans and chimpanzees,"  to reset their mitochondrial clock back to 200,000 years. * Even Younger Y-Chromosomal Adam: (Although he should be called, "Y-Chromosomal Noah.") While we inherit our mtDNA only from our mothers, only men have a Y chromosome (which incidentally genetically disproves the claim that the fetus is "part of the woman's body," since the little boy's y chromosome could never be part of mom's body). Based on documented mutation rates on and the extraordinary lack of mutational differences in this specifically male DNA, the Y-chromosomal Adam would have lived only a few thousand years ago! (He's significantly younger than mtEve because of the genetic bottleneck of the global flood.) Yet while the Darwinian camp wrongly claimed for decades that humans were 98% genetically similar to chimps, secular scientists today, using the same type of calculation only more accurately, have unintentionally documented that chimps are about as far genetically from what makes a human being a male, as mankind itself is from sponges! Geneticists have found now that sponges are 70% the same as humans genetically, and separately, that human and chimp Y chromosomes are  "horrendously" 30%

It's been a week! The Verge's Nilay Patel, David Pierce, and Alex Cranz rejoin the studio to process all the tech news and announcements. Apple had its annual hardware event where the iPhone 15 and new Apple Watch lineup were shown off. Later, senior tech and policy reporter Adi Robertson joins the show to walk us through the US v Google antitrust trial that kicked off earlier in the week. Further reading: iPhone 15 event: all the news on Apple's new phones  Here's why Apple put a Thread radio in the iPhone 15 Pro  Rumors of Lightning's death are just slightly exaggerated The iPhone Mini is officially gone, long live the iPhone Mini USB-C Backbone One controllers will be ‘upgraded' to work with the iPhone 15 lineup. The iPhone is getting new ringtones with iOS 17 Apple announces more iOS 17 features coming later this year: Apple Music updates How Google plans to win its antitrust trial What to expect from the Google Search antitrust trial  US v. Google antitrust trial: updates Developers respond to Unity's new pricing scheme Unity cancels town hall over reported death threats What happens when Google Search doesn't have the answers? Google AMP: how Google tried to fix the web by taking it over A storefront for robots The little search engine that couldn't Who killed Google Reader? Email us at vergecast@theverge.com or call us at 866-VERGE11, we love hearing from you. Learn more about your ad choices. Visit podcastchoices.com/adchoices

En el espacio ‘Qué fue de…’ en La Terraza de Radio Euskadi, repasamos tecnologías, software y dispositivos que durante muchos años fueron muy utilizados y desaparecieron o, directamente, parecía que iban a tener un gran éxito, pero se quedaron por el camino. En esta ocasión vamos a hablar de desarrollos que no triunfaron y que llevaban la firma de Google como las Google Glass, Google+, Google Reader o Project ARA.

大家一看到这个并非一下就能明白但听完全篇觉得还真能把所有内容串起来的奇奇怪怪的标题就知道，Leon 又回来啦~不过如果你以为我们终于赶上热点聊聊那个变成了 X 的 logo 的话，那就还是错了，我们录音时还是 Threads 上线不久之时，而且话题也很快变成我们最近都在玩的游戏——《塞尔达传说：王国之泪》P.S. 本期关于游戏的部分还是有轻微剧透的哟~# 内容提要02:40 · 关于 JJ 不再续费的 Notion 和重新启用的 Bear05:38 · 不管怎么折腾，大家还是会回 Twitter 的12:50 · Threads 更像是个恶心人的东西23:39 · 一号主播吐槽这一代塞尔达38:51 · 一号主播继续吐槽这一代塞尔达# 参考链接Notion 的推荐赚佣金计划现在也有，不过要求比较高 3:07以原生技术开发的全平台文档应用 Craft 3:48主打「记录想法与灵感」的 flomo 浮墨笔记 3:50很多人盼星星盼月亮的 2.0 版本 Bear 本月终于上线 4:01本月初 Twitter 推出了针对普通和收费用户的每日阅读上限新政 5:40Twitter，哦不对，是 X 现在的首页 6:03在上一波「Twitter 出逃」时比较热门的 Mastodon 9:30已经淡出大家视野蛮久的 Tumblr 11:23本台吐槽 Facebook 的那期播客 14:36Threads 近期的一些数据 20:17说起来，Google Reader 离开正好十年了 22:32两万字解读《王国之泪》：任天堂超越神作的决心 27:21

Unlike some tech giants that have notoriously pulled the plug on beloved products (remember Google's sudden discontinuation of Google Reader?), 37signals takes a vastly different approach with their pledge to support ALL of their products for the life of the internet.This week host Kimberly Rhodes sits down with Jason Fried and David Heinemeier Hansson, the co-founders of 37signals, to explore the importance of longevity and trust in the SaaS industry.Drawing parallels to iconic brands like Porsche and Rolex, Jason and David take a deep dive into the challenges of product discontinuation and its impact on loyal customers. From Ta-da List to Basecamp, listen in as they reveal the principles that drive their support decisions and why longevity matters when building a brand that customers will rely on for decades.Check out the full video episode on YouTubeShow Notes: [00:00] - Kimberly introduces the podcast and the topic of 37signals' core principle to maintain its products until the end of the internet.[00:36] - David discusses the risk of relying on big companies for software services, sharing the recent example of Google killing off its domain selling service.[02:06] - David explains why Google tends to abandon services leaving users to deal with the aftermath.[03:50] - How to become a legacy brand—like Porsche.[05:20] - David shares 37signal's philosophy to keep products running until the end of the internet (example: 17 years of maintaining Ta-da List).[06:08] - Short-term profitability vs. long-term commitment to customers: The moral obligation (and trade-off) of maintaining legacy products.[08:07] - Kimberly draws a parallel between the changing ownership of mortgages and software services.[08:58] - Brand building through commitment and longevity. [10:05] - Jason shares how 37signals prioritizes their commitment to customers with their core apps.[12:16] - The challenge of balancing the desires of existing customers with the need to appeal to new customers. [15:47] - The most profitable product in the 37signals portfolio.[17:37] - Kimberly asks about the decision-making process between creating new versions of Basecamp versus adding features to the existing ones.[18:02] - Some updates are like facelifts—others involve fundamental changes. [20:20] - The costs involved in maintaining apps like Ta-da List.[21:35] - David highlights the BIG return on investment in brand power that comes with the commitment to maintaining products. [23:12] - How the murder of Google Reader still impacts users' trust in new Google products a decade later.[24:06] - The high failure rate of venture-backed companies.[23:48] - Did you know full video of episodes of Rework are available? Check out our YouTube channel or find us on Twitter. As always, if you have questions for David and Jason about a better way to work and run your business, we'd love to answer them. Leave your voicemails at 708-628-7850 or send an email. And don't forget you can find show notes and transcripts on our website.Links and Resources:From David's HEY World: You can't trust Google Sign up for a 30-day free trial at Basecamp.comHEY World | HEY Dev.37signals37signals on YouTubeThe REWORK podcastThe 37signals Dev Blog@37signals on Twitter 

Once upon a time, the RSS icon was a common sight on web pages. But these days, it's rare to see the friendly widget on the web. So what happened? Why has RSS faded away across much of the web landscape? See omnystudio.com/listener for privacy information.

Chris breaks out his banjo, some thoughts on making music vs recording music, what happened to Google Reader and social reading, what black box properties can't Dave or Chris remember, follow up for dev teams communicating with designers, and what's Adobe going to do about Figma?

This week we discuss RHEL licensing changes, check the vibe of DevOps and some thoughts on programing language. Plus, has ChatGPT already become boring? Runner-up Titles I don't like listening to fellow thought leaders. I listen to myself enough. Dammit, alarm was set for PM A massive failure of one The end of free It's not all smiles and thumbs Goose-cow “I used to, but I don't anymore.” The Podcast Review podcast. Rundown RHEL Furthering the evolution of CentOS Stream (https://www.redhat.com/en/blog/furthering-evolution-centos-stream) Red Hat strikes a crushing blow against RHEL downstreams (https://www.theregister.com/2023/06/23/red_hat_centos_move/) IBM/Red Hat Sparks Anger at GPL ‘breach' as RHEL Source Locked Up (https://devops.com/rhel-gpl-richixbw/) Rocky Strikes Back At Red Hat (https://hackaday.com/2023/06/30/rocky-strikes-back-at-red-hat/) The Suicide Attempt by Red Hat [Opinion] (https://news.itsfoss.com/red-hat-fiasco/) Rant about Red Hat's Licensing Change for REHL (https://youtube.com/watch?v=4fAq6AphRn0&feature=share) Reddit Reddit CEO tells employees that subreddit blackout “will pass” (https://www.theverge.com/2023/6/13/23759559/reddit-internal-memo-api-pricing-changes-steve-huffman) Apollo's Christian Selig explains his fight with Reddit — and why users revolted (https://www.theverge.com/2023/6/13/23759180/reddit-protest-private-apollo-christian-selig-subreddit) Reddit doubles down (https://www.platformer.news/p/reddit-doubles-down?utm_medium=email) Hackers threaten to leak 80GB of confidential data stolen from Reddit (https://techcrunch.com/2023/06/19/hackers-threaten-to-leak-80gb-of-confidential-data-stolen-from-reddit) DevOps Second Wave DevOps (https://www.systeminit.com/blog-second-wave-devops/) Kelsey Hightower Predicts How the Kubernetes Community Will Evolve (https://thenewstack.io/kelsey-hightower-predicts-how-the-kubernetes-community-will-evolve/) Kelsey Hightower Retires (https://twitter.com/kelseyhightower/status/1673366087541600256?s=20) Even the best rides come to an end featuring Kelsey Hightower (https://changelog.com/friends/6) (Podcast) Stack Overflow Developer Survey 2023 (https://survey.stackoverflow.co/2023/) Relevant to your Interests AWS teases mysterious mil-spec ‘Snowblade' server (https://www.theregister.com/2023/06/07/aws_snowblade_military_edge_server/) To fill offices, Google issues ultimatum while Salesforce tries charity (https://www.washingtonpost.com/business/2023/06/08/google-salesforce-return-to-office/) Amazon is pursuing 'too many ideas' and needs to focus on best opportunities (https://www.cnbc.com/2023/06/07/amazon-is-pursuing-too-many-ideas-bernstein-says-in-open-letter.html) There are better places for Amazon to put their capital to work, says Bernstein's Mark Shmulik (https://www.youtube.com/watch?v=j9Z2HeYkl4c) The best password managers for 2023 | Engadget (https://www.engadget.com/best-password-manager-134639599.html?guccounter=1&guce_referrer=aHR0cHM6Ly9uZXdzLmdvb2dsZS5jb20v&guce_referrer_sig=AQAAAIYHiHrsIv_lVu8RNqY46BjFzlgU4pFDBXmk1gQxq2wlQOz02b5tuepColb1KJFoYYwQVWy2SjTUKWVY2oAEMzfkYXlXs97_PE0gpwNUA4RjnDwE_YEm7FB323M9oOBQJNHboj1t77QC9HriDL8cJP-VcplJ5UlJvvwHZRzMn9PC) After a Rocky Year, Zuckerberg Lays Out Meta's Road Map to Employees (https://www.nytimes.com/2023/06/08/technology/mark-zuckerberg-meta.html) Hybrid combines the worst of office and remote work (https://world.hey.com/dhh/hybrid-combines-the-worst-of-office-and-remote-work-d3174e50) Twilio to sell ValueFirst business to Tanla (NYSE:TWLO) (https://seekingalpha.com/news/3978773-twilio-to-sell-valuefirst-business-to-tanla) Jeff Bezos Has Gained $10 on Mystery Purchase of One Amazon Share (https://www.bloomberg.com/news/articles/2023-06-09/billionaire-jeff-bezos-just-bought-one-share-of-amazon-and-no-one-knows-why#xj4y7vzkg) Jeff Bezos Has Gained $10 on Mystery Purchase of One Amazon Share (https://www.bloomberg.com/news/articles/2023-06-09/billionaire-jeff-bezos-just-bought-one-share-of-amazon-and-no-one-knows-why#xj4y7vzkg) CNET's Free Shopping Extension Saves You Time and Money. Give It a Try Today (https://www.cnet.com/tech/services-and-software/use-cnet-shopping-to-seek-out-the-best-deals/) Modular: Our launch & what's next (https://www.modular.com/blog/our-launch-whats-next) Exclusive-Broadcom set to win EU nod for $61 billion VMware deal, sources say (https://finance.yahoo.com/news/exclusive-eu-antitrust-regulators-okay-091426470.html) Amazon is reportedly trying to offer Prime subscribers free cell phone service | Engadget (https://www.engadget.com/amazon-is-reportedly-trying-to-offer-prime-subscribers-free-cell-phone-service-140026387.html) Cloud cost management startup CloudZero lands $32M investment (https://techcrunch.com/2023/06/12/cloud-cost-management-startup-cloudzero-lands-32m-investment/) Twitter stiffs Google (https://www.platformer.news/p/twitter-stiffs-google) Open Sourcing AWS Cedar Is a Game Changer for IAM (https://thenewstack.io/open-sourcing-aws-cedar-is-a-game-changer-for-iam/) Oracle beats on top and bottom lines as cloud revenue jumps (https://www.cnbc.com/2023/06/12/oracle-orcl-q4-earnings-report-2023.html) America to halt $68.7bn Microsoft takeover of Activision Blizzard (https://www.thetimes.co.uk/article/america-to-halt-68-7bn-microsoft-takeover-of-activision-blizzard-d80jvxm6f) Meta's Open-Source 'MusicGen' AI Is Like ChatGPT for Tunes (https://gizmodo.com/meta-open-source-musicgen-ai-like-chatgpt-for-music-1850528986) Google's return-to-office crackdown gets backlash from some employees: (https://www.cnbc.com/2023/06/13/google-rto-crackdown-gets-backlash-check-my-work-not-my-badge.html) Forrester Wave Integrated Software Delivery Platforms, Q2 2023 (https://www.forrester.com/blogs/the-forrester-wave-integrated-software-delivery-platforms-q2-2023-say-goodbye-to-the-devops-tax/) The economic potential of generative AI: The next productivity frontier (https://www.mckinsey.com/capabilities/mckinsey-digital/our-insights/the-economic-potential-of-generative-ai-the-next-productivity-frontier?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) 1 big thing: Where AI's productivity revolution will strike first (https://www.axios.com/newsletters/axios-login-da50d8f4-fb10-4952-af38-01163b9acbd3.html?chunk=0&utm_term=emshare#story0) For the first time in almost 30 years, a company other than IBM received the most US patents (https://finance.yahoo.com/news/first-time-almost-30-years-192900742.html) AMD stock pops on potential Amazon superchip deal, CEO bullishness (https://finance.yahoo.com/news/amd-stock-pops-on-potential-amazon-superchip-deal-ceo-bullishness-112819279.html) Amazon cloud services back up after big outage hits thousands of users (https://www.reuters.com/technology/amazon-says-multiple-cloud-services-down-users-2023-06-13/) Proven Practices for Developing a Multicloud Strategy | Amazon Web Services (https://aws.amazon.com/blogs/enterprise-strategy/proven-practices-for-developing-a-multicloud-strategy/) 40 photos from inside Metropolitan Park—the first phase of Amazon's HQ2 (https://www.aboutamazon.com/news/amazon-offices/amazon-headquarters-hq2-arlington-virginia-photos?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) The Forrester Wave™: Integrated Software Delivery Platforms, Q2 2023 (https://page.gitlab.com/forrester-wave-integrated-software-delivery-platforms-2023.html?utm_source=cote&utm_campaign=devrel&utm_content=newsletter20230615&utm_medium=email) AWS US-EAST-1 wobbled after Lambda management issues spread (https://www.theregister.com/2023/06/14/aws_us_east_1_brownout/) The store is for people, but the storefront is for robots (https://www.theverge.com/23753963/google-seo-shopify-small-business-ai) A Look Back at Q1 '23 Public Cloud Software Earnings (https://cloudedjudgement.substack.com/p/a-look-back-at-q1-23-public-cloud?utm_source=post-email-title&publication_id=56878&post_id=128805971&isFreemail=true&utm_medium=email) Apple Is Taking On Apples in a Truly Weird Trademark Battle (https://www.wired.com/story/apple-vs-apples-trademark-battle/) Apple Watch alerts 29-year-old Cincinnati woman to blood clot in lungs while sleeping (https://9to5mac.com/2023/06/19/apple-watch-blood-clot-sleeping/) Return to Office Enters the Desperation Phase (https://www.nytimes.com/2023/06/20/business/return-to-office-remote-work.html) Critical 'nOAuth' Flaw in Microsoft Azure AD Enabled Complete Account Takeover (https://thehackernews.com/2023/06/critical-noauth-flaw-in-microsoft-azure.html) What happened to Oracle? Why do they keep acquiring companies? (https://www.tiktok.com/t/ZT8JH8X5Y/) How an ex-Googler is reimagining the oldest computing interface of all (https://www.fastcompany.com/90907013/warp-terminal-command-line) WFH 4 ever (https://www.axios.com/2023/06/23/work-from-home-remote-workplace-trend) Databricks picks up MosaicML, an OpenAI competitor, for $1.3B (https://techcrunch.com/2023/06/26/databricks-picks-up-mosaicml-an-openai-competitor-for-1-3b/) Introducing LLaMA: A foundational, 65-billion-parameter language model (https://ai.facebook.com/blog/large-language-model-llama-meta-ai/?utm_source=newsletter&utm_medium=email&utm_campaign=newsletter_axioslogin&stream=top) AI's next conflict is between open and closed (https://www.axios.com/newsletters/axios-login-e2a8f546-c6e2-421c-a7dc-0996d64bf312.html?chunk=0&utm_term=emshare#story0) Amazon is investing another $7.8B in Ohio-based cloud computing operations, (https://apnews.com/article/amazon-aws-ohio-data-center-investment-e35c8b726269b6b78ce05854f9f31d27) A new law protecting pregnant workers is about to take effect (https://www.axios.com/2023/06/22/pregnant-workers-fairness-act-2023-explain) Amazon launches AWS AppFabric to help customers connect their SaaS apps (https://techcrunch.com/2023/06/27/amazon-launches-aws-appfabric-to-help-customers-connect-their-saas-apps/?guccounter=1&guce_referrer=aHR0cHM6Ly9uZXdzLmdvb2dsZS5jb20v&guce_referrer_sig=AQAAAGcA6HN4Zti_4dKCpuMURoiAkkQ_uR0GBWFOG215KnmRsvryBDclj9SjWv-95R0yA0wFRXevcP-HUdwk-E3ZyR3d23rc5VGVCNXFGK5L3mAPvoEOJxRs6WZFKQvDUBIyw5V3NpdWGkkQ-fXDh4Rijfdp2l_ekJTxepVJjoYJSyKz) State of Kubernetes Cost Optimization Report (https://inthecloud.withgoogle.com/state-of-kubernetes-cost-optimization-report/dl-cd.html) FTC Request, Answered: How Cloud Providers Do Business (https://www.lastweekinaws.com/blog/ftc-request-answered-how-cloud-providers-do-business/) OrbStack · Fast, light, simple Docker & Linux on macOS (https://orbstack.dev/?ref=console.dev) Surprise! You Work for Amazon. (https://www.theatlantic.com/technology/archive/2023/06/amazon-hub-delivery-last-mile/674559/) btop - the htop alternative (https://haydenjames.io/btop-the-htop-alternative/) We Raised A Bunch Of Money (https://fly.io/blog/we-raised-a-bunch-of-money/) Twitter has stopped paying its Google Cloud bills (https://www.businessinsider.com/elon-musk-twitter-stopped-paying-google-cloud-bills-money-platformer-2023-6) Report: 2022 Microsoft Azure Revenue Less Than Estimated, Half That Of AWS | CRN (https://www.crn.com/news/cloud/report-2022-microsoft-azure-revenue-less-than-estimated-half-that-of-aws) Google Domains shutting down, assets sold and being migrated to Squarespace (https://9to5google.com/2023/06/15/google-domains-squarespace/) Is Waze next? (https://www.theverge.com/2023/6/27/23776329/google-waze-layoffs-ads) The real story of how Facebook almost acquired Waze, but we ended up with Google (https://post.news/@/noam/2RTRvTNNxSCQb3yNjqa0DPfr1Yk) Google killed its Iris augmented-reality smart glasses (https://www.businessinsider.com/google-ar-iris-augmented-reality-smart-glasses-2023-6) Who killed Google Reader? (https://www.theverge.com/23778253/google-reader-death-2013-rss-social) Mark Zuckerberg is ready to fight Elon Musk in a cage match (https://www.theverge.com/2023/6/21/23769263/mark-zuckerberg-elon-musk-fight-cage-match-worldstar) IBM to Acquire Apptio Inc., (https://newsroom.ibm.com/2023-06-26-IBM-to-Acquire-Apptio-Inc-,-Providing-Actionable-Financial-and-Operational-Insights-Across-Enterprise-IT) IBM Re-ups On FinOps With Its Apptio Acquisition (https://www.forrester.com/blogs/ibm-re-ups-on-finops-with-its-apptio-acquisition/) Nonsense Texas Bans Kids From Social Media Without Mom and Dad's Ok (https://gizmodo.com/texas-law-kids-social-media-ban-without-parents-consent-1850540419) Summer intern's commute goes viral: She flies from South Carolina to New Jersey (https://www.cnn.com/2023/06/15/business/tiktok-summer-intern-commute/index.html) Twitter evicted from office amid lawsuits over unpaid rent and cleaning bills (https://arstechnica.com/tech-policy/2023/06/judge-ruled-twitter-must-be-evicted-from-colorado-office-over-unpaid-rent/) Fishing crew denied $3.5M in prize money after 600-pound marlin DQ'd in tournament (https://nypost.com/2023/06/19/massive-marlin-dqd-in-big-rock-blue-marlin-tournament-over-mutilation/) 'World's Largest' Buc-ee's store opens (https://www.wyff4.com/article/bucees-world-largest-tennessee/44343171) now on Bus-ee's Map (https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&ved=2ahUKEwjgoKnr-vX_AhVslGoFHeeBBREQFnoECBgQAQ&url=https%3A%2F%2Fwww.google.com%2Fmymaps%2Fviewer%3Fmid%3D1IBCXZDU73Q5pjsDWVkoQ5O0GLoUd-bg%26hl%3Den&usg=AOvVaw3joznC0GgnH9dU-z_XGEw5&opi=89978449) Magic Mushrooms. LSD. Ketamine. The Drugs That Power Silicon Valley. (https://www.wsj.com/articles/silicon-valley-microdosing-ketamine-lsd-magic-mushrooms-d381e214) 'Fueled by inflation': USPS stamp prices are increasing soon. Here's what to know. (https://www.usatoday.com/story/money/2023/06/28/stamp-price-increase-usps/70363626007/) At least a year younger on paper: South Korea makes changes to age-counting law (https://www.usatoday.com/story/news/world/2023/06/28/south-korea-changes-age-counting-law/70363453007/) Sony just spilled confidential PlayStation information because of a Sharpie (https://www.theverge.com/2023/6/28/23777298/sony-ftc-microsoft-confidential-documents-marker-pen-scanner-oops) Australia legalises psychedelics for mental health (https://www.bbc.co.uk/news/world-australia-66072427) Listener Feedback Let's Get To The News | Craig Box | Substack (https://craigbox.substack.com/) When You Don't Have a Seat At the (Managed Database) Table (https://unskript.com/blog/when-you-don-t-have-a-seat-at-the-(managed-database)-table> Show more) by Doug Sillars Conferences August 8th Kubernetes Community Day Australia (https://community.cncf.io/events/details/cncf-kcd-australia-presents-kubernetes-community-day-australia-2023/) in Sydney, Matt attending. August 21st to 24th SpringOne (https://springone.io/) & VMware Explore US (https://www.vmware.com/explore/us.html), in Las Vegas. Explore EU CFP is open. Sep 6th to 7th DevOpsDays Des Moines (https://devopsdays.org/events/2023-des-moines/welcome/), Coté speaking. Sep 18th to 19th SHIFT (https://shift.infobip.com/) in Zadar, Coté speaking. October 6, 2023, KCD Texas 2023 (https://community.cncf.io/events/details/cncf-kcd-texas-presents-kcd-texas-2023/), CFP Closes: August 30, 2023 Jan 29, 2024 to Feb 1, 2024 That Conference Texas CFP Open 6/1 - 8/21 (https://that.us/call-for-counselors/tx/2024/) If you want your conference mentioned, let's talk media sponsorships. SDT news & hype Join us in Slack (http://www.softwaredefinedtalk.com/slack). Get a SDT Sticker! Send your postal address to stickers@softwaredefinedtalk.com (mailto:stickers@softwaredefinedtalk.com) and we will send you free laptop stickers! Follow us on Twitch (https://www.twitch.tv/sdtpodcast), Twitter (https://twitter.com/softwaredeftalk), Instagram (https://www.instagram.com/softwaredefinedtalk/), Mastodon (https://hachyderm.io/@softwaredefinedtalk), BlueSky (https://bsky.app/profile/softwaredefinedtalk.com), LinkedIn (https://www.linkedin.com/company/software-defined-talk/), TikTok (https://www.tiktok.com/@softwaredefinedtalk) and YouTube (https://www.youtube.com/channel/UCi3OJPV6h9tp-hbsGBLGsDQ/featured). Use the code SDT to get $20 off Coté's book, Digital WTF (https://leanpub.com/digitalwtf/c/sdt), so $5 total. Become a sponsor of Software Defined Talk (https://www.softwaredefinedtalk.com/ads)! Recommendations Brandon: Cloudcast: MidYear 2023 Update (https://www.thecloudcast.net/2023/07/midyear-2023-update.html) Governments Building Software This Is What Happens When Governments Build Software - Odd Lots (https://omny.fm/shows/odd-lots/this-is-what-happens-when-governments-build-softwa) The Book I Wish Every Policymaker Would Read (https://www.nytimes.com/2023/06/06/opinion/ezra-klein-podcast-jennifer-pahlka.html) Tony Hsieh and the Emptiness of the Tech-Mogul Myth (https://www.newyorker.com/news/our-columnists/tony-hsieh-and-the-emptiness-of-the-tech-mogul-myth) (via Coté's newsletter) Coté: Hand Mirror app (https://handmirror.app), also in Setapp (https://setapp.com) if you have that. If Books could Kill (https://www.patreon.com/IfBooksPod) Photo Credits Header (https://unsplash.com/photos/5yuRImxKOcU) Artwork (https://www.freepnglogos.com/images/linux-22615.html)

Meta has officially launched its answer to Twitter called Threads. Richard Lawler from The Verge talks about what Threads is about. Mikah Sargent talked about Apple's gaming porting tool for macOS, discovered by Christina Warren a couple of episodes ago, that aims to bring real gaming to Macs. She joins the show to talk about the update the tool has received recently. Jason Howell talks about how voice actors are losing their voices to AI through services like Revoicer, even when these voice actors did not agree to permit these companies to use their voices. Finally, Mikah talks about "who" killed Google Reader. Hosts: Jason Howell and Mikah Sargent Guests: Richard Lawler and Christina Warren Download or subscribe to this show at https://twit.tv/shows/tech-news-weekly. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: bitwarden.com/twit AWS Insiders - TNW kolide.com/tnw

Meta has officially launched its answer to Twitter called Threads. Richard Lawler from The Verge talks about what Threads is about. Mikah Sargent talked about Apple's gaming porting tool for macOS, discovered by Christina Warren a couple of episodes ago, that aims to bring real gaming to Macs. She joins the show to talk about the update the tool has received recently. Jason Howell talks about how voice actors are losing their voices to AI through services like Revoicer, even when these voice actors did not agree to permit these companies to use their voices. Finally, Mikah talks about "who" killed Google Reader. Hosts: Jason Howell and Mikah Sargent Guests: Richard Lawler and Christina Warren Download or subscribe to this show at https://twit.tv/shows/tech-news-weekly. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: bitwarden.com/twit AWS Insiders - TNW kolide.com/tnw

Meta has officially launched its answer to Twitter called Threads. Richard Lawler from The Verge talks about what Threads is about. Mikah Sargent talked about Apple's gaming porting tool for macOS, discovered by Christina Warren a couple of episodes ago, that aims to bring real gaming to Macs. She joins the show to talk about the update the tool has received recently. Jason Howell talks about how voice actors are losing their voices to AI through services like Revoicer, even when these voice actors did not agree to permit these companies to use their voices. Finally, Mikah talks about "who" killed Google Reader. Hosts: Jason Howell and Mikah Sargent Guests: Richard Lawler and Christina Warren Download or subscribe to this show at https://twit.tv/shows/tech-news-weekly. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: bitwarden.com/twit AWS Insiders - TNW kolide.com/tnw

Meta has officially launched its answer to Twitter called Threads. Richard Lawler from The Verge talks about what Threads is about. Mikah Sargent talked about Apple's gaming porting tool for macOS, discovered by Christina Warren a couple of episodes ago, that aims to bring real gaming to Macs. She joins the show to talk about the update the tool has received recently. Jason Howell talks about how voice actors are losing their voices to AI through services like Revoicer, even when these voice actors did not agree to permit these companies to use their voices. Finally, Mikah talks about "who" killed Google Reader. Hosts: Jason Howell and Mikah Sargent Guests: Richard Lawler and Christina Warren Download or subscribe to this show at https://twit.tv/shows/tech-news-weekly. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: bitwarden.com/twit AWS Insiders - TNW kolide.com/tnw

Meta has officially launched its answer to Twitter called Threads. Richard Lawler from The Verge talks about what Threads is about. Mikah Sargent talked about Apple's gaming porting tool for macOS, discovered by Christina Warren a couple of episodes ago, that aims to bring real gaming to Macs. She joins the show to talk about the update the tool has received recently. Jason Howell talks about how voice actors are losing their voices to AI through services like Revoicer, even when these voice actors did not agree to permit these companies to use their voices. Finally, Mikah talks about "who" killed Google Reader. Hosts: Jason Howell and Mikah Sargent Guests: Richard Lawler and Christina Warren Download or subscribe to this show at https://twit.tv/shows/tech-news-weekly. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: bitwarden.com/twit AWS Insiders - TNW kolide.com/tnw

Meta has officially launched its answer to Twitter called Threads. Richard Lawler from The Verge talks about what Threads is about. Mikah Sargent talked about Apple's gaming porting tool for macOS, discovered by Christina Warren a couple of episodes ago, that aims to bring real gaming to Macs. She joins the show to talk about the update the tool has received recently. Jason Howell talks about how voice actors are losing their voices to AI through services like Revoicer, even when these voice actors did not agree to permit these companies to use their voices. Finally, Mikah talks about "who" killed Google Reader. Hosts: Jason Howell and Mikah Sargent Guests: Richard Lawler and Christina Warren Download or subscribe to this show at https://twit.tv/shows/tech-news-weekly. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: bitwarden.com/twit AWS Insiders - TNW kolide.com/tnw

Meta has officially launched its answer to Twitter called Threads. Richard Lawler from The Verge talks about what Threads is about. Mikah Sargent talked about Apple's gaming porting tool for macOS, discovered by Christina Warren a couple of episodes ago, that aims to bring real gaming to Macs. She joins the show to talk about the update the tool has received recently. Jason Howell talks about how voice actors are losing their voices to AI through services like Revoicer, even when these voice actors did not agree to permit these companies to use their voices. Finally, Mikah talks about "who" killed Google Reader. Hosts: Jason Howell and Mikah Sargent Guests: Richard Lawler and Christina Warren Download or subscribe to this show at https://twit.tv/shows/tech-news-weekly. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: bitwarden.com/twit AWS Insiders - TNW kolide.com/tnw

Meta has officially launched its answer to Twitter called Threads. Richard Lawler from The Verge talks about what Threads is about. Mikah Sargent talked about Apple's gaming porting tool for macOS, discovered by Christina Warren a couple of episodes ago, that aims to bring real gaming to Macs. She joins the show to talk about the update the tool has received recently. Jason Howell talks about how voice actors are losing their voices to AI through services like Revoicer, even when these voice actors did not agree to permit these companies to use their voices. Finally, Mikah talks about "who" killed Google Reader. Hosts: Jason Howell and Mikah Sargent Guests: Richard Lawler and Christina Warren Download or subscribe to this show at https://twit.tv/shows/tech-news-weekly. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: bitwarden.com/twit AWS Insiders - TNW kolide.com/tnw

Meta has officially launched its answer to Twitter called Threads. Richard Lawler from The Verge talks about what Threads is about. Mikah Sargent talked about Apple's gaming porting tool for macOS, discovered by Christina Warren a couple of episodes ago, that aims to bring real gaming to Macs. She joins the show to talk about the update the tool has received recently. Jason Howell talks about how voice actors are losing their voices to AI through services like Revoicer, even when these voice actors did not agree to permit these companies to use their voices. Finally, Mikah talks about "who" killed Google Reader. Hosts: Jason Howell and Mikah Sargent Guests: Richard Lawler and Christina Warren Download or subscribe to this show at https://twit.tv/shows/tech-news-weekly. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: bitwarden.com/twit AWS Insiders - TNW kolide.com/tnw

Meta has officially launched its answer to Twitter called Threads. Richard Lawler from The Verge talks about what Threads is about. Mikah Sargent talked about Apple's gaming porting tool for macOS, discovered by Christina Warren a couple of episodes ago, that aims to bring real gaming to Macs. She joins the show to talk about the update the tool has received recently. Jason Howell talks about how voice actors are losing their voices to AI through services like Revoicer, even when these voice actors did not agree to permit these companies to use their voices. Finally, Mikah talks about "who" killed Google Reader. Hosts: Jason Howell and Mikah Sargent Guests: Richard Lawler and Christina Warren Download or subscribe to this show at https://twit.tv/shows/tech-news-weekly. Get episodes ad-free with Club TWiT at https://twit.tv/clubtwit Sponsors: bitwarden.com/twit AWS Insiders - TNW kolide.com/tnw

RobChrisRob talked about the death of Google Reader, and the ongoing collapse of Reddit & Twitter, the trailer for Zom 100, Fue5, the AI that screws with telemarketer, the Philippines tourism trailer that got caught using stock footage from NOT the Philippines, a machine that lasers weeds instead of using herbicides, Elon's genius idea to give people who drive on the wrong side of the car a stick instead of giving them the car they want, iPhones calling 9/11 because it confuses dancing with car crashes, and finally a brief discussion of Indy 5 and then it gets spoilery so you should nope out!

Il 95% degli utenti di IRL erano fake. La chiusura di Stitcher. Il GameBoy di guerra. Aziende europee contro AI act. Gli LLM senza censure. Reddit il giorno dopo. Queste e molte altre le notizie tech commentate nella puntata d questa settimana.Dallo studio distribuito di digitalia: Franco Solerio, Michele Di MaioProduttori esecutivi:Andrea Scarpellini, Giuseppe Benedetti, Nicola Bisceglie, Andrea Malesani, Danny Manzini, Riccardo Peruzzini, Paolo Boschetti, Diego Venturin, Roberto Esposito, Michele Olivieri, Matteo Faccio, Davide Fogliarini, Mario Cervai, Antonio Turdo (Thingyy), Christian Fabiani, Alex Ordiner, Elisa Emaldi - Marco Crosa, Marcello Piliego, Marco Mandia, Adriano Guarino, Ivan Vannicelli, Mirto Tondini, Stefano Augusto Innocenti, Roberto Tarzia, Matteo Molinari, Michele Coiro, Christian A Marca, Zambianchi Marco Francesco Mauro, Yoandi Herrera, Yoandi Herrera, Maurizio Galluzzo, ---, Diego Donati, Davide Tinti, Manuel Zavatta, Nicola Gabriele D., Capitan Harlock, Nicola Fort, daxda, Fiorenzo PillaSponsor:Squarespace.com - utilizzate il codice coupon "DIGITALIA" per avere il 10% di sconto sul costo dell'abbonamento.Links:Apple's market cap hits $3 trillion once againUncensored Chatbots Provoke a Fracas Over Free SpeechTwitter is DDOSing itselfLa sfida Musk-Zuckerberg dentro il Colosseo? : Se fanno beneficenza...Linda Yaccarino's vision for Twitter 2.0 emergesAI-Generated Books of Nonsense Are All Over Amazon's Bestseller ListsEuropean companies: "AI Act could jeopardise technological sovereignty"At least one big third-party Reddit iOS app will live onWho killed Google Reader?Reddit protest plunges user engagement, site activityHumans may be more likely to believe disinformation generated by AII consider myself a patient person, but 'The Password Game' might break meValve is reportedly banning games featuring AI generated contentThe iconic Gulf War Nintendo Game Boy is heading into retirementIt looks like Google might be giving Waze the Nest treatmentThe case for a digital euroPicks up where he left off with RPG he started almost 40 years ago on a C=64ChatGPT si fa imbrogliare e regala codici Windows 11 ProNASA is creating a ChatGPT-like assistant for astronautsSTITCHER FAREWELL — Stitcher Help CenterLet's welcome Meta, not block themRabbit Hole, quando la serie tv diventa un bagno di realtàSocial app IRL to shut down after admitting 95% of its users were fakeGingilli del giorno: Rate Your MusicThe Deep SeaSupporta Digitalia, diventa produttore esecutivo.

Second time the charm for Apple to close above $3 trillion? Google says it will remove news links in Canada. Meta will allow you to download apps directly from Ads. Self driving cars are giving cops more surveillance tape. And, of course, the Weekend Longreads Suggestions.Links:Apple's market cap tops $3 trillion (CNBC)Canada's ‘link tax' law could break how the web works, says Google (Android Police)Meta is planning to let people in the EU download apps through Facebook (The Verge)Fidelity Joins Spot-Bitcoin ETF Race With Fresh SEC Filing (Bloomberg)Police Are Requesting Self-Driving Car Footage For Video Evidence (Bloomberg)Weekend Longreads Suggestions:When Will AI Generate a Hollywood Blockbuster? “Give It About Three Years.” (Inverse)These Tech Companies Think They Can ‘Solve' the Wildfire Crisis (Motherboard)Who killed Google Reader? (The Verge)Mixtape Sites Like DatPiff Propelled Rap. Can They Be Preserved? (NYTimes)See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

We're taking a short break from our usual programming about podcasting to dive into what's next for us. Ilya quit his job at Google on June 1st and Arnab left his job at Amazon last year. On this episode, we're discussing why we decided to jump ship, how we manage risk, financial planning, etc. We're also going a bit personal and talking about our approach to career planning. [02:21] Ilya's left Google to work on a podcasting company with Arnab [03:23] What did Ilya do at Google? [04:54] Google's “defragging” of Google Reader [09:48] Getting tired of a corporate job [16:07] Wantepreneurs vs. entrepreneurs [22:35] Realizing I can't do it anymore and conquering fears [25:53] Preparing finances to jump corporate ship [33:48] Indie development model [37:06] Preparing the family for leaving your job [43:12] Health Insurance Full show notes with links: https://www.metacastpodcast.com/p/024-pt1-leaving-jobs-at-google-and-amazon We're always happy to hear back from our listeners, so don't hesitate to drop us a note! - Email: hello@metacastpodcast.com - Ilya's LinkedIn: https://www.linkedin.com/in/ilyabezdelev/ - Arnab's Twitter: https://twitter.com/or9ob Subscribe to our newsletter where we announce new episodes, publish key takeaways, and ramble about interesting stuff at https://www.metacastpodcast.com.

On this episode of The Cyber PR Music Podcast, host Ariel Hyatt speaks with software engineer and Myxt co-founder Chris Wetherell about AI in music and the need for a cultural understanding around technology. Wetherell shares insights on his current work in mastering, audio pattern detection, and transcription services, as well as the breakthrough in AI language translation that happened in 2017. He also discusses his concerns about government understanding of technology and the weaponization of social media, a topic he knows a LOT about as he had a front-row seat at Twitter. Key takeaways include the importance of musicians developing a point of view on AI in music, the potential impact on vocalists and instrumentalists, and the need for early conversation around the cultural impact of technology. About Chris Wetherell Chris Wetherell is a musician turned Co-Founder and Chief Executive Officer of Myxt. An early engineer at Google, Chris started the popular Google Reader app used by millions worldwide. Chris then went on to work at Twitter as the lead on implementing its Retweet feature. He also started Thing Labs, Avocado Software, and was most recently the Chief Product Officer of the geographic data analysis platform, Tierra. Chris attended University of California, Berkeley where he studied Computer Science and Music. Link About it: Myxt - https://myxt.com/  Eleven Labs - https://beta.elevenlabs.io/    Key takeaways: - Musicians should develop a point of view on AI in music to prepare for its impact on the industry. - Vocalists should take action to own the transformation of their own voice with AI. - There are concerns about the weaponization of social media and how AI can facilitate language generation. - There is a prediction of a new development in the music industry that will likely create a new business model. - The conversation around the cultural impact of technology should be held early on in its development.  

Why the death of Reader 10 years ago might come back to haunt Google, Samsung's AI moon photos raise a philosophical question, Jim's frustrations with Ubuntu, and connecting a POS system.   Plugs Support us on patreon FreeBSD History: Understanding the origins of DTrace   News/discussion Requiem for Google Reader, gone but not forgotten Samsung's […]

RSS has been such an integral part of my life basically since Google Reader. And since Google Reader shut down, I have been on a bit of a quest to find a good replacement. I think Reader by Readwise is that Replacement.This clip is brought to you TextExpander ★ Support this podcast ★

RSS has been such an integral part of my life basically since Google Reader. And since Google Reader shut down, I have been on a bit of a quest to find a good replacement. I think Reader by Readwise is that Replacement. This clip is brought to you TextExpander

RSS has been such an integral part of my life basically since Google Reader. And since Google Reader shut down, I have been on a bit of a quest to find a good replacement. I think Reader by Readwise is that Replacement.This clip is brought to you TextExpander Get your FREE copy of my Automations Library ★ Support this podcast ★

About BrianBrian leads the Google Cloud Product and Industry Marketing team. This team is focused on accelerating the growth of Google Cloud by establishing thought leadership, increasing demand and usage, enabling their sales teams and partners to tell their product stories with excellence, and helping their customers be the best advocates for them.Before joining Google, Brian spent over 25 years in product marketing or engineering in different forms. He started his career at Microsoft and had a very non-traditional path for 20 years. Brian worked in every product division except for cloud. He did marketing, product management, and engineering roles. And, early on, he was the first speech writer for Steve Ballmer and worked on Bill Gates' speeches too. His last role was building up the Microsoft Surface business from scratch as VP of the hardware businesses. After Microsoft, Brian spent a year as CEO at a hardware startup called Doppler Labs, where they made a run at transforming hearing, and then spent two years as VP at Amazon Web Services leading product marketing, developer advocacy, and a bunch more marketing teams.Brian has three kids still at home, Barty, Noli, and Alder, who are all named after trees in different ways. His wife Edie and him met right at the beginning of their first year at Yale University, where Brian studied math, econ, and philosophy and was the captain of the Swim and Dive team his senior year. Edie has a PhD in forestry and runs a sustainability and forestry consulting firm she started, that is aptly named “Three Trees Consulting”. As a family they love the outdoors, tennis, running, and adventures in Brian's 1986 Volkswagen Van, which is his first and only car, that he can't bring himself to get rid of.Links Referenced: Google Cloud: https://cloud.google.com @isforat: https://twitter.com/IsForAt LinkedIn: https://www.linkedin.com/in/brhall/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is brought to us by our friends at Pinecone. They believe that all anyone really wants is to be understood, and that includes your users. AI models combined with the Pinecone vector database let your applications understand and act on what your users want… without making them spell it out. Make your search application find results by meaning instead of just keywords, your personalization system make picks based on relevance instead of just tags, and your security applications match threats by resemblance instead of just regular expressions. Pinecone provides the cloud infrastructure that makes this easy, fast, and scalable. Thanks to my friends at Pinecone for sponsoring this episode. Visit Pinecone.io to understand more.Corey: This episode is brought to you in part by our friends at Veeam. Do you care about backups? Of course you don't. Nobody cares about backups. Stop lying to yourselves! You care about restores, usually right after you didn't care enough about backups. If you're tired of the vulnerabilities, costs, and slow recoveries when using snapshots to restore your data, assuming you even have them at all living in AWS-land, there is an alternative for you. Check out Veeam, that's V-E-E-A-M for secure, zero-fuss AWS backup that won't leave you high and dry when it's time to restore. Stop taking chances with your data. Talk to Veeam. My thanks to them for sponsoring this ridiculous podcast.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. This episode is brought to us by our friends at Google Cloud and, as a part of that, they have given me someone to, basically, harass for the next half hour. Brian Hall is the VP of Product Marketing over at Google Cloud. Brian, welcome back.Brian: Hello, Corey. It's good to be here, and technically, we've given you time to harass me by speaking with me because you never don't have the time to harass me on Twitter and other places, and you're very good at it.Corey: Well, thank you. Again, we first met back when you were doing, effectively, the same role over at AWS. And before that, you spent only 20 years or so at Microsoft. So, you've now worked at all three of the large hyperscale cloud providers. You probably have some interesting perspectives on how the industry has evolved over that time. So, at the time of this recording, it is after Google Next and before re:Invent. There was also a Microsoft event there that I didn't pay much attention to. Where are we as a culture, as an industry, when it comes to cloud?Brian: Well, I'll start with it is amazing how early days it still is. I don't want to be put on my former Amazon cap too much, and I think it'd be pushing it a little bit to say it's complete and total day one with the cloud. But there's no question that there is a ton of evolution still to come. I mean, if you look at it, you can kind of break it into three eras so far. And roll with me here, and happy to take any dissent from you.But there was kind of a first era that was very much led by Amazon. We can call it the VM era or the component era, but being able to get compute on-demand, get nearly unlimited or actually unlimited storage with S3 was just remarkable. And it happened pretty quickly that startups, new tech companies, had to—like, it would be just wild to not start with AWS and actually start ordering servers and all that kind of stuff. And so, I look at that as kind of the first phase. And it was remarkable how long Amazon had a run really as the only player there. And maybe eight years ago—six years ago—we could argue on timeframes, things shifted a little bit because the enterprises, the big companies, and the governments finally realized, “Holy crow. This thing has gotten far enough that it's not just for these startups.”Corey: Yeah. There was a real change. There was an eye-opening moment there where it isn't just, “I want to go and sell things online.” It's, “And I also want to be a bank. Can we do that with you?” And, “Huh.”Brian: My SAP—like I don't know big that darn thing is going to get. Could I put it in your cloud? And, “Oh, by the way, CapEx forecasting stinks. Can you get me out of that?” And so, it became like the traditional IT infrastructure. All of the sudden, the IT guys showed up at the party, which I know is—it sounds fun to me, but that doesn't sound like the best addition to a party for many people. And so essentially, old-school IT infrastructure finally came to the cloud and Microsoft couldn't miss that happening when it did. But it was a major boon for AWS just because of the position that they had already.Corey: And even Google as well. All three of you now are pivoting in a lot of the messaging to talk to the big E enterprises out there. And I've noticed for the last few years, and I'm not entirely alone. When I go to re:Invent, and I look at announcements they're making, sure they have for the serverless stuff and how to run websites and EC2 nonsense. And then they're talking about IOT things and other things that just seem very oriented on a persona I don't understand. Everyone's doing stuff with mainframes now for example. And it feels like, “Oh, those of us who came here for the web services like it says on the name of the company aren't really feeling like it's for us anymore.” It's the problem of trying to be for everyone and pivoting to where the money is going, but Google's done this at least as much as anyone has in recent years. Are those of us who don't have corporate IT-like problems no longer the target market for folks or what's changed?Brian: It's still the target market, so like, you take the corporate IT, they're obviously still moving to the cloud. And there's a ton of opportunity. Just take existing IT spending and see a number over $1 trillion per year, and if you take the run rates of Microsoft, Amazon, Google Cloud, it's certainly over $100 billion, but that means it's still less than ten percent of what is existing IT spending. There are many people that think that existing IT spend number is significantly higher than that. But to your point on what's changing, there's actually a third wave that's happening.So, if the first wave was you start a company. You're a tech company, of course, you start it on AWS or on the Cloud. Second wave is all the IT people, IT departments, the central organizations that run technology for all the people that are not technology people come to the cloud. This third wave is everybody has to become a technology person. If you're a business leader, like you're at a fast-food restaurant and you're responsible for the franchisee relations, before, like, you needed to get an EDI system running or something, and so you told your IT department to figure out.Now, you have to actually think about what apps do we want to provide to our customers. How do I get the right data to my franchisees so that they can make business decisions? How can I automate all that? And you know, whereas before I was a guy wearing a suit or a gal wearing a suit who didn't need to know technology, I now have to. And that's what's changing the most. And it's why the Target Addressable Market—or the TAM as business folk sometimes say—it's really hard to estimate looking forward if every business is really needing to become a technology business in many ways. And it didn't dawn on me, honestly, and you can give me all the ribbing that I probably deserve for this—but it didn't really dawn on me until I came to Google and kept hearing the transformation word, “Digital transformation, digital transformation,” and honestly, having been in software for so long, I didn't really know what digital transformation meant until I started seeing all of these folks, like every company have to become a tech company effectively.Corey: Yeah. And it turns out there aren't enough technologists to go around, so it's very challenging to wind up getting the expertise in-house. It's natural to start looking at, “Well, how do we effectively outsource this?” And well, you can absolutely have a compression algorithm for experience. It's called, “Buying products and services and hiring people who have that experience already baked in either to the product or they show up knowing how to do something because they've done this before.”Brian: That's right. The thing I think we have to—for those of us that come from the technology side, this transformation is scary for the people who all of the sudden have to get tech and be like—Corey, if you or I—actually, you're very artistic, so maybe this wouldn't do it for you—but if I were told, “Hey, Brian, for your livelihood, you now need to incorporate painting,” like…Corey: [laugh]. I can't even write legibly let alone draw or paint. That is not my skill set. [laugh].Brian: I'd be like, “Wait, what? I'm not good at painting. I've never been a painting person, like I'm not creative.” “Okay. Great. Then we're going to fire you, or we're going to bring someone in who can.” Like, that'd be scary. And so, having more services, more people that can help as every company goes through a transition like that—and it's interesting, it's why during Covid, the cloud did really well, and some people kind of said, “Well, it's because they—people didn't want to send their people into their data centers.” No. That wasn't it. It was really because it just forced the change to digital. Like the person to, maybe, batter the analogy a little bit—the person who was previously responsible for all of the physical banks, which are—a bank has, you know, that are retail locations—the branches—they have those in order to service the retail customers.Corey: Yeah.Brian: That person, all of the sudden, had to figure out, “How do I do all that service via phone, via agents, via an app, via our website.” And that person, that entire organization, was forced digital in many ways. And that certainly had a lot of impact on the cloud, too.Corey: Yeah. I think that some wit observed a few years back that Covid has had more impact on your digital transformation than your last ten CIOs combined.Brian: Yeah.Corey: And—yeah, suddenly, you're forcing people into a position where there really is no other safe option. And some of that has unwound but not a lot of it. There's still seem to be those same structures and ability to do things from remote locations then there were before 2020.Brian: Yeah. Since you asked, kind of, where we are in the industry, to bring all of that to an endpoint, now what this means is people are looking for cloud providers, not just to have the primitives, not just to have the IT that they—their central IT needed, but they need people who can help them build the things that will help their business transform. It makes it a fun, new stage, new era, a transformation era for companies like Google to be able to say, “Hey, here's how we build things. Here's what we've learned over a period of time. Here's what we've most importantly learned from other customers, and we want to help be your strategic partner in that transformation.” And like I said, it'd be almost impossible to estimate what the TAM is for that. The real question is how quickly can we help customers and innovate in our Cloud solutions in order to make more of the stuff more powerful and faster to help people build.Corey: I want to say as well that—to be clear—you folks can buy my attention but not my opinion. I will not say things if I do not believe them. That's the way the world works here. But every time I use Google Cloud for something, I am taken aback yet again by the developer experience, how polished it is. And increasingly lately, it's not just that you're offering those low-lying primitives that composed together to build things higher up the stack, you're offering those things as well across a wide variety of different tooling options. And they just tend to all make sense and solve a need rather than requiring me to build it together myself from popsicle sticks.And I can't shake the feeling that that's where the industry is going. I'm going to want someone to sell me an app to do expense reports. I'm not going to want—well, I want a database and a front-end system, and how I wind up storing all the assets on the backend. No. I just want someone to give me something that solves that problem for me. That's what customers across the board are looking for as best I can see.Brian: Well, it certainly expands the number of customers that you can serve. I'll give you an example. We have an AI agent product called Call Center AI which allows you to either build a complete new call center solution, or more often it augments an existing call center platform. And we could sell that on an API call basis or a number of agent seats basis or anything like that. But that's not actually how call center leaders want to buy. Imagine we come in and say, “This many API calls or $4 per seat or per month,” or something like that. There's a whole bunch of work for that call center leader to go figure out, “Well, do I want to do this? Do I not? How should I evaluate it versus others?” It's quite complex. Whereas, if we come in and say, “Hey, we have a deal for you. We will guarantee higher customer satisfaction. We will guarantee higher agent retention. And we will save you money. And we will only charge you some percentage of the amount of money that you're saved.”Corey: It's a compelling pitch.Brian: Which is an easier one for a business decision-maker to decide to take?Corey: It's no contest. I will say it's a little odd that—one thing—since you brought it up, one thing that struck me as a bit strange about Contact Center AI, compared to most of the services I would consider to be Google Cloud, instead of, “Click here to get started,” it's, “Click here to get a demo. Reach out to contact us.” It feels—Brian: Yeah.Corey: —very much like the deals for these things are going to get signed on a golf course.Brian: [laugh]. They—I don't know about signed on a golf course. I do know that there is implementation work that needs to be done in order to build the models because it's the model for the AI, figuring out how your particular customers are served in your particular context that takes the work. And we need to bring in a partner or bring in our expertise to help build that out. But it sounds to me like you're looking to go golfing since you've looked into this situation.Corey: Just like painting, I'm no good at golfing either.Brian: [laugh].Corey: Honestly, it's—it just doesn't have the—the appeal isn't there for me for whatever reason. I smile; I nod; I tend to assume that, “Yeah, that's okay. I'll leave some areas for other people to go exploring in.”Brian: I see. I see.Corey: So, two weeks before Google Cloud Next occurred, you folks wound up canceling Stadia, which had been rumored for a while. People had been predicting it since it was first announced because, “Just wait. They're going to Google Reader it.” And yeah, it was consumer-side, and I do understand that that was not Cloud. But it did raise the specter of—for people to start talking once again about, “Oh, well, Google doesn't have any ability to focus on things long-term. They're going to turn off Cloud soon, too. So, we shouldn't be using it at all.” I do not agree with that assessment.But I want to get your take on it because I do have some challenges with the way that your products and services go to market in some ways. But I don't have the concern that you're going to turn it all off and decide, “Yeah, that was a fun experiment. We're done.” Not with Cloud, not at this point.Brian: Yeah. So, I'd start with at Google Cloud, it is our job to be a trusted enterprise platform. And I can't speak to before I was here. I can't speak to before Thomas Kurian, who's our CEO, was here before. But I can say that we are very, very focused on that. And deprecating products in a surprising way or in a way that doesn't take into account what customers are on it, how can we help those customers is certainly not going to help us do that. And so, we don't do that anymore.Stadia you brought up, and I wasn't part of starting Stadia. I wasn't part of ending Stadia. I honestly don't know anything about Stadia that any average tech-head might not know. But it is a different part of Google. And just like Amazon has deprecated plenty of services and devices and other things in their consumer world—and Microsoft has certainly deprecated many, many, many consumer and other products—like, that's a different model. And I won't say whether it's good, bad, or righteous, or not.But I can say at Google Cloud, we're doing a really good job right now. Can we get better? Of course. Always. We can get better at communicating, engaging customers in advance. But we now have a clean deprecation policy with a set of enterprise APIs that we commit to for stated periods of time. We also—like people should take a look. We're doing ten-year deals with companies like Deutsche Bank. And it's a sign that Google is here to last and Google Cloud in particular. It's also at a market level, just worth recognizing.We are a $27 billion run rate business now. And you earn trust in drips. You lose it in buckets. And we're—we recognize that we need to just keep every single day earning trust. And it's because we've been able to do that—it's part of the reason that we've gotten as large and as successful as we have—and when you get large and successful, you also tend to invest more and make it even more clear that we're going to continue on that path. And so, I'm glad that the market is seeing that we are enterprise-ready and can be trusted much, much more. But we're going to keep earning every single day.Corey: Yeah. I think it's pretty fair to say that you have definitely gotten yourselves into a place where you've done the things that I would've done if I wanted to shore up trust that the platform was not going to go away. Because these ten-year deals are with the kinds of companies that, shall we say, do not embark on signing contracts lightly. They very clearly, have asked you the difficult, pointed questions that I'm basically asking you now as cheap shots. And they ask it in very serious ways through multiple layers of attorneys. And if the answers aren't the right answers, they don't sign the contract. That is pretty clearly how the world works.The fact that companies are willing to move things like core trading systems over to you on a ten-year time horizon, tells me that I can observe whatever I want from the outside, but they have actual existential risk questions tied to what they're doing. And they are in some ways betting their future on your folks. You clearly know what those right answers are and how to articulate them. I think that's the side of things that the world does not get to see or think about very much. Because it is easy to point at all the consumer failings and the hundreds of messaging products that you continually replenish just in order to kill.Brian: [laugh].Corey: It's—like, what is it? The tree of liberty must be watered periodically from time to time, but the blood of patriots? Yeah. The logo of Google must be watered by the blood of canceled messaging products.Brian: Oh, come on. [laugh].Corey: Yeah. I'm going to be really scared if there's an actual, like, Pub/Sub service. I don't know. That counts as messaging, sort of. I don't know.Brian: [laugh]. Well, thank you. Thank you for the recognition of how far we've come in our trust from enterprises and trust from customers.Corey: I think it's the right path. There's also reputational issues, too. Because in the absence of new data, people don't tend to change their opinion on things very easily. And okay, there was a thing I was using. It got turned off. There was a big kerfuffle. That sticks in people's minds. But I've never seen an article about a Google service saying, “Oh, yeah. It hasn't been turned off or materially changed. In fact, it's gotten better with time. And it's just there working reliably.” You're either invisible, or you're getting yelled at.It feels like it's a microcosm of my early career stage of being a systems administrator. I'm either invisible or the mail system's broke, and everyone wants my head. I don't know what the right answer is—Brian: That was about right to me.Corey: —in this thing. Yeah. I don't know what the right answer on these things is, but you're definitely getting it right. I think the enterprise API endeavors that you've gone through over the past year or two are not broadly known. And frankly, you've definitely are ex-AWS because enterprise APIs is a terrible name for what these things are.Brian: [laugh].Corey: I'll let you explain it. Go ahead. And bonus points if you can do it without sounding like a press release. Take it away.Brian: There are a set of APIs that developers and companies should be able to know are going to be supported for the period of time that they need in order to run their applications and truly bet on them. And that's what we've done.Corey: Yeah. It's effectively a commitment that there will not be meaningful deprecations or changes to the API that are breaking changes without significant notice periods.Brian: Correct.Corey: And to be clear, that is exactly what all of the cloud providers have in their enterprise contracts. They're always notice periods around those things. There are always, at least, certain amounts of time and significant breach penalties in the event that, “Yeah, today, I decided that we were just not going to spin up VMs in that same way as we always have before. Sorry. Sucks to be you.” I don't see that happening on the Google Cloud side of the world very often, not like it once did. And again, we do want to talk about reputations.There are at least four services that I'm aware of that AWS has outright deprecated. One, Sumerian has said we're sunsetting the service in public. But on the other end of the spectrum, RDS on VMWare has been completely memory-holed. There's a blog post or two but nothing else remains in any of the AWS stuff, I'm sure, because that's an, “Enterprise-y” service, they wound up having one on one conversations with customers or there would have been a hue and cry. But every cloud provider does, in the fullness of time, turn some things off as they learn from their customers.Brian: Hmm. I hadn't heard anything about AWS Infinidash for a while either.Corey: No, no. It seems to be one of those great services that we made up on the internet one day for fun. And I love that just from a product marketing perspective. I mean, you know way more about that field than I do given that it's your job, and I'm just sitting here in this cheap seats throwing peanuts at you. But I love the idea of customers just come up and make up a product one day in your space and then the storytelling that immediately happens thereafter. Most companies would kill for something like that just because you would expect on some level to learn so much about how your reputation actually works. When there's a platonic ideal of a service that isn't bothered by pesky things like, “It has to exist,” what do people say about it? And how does that work?And I'm sort of surprised there wasn't more engagement from Amazon on that. It always seems like they're scared to say anything. Which brings me to a marketing question I have for you. You and Amazing have similar challenges—you being Google in this context, not you personally—in that your customers take themselves deadly seriously. And as a result, you have to take yourselves with at least that same level of seriousness. You can't go on Twitter and be the Wendy's Twitter account when you're dealing with enterprise buyers of cloud platforms. I'm kind of amazed, and I'd love to know. How can you manage to say anything at all? Because it just seems like you are so constrained, and there's no possible thing you can say that someone won't take issue with. And yes, some of the time, that someone is me.Brian: Well, let's start with going back to Infinidash a little bit. Yes, you identified one interesting thing about that episode, if I can call it an episode. The thing that I tell you though that didn't surprise me is it shows how much of cloud is actually learned from other people, not from the cloud provider itself. I—you're going to be going to re:Invent. You were at Google Cloud Next. Best thing about the industry conferences is not what the provider does. It's the other people that are there that you learn from. The folks that have done something that you've been trying to do and couldn't figure out how to do, and then they explained it to you, just the relationships that you get that help you understand what's going on in this industry that's changing so fast and has so much going on.And so,   And so, that part didn't surprise me. And that gets a little bit to the second part of your—that we're talking about. “How do you say anything?” As long as you're helping a customer say it. As long as you're helping someone who has been a fan of a product and has done interesting things with it say it, that's how you communicate for the most part, putting a megaphone in front of the people who already understand what's going on and helping their voice be heard, which is a lot more fun, honestly, than creating TV ads and banner ads and all of the stuff that a lot of consumer and traditional companies. We get to celebrate our customers and our creators much, much more.Corey: This episode is sponsored in part by our friends at Uptycs, because they believe that many of you are looking to bolster your security posture with CNAPP and XDR solutions. They offer both cloud and endpoint security in a single UI and data model. Listeners can get Uptycs for up to 1,000 assets through the end of 2023 (that is next year) for $1. But this offer is only available for a limited time on UptycsSecretMenu.com. That's U-P-T-Y-C-S Secret Menu dot com.Corey: I think that it's not super well understood by a lot of folks out there that the official documentation that any cloud provider puts out there is kind of a last resort. Or I'm looking for the specific flag to a specific parameter of a specific command. Great. Sure. But what I really want to do whenever I'm googling how to do something—and yes, that—we're going to be googling—welcome. You've successfully owned that space to the point where it's become common parlance. Good work is I want to see what other people had said. I want to find blog posts, ideally recent ones, talking about how to do the thing that I'm trying to do. If I'm trying to do something relatively not that hard or not that uncommon, if I spin up three web servers behind a load-balancer, and I can't find any community references on how to do that thing, either I'm trying to do something absolutely bizarre and I should re-think it, or there is no community/customer base for the product talking about how to do things with it.And I have noticed a borderline Cambrian explosion over the last few years of the Google Cloud community. I'm seeing folks who do not work at Google, and also who have never worked at Google, and sometimes still think they work at Google in some cases. It's not those folks. It is people who are just building things as a customer. And they, in turn, become very passionate advocates for the platform. And they start creating content on these things.Brian: Yeah. We've been blessed to have, not only, the customer base grow, but essentially the passion among that customer base, and we've certainly tried to help building community and catalyzing the community, but it's been fun to watch how our customers' success turns into our success which turns into customer success. And it's interesting, in particular, to see too how much of that passion comes from people seeing that there is another way to do things.It's clear that many people in our industry knew cloud through the lens of Amazon, knew tech in general through the lenses of Microsoft and Oracle and a lot of other companies. And Google, which we try and respect specifically what people are trying to accomplish and how they know how to do it, we also many ways have taken a more opinionated approach, if you will, to say, “Hey, here's how this could be done in a different way.” And when people find something that's unexpectedly different and also delightful, it's more likely that they're going to be strong advocates and share that passion with the world.Corey: It's a virtuous cycle that leads to the continued growth and success of a platform. Something I've been wondering about in the broader sense, is what happens after this? Because if, let's say for the sake of argument, that one of the major cloud providers decided, “Okay. You know, we're going to turn this stuff off. We've decided we don't really want to be in the cloud business.” It turns out that high-margin businesses that wind up turning into cash monsters as soon as you stop investing heavily in growing them, just kind of throw off so much that, “We don't know what to do with. And we're running out of spaces to store it. So, we're getting out of it.” I don't know how that would even be possible at some point. Because given the amount of time and energy some customers take to migrate in, it would be a decade-long project for them to migrate back out again.So, it feels on some level like on the scale of a human lifetime, that we will be seeing the large public cloud providers, in more or less their current form, for the rest of our lives. Is that hopelessly naïve? Am I missing—am I overestimating how little change happens in the sweep of a human lifetime in technology?Brian: Well, I've been in the tech industry for 27 years now. And I've just seen a continual moving up the stack. Where, you know, there are fundamental changes. I think the PC becoming widespread, fundamental change; mobile, certainly becoming primary computing experience—what I know you call a toilet computer, I call my mobile; that's certainly been a change. Cloud has certainly been a change. And so, there are step functions for sure. But in general, what has been happening is things just keep moving up the stack. And as things move up the stack, there are companies that evolve and learn to do that and provide more value and more value to new folks. Like I talked about how businesspeople are leaders in technology now in a way that they never were before. And you need to give them the value in a way that they can understand it, and they can consume it, and they can trust it. And it's going to continue to move in that direction.And so, what happens then as things move up the stack, the abstractions start happening. And so, there are companies that were just major players in the ‘90s, whether it's Novell or Sun Microsystems or—I was actually getting a tour of the Sunnyvale/Mountain View Google Campuses yesterday. And the tour guide said, “This used to be the site of a company that was called Silicon Graphics. They did something around, like, making things for Avatar.” I felt a little aged at that point.But my point is, there are these companies that were amazing in their time. They didn't move up the stack in a way that met the net set of needs. And it's not like that crater the industry or anything, it's just people were able to move off of it and move up. And I do think that's what we'll see happening.Corey: In some cases, it seems to slip below the waterline and become, effectively, plumbing, where everyone uses it, but no one knows who they are or what they do. The Tier 1 backbone providers these days tend to be in that bucket. Sure, some of them have other businesses, like Verizon. People know who Verizon is, but they're one of the major Tier 1 carriers in the United States just of the internet backbone.Brian: That's right. And that doesn't mean it's not still a great business.Corey: Yeah.Brian: It just means it's not front of mind for maybe the problems you're trying to solve or the opportunities we're trying to capture at that point in time.Corey: So, my last question for you goes circling back to Google Cloud Next. You folks announced an awful lot of things. And most of them, from my perspective, were actually pretty decent. What do you think is the most impactful announcement that you made that the industry largely overlooked?Brian: Most impactful that the industry—well, overlooked might be the wrong way to put this. But there's this really interesting thing happening in the cloud world right now where whereas before companies, kind of, chose their primary cloud writ large, today because multi-cloud is actually happening in the vast majority of companies have things in multiple places, people make—are making also the decision of, “What is going to be my strategic data provider?” And I don't mean data in the sense of the actual data and meta-data and the like, but my data cloud.Corey: Mm-hmm.Brian: How do I choose my data cloud specifically? And there's been this amazing profusion of new data companies that do better ETL or ELT, better data cleaning, better packaging for AI, new techniques for scaling up/scaling down at cost. A lot of really interesting stuff happening in the dataspace. But it's also created almost more silos. And so, the most important announcement that we made probably didn't seem like a really big announcement to a lot of people, but it really was about how we're connecting together more of our data cloud with BigQuery, with unstructured and structured data support, with support for data lakes, including new formats, including Iceberg and Delta and Hudi to come how—Looker is increasingly working with BigQuery in order to make it, so that if you put data into Google Cloud, you not only have these super first-class services that you can use, ranging from databases like Spanner to BigQuery to Looker to AI services, like Vertex AI, but it's also now supporting all these different formats so you can bring third-party applications into that one place. And so, at the big cloud events, it's a new service that is the biggest deal. For us, the biggest deal is how this data cloud is coming together in an open way to let you use the tool that you want to use, whether it's from Google or a third party, all by betting on Google's data cloud.Corey: I'm really impressed by how Google is rather clearly thinking about this from the perspective of the data has to be accessible by a bunch of different things, even though it may take wildly different forms. It is making the data more fluid in that it can go to where the customer needs it to be rather than expecting the customer to come to it where it lives. That, I think, is a trend that we have not seen before in this iteration of the tech industry.Brian: I think you got that—you picked that up very well. And to some degree, if you step back and look at it, it maybe shouldn't be that surprising that Google is adept at that. When you think of what Google search is, how YouTube is essentially another search engine producing videos that deliver on what you're asking for, how information is used with Google Maps, with Google Lens, how it is all about taking information and making it as universally accessible and helpful as possible. And if we can do that for the internet's information, why can't we help businesses do it for their business information? And that's a lot of where Google certainly has a unique approach with Google Cloud.Corey: I really want to thank you for being so generous with your time. If people want to learn more about what you're up to, where's the best place for them to find you?Brian: cloud.google.com for Google Cloud information of course. And if it's still running when this podcast goes, @isforat, I-S-F-O-R-A-T, on Twitter.Corey: And we will put links to both of those in the show notes. Thank you so much for you time. I appreciate it.Brian: Thank you, Corey. It's been good talking with you.Corey: Brian Hall, VP of Product Marketing at Google Cloud. I'm Cloud Economist Corey Quinn and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice. Whereas, if you've hated this podcast, please, leave a five-star review on your podcast platform of choice along with an insulting angry comment dictating that, “No. Large companies make ten-year-long commitments casually all the time.”Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Depois de uma rápida sessão nostalgia com o Google Reader, Bia e Marcus comentam o anúncio (e os concorrentes) do Amazon Kindle Scribe.

Sam Bankman-Fried finally scoops up Voyager's assets. Meta says Russia has launched the biggest disinformation campaign of the war. Nreal has finally brough the first real contender for the AR wars to American shores for the first time. And would you consider a Metaverse white paper from the sci-fi writer than inspired the very notion of a Metaverse?Sponsors:Online.UC.eduMasterworks.com/ride **Links:Crypto Exchange FTX Wins Bankrupt Firm Voyager's Assets (Bloomberg)‘Smash and grab': Meta uncovers Russia's ‘largest and most complex' info op since the war began (Protocol)Meta makes it easier to switch between Facebook and Instagram accounts (CNBC)Nreal's $379 AR glasses launch in the US today (The Verge)If you still miss Google Reader, Substack has a new web-based RSS client (The Verge)Walmart enters the metaverse with Roblox experiences aimed at younger shoppers (CNBC)Neal Stephenson's Lamina1 drops white paper on building the open metaverse (GamesBeat)**Net est. returns for all realized and unrealized offerings is 15.3%, from inception through 6/30/22. See important Reg A and performance disclosures at masterworks.io/cdSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

About AllenAllen is a cloud architect at Tyler Technologies. He helps modernize government software by creating secure, highly scalable, and fault-tolerant serverless applications.Allen publishes content regularly about serverless concepts and design on his blog - Ready, Set Cloud!Links Referenced: Ready, Set, Cloud blog: https://readysetcloud.io Tyler Technologies: https://www.tylertech.com/ Twitter: https://twitter.com/allenheltondev Linked: https://www.linkedin.com/in/allenheltondev/ TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored in part by our friends at AWS AppConfig. Engineers love to solve, and occasionally create, problems. But not when it's an on-call fire-drill at 4 in the morning. Software problems should drive innovation and collaboration, NOT stress, and sleeplessness, and threats of violence. That's why so many developers are realizing the value of AWS AppConfig Feature Flags. Feature Flags let developers push code to production, but hide that that feature from customers so that the developers can release their feature when it's ready. This practice allows for safe, fast, and convenient software development. You can seamlessly incorporate AppConfig Feature Flags into your AWS or cloud environment and ship your Features with excitement, not trepidation and fear. To get started, go to snark.cloud/appconfig. That's snark.cloud/appconfig.Corey: I come bearing ill tidings. Developers are responsible for more than ever these days. Not just the code that they write, but also the containers and the cloud infrastructure that their apps run on. Because serverless means it's still somebody's problem. And a big part of that responsibility is app security from code to cloud. And that's where our friend Snyk comes in. Snyk is a frictionless security platform that meets developers where they are - Finding and fixing vulnerabilities right from the CLI, IDEs, Repos, and Pipelines. Snyk integrates seamlessly with AWS offerings like code pipeline, EKS, ECR, and more! As well as things you're actually likely to be using. Deploy on AWS, secure with Snyk. Learn more at Snyk.co/scream That's S-N-Y-K.co/screamCorey: Welcome to Screaming in the Cloud. I'm Corey Quinn. Every once in a while I wind up stumbling into corners of the internet that I previously had not traveled. Somewhat recently, I wound up having that delightful experience again by discovering readysetcloud.io, which has a whole series of, I guess some people might call it thought leadership, I'm going to call it instead how I view it, which is just amazing opinion pieces on the context of serverless, mixed with APIs, mixed with some prognostications about the future.Allen Helton by day is a cloud architect at Tyler Technologies, but that's not how I encountered you. First off, Allen, thank you for joining me.Allen: Thank you, Corey. Happy to be here.Corey: I was originally pointed towards your work by folks in the AWS Community Builder program, of which we both participate from time to time, and it's one of those, “Oh, wow, this is amazing. I really wish I'd discovered some of this sooner.” And every time I look through your back catalog, and I click on a new post, I see things that are either I've really agree with this or I can't stand this opinion, I want to fight about it, but more often than not, it's one of those recurring moments that I love: “Damn, I wish I had written something like this.” So first, you're absolutely killing it on the content front.Allen: Thank you, Corey, I appreciate that. The content that I make is really about the stuff that I'm doing at work. It's stuff that I'm passionate about, stuff that I'd spend a decent amount of time on, and really the most important thing about it for me, is it's stuff that I'm learning and forming opinions on and wants to share with others.Corey: I have to say, when I saw that you were—oh, your Tyler Technologies, which sounds for all the world like, oh, it's a relatively small consultancy run by some guy presumably named Tyler, and you know, it's a petite team of maybe 20, 30 people on the outside. Yeah, then I realized, wait a minute, that's not entirely true. For example, for starters, you're publicly traded. And okay, that does change things a little bit. First off, who are you people? Secondly, what do you do? And third, why have I never heard of you folks, until now?Allen: Tyler is the largest company that focuses completely on the public sector. We have divisions and products for pretty much everything that you can imagine that's in the public sector. We have software for schools, software for tax and appraisal, we have software for police officers, for courts, everything you can think of that runs the government can and a lot of times is run on Tyler software. We've been around for decades building our expertise in the domain, and the reason you probably haven't heard about us is because you might not have ever been in trouble with the law before. If you [laugh] if you have been—Corey: No, no, I learned very early on in the course of my life—which will come as a surprise to absolutely no one who spent more than 30 seconds with me—that I have remarkably little filter and if ten kids were the ones doing something wrong, I'm the one that gets caught. So, I spent a lot of time in the principal's office, so this taught me to keep my nose clean. I'm one of those squeaky-clean types, just because I was always terrified of getting punished because I knew I would get caught. I'm not saying this is the right way to go through life necessarily, but it did have the side benefit of, no, I don't really engage with law enforcement going throughout the course of my life.Allen: That's good. That's good. But one exposure that a lot of people get to Tyler is if you look at the bottom of your next traffic ticket, it'll probably say Tyler Technologies on the bottom there.Corey: Oh, so you're really popular in certain circles, I'd imagine?Allen: Super popular. Yes, yes. And of course, you get all the benefits of writing that code that says ‘if defendant equals Allen Helton then return.'Corey: I like that. You get to have the exception cases built in that no one's ever going to wind up looking into.Allen: That's right. Yes.Corey: The idea of what you're doing makes an awful lot of sense. There's a tremendous need for a wide variety of technical assistance in the public sector. What surprises me, although I guess it probably shouldn't, is how much of your content is aimed at serverless technologies and API design, which to my way of thinking, isn't really something that public sector has done a lot with. Clearly I'm wrong.Allen: Historically, you're not wrong. There's an old saying that government tends to run about ten years behind on technology. Not just technology, but all over the board and runs about ten years behind. And until recently, that's really been true. There was a case last year, a situation last year where one of the state governments—I don't remember which one it was—but they were having a crisis because they couldn't find any COBOL developers to come in and maintain their software that runs the state.And it's COBOL; you're not going to find a whole lot of people that have that skill. A lot of those people are retiring out. And what's happening is that we're getting new people sitting in positions of power and government that want innovation. They know about the cloud and they want to be able to integrate with systems quickly and easily, have little to no onboarding time. You know, there are people in power that have grown up with technology and understand that, well, with everything else, I can be up and running in five or ten minutes. I cannot do this with the software I'm consuming now.Corey: My opinion on it is admittedly conflicted because on the one hand, yeah, I don't think that governments should be running on COBOL software that runs on mainframes that haven't been supported in 25 years. Conversely, I also don't necessarily want them being run like a seed series startup, where, “Well, I wrote this code last night, and it's awesome, so off I go to production with it.” Because I can decide not to do business anymore with Twitter for Pets, and I could go on to something else, like PetFlicks, or whatever it is I choose to use. I can't easily opt out of my government. The decisions that they make stick and that is going to have a meaningful impact on my life and everyone else's life who is subject to their jurisdiction. So, I guess I don't really know where I believe the proper, I guess, pace of technological adoption should be for governments. Curious to get your thoughts on this.Allen: Well, you certainly don't want anything that's bleeding edge. That's one of the things that we kind of draw fine lines around. Because when we're dealing with government software, we're dealing with, usually, critically sensitive information. It's not medical records, but it's your criminal record, and it's things like your social security number, it's things that you can't have leaking out under any circumstances. So, the things that we're building on are things that have proven out to be secure and have best practices around security, uptime, reliability, and in a lot of cases as well, and maintainability. You know, if there are issues, then let's try to get those turned around as quickly as we can because we don't want to have any sort of downtime from the software side versus the software vendor side.Corey: I want to pivot a little bit to some of the content you've put out because an awful lot of it seems to be, I think I'll call it variations on a theme. For example, I just read some recent titles, and to illustrate my point, “Going API First: Your First 30 Days,” “Solutions Architect Tips how to Design Applications for Growth,” “3 Things to Know Before Building A Multi-Tenant Serverless App.” And the common thread that I see running through all of these things are these are things that you tend to have extraordinarily strong and vocal opinions about only after dismissing all of them the first time and slapping something together, and then sort of being forced to live with the consequences of the choices that you've made, in some cases you didn't realize you were making at the time. Are you one of those folks that has the wisdom to see what's coming down the road, or did you do what the rest of us do and basically learn all this stuff by getting it hilariously wrong and having to careen into rebound situations as a result?Allen: [laugh]. I love that question. I would like to say now, I feel like I have the vision to see something like that coming. Historically, no, not at all. Let me talk a little bit about how I got to where I am because that will shed a lot of context on that question.A few years ago, I was put into a position at Tyler that said, “Hey, go figure out this cloud thing.” Let's figure out what we need to do to move into the cloud safely, securely, quickly, all that rigmarole. And so, I did. I got to hand-select team of engineers from people that I worked with at Tyler over the past few years, and we were basically given free rein to learn. We were an R&D team, a hundred percent R&D, for about a year's worth of time, where we were learning about cloud concepts and theory and building little proof of concepts.CI/CD, serverless, APIs, multi-tenancy, a whole bunch of different stuff. NoSQL was another one of the things that we had to learn. And after that year of R&D, we were told, “Okay, now go do something with that. Go build this application.” And we did, building on our theory our cursory theory knowledge. And we get pretty close to go live, and then the business says, “What do you do in this scenario? What do you do in that scenario? What do you do here?”Corey: “I update my resume and go work somewhere else. Where's the hard part here?”Allen: [laugh].Corey: Turns out, that's not a convincing answer.Allen: Right. So, we moved quickly. And then I wouldn't say we backpedaled, but we hardened for a long time before the—prior to the go-live, with the lessons that we've learned with the eyes of Tyler, the mature enterprise company, saying, “These are the things that you have to make sure that you take into consideration in an actual production application.” One of the things that I always pushed—I was a manager for a few years of all these cloud teams—I always push do it; do it right; do it better. Right?It's kind of like crawl, walk, run. And if you follow my writing from the beginning, just looking at the titles and reading them, kind of like what you were doing, Corey, you'll see that very much. You'll see how I talk about CI/CD, you'll see me how I talk about authorization, you'll see me how I talk about multi-tenancy. And I kind of go in waves where maybe a year passes and you see my content revisit some of the topics that I've done in the past. And they're like, “No, no, no, don't do what I said before. It's not right.”Corey: The problem when I'm writing all of these things that I do, for example, my entire newsletter publication pipeline is built on a giant morass of Lambda functions and API Gateways. It's microservices-driven—kind of—and each microservice is built, almost always, with a different framework. Lately, all the new stuff is CDK. I started off with the serverless framework. There are a few other things here and there.And it's like going architecting, back in time as I have to make updates to these things from time to time. And it's the problem with having done all that myself is that I already know the answer to, “What fool designed this?” It's, well, you're basically watching me learn what I was, doing bit by bit. I'm starting to believe that the right answer on some level, is to build an inherent shelf-life into some of these things. Great, in five years, you're going to come back and re-architect it now that you know how this stuff actually works rather than patching together 15 blog posts by different authors, not all of whom are talking about the same thing and hoping for the best.Allen: Yep. That's one of the things that I really like about serverless, I view that as a giant pro of doing Serverless is that when we revisit with the lessons learned, we don't have to refactor everything at once like if it was just a big, you know, MVC controller out there in the sky. We can refactor one Lambda function at a time if now we're using a new version of the AWS SDK, or we've learned about a new best practice that needs to go in place. It's a, “While you're in there, tidy up, please,” kind of deal.Corey: I know that the DynamoDB fanatics will absolutely murder me over this one, but one of the reasons that I have multiple Dynamo tables that contain, effectively, variations on the exact same data, is because I want to have the dependency between the two different microservices be the API, not, “Oh, and under the hood, it's expecting this exact same data structure all the time.” But it just felt like that was the wrong direction to go in. That is the justification I use for myself why I run multiple DynamoDB tables that [laugh] have the same content. Where do you fall on the idea of data store separation?Allen: I'm a big single table design person myself, I really like the idea of being able to store everything in the same table and being able to create queries that can return me multiple different types of entity with one lookup. Now, that being said, one of the issues that we ran into, or one of the ambiguous areas when we were getting started with serverless was, what does single table design mean when you're talking about microservices? We were wondering does single table mean one DynamoDB table for an entire application that's composed of 15 microservices? Or is it one table per microservice? And that was ultimately what we ended up going with is a table per microservice. Even if multiple microservices are pushed into the same AWS account, we're still building that logical construct of a microservice and one table that houses similar entities in the same domain.Corey: So, something I wish that every service team at AWS would do as a part of their design is draw the architecture of an application that you're planning to build. Great, now assume that every single resource on that architecture diagram lives in its own distinct AWS account because somewhere in some customer, there's going to be an account boundary at every interconnection point along the way. And so, many services don't do that where it's, “Oh, that thing and the other thing has to be in the same account.” So, people have to write their own integration shims, and it makes doing the right thing of putting different services into distinct bounded AWS accounts for security or compliance reasons way harder than I feel like it needs to be.Allen: [laugh]. Totally agree with you on that one. That's one of the things that I feel like I'm still learning about is the account-level isolation. I'm still kind of early on, personally, with my opinions in how we're structuring things right now, but I'm very much of a like opinion that deploying multiple things into the same account is going to make it too easy to do something that you shouldn't. And I just try not to inherently trust people, in the sense that, “Oh, this is easy. I'm just going to cross that boundary real quick.”Corey: For me, it's also come down to security risk exposure. Like my lasttweetinaws.com Twitter shitposting thread client lives in a distinct AWS account that is separate from the AWS account that has all of our client billing data that lives within it. The idea being that if you find a way to compromise my public-facing Twitter client, great, the blast radius should be constrained to, “Yay, now you can, I don't know, spin up some cryptocurrency mining in my AWS account and I get to look like a fool when I beg AWS for forgiveness.”But that should be the end of it. It shouldn't be a security incident because I should not have the credit card numbers living right next to the funny internet web thing. That sort of flies in the face of the original guidance that AWS gave at launch. And right around 2008-era, best practices were one customer, one AWS account. And then by 2012, they had changed their perspective, but once you've made a decision to build multiple services in a single account, unwinding and unpacking that becomes an incredibly burdensome thing. It's about the equivalent of doing a cloud migration, in some ways.Allen: We went through that. We started off building one application with the intent that it was going to be a siloed application, a one-off, essentially. And about a year into it, it's one of those moments of, “Oh, no. What we're building is not actually a one-off. It's a piece to a much larger puzzle.”And we had a whole bunch of—unfortunately—tightly coupled things that were in there that we're assuming that resources were going to be in the same AWS account. So, we ended up—how long—I think we took probably two months, which in the grand scheme of things isn't that long, but two months, kind of unwinding the pieces and decoupling what was possible at the time into multiple AWS accounts, kind of, segmented by domain, essentially. But that's hard. AWS puts it, you know, it's those one-way door decisions. I think this one was a two-way door, but it locked and you could kind of jimmy the lock on the way back out.Corey: And you could buzz someone from the lobby to let you back in. Yeah, the biggest problem is not necessarily the one-way door decisions. It's the one-way door decisions that you don't realize you're passing through at the time that you do them. Which, of course, brings us to a topic near and dear to your heart—and I only recently started have opinions on this myself—and that is the proper design of APIs, which I'm sure will incense absolutely no one who's listening to this. Like, my opinions on APIs start with well, probably REST is the right answer in this day and age. I had people, like, “Well, I don't know, GraphQL is pretty awesome.” Like, “Oh, I'm thinking SOAP,” and people look at me like I'm a monster from the Black Lagoon of centuries past in XML-land. So, my particular brand of strangeness side, what do you see that people are doing in the world of API design that is the, I guess, most common or easy to make mistakes that you really wish they would stop doing?Allen: If I could boil it down to one word, fundamentalism. Let me unpack that for you.Corey: Oh, please, absolutely want to get a definition on that one.Allen: [laugh]. I approach API design from a developer experience point of view: how easy is it for both internal and external integrators to consume and satisfy the business processes that they want to accomplish? And a lot of times, REST guidelines, you know, it's all about entity basis, you know, drill into the appropriate entities and name your endpoints with nouns, not verbs. I'm actually very much onto that one.But something that you could easily do, let's say you have a business process that given a fundamentally correct RESTful API design takes ten API calls to satisfy. You could, in theory, boil that down to maybe three well-designed endpoints that aren't, quote-unquote, “RESTful,” that make that developer experience significantly easier. And if you were a fundamentalist, that option is not even on the table, but thinking about it pragmatically from a developer experience point of view, that might be the better call. So, that's one of the things that, I know feels like a hot take. Every time I say it, I get a little bit of flack for it, but don't be a fundamentalist when it comes to your API designs. Do something that makes it easier while staying in the guidelines to do what you want.Corey: For me the problem that I've kept smacking into with API design, and it honestly—let me be very clear on this—my first real exposure to API design rather than API consumer—which of course, I complain about constantly, especially in the context of the AWS inconsistent APIs between services—was when I'm building something out, and I'm reading the documentation for API Gateway, and oh, this is how you wind up having this stage linked to this thing, and here's the endpoint. And okay, great, so I would just populate—build out a structure or a schema that has the positional parameters I want to use as variables in my function. And that's awesome. And then I realized, “Oh, I might want to call this a different way. Aw, crap.” And sometimes it's easy; you just add a different endpoint. Other times, I have to significantly rethink things. And I can't shake the feeling that this is an entire discipline that exists that I just haven't had a whole lot of exposure to previously.Allen: Yeah, I believe that. One of the things that you could tie a metaphor to for what I'm saying and kind of what you're saying, is AWS SAM, the Serverless Application Model, all it does is basically macros CloudFormation resources. It's just a transform from a template into CloudFormation. CDK does same thing. But what the developers of SAM have done is they've recognized these business processes that people do regularly, and they've made these incredibly easy ways to satisfy those business processes and tie them all together, right?If I want to have a Lambda function that is backed behind a endpoint, an API endpoint, I just have to add four or five lines of YAML or JSON that says, “This is the event trigger, here's the route, here's the API.” And then it goes and does four, five, six different things. Now, there's some engineers that don't like that because sometimes that feels like magic. Sometimes a little bit magic is okay.Corey: This episode is sponsored in part by our friends at Sysdig. Sysdig secures your cloud from source to run. They believe, as do I, that DevOps and security are inextricably linked. If you wanna learn more about how they view this, check out their blog, it's definitely worth the read. To learn more about how they are absolutely getting it right from where I sit, visit Sysdig.com and tell them that I sent you. That's S Y S D I G.com. And my thanks to them for their continued support of this ridiculous nonsense.Corey: I feel like one of the benefits I've had with the vast majority of APIs that I've built is that because this is all relatively small-scale stuff for what amounts to basically shitposting for the sake of entertainment, I'm really the only consumer of an awful lot of these things. So, I get frustrated when I have to backtrack and make changes and teach other microservices to talk to this thing that has now changed. And it's frustrating, but I have the capacity to do that. It's just work for a period of time. I feel like that equation completely shifts when you have published this and it is now out in the world, and it's not just users, but in many cases paying customers where you can't really make those changes without significant notice, and every time you do you're creating work for those customers, so you have to be a lot more judicious about it.Allen: Oh, yeah. There is a whole lot of governance and practice that goes into production-level APIs that people integrate with. You know, they say once you push something out the door into production that you're going to support it forever. I don't disagree with that. That seems like something that a lot of people don't understand.And that's one of the reasons why I push API-first development so hard in all the content that I write is because you need to be intentional about what you're letting out the door. You need to go in and work, not just with the developers, but your product people and your analysts to say, what does this absolutely need to do, and what does it need to do in the future? And you take those things, and you work with analysts who want specifics, you work with the engineers to actually build it out. And you're very intentional about what goes out the door that first time because once it goes out with a mistake, you're either going to version it immediately or you're going to make some people very unhappy when you make a breaking change to something that they immediately started consuming.Corey: It absolutely feels like that's one of those things that AWS gets astonishingly right. I mean, I had the privilege of interviewing, at the time, Jeff Barr and then Ariel Kelman, who was their head of marketing, to basically debunk a bunch of old myths. And one thing that they started talking about extensively was the idea that an API is fundamentally a promise to your customers. And when you make a promise, you'd better damn well intend on keeping it. It's why API deprecations from AWS are effectively unique whenever something happens.It's the, this is a singular moment in time when they turn off a service or degrade old functionality in favor of new. They can add to it, they can launch a V2 of something and then start to wean people off by calling the old one classic or whatnot, but if I built something on AWS in 2008 and I wound up sleeping until today, and go and try and do the exact same thing and deploy it now, it will almost certainly work exactly as it did back then. Sure, reliability is going to be a lot better and there's a crap ton of features and whatnot that I'm not taking advantage of, but that fundamental ability to do that is awesome. Conversely, it feels like Google Cloud likes to change around a lot of their API stories almost constantly. And it's unplanned work that frustrates the heck out of me when I'm trying to build something stable and lasting on top of it.Allen: I think it goes to show the maturity of these companies as API companies versus just vendors. It's one of the things that I think AWS does [laugh]—Corey: You see the similar dichotomy with Microsoft and Apple. Microsoft's new versions of Windows generally still have functionalities in them to support stuff that was written in the '90s for a few use cases, whereas Apple's like, “Oh, your computer's more than 18-months old? Have you tried throwing it away and buying a new one? And oh, it's a new version of Mac OS, so yeah, maybe the last one would get security updates for a year and then get with the times.” And I can't shake the feeling that the correct answer is in some way, both of those, depending upon who your customer is and what it is you're trying to achieve.If Microsoft adopted the Apple approach, their customers would mutiny, and rightfully so; the expectation has been set for decades that isn't what happens. Conversely, if Apple decided now we're going to support this version of Mac OS in perpetuity, I don't think a lot of their application developers wouldn't quite know what to make of that.Allen: Yeah. I think it also comes from a standpoint of you better make it worth their while if you're going to move their cheese. I'm not a Mac user myself, but from what I hear for Mac users—and this could be rose-colored glasses—but is that their stuff works phenomenally well. You know, when a new thing comes out—Corey: Until it doesn't, absolutely. It's—whenever I say things like that on this show, I get letters. And it's, “Oh, yeah, really? They'll come up with something that is a colossal pain in the ass on Mac.” Like, yeah, “Try building a system-wide mute key.”It's yeah, that's just a hotkey away on windows and here in Mac land. It's, “But it makes such beautiful sounds. Why would you want them to be quiet?” And it's, yeah, it becomes this back-and-forth dichotomy there. And you can even explain it to iPhones as well and the Android ecosystem where it's, oh, you're going to support the last couple of versions of iOS.Well, as a developer, I don't want to do that. And Apple's position is, “Okay, great.” Almost half of the mobile users on the planet will be upgrading because they're in the ecosystem. Do you want us to be able to sell things those people are not? And they're at a point of scale where they get to dictate those terms.On some level, there are benefits to it and others, it is intensely frustrating. I don't know what the right answer is on the level of permanence on that level of platform. I only have slightly better ideas around the position of APIs. I will say that when AWS deprecates something, they reach out individually to affected customers, on some level, and invariably, when they say, “This is going to be deprecated as of August 31,” or whenever it is, yeah, it is going to slip at least twice in almost every case, just because they're not going to turn off a service that is revenue-bearing or critical-load-bearing for customers without massive amounts of notice and outreach, and in some cases according to rumor, having engineers reach out to help restructure things so it's not as big of a burden on customers. That's a level of customer focus that I don't think most other companies are capable of matching.Allen: I think that comes with the size and the history of Amazon. And one of the things that they're doing right now, we've used Amazon Cloud Cams for years, in my house. We use them as baby monitors. And they—Corey: Yea, I saw this I did something very similar with Nest. They didn't have the Cloud Cam at the right time that I was looking at it. And they just announced that they're going to be deprecating. They're withdrawing them for sale. They're not going to support them anymore. Which, oh at Amazon—we're not offering this anymore. But you tell the story; what are they offering existing customers?Allen: Yeah, so slightly upset about it because I like my Cloud Cams and I don't want to have to take them off the wall or wherever they are to replace them with something else. But what they're doing is, you know, they gave me—or they gave all the customers about eight months head start. I think they're going to be taking them offline around Thanksgiving this year, just mid-November. And what they said is as compensation for you, we're going to send you a Blink Cam—a Blink Mini—for every Cloud Cam that you have in use, and then we are going to gift you a year subscription to the Pro for Blink.Corey: That's very reasonable for things that were bought years ago. Meanwhile, I feel like not to be unkind or uncharitable here, but I use Nest Cams. And that's a Google product. I half expected if they ever get deprecated, I'll find out because Google just turns it off in the middle of the night—Allen: [laugh].Corey: —and I wake up and have to read a blog post somewhere that they put an update on Nest Cams, the same way they killed Google Reader once upon a time. That's slightly unfair, but the fact that joke even lands does say a lot about Google's reputation in this space.Allen: For sure.Corey: One last topic I want to talk with you about before we call it a show is that at the time of this recording, you recently had a blog post titled, “What does the Future Hold for Serverless?” Summarize that for me. Where do you see this serverless movement—if you'll forgive the term—going?Allen: So, I'm going to start at the end. I'm going to work back a little bit on what needs to happen for us to get there. I have a feeling that in the future—I'm going to be vague about how far in the future this is—that we'll finally have a satisfied promise of all you're going to write in the future is business logic. And what does that mean? I think what can end up happening, given the right focus, the right companies, the right feedback, at the right time, is we can write code as developers and have that get pushed up into the cloud.And a phrase that I know Jeremy Daly likes to say ‘infrastructure from code,' where it provisions resources in the cloud for you based on your use case. I've developed an application and it gets pushed up in the cloud at the time of deploying it, optimized resource allocation. Over time, what will happen—with my future vision—is when you get production traffic going through, maybe it's spiky, maybe it's consistently at a scale that outperforms the resources that it originally provisioned. We can have monitoring tools that analyze that and pick that out, find the anomalies, find the standard patterns, and adjust that infrastructure that it deployed for you automatically, where it's based on your production traffic for what it created, optimizes it for you. Which is something that you can't do on an initial deployment right now. You can put what looks best on paper, but once you actually get traffic through your application, you realize that, you know, what was on paper might not be correct.Corey: You ever noticed that whiteboard diagrams never show the reality, and they're always aspirational, and they miss certain parts? And I used to think that this was the symptom I had from working at small, scrappy companies because you know what, those big tech companies, everything they build is amazing and awesome. I know it because I've seen their conference talks. But I've been a consultant long enough now, and for a number of those companies, to realize that nope, everyone's infrastructure is basically a trash fire at any given point in time. And it works almost in spite of itself, rather than because of it.There is no golden path where everything is shiny, new and beautiful. And that, honestly, I got to say, it was really [laugh] depressing when I first discovered it. Like, oh, God, even these really smart people who are so intelligent they have to have extra brain packs bolted to their chests don't have the magic answer to all of this. The rest of us are just screwed, then. But we find ways to make it work.Allen: Yep. There's a quote, I wish I remembered who said it, but it was a military quote where, “No battle plan survives impact with the enemy—first contact with the enemy.” It's kind of that way with infrastructure diagrams. We can draw it out however we want and then you turn it on in production. It's like, “Oh, no. That's not right.”Corey: I want to mix the metaphors there and say, yeah, no architecture survives your first fight with a customer. Like, “Great, I don't think that's quite what they're trying to say.” It's like, “What, you don't attack your customers? Pfft, what's your customer service line look like?” Yeah, it's… I think you're onto something.I think that inherently everything beyond the V1 design of almost anything is an emergent property where this is what we learned about it by running it and putting traffic through it and finding these problems, and here's how it wound up evolving to account for that.Allen: I agree. I don't have anything to add on that.Corey: [laugh]. Fair enough. I really want to thank you for taking so much time out of your day to talk about how you view these things. If people want to learn more, where is the best place to find you?Allen: Twitter is probably the best place to find me: @AllenHeltonDev. I have that username on all the major social platforms, so if you want to find me on LinkedIn, same thing: AllenHeltonDev. My blog is always open as well, if you have any feedback you'd like to give there: readysetcloud.io.Corey: And we will, of course, put links to that in the show notes. Thanks again for spending so much time talking to me. I really appreciate it.Allen: Yeah, this was fun. This was a lot of fun. I love talking shop.Corey: It shows. And it's nice to talk about things I don't spend enough time thinking about. Allen Helton, cloud architect at Tyler Technologies. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this podcast, please leave a five-star review on your podcast platform of choice along with an angry comment that I will reject because it was not written in valid XML.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

Lara Croft első élmények Persona 4 “sajtreszelő” Marvel Heroes béta mi lesz velünk Google Reader nélkül? Fez Steam és iOS irányba kacsingat Riccitello az EA-tól, Ron Gilbert a Double Finetól lép le Final Fantasy XV PS4 exkluzív lesz? az V pedig jön mobiltelefonra? és persze Battlefield… a BF4 megjelenése előtt kezdődik a felhajtás (Eredeti megjelenés: 2013.03.24.)

Dr. Brian Sovryn--the Golden Stallion--is here for another SOVRYN REWIND! SOVRYN REWIND comprises episodes from Sovryn Tech's long history that you may have missed...but you don't want to miss it now! Below are the original show notes, with some updated links and info: Sovryn Tech Ep. 0014: "Cock Rock" Could the Romans have built a digital computer? Stars that are older than the universe? Also, what do to about Google Reader, a little music, and much, much more... Special Guest: None Stories of the Week: —”Could the Ancient Romans Have Built A Digital Computer?” Link: gizmodo.com/5988619/could-the-a…-a-digital-computer Tech Roulette: —“Strange ‘Methusalah' Star Looks Older Than the Universe" Link: www.space.com/20112-oldest-known….html?cmpid=514630 Website of the Week: —“Free Music Theory Lessons from a Great Musician" Link: hannahhoffman.net/ Listener E-Mail: —”A Listener Response to the GGGG's” Software of the Week: —“Feedly: Your Google Reader Replacement” Link: www.feedly.com/ Game Talk: —“Video Games Gave Him the Chance to Prove He's an American" Link: tinyurl.com/d6lf6fr Hacker Stories: —”Hackers Publish CIA Director's Financial Records” Link: rt.com/usa/hackers-cia-brenn…inancial-records-334/ —”Guccifer Hacks Hillary Clinton's E-mails” Link: tinyurl.com/c9ateo5 Pick of the Week: —"Brian Sovryn's Favorite Band of All Time: KISS” Link: www.kissonline.com/ ------------------------------------------------------------------------- Donate with BTC: 3GYKVWkVE6iAYEnExfiNfCHJkSDFYWEs43 Donate with CashApp: $sovryntech Donate with Venmo: @bsovryn You can e-mail the show at: questions@sovryntech.com ------------------------------------------------------------------------- http://sovryntech.com --- Send in a voice message: https://anchor.fm/sovryn/message Support this podcast: https://anchor.fm/sovryn/support

About CaseyCasey spends his days leveraging AWS to help organizations improve the speed at which they deliver software. With a background in software development, he has spent the past 20 years architecting, building, and supporting software systems for organizations ranging from startups to Fortune 500 enterprises.Links Referenced: “17 Ways to Run Containers in AWS”: https://www.lastweekinaws.com/blog/the-17-ways-to-run-containers-on-aws/ “17 More Ways to Run Containers on AWS”: https://www.lastweekinaws.com/blog/17-more-ways-to-run-containers-on-aws/ kubernetestheeasyway.com: https://kubernetestheeasyway.com snark.cloud/quinntainers: https://snark.cloud/quinntainers ECS Chargeback: https://github.com/gaggle-net/ecs-chargeback  twitter.com/nektos: https://twitter.com/nektos TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is sponsored by our friends at Revelo. Revelo is the Spanish word of the day, and its spelled R-E-V-E-L-O. It means “I reveal.” Now, have you tried to hire an engineer lately? I assure you it is significantly harder than it sounds. One of the things that Revelo has recognized is something I've been talking about for a while, specifically that while talent is evenly distributed, opportunity is absolutely not. They're exposing a new talent pool to, basically, those of us without a presence in Latin America via their platform. It's the largest tech talent marketplace in Latin America with over a million engineers in their network, which includes—but isn't limited to—talent in Mexico, Costa Rica, Brazil, and Argentina. Now, not only do they wind up spreading all of their talent on English ability, as well as you know, their engineering skills, but they go significantly beyond that. Some of the folks on their platform are hands down the most talented engineers that I've ever spoken to. Let's also not forget that Latin America has high time zone overlap with what we have here in the United States, so you can hire full-time remote engineers who share most of the workday as your team. It's an end-to-end talent service, so you can find and hire engineers in Central and South America without having to worry about, frankly, the colossal pain of cross-border payroll and benefits and compliance because Revelo handles all of it. If you're hiring engineers, check out revelo.io/screaming to get 20% off your first three months. That's R-E-V-E-L-O dot I-O slash screaming.Corey: Couchbase Capella Database-as-a-Service is flexible, full-featured and fully managed with built in access via key-value, SQL, and full-text search. Flexible JSON documents aligned to your applications and workloads. Build faster with blazing fast in-memory performance and automated replication and scaling while reducing cost. Capella has the best price performance of any fully managed document database. Visit couchbase.com/screaminginthecloud to try Capella today for free and be up and running in three minutes with no credit card required. Couchbase Capella: make your data sing.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. My guest today is someone that I had the pleasure of meeting at re:Invent last year, but we'll get to that story in a minute. Casey Lee is the CTO with a company called Gaggle, which is—as they frame it—saving lives. Now, that seems to be a relatively common position that an awful lot of different tech companies take. “We're saving lives here.” It's, “You show banner ads and some of them are attack platforms for JavaScript malware. Let's be serious here.” Casey, thank you for joining me, and what makes the statement that Gaggle saves lives not patently ridiculous?Casey: Sure. Thanks, Corey. Thanks for having me on the show. So Gaggle, we're ed-tech company. We sell software to school districts, and school districts use our software to help protect their students while the students use the school-issued Google or Microsoft accounts.So, we're looking for signs of bullying, harassment, self-harm, and potentially suicide from K-12 students while they're using these platforms. They will take the thoughts, concerns, emotions they're struggling with and write them in their school-issued accounts. We detect that and then we notify the school districts, and they get the students the help they need before they can do any permanent damage to themselves. We protect about 6 million students throughout the US. We ingest a lot of content.Last school year, over 6 billion files, about the equal number of emails ingested. We're looking for concerning content and then we have humans review the stuff that our machine learning algorithms detect and flag. About 40 million items had to go in front of humans last year, resulted in about 20,000 what we call PSSes. These are Possible Student Situations where students are talking about harming themselves or harming others. And that resulted in what we like to track as lives saved. 1400 incidents last school year where a student was dealing with suicide ideation, they were planning to take their own lives. We detect that and get them help within minutes before they can act on that. That's what Gaggle has been doing. We're using tech, solving tech problems, and also saving lives as we do it.Corey: It's easy to lob a criticism at some of the things you're alluding to, the idea of oh, you're using machine learning on student data for young kids, yadda, yadda, yadda. Look at the outcome, look at the privacy controls you have in place, and look at the outcomes you're driving to. Now, I don't necessarily trust the number of school administrations not to become heavy-handed and overbearing with it, but let's be clear, that's not the intent. That is not what the success stories you have alluded to. I've got to say I'm a fan, so thanks for doing what you're doing. I don't say that very often to people who work in tech companies.Casey: Cool. Thanks, Corey.Corey: But let's rewind a bit because you and I had passed like ships in the night on Twitter for a while, but last year at re:Invent something odd happened. First, my business partner procrastinated at getting his ticket—that's not the odd part; he does that a lot—but then suddenly ticket sales slammed shut and none were to be had anywhere. You reached out with a, “Hey, I have a spare ticket because someone can't go. Let me get it to you.” And I said, “Terrific. Let me pay you for the ticket and take you to dinner.”You said, “Yes on the dinner, but I'd rather you just look at my AWS bill and don't worry about the cost of the ticket.” “All right,” said I. I know a deal when I see one. We grabbed dinner at the Venetian. I said, “Bust out your laptop.” And you said, “Oh, I was kidding.” And I said, “Great. I wasn't. Bust it out.”And you went from laughing to taking notes in about the usual time that happens when I start looking at these things. But how was your recollection of that? I always tend to romanticize some of these things. Like, “And then everyone's restaurant just turned, stopped, and clapped the entire time.” Maybe that part didn't happen.Casey: Everything was right up until the clapping part. That was a really cool experience. I appreciate you walking through that with me. Yeah, we've got lots of opportunity to save on our AWS bill here at Gaggle, and in that little bit of time that we had together, I think I walked away with no more than a dozen ideas for where to shave some costs. The most obvious one, the first thing that you keyed in on, is we had RIs coming due that weren't really well-optimized and you steered me towards savings plans. We put that in place and we're able to apply those savings plans not just to our EC2 instances but also to our serverless spend as well.So, that was a very worthwhile and cost-effective dinner for us. The thing that was most surprising though, Corey, was your approach. Your approach to how to review our bill was not what I thought at all.Corey: Well, what did you expect my approach was going to be? Because this always is of interest to me. Like, do you expect me to, like, whip a portable machine learning rig out of my backpack full of GPUs or something?Casey: I didn't know if you had, like, some secret tool you were going to hit, or if nothing else, I thought you were going to go for the Cost Explorer. I spend a lot of time in Cost Explorer, that's my go-to tool, and you wanted nothing to do with Cost Exp—I think I was actually pulling up Cost Explorer for you and you said, “I'm not interested. Take me to the bills.” So, we went right to the billing dashboard, you started opening up the invoices, and I thought to myself, “I don't remember the last time I looked at an AWS invoice.” I just, it's noise; it's not something that I pay attention to.And I learned something, that you get a real quick view of both the cost and the usage. And that's what you were keyed in on, right? And you were looking at things relative to each other. “Okay, I have no idea about Gaggle or what they do, but normally, for a company that's spending x amount of dollars in EC2, why is your data transfer cost the way it is? Is that high or low?” So, you're looking for kind of relative numbers, but it was really cool watching you slice and dice that bill through the dashboard there.Corey: There are a few things I tie together there. Part of it is that this is sort of a surprising thing that people don't think about but start with big numbers first, rather than going alphabetically because I don't really care about your $6 Alexa for Business spend. I care a bit more about the $6 million, or whatever it happens to be at EC2—I'm pulling numbers completely out of the ether, let's be clear; I don't recall what the exact magnitude of your bill is and it's not relevant to the conversation.And then you see that and it's like, “Huh. Okay, you're spending $6 million on EC2. Why are you spending 400 bucks on S3? Seems to me that those two should be a little closer aligned. What's the deal here? Oh, God, you're using eight petabytes of EBS volumes. Oh, dear.”And just, it tends to lead to interesting stuff. Break it down by region, service, and use case—or usage type, rather—is what shows up on those exploded bills, and that's where I tend to start. It also is one of the easiest things to wind up having someone throw into a PDF and email my way if I'm not doing it in a restaurant with, you know, people clapping standing around.Casey: [laugh]. Right.Corey: I also want to highlight that you've been using AWS for a long time. You're a Container Hero; you are not bad at understanding the nuances and depths of AWS, so I take praise from you around this stuff as valuing it very highly. This stuff is not intuitive, it is deeply nuanced, and you have a business outcome you are working towards that invariably is not oriented day in day out around, “How do I get these services for less money than I'm currently paying?” But that is how I see the world and I tend to live in a very different space just based on the nature of what I do. It's sort of a case study and the advantage of specialization. But I know remarkably little about containers, which is how we wound up reconnecting about a week or so before we did this recording.Casey: Yeah. I saw your tweet; you were trying to run some workload—container workload—and I could hear the frustration on the other end of Twitter when you were shaking your fist at—Corey: I should not tweet angrily, and I did in this case. And, eh, every time I do I regret it. But it played well with the people, so that does help. I believe my exact comment was, “‘me: I've got this container. Run it, please.' ‘Google Cloud: Run. You got it, boss.' AWS has 17 ways to run containers and they all suck.”And that's painting with an overly broad brush, let's be clear, but that was at the tail end of two or three days of work trying to solve a very specific, very common, business problem, that I was just beating my head off of a wall again and again and again. And it took less than half an hour from start to finish with Google Cloud Run and I didn't have to think about it anymore. And it's one of those moments where you look at this and realize that the future is here, we just don't see it in certain ways. And you took exception to this. So please, let's dive in because 280 characters of text after half a bottle of wine is not the best context to have a nuanced discussion that leaves friendships intact the following morning.Casey: Nice. Well, I just want to make sure I understand the use case first because I was trying to read between the lines on what you needed, but let me take a guess. My guess is you got your source code in GitHub, you have a Docker file, and you want to be able to take that repo from GitHub and just have it continuously deployed somewhere in Run. And you don't want to have headaches with it; you just want to push more changes up to GitHub, Docker Build runs and updates some service somewhere. Am I right so far?Corey: Ish, but think a little further up the stack. It was in service of this show. So, this show, as people who are listening to this are probably aware by this point, periodically has sponsors, which we love: We thank them for participating in the ongoing support of this show, which empowers conversations like this. Sometimes a sponsor will come to us with, “Oh, and here's the URL we want to give people.” And it's, “First, you misspelled your company name from the common English word; there are three sublevels within the domain, and then you have a complex UTM tagging tracking co—yeah, you realize people are driving to work when they're listening to this?”So, I've built a while back a link shortener, snark.cloud because is it the shortest thing in the world? Not really, but it's easily understandable when I say that, and people hear it for what it is. And that's been running for a long time as an S3 bucket with full of redirects, behind CloudFront. So, I wind up adding a zero-byte object with a redirect parameter on it, and it just works.Now, the challenge that I have here as a business is that I am increasingly prolific these days. So, anything that I am not directly required to be doing, I probably shouldn't necessarily be the one to do it. And care and feeding of those redirect links is a prime example of this. So, I went hunting, and the things that I was looking for were, obviously, do the redirect. Now, if you pull up GitHub, there are hundreds of solutions here.There are AWS blog posts. One that I really liked and almost got working was Eric Johnson's three-part blog post on how to do it serverlessly, with API Gateway, and DynamoDB, no Lambdas required. I really liked aspects of what that was, but it was complex, I kept smacking into weird challenges as I went, and front end is just baffling to me. Because I needed a front end app for people to be able to use here; I need to be able to secure that because it turns out that if you just have a, anyone who stumbles across the URL can redirect things to other places, well, you've just empowered a whole bunch of spam email, and you're going to find that service abused, and everyone starts blocking it, and then you have trouble. Nothing lasts the first encounter with jerks.And I was getting more and more frustrated, and then I found something by a Twitter engineer on GitHub, with a few creative search terms, who used to work at Google Cloud. And what it uses as a client is it doesn't build any kind of custom web app. Instead, as a database, it uses not S3 objects, not Route 53—the ideal database—but a Google sheet, which sounds ridiculous, but every business user here knows how to use that.Casey: Sure.Corey: And it looks for the two columns. The first one is the slug after the snark.cloud, and the second is the long URL. And it has a TTL of five seconds on cache, so make a change to that spreadsheet, five seconds later, it's live. Everyone gets it, I don't have to build anything new, I just put it somewhere around the relevant people can access it, I gave him a tutorial and a giant warning on it, and everyone gets that. And it just works well. It was, “Click here to deploy. Follow the steps.”And the documentation was a little, eh, okay, I had to undo it once and redo it again. Getting the domain registered was getting—ported over took a bit of time, and there were some weird SSL errors as the certificates were set up, but once all of that was done, it just worked. And I tested the heck out of it, and cold starts are relatively low, and the entire thing fits within the free tier. And it is reminiscent of the magic that I first saw when I started working with some of the cloud providers services, years ago. It's been a long time since I had that level of delight with something, especially after three days of frustration. It's one of the, “This is a great service. Why are people not shouting about this from the rooftops?” That was my perspective. And I put it out on Twitter and oh, Lord, did I get comments. What was your take on it?Casey: Well, so my take was, when you're evaluating a platform to use for running your applications, how fast it can get you to Hello World is not necessarily the best way to go. I just assumed you're wrong. I assumed of the 17 ways AWS has to run containers, Corey just doesn't understand. And so I went after it. And I said, “Okay, let me see if I can find a way that solves his use case, as I understand it, through a quick tweet.”And so I tried to App Runner; I saw that App Runner does not meet your needs because you have to somehow get your Docker image pushed up to a repo. App Runner can take an image that's already been pushed up and deployed for you or it can build from source but neither of those were the way I understood your use case.Corey: Having used App Runner before via the Copilot CLI, it is the closest as best I can tell to achieving what I want. But also let's be clear that I don't believe there's a free tier; there needs to be a load balancer in front of it, so you're starting with 15 bucks a month for this thing. Which is not the end of the world. Had I known at the beginning that all of this was going to be there, I would have just signed up for a bit.ly account and called it good. But here we are.Casey: Yeah. I tried Copilot. Copilot is a great developer experience, but it also is just pulling together tons of—I mean just trying to do a Copilot service deploy, VPCs are being created and tons IAM roles are being created, code pipelines, there's just so much going on. I was like 20 minutes into it, and I said, “Yeah, this is not fitting the bill for what Corey was looking for.” Plus, it doesn't solve my the way I understood your use case, which is you don't want to worry about builds, you just want to push code and have new Docker images get built for you.Corey: Well, honestly, let's be clear here, once it's up and running, I don't want to ever have to touch the silly thing again.Casey: Right.Corey: And that's so far has been the case, after I forked the repo and made a couple of changes to it that I wanted to see. One of them was to render the entire thing case insensitive because I get that one wrong a lot, and the other is I wanted to change the permanent 301 redirect to a temporary 302 redirect because occasionally, sponsors will want to change where it goes in the fullness of time. And that is just fine, but I want to be able to support that and not have to deal with old cached data. So, getting that up and running was a bit of a challenge. But the way that it worked, was following the instructions in the GitHub repo.The developer environment had spun up in the Google's Cloud Shell was just spectacular. It prompted me for a few things and it told me step by step what to do. This is the sort of thing I could have given a basically non-technical user, and they would have had success with it.Casey: So, I tried it as well. I said, “Well, okay, if I'm going to respond to Corey here and challenge him on this, I need to try Cloud Run.” I had no experience with Cloud Run. I had a small example repo that loosely mapped what I understood you were trying to do. Within five minutes, I had Cloud Run working.And I was surprised anytime I pushed a new change, within 45 seconds the change was built and deployed. So, here's my conclusion, Corey. Google Cloud Run is great for your use case, and AWS doesn't have the perfect answer. But here's my challenge to you. I think that you just proved why there's 17 different ways to run containers on AWS, is because there's that many different types of users that have different needs and you just happen to be number 18 that hasn't gotten the right attention yet from AWS.Corey: Well, let's be clear, like, my gag about 17 ways to run containers on AWS was largely a joke, and it went around the internet three times. So, I wrote a list of them on the blog post of “17 Ways to Run Containers in AWS” and people liked it. And then a few months later, I wrote “17 More Ways to Run Containers on AWS” listing 17 additional services that all run containers.And my favorite email that I think I've ever received in feedback was from a salty AWS employee, saying that one of them didn't really count because of some esoteric reason. And it turns out that when I'm trying to make a point of you have a sarcastic number of ways to run containers, pointing out that well, one of them isn't quite valid, doesn't really shatter the argument, let's be very clear here. So, I appreciate the feedback, I always do. And it's partially snark, but there is an element of truth to it in that customers don't want to run containers, by and large. That is what they do in service of a business goal.And they want their application to run which is in turn to serve as the business goal that continues to abstract out into, “Remain a going concern via the current position the company stakes out.” In your case, it is saving lives; in my case, it is fixing horrifying AWS bills and making fun of Amazon at the same time, and in most other places, there are somewhat more prosaic answers to that. But containers are simply an implementation detail, to some extent—to my way of thinking—of getting to that point. An important one [unintelligible 00:18:20], let's be clear, I was very anti-container for a long time. I wrote a talk, “Heresy in the Church of Docker” that then was accepted at ContainerCon. It's like, “Oh, boy, I'm not going to leave here alive.”And the honest answer is many years later, that Kubernetes solves almost all the criticisms that I had with the downside of well, first, you have to learn Kubernetes, and that continues to be mind-bogglingly complex from where I sit. There's a reason that I've registered kubernetestheeasyway.com and repointed it to ECS, Amazon's container service that is not requiring you to cosplay as a cloud provider yourself. But even ECS has a number of challenges to it, I want to be very clear here. There are no silver bullets in this.And you're completely correct in that I have a large, complex environment, and the application is nuanced, and I'm willing to invest a few weeks in setting up the baseline underlying infrastructure on AWS with some of these services, ideally not all of them at once because that's something a lunatic would do, but getting them up and running. The other side of it, though, is that if I am trying to evaluate a cloud provider's handling of containers and how this stuff works, the reason that everyone starts with a Hello World-style example is that it delivers ideally, the meantime to dopamine. There's a reason that Hello World doesn't have 18 different dependencies across a bunch of different databases and message queues and all the other complicated parts of running a modern application. Because you just want to see how it works out of the gate. And if getting that baseline empty container that just returns the string ‘Hello World' is that complicated and requires that much work, my takeaway is not that this user experience is going to get better once I'd make the application itself more complicated.So, I find that off-putting. My approach has always been find something that I can get the easy, minimum viable thing up and running on, and then as I expand know that you'll be there to catch me as my needs intensify and become ever more complex. But if I can't get the baseline thing up and running, I'm unlikely to be super enthused about continuing to beat my head against the wall like, “Well, I'll just make it more complex. That'll solve the problem.” Because it often does not. That's my position.Casey: Yeah, I agree that dopamine hit is valuable in getting attached to want to invest into whatever tech stack you're using. The challenge is your second part of that. Your second part is will it grow with me and scale with me and support the complex edge cases that I have? And the problem I've seen is a lot of organizations will start with something that's very easy to get started with and then quickly outgrow it, and then come up with all sorts of weird Rube Goldberg-type solutions. Because they jumped all in before seeing—I've got kind of an example of that.I'm happy to announce that there's now 18 ways to run containers on AWS. Because in your use case, in the spirit of AWS customer obsession, I hear your use case, I've created an open-source project that I want to share called Quinntainers—Corey: Oh, no.Casey: —and it solves—yes. Quinntainers is live and is ready for the world. So, now we've got 18 ways to run containers. And if you have Corey's use case of, “Hey, here's my container. Run it for me,” now we've got a one command that you can run to get things going for you. I can share a link for you and you could check it out. This is a [unintelligible 00:21:38]—Corey: Oh, we're putting that in the [show notes 00:21:37], for sure. In fact, if you go to snark.cloud/quinntainers, you'll find it.Casey: You'll find it. There you go. The idea here was this: There is a real use case that you had, and I looked at AWS does not have an out-of-the-box simple solution for you. I agree with that. And Google Cloud Run does.Well, the answer would have been from AWS, “Well, then here, we need to make that solution.” And so that's what this was, was a way to demonstrate that it is a solvable problem. AWS has all the right primitives, just that use case hadn't been covered. So, how does Quinntainers work? Real straightforward: It's a command-line—it's an NPM tool.You just run a [MPX 00:22:17] Quinntainer, it sets up a GitHub action role in your AWS account, it then creates a GitHub action workflow in your repo, and then uses the Quinntainer GitHub action—reusable action—that creates the image for you; every time you push to the branch, pushes it up to ECR, and then automatically pushes up that new version of the image to App Runner for you. So, now it's using App Runner under the covers, but it's providing that nice developer experience that you are getting out of Cloud Run. Look, is container really the right way to go with running containers? No, I'm not making that point at all. But the point is it is a—Corey: It might very well be.Casey: Well, if you want to show a good Hello World experience, Quinntainer's the best because within 30 seconds, your app is now set up to continuously deliver containers into AWS for your very specific use case. The problem is, it's not going to grow for you. I mean that it was something I did over the weekend just for fun; it's not something that would ever be worthy of hitching up a real production workload to. So, the point there is, you can build frameworks and tools that are very good at getting that initial dopamine hit, but then are not going to be there for you unnecessarily as you mature and get more complex.Corey: And yet, I've tilted a couple of times at the windmill of integrating GitHub actions in anything remotely resembling a programmatic way with AWS services, as far as instance roles go. Are you using permanent credentials for this as stored secrets or are you doing the [OICD 00:23:50][00:23:50] handoff?Casey: OIDC. So, what happens is the tool creates the IAM role for you with the trust policy on GitHub's OIDC provider, sets all that up for you in your account, locks it down so that just your repo and your main branch is able to push or is able to assume the role, the role is set up just to allow deployments to App Runner and ECR repository. And then that's it. At that point, it's out of your way. And you're just git push, and couple minutes later, your updates are now running an App Runner for you.Corey: This episode is sponsored in part by our friends at Vultr. Optimized cloud compute plans have landed at Vultr to deliver lightning fast processing power, courtesy of third gen AMD EPYC processors without the IO, or hardware limitations, of a traditional multi-tenant cloud server. Starting at just 28 bucks a month, users can deploy general purpose, CPU, memory, or storage optimized cloud instances in more than 20 locations across five continents. Without looking, I know that once again, Antarctica has gotten the short end of the stick. Launch your Vultr optimized compute instance in 60 seconds or less on your choice of included operating systems, or bring your own. It's time to ditch convoluted and unpredictable giant tech company billing practices, and say goodbye to noisy neighbors and egregious egress forever.Vultr delivers the power of the cloud with none of the bloat. "Screaming in the Cloud" listeners can try Vultr for free today with a $150 in credit when they visit getvultr.com/screaming. That's G E T V U L T R.com/screaming. My thanks to them for sponsoring this ridiculous podcast.Corey: Don't undersell what you've just built. This is something that—is this what I would use for a large-scale production deployment, obviously not, but it has streamlined and made incredibly accessible things that previously have been very complex for folks to get up and running. One of the most disturbing themes behind some of the feedback I got was, at one point I said, “Well, have you tried running a Docker container on Lambda?” Because now it supports containers as a packaging format. And I said no because I spent a few weeks getting Lambda up and running back when it first came out and I've basically been copying and pasting what I got working ever since the way most of us do.And response is, “Oh, that explains a lot.” With the implication being that I'm just a fool. Maybe, but let's be clear, I am never the only person in the room who doesn't know how to do something; I'm just loud about what I don't know. And the failure mode of a bad user experience is that a customer feels dumb. And that's not okay because this stuff is complicated, and when a user has a bad time, it's a bug.I learned that in 2012. From Jordan Sissel the creator of LogStash. He has been an inspiration to me for the last ten years. And that's something I try to live by that if a user has a bad time, something needs to get fixed. Maybe it's the tool itself, maybe it's the documentation, maybe it's the way that GitHub repo's readme is structured in a way that just makes it accessible.Because I am not a trailblazer in most things, nor do I intend to be. I'm not the world's best engineer by a landslide. Just look at my code and you'd argue the fact that I'm an engineer at all. But if it's bad and it works, how bad is it? Is sort of the other side of it.So, my problem is that there needs to be a couple of things. Ignore for a second the aspect of making it the right answer to get something out of the door. The fact that I want to take this container and just run it, and you and I both reach for App Runner as the default AWS service that does this because I've been swimming in the AWS waters a while and you're a frickin AWS Container Hero, where it is expected that you know what most of these things do. For someone who shows up on the containers webpage—which by the way lists, I believe 15 ways to run containers on mobile and 19 ways to run containers on non-mobile, which is just fascinating in its own right—and it's overwhelming, it's confusing, and it's not something that makes it is abundantly clear what the golden path is. First, get it up and working, get it running, then you can add nuance and flavor and the rest, and I think that's something that's gotten overlooked in our mad rush to pretend that we're all Google engineers, circa 2012.Casey: Mmm. I think people get stressed out when they tried to run containers in AWS because they think, “What is that golden path?” You said golden path. And my advice to people is there is no golden path. And the great thing about AWS is they do continue to invest in the solutions they come up with. I'm still bitter about Google Reader.Corey: As am I.Casey: Yeah. I built so much time getting my perfect set of RSS feeds and then I had to find somewhere else to—with AWS, the different offerings that are available for running containers, those are there intentionally, it's not by accident. They're there to solve specific problems, so the trick is finding what works best for you and don't feel like one is better than the other is going to get more attention than others. And they each have different use cases.And I approach it this way. I've seen a couple of different people do some great flowcharts—I think Forrest did one, Vlad did one—on ways to make the decision on how to run your containers. And I break it down to three questions. I ask people first of all, where are you going to run these workloads? If someone says, “It has to be in the data center,” okay, cool, then ECS Anywhere or EKS Anywhere and we'll figure out if Kubernetes is needed.If they need specific requirements, so if they say, “No, we can run in the cloud, but we need privileged mode for containers,” or, “We need EBS volumes,” or, “We want really small container sizes,” like, less than a quarter-VCP or less than half a gig of RAM—or if you have custom log requirements, Fargate is not going to work for you, so you're going to run on EC2. Otherwise, run it on Fargate. But that's the first question. Figure out where are you going to run your containers. That leads to the second question: What's your control plane?But those are different, sort of related but different questions. And I only see six options there. That's App Runner for your control plane, LightSail for your control plane, Rosa if you're invested in OpenShift already, EKS either if you have Momentum and Kubernetes or you have a bunch of engineers that have a bunch of experience with Kubernetes—if you don't have either, don't choose it—or ECS. The last option Elastic Beanstalk, but let's leave that as a—if you're not currently invested in Elastic Beanstalk don't start today. But I look at those as okay, so I—first question, where am I going to run my containers? Second question, what do I want to use for my control plane? And there's different pros and cons of each of those.And then the third question, how do I want to manage them? What tools do I want to use for managing deployment? All those other tools like Copilot or App2Container or Proton, those aren't my control plane; those aren't where I run my containers; that's how I manage, deploy, and orchestrate all the different containers. So, I look at it as those three questions. But I don't know, what do you think of that, Corey?Corey: I think you're onto something. I think that is a terrific way of exploring that question. I would argue that setting up a framework like that—one or very similar—is what the AWS containers page should be, just coming from the perspective of what is the neophyte customer experience. On some level, you almost need a slide of have choose your level of experience ranging from, “What's a container?” To, “I named my kid Kubernetes because I make terrible life decisions,” and anywhere in between.Casey: Sure. Yeah, well, and I think that really dictates the control plane level. So, for example, LightSail, where does LightSail fit? To me, the value of LightSail is the simplicity. I'm looking at a monthly pricing: Seven bucks a month for a container.I don't know how [unintelligible 00:30:23] works, but I can think in terms of monthly pricing. And it's tailored towards a console user, someone just wants to click in, point to an image. That's a very specific user, there's thousands of customers that are very happy with that experience, and they use it. App Runner presents that scale to zero. That's one of the big selling points I see with App Runner. Likewise, with Google Cloud Run. I've got that scale to zero. I can't do that with ECS, or EKS, or any of the other platforms. So, if you've got something that has a ton of idle time, I'd really be looking at those. I would argue that I think I did the math, Google Cloud Run is about 30% more expensive than App Runner.Corey: Yeah, if you disregard the free tier, I think that's have it—running persistently at all times throughout the month, the drop-out cold starts would cost something like 40 some odd bucks a month or something like that. Don't quote me on it. Again and to be clear, I wound up doing this very congratulatory and complimentary tweet about them on I think it was Thursday, and then they immediately apparently took one look at this and said, “Holy shit. Corey's saying nice things about us. What do we do? What do we do?” Panic.And the next morning, they raised prices on a bunch of cloud offerings. Whew, that'll fix it. Like—Casey: [laugh].Corey: Di-, did you miss the direction you're going on here? No, that's the exact opposite of what you should be doing. But here we are. Interestingly enough, to tie our two conversation threads together, when I look at an AWS bill, unless you're using Fargate, I can't tell whether you're using Kubernetes or not because EKS is a small charge. And almost every case for the control plane, or Fargate under it.Everything else just manifests as EC2 spend. From the perspective of the cloud provider. If you're running a Kubernetes cluster, it is a single-tenant application that can have some very funky behaviors like cross-AZ chatter back and fourth because there's no internal mechanism to say talk to the free thing, rather than the two cents a gigabyte thing. It winds up spinning up and down in a bunch of different ways, and the behavior patterns, because of how placement works are not necessarily deterministic, depending upon workload. And that becomes something that people find odd when, “Okay, we look at our bill for a week, what can you say?”“Well, first question. Are you running Kubernetes at all?” And they're like, “Who invited these clowns?” Understand, we're not prying into your workloads for a variety of excellent legal and contractual reasons, here. We are looking at how they behave, and for specific workloads, once we have a conversation engineering team, yeah, we're going to dive in, but it is not at all intuitive from the outside to make any determination whether you're running containers, or whether you're running VMs that you just haven't done anything with in 20 years, or what exactly is going on. And that's just an artifact of the billing system.Casey: We ran into this challenge in Gaggle. We don't use EKS, we use ECS, but we have some shared clusters, lots of EC2 spend, hard to figure out which team is creating the services that's running that up. We actually ended up creating a tool—we open-sourced it—ECS Chargeback, and what it does is it looks at the CPU memory reservations for each task definition, and then prorates the overall charge of the ECS cluster, and then creates metrics in Datadog to give us a breakdown of cost per ECS service. And it also measures what we like to refer to as waste, right? Because if you're reserving four gigs of memory, but your utilization never goes over two gigs, we're paying for that reservation, but you're underutilizing.So, we're able to also show which services have the highest degree of waste, not just utilization, so it helps us go after it. But this is a hard problem. I'd be curious, how do you approach these shared ECS resources and slicing and dicing those bills?Corey: Everyone has a different approach, too. This there is no unifiable, correct answer. A previous show guest, Peter Hamilton, over at Remind had done something very similar, open-sourced a bunch of these things. Understanding what your spend is important on this, and it comes down to getting at the actual business concern because in some cases, effectively dead reckoning is enough. You take a look at the cluster that is really hard to attribute because it's a shared service. Great. It is 5% of your bill.First pass, why don't we just agree that it is a third for Service A, two-thirds for Service B, and we'll call it mostly good at that point? That can be enough in a lot of cases. With scale [laugh] you're just sort of hand-waving over many millions of dollars a year there. How about we get into some more depth? And then you start instrumenting and reporting to something, be it CloudWatch, be a Datadog, be it something else, and understanding what the use case is.In some cases, customers have broken apart shared clusters for that specific reason. I don't think that's necessarily the best approach from an engineering perspective, but again, this is not purely an engineering decision. It comes down to serving the business need. And if you're taking up partial credits on that cluster, for a tax credit for R&D for example, you want that position to be extraordinarily defensible, and spending a few extra dollars to ensure that it is the right business decision. I mean, again, we're pure advisory; we advise customers on what we would do in their position, but people often mistake that to be we're going to go for the lowest possible price—bad idea, or that we're going to wind up doing this from a purely engineering-centric point of view.It's, be aware of that in almost every case, with some very notable weird exceptions, the AWS Bill costs significantly less than the payroll expense that you have of people working on the AWS environment in various ways. People are more expensive, so the idea of, well, you can save a whole bunch of engineering effort by spending a bit more on your cloud, yeah, let's go ahead and do that.Casey: Yeah, good point.Corey: The real mark of someone who's senior enough is their answer to almost any question is, “It depends.” And I feel I've fallen into that trap as well. Much as I'd love to sit here and say, “Oh, it's really simple. You do X, Y, and Z.” Yeah… honestly, my answer, the simple answer, is I think that we orchestrate a cyber-bullying campaign against AWS through the AWS wishlist hashtag, we get people to harass their account managers with repeated requests for, “Hey, could you go ahead and [dip 00:36:19] that thing in—they give that a plus-one for me, whatever internal system you're using?”Just because this is a problem we're seeing more and more. Given that it's an unbounded growth problem, we're going to see it more and more for the foreseeable future. So, I wish I had a better answer for you, but yeah, that's stuff's super hard is honest, but it's also not the most useful answer for most of us.Casey: I'd love feedback from anyone from you or your team on that tool that we created. I can share link after the fact. ECS Chargeback is what we call it.Corey: Excellent. I will follow up with you separately on that. That is always worth diving into. I'm curious to see new and exciting approaches to this. Just be aware that we have an obnoxious talent sometimes for seeing these things and, “Well, what about”—and asking about some weird corner edge case that either invalidates the entire thing, or you're like, “Who on earth would ever have a problem like that?” And the answer is always, “The next customer.”Casey: Yeah.Corey: For a bounded problem space of the AWS bill. Every time I think I've seen it all, I just have to talk to one more customer.Casey: Mmm. Cool.Corey: In fact, the way that we approached your teardown in the restaurant is how we launched our first pass approach. Because there's value in something like that is different than the value of a six to eight-week-long, deep-dive engagement to every nook and cranny. And—Casey: Yeah, for sure. It was valuable to us.Corey: Yeah, having someone come in to just spend a day with your team, diving into it up one side and down the other, it seems like a weird thing, like, “How much good could you possibly do in a day?” And the answer in some cases is—we had a Honeycomb saying that in a couple of days of something like this, we wound up blowing 10% off their entire operating budget for the company, it led to an increased valuation, Liz Fong-Jones says that—on multiple occasions—that the company would not be what it was without our efforts on their bill, which is just incredibly gratifying to hear. It's easy to get lost in the idea of well, it's the AWS bill. It's just making big companies spend a little bit less to another big company. And that's not exactly, you know, saving the lives of K through 12 students here.Casey: It's opening up opportunities.Corey: Yeah. It's about optimizing for the win for everyone. Because now AWS gets a lot more money from Honeycomb than they would if Honeycomb had not continued on their trajectory. It's, you can charge customers a lot right now, or you can charge them a little bit over time and grow with them in a partnership context. I've always opted for the second model rather than the first.Casey: Right on.Corey: But here we are. I want to thank you for taking so much time out of well, several days now to argue with me on Twitter, which is always appreciated, particularly when it's, you know, constructive—thanks for that—Casey: Yeah.Corey: For helping me get my business partner to re:Invent, although then he got me that horrible puzzle of 1000 pieces for the Cloud-Native Computing Foundation landscape and now I don't ever want to see him again—so you know, that happens—and of course, spending the time to write Quinntainers, which is going to be at snark.cloud/quinntainers as soon as we're done with this recording. Then I'm going to kick the tires and send some pull requests.Casey: Right on. Yeah, thanks for having me. I appreciate you starting the conversation. I would just conclude with I think that yes, there are a lot of ways to run containers in AWS; don't let it stress you out. They're there for intention, they're there by design. Understand them.I would also encourage people to go a little deeper, especially if you got a significantly large workload. You got to get your hands dirty. As a matter of fact, there's a hands-on lab that a company called Liatrio does. They call it their Night Lab; it's a one-day free, hands-on, you run legacy monolithic job applications on Kubernetes, gives you first-hand experience on how to—gets all the way up into observability and doing things like Canary deployments. It's a great, great lab.But you got to do something like that to really get your hands dirty and understand how these things work. So, don't sweat it; there's not one right way. There's a way that will probably work best for each user, and just take the time and understand the ways to make sure you're applying the one that's going to give you the most runway for your workload.Corey: I will definitely dig into that myself. But I think you're right, I think you have nailed a point that is, again, a nuanced one and challenging to put in a rage tweet. But the services don't exist in a vacuum. They're not there because, despite the joke, someone wants to get promoted. It's because there are customer needs that are going on that, and this is another way of meeting those needs.I think there could be better guidance, but I also understand that there are a lot of nuanced perspectives here and that… hell is someone else's workflow—Casey: [laugh].Corey: —and there's always value in broadening your perspective a bit on those things. If people want to learn more about you and how you see the world, where's the best place to find you?Casey: Probably on Twitter: twitter.com/nektos, N-E-K-T-O-S.Corey: That might be the first time Twitter has been described as a best place for anything. But—Casey: [laugh].Corey: Thank you once again, for your time. It is always appreciated.Casey: Thanks, Corey.Corey: Casey Lee, CTO at Gaggle and AWS Container Hero. And apparently writing code in anger to invalidate my points, which is always appreciated. Please do more of that, folks. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, or the YouTube comments, which is always a great place to go reading, whereas if you've hated this podcast, please leave a five-star review in the usual places and an angry comment telling me that I'm completely wrong, and then launching your own open-source tool to point out exactly what I've gotten wrong this time.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.Announcer: This has been a HumblePod production. Stay humble.

【本期嘉宾】沈振宇、苏青阳、金叶宸；【连麦嘉宾】高欣艺（小丸子）、汪天凡、黄海均、清风沈振宇（潮玩族、千岛社区创始人）苏青阳（社区产品经理，微信公众号：互联网苏青阳，ID：suqingyang2019）金叶宸（「即刻吵架王」，微信公众号：圆首金老汉，ID：chairmanJLH）主播：潘乱（乱翻书主理人）连麦嘉宾：高欣艺（小丸子，前豆瓣FM电台产品经理）汪天凡（贝塔斯曼合伙人）黄海均（豆瓣小组产品经理）清风（「吃喝玩乐在北京」组长）【时间线】03:25 大家都是哪一年注册豆瓣的？现在上豆瓣的频次是怎么样的，目的是什么？07:32 豆瓣的影评为什么能做这么好呢？13:20 「饭圈的出现，是对豆瓣影评生态的毁灭性打击」16:09 豆瓣的书影音跟小组，其实已经是两拨用户了？为什么会形成这个结果呢？21:53 「阿北：豆瓣是帮助每一个人发现生活中最适合自己的未知事物」27:54 前豆瓣电台产品经理高欣艺分享：当年豆瓣FM的得与失34:31 苏青阳分享：网易云音乐与豆瓣FM的比较42:06 「为了避免毁掉我们心中的圣地，当时我劝张一鸣不要买豆瓣」45:12 类似于Google Reader的豆瓣「九点」为什么没做好？52:18 社区如果只迎合老用户的需求，会出现什么情况？56:12 为什么豆瓣这个只有几百万日活的App ，能够掌控整个中国影视审美标准？60:50 豆瓣转型移动的过程中，为什么经常分分合合来回反复？71:23 「我的印象里是感觉豆瓣这个公司没有CEO」80:49 「在PC往移动端转型的时候，豆瓣可能没有想清楚自己要做一个什么样的移动端产品」86:09 「豆瓣给人的感觉是：只有产品线，没有业务线。」90:04 为什么我们要批评豆瓣？正因为我们太喜欢豆瓣了！92:50「欢迎加入千岛潮玩族，欢迎加入上海必有回响科技！」【相关推荐】1、豆瓣电影评分八问——阿北https://blog.douban.com/douban/2015/12/18/3060/2、复盘豆瓣：在算法和社交中反复摇摆——潘乱https://mp.weixin.qq.com/s/pdtPXJ54FdpwXa6iaWpIag【开场&结尾音乐】我々楽 - Fairy tale of the moon微信公众号：乱翻书视频号：潘乱商业合作：联系微信 tongxing717本期编辑：怀杭

I talk to Liam Murray about how he landed at a pro-life conviction—despite walking away from his Catholic upbringing. Also discussed: Daylight Saving Time; the death of Google Reader; why are there Catholics in Scotland? Email us at changedmymindpod@gmail.com Support us at https://patreon.com/changedmymind Sign up for my Substack at https://luketharrington.substack.com Follow Liam on Twitter at https://twitter.com/liammurray

Chegou mais um Na Sarjeta! Neste programa Leonardo Maciel, Rafael Marçal e Wesley Samp conversam sobre a época do Google Reader e como usuário e autor tinha mais controle sobre […]

The newly announced electric F-150 is maybe the biggest EV effort since the launch of Tesla. Google is launching its first ever retail store. Internet Explorer is finally going to that great recycle bin in the sky. But could Google be breathing new life into RSS feeds in web browsers?Sponsors:Tovala.com/rideKraken.com/techmemeLinks:Ford's Electric F-150 Pickup Aims to Be the Model T of E.V.s (New York Times)Ford unveils the F-150 Lightning, its all-electric pickup truck that will start under $40,000 (Tech Crunch)'I'm not very social': ByteDance founder to hand CEO reins to college roommate (Reuters)Google is opening its first physical retail store this summer in NYC (The Verge)Apple cites 'significant' malware on Mac while defending iOS App Store in Fortnite trial (CNet)Microsoft is finally retiring Internet Explorer in 2022 (The Verge)Chrome testing RSS-powered ‘Follow' button & feed that keeps the Google Reader dream alive (9to5 Google)See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

With Gareth Myles and Ted SalmonJoin us on Mewe RSS Link: https://techaddicts.libsyn.com/rss iTunes | Google Podcasts | Stitcher | Tunein | Spotify  Amazon | Pocket Casts | Castbox |  PodHubUK   Show Notes: Feedback Steve Litchfield told me this week that he really enjoys Tech Addicts for what it is - listening in on two blokes natter about whatever tech stuff they find as they surf around the internet! Praise indeed.   Hardline on the hardware: Apple Expected to Release 2021 iMac in Colours Seven-Screen Aurora A7 “Battlestation” Laptop Costs Up to $20,000 Kuube Solar-Powered Smart Benches New Wearable Device Turns Your Body Into a Biological Battery Further Huawei P50 camera details leaked as 1-inch Sony IMX800 sensor is teased 29million people who bought a phone since 2015 could be due a refund  Twitter announces paid Super Follows to let you charge for tweets Customizable Framework Laptop Lets You Pick Ports, Reduces E-Waste Canon's cute new camera is like a Pixar character – and it dances on your desk! Huawei Electric cars  Ted's Feedback on Roku Streambar -   Flap your trap about an App: Chrome may be getting a Google Reader-like feature  Google Recorder now has a companion web app for storage and sharing  LastPass analytics code raises questions about potential security issues Google Chat Replacing Hangouts  Hark Back: 12” Bedroom Portable TV - and in particular Space Helmet Design! Philette Bargain Basement: Anker Soundcore Motion Boom Outdoor Speaker with Titanium Drivers, BassUp Technology, IPX7 Waterproof, 24H Playtime, Soundcore App, Built-In Handle, Portable Bluetooth Speaker for Outdoors, Camping £69 save £20.  Nokia Bundles Clearance - top is 8.3 5G from £499 to £299 Samsung Galaxy Tab S7+ Wi-Fi Android Tablet Mystic - Black (UK Version) + Free AKG Y500 Headphones - £655 on Amazon - Claim a free pair of AKG Y500 Headphones Xiaomi Mi Smart Scale 2, Person Weighing Scale, White - £16.55 (+£4.49 non-prime / UK Mainland) Dispatched & Sold By Amazon EU HUAWEI WATCH GT 2 Pro £199.99 (2 colours) / Poss £189.99 with unique code @ Huawei £199.99 down from £299.99  TP-Link Tapo Smart Plug Wi-Fi Outlet, Works with Amazon Alexa (Echo and Echo Dot), Google Home, Wireless Smart Socket, Remote Control Timer Switch, Device Sharing, No Hub Required (Tapo P100) - RRP: £12.99 Price: £8.99  Saving: £4.00 Moto Madness Deals - Motorola Edge now £349 £200 off - Wow!    Main Show URL: http://www.techaddicts.uk | PodHubUK Contact:: contact@techaddicts.uk | @techaddictsuk Gareth - @garethmyles | garethmyles.com Ted - tedsalmon.com | Ted's PayPal | Ted's Amazon | tedsalmon@post.com YouTube: Tech Addicts   The PodHubUK PodcastsPodHubUK - Twitter - MeWe PSC Group - PSC Photos - PSC Classifieds - WhateverWorks - Camera Creations - TechAddictsUK - The TechBox - Chewing Gum for the Ears - Projector Room - PixelSwim - Gavin's Gadgets - Ted's Salmagundi - Steve's Rants'n'Raves - Ted's Amazon - Steve's Amazon - Buy Ted a Coffee    

A few years after the Great Recession, you couldn't scroll through Google Reader without seeing the word “disrupt.” TechCrunch named a conference after it, the New York Times named a column after it, investor Marc Andreessen warned that “software disruption” would eat the world; not long after, Peter Thiel, his fellow Facebook board member, called “disrupt” one of his favorite words.

In this episode of the TeacherCast Podcast, Jeff sits down with the Jed-iPad Master, Toby Price, and Dave Meister to talk about how administrators use technology in their school districts. Topics Covered:How has educational technology changed in the last few years The role of school districts within the digital community Reaching out to families without computers in their homes How are we preparing our graduates for the digital job market Introducing and integrating technology in the middle and upper grades Teaching students to blog Using blogging to foster great writing skills and gain a voice in the world What new technology experiences are schools creating for our students Great Educational Apps How to teach the parents about this great technology How should we suggest students transfer their digital files? What types of online accounts can we ask our students to have connections to How to work around district filters Presenting resumes in a digital job market. Coping with a diminishing technology budget Are we preparing our students correctly for the world? How to find “Pockets of Excellence” Teacher Training Programs Google+ in the Classroom Should we fear Facebook and other social networking sites How should teachers keep an online public/private life The Digital Resume First thoughts on these topics Social Media and Social Networking Facebook Twitter Skype Text Messaging QR Codes in the classroom Cell Phones/Internet Devices in schools Students bringing in laptops to learn with Students bringing in iPads or tablets to learn with Google+ LiveBinders.com Online Learning for credit in k-12 education Apps Discussed: http://itunes.apple.com/us/app/splashtop-remote-desktop-for/id382509315?mt=8 (Splashtop Remote Desktop) This is the ONLY remote desktop app that streams video and audio from your PC or Mac, allowing you to interact with your PowerPoint, Keynote, Word, Excel, Outlook, Quicken, IE, Firefox, Safari, World of Warcraft, and other PC / MAC applications. http://itunes.apple.com/us/app/splashtop-whiteboard/id437679527?mt=8 (Splashtop Whiteboard) Turn your iPad into a mobile interactive whiteboard! http://itunes.apple.com/us/app/replaynote/id419786855?mt=8 (ReplyNote) ReplayNote is an app that records your writing and voice, then converts it to YouTube video. http://itunes.apple.com/us/app/screenchomp/id442415881?mt=8 (ScreenChomp) A simple doodling board, markers, and one-click sharing tools make spreading your ideas and know-how easy and fun! Just – Record It. Sketch It. Share It. – to create a sharable, replay-able video that tells your story clearly. http://itunes.apple.com/us/app/golfshot-golf-gps/id319897973?mt=8 (GolfShot: Golf GPS) #1 Golf GPS App Worldwide http://itunes.apple.com/us/app/twitter/id333903271?mt=8 (Twitter) Follow your interests: instant updates from your friends, industry experts, favorite celebrities, and what's happening around the world. Get short bursts of timely information on the official Twitter app for iPhone and iPad. http://itunes.apple.com/us/app/stumbleupon!/id386244833?mt=8 (Stumble Upon) StumbleUpon is a discovery engine that finds the best of everything that is out there on the web, recommended just for you. With a touch of the Stumble button, or swipe of the iPad screen, you'll discover photos, videos and web pages recommended by friends and people sharing your interests. http://itunes.apple.com/us/app/flipboard/id358801284?mt=8 (Flipboard) Named Apple's iPad App of the Year and one of TIME's top 50 innovations of 2010, Flipboard is a fast, beautiful way to flip through the news, photos, videos, and updates your friends are sharing on Facebook, Twitter, Google Reader, Flickr, and Instagram. http://itunes.apple.com/us/app/caseys-contraptions-hd/id399408335?mt=8 (Casey's Contraptions) Help Casey get his toys back by building crazy contraptions. Create Rube Goldberg-like machines with toys and everyday items to solve...