Podcasts about Scrypt

tales ending whimper scrypt

Play Episode Listen Later Sep 21, 2022 9:47

Disciple Up # 276 Gideon Pt 5, Ending with a Whimper By Louie Marsh Intro. We're taking four weeks to read through six I wrote on the life of Gideon for my radio show, Tales From the Scrypt. Let me know what you think of this short form podcasting ok? Would you like more? Would you like another podcast called Tales from the Scrypt? Or change Disciple Up into this short form scripted format? Let me know, I'm waiting! louie@discipleup.org facebook.com/discipleup

Gideon Pt 3 - The Amazing Shrinking Army

army tales shrinking scrypt

Play Episode Listen Later Sep 14, 2022 17:14

Disciple Up # 274 The Amazing Shrinking Army, Gideon Pt. 4 By Louie Marsh, Intro. We're taking four weeks to read through six episodes I wrote on the life of Gideon for my radio show, Tales From the Scrypt. Let me know what you think of this short form podcasting ok? Would you like more? Would you like another podcast called Tales from the Scrypt? Or change Disciple Up into this short form scripted format? Let me know, I'm waiting! louie@discipleup.org facebook.com/discipleup

Michael Wagner - Star Atlas founder and CEO, Ep 9

The Zeitgeist

Play Episode Listen Later Sep 8, 2022 30:21

Brian Friel sits down with Star Atlas founder and CEO Michael Wagner to learn about what it's like building web3's first giant strategy MMO on Solana. Show Notes:0:58 - What is Star Atlas? 03:44 - Background / Founders of SA 07:01 - Going for a AAA game 09:32 - Phantom integration in Star Atlas10:20 - Recent events, achievements and releases15:08 - The DAO 19:27 - Interacting with the SA ecosystem23:44 - Star Atlas, AAA gaming and Web 3.028:09 - Builders he admires Full Transcript: Brian (00:05):Hey everyone. Welcome back to The Zeitgeist, the show where we highlight the founders, developers, and designers who are pushing the web 3.0 space forward. I'm Brian Friel, Developer Relations at Phantom, and I'm super excited to introduce my guest, Michael Wagner. Michael is the founder and CEO of Star Atlas, one of the most ambitious games being built on Solana and in web 3.0 in general. Michael, welcome to the show.Michael (00:29):Hey, Brian. Fantastic to be here and really looking forward to our conversation.Brian (00:33):I'm really excited as well. You guys are building something that a lot of people on Solana are really excited about. Anatoly, our first guest, actually quoted you guys as saying that he thinks you guys are "the most ambitious project being built on Solana maybe just outside of Serum." But for maybe listeners who are unfamiliar with Star Atlas, could you give us a quick breakdown on, what is, in your own world, what is Star Atlas, and how does it maybe differ from other crypto-based games that are out there?Michael (00:57):Yeah. Just on that interpretation of being the most ambitious project, I think that again, that is very subject to interpretation. It is a large vision. It's a very grand vision with a long roadmap ahead of us. Some people, I think, might be concerned about the grandiosity of the underlying vision itself. But we have a lot of confidence in what we're doing and the progress we've made and features and products we've launched and the success we've had to date. So, with that being said, let me just start with the flagship component of what we're building here at Automata, the studio behind Star Atlas, which is a grand strategy, space exploration, massively multiplayer online game.Michael (01:32):And we're building that in Unreal Engine 5. We've been building in UE 5 since early access and of course, building on the Solana blockchain. And one of the really pioneering gaming groups and projects to adopt Solana as our layer one protocol, going all the way back to 2020.Michael (01:47):Now, within this giant strategy MMO, you'll be navigating the stars, you'll be flying your ships. Which, by the way, all of the assets in the game are non-fungible tokens or NFTs. So, flying your ships and operating your land and outfitting your ships with crew members and components and modules, leveling up, progressing, getting new attributes and enhancements, and moving your way through skill trees. So, anybody who's a fan out there of MMOs will be familiar with these gameplay mechanics. But I do want to clarify that, although the Unreal Engine product is our flagship, it is our North Star, it's where we're focusing the majority of our energy, we actually develop across really five different segments within our business. And so, Unreal Engine or the fully immersive triple A game is one of those. We're also building out gameplay modals in browser as well.Michael (02:32):We're using Play Canvas as the game development engine there, and it's fully 3D-enabled, WebGL-based assets. And we actually have a release that's planned for this year; up and coming, anyway. And I'm sure we can get more into what that will look like, later in the conversation. But we also build infrastructure tools, architecture, primitives, that are essential to developing and refining the ecosystem and really encouraging innovation and development around all that we're building at Star Atlas.Michael (02:59):We have a marketplace that we've custom-created from scratch, built from the ground up. And then we also have a mobile gaming division as well. So, obviously a lot there; encompasses a lot. As I said, very big vision. But we're also very surgical in how we approach this and tactical in how we tackle these challenges that are in front of us.Brian (03:15):Yeah. No, I'm super excited about that. And you mentioned a call to arms for MMO-based players out there. I used to be a big wild player back in the day. I totally think this is a really awesome vision. Letting these end users level up in a way that they owning the NFTs that they have and having this be very user-centric, I think,Brian (03:31):Is a really revolutionary model. Before we dive into all of that, could you give us a little background on maybe who you are and who the rest of the founders were, and how did you all decide, "Now is the time that we want to build this game on Solana?"Michael (03:44):Sure. I'll be brief here. I will say my background is in traditional finance. Previously worked in portfolio management. I hold this chartered financial analyst designation, so really expertise in all things investment management and investment analysis decision-making. But the more exciting part of my life started back in 2013, when I got introduced to Bitcoin and cryptocurrencies and really SCRYPT coin mining with GPUs.Michael (04:07):Now, I grew up as a big computer nerd and part of a computer gaming group. Built all my PCs as I was growing up. And we would spend our weekends playing video games and drinking Mountain Dew. And those were our parties. So, one of my buddies from back in that era introduced this idea of building out SCRYPT coin rigs in milk crates. And so, it didn't take me long to essentially sink every penny I had into buying GPUs and just putting these rigs together and getting involved in the blockchain ecosystem. Terrible timing for me. It was immediately preceding the collapse of Mt. Gox in 2013, the largest Fiat on-ramp and exchange at the time.Michael (04:43):And we went through, one of many that I've experienced now, crypto winters and bear cycles. But my interest was certainly captivated. And I just spent the next couple of years learning as much as I could and by 2015 had made the decision to go full-time crypto. 2016 I launched my first company in the space, which was at the center of the legal cannabis industry in crypto, providing financial solutions there. And it was really through that company, and through a series of acquisitions, that I onboarded two individuals who went on to co-found Star Atlas with me. That's Danny Floyd, who's our chief product officer and Jacob Floyd, who's our chief technology officer. And also, along that path, I got connected with Pablo Queiroga, coincidentally, serendipitously, you might say, in Las Vegas, actually in a coffee shop. Just overheard him having a conversation about one of his ventures that he was working on.Michael (05:29):And that was in 2018. But really just fast forward a couple of years: 2020, we're in the middle of the pandemic. The company that I had previously founded, called Tokes, things were moving a bit slow. And just given where our passions, interests, and expertise lie, particularly with Jacob, Danny, and myself, who were all working on Tokes at the time, and understanding, seeing the trends that were moving forward across the crypto space, which was predominantly DeFi, NFTs were up-and-coming in a very nascent stage of blockchain gaming. We just felt that we could actually build something bigger and better. And that was the idea of, "Let's bring a AAA MMO to the blockchain." And by the end of that year, Pablo was fully recruited onto the co-founding team as well. And we had our formal debut in January of 2021. And the team is now about 240 people strong.Brian (06:18):Wow. That is seriously impressive. Like you said, January, 2021, I think you guys were one of the earliest, serious projects that planted your flag on Solana. I'm curious, shifting over to the product now, in addition to being earliest Solana, I think you guys, like you said, you're also early to bringing a AAA game into the blockchain context. In particular, I think you're one of the first major games that is building in Unity Engine 5 and trying to combine that with a crypto world that is normally very web-based. Like you said, you guys are doing some stuff in Canvas and WebGL as well. Can you talk a little bit about that decision to go AAA, to go to the top, Unity Engine 5, and how that implications are for your project?Michael (07:00):Well, I think one of the valid criticisms that exist in, really from the traditional gaming community, but even within this crypto ecosphere, if you will, is that the gameplay mechanics that were present back at that time and even persist through to this day is that they're relatively simple mechanics: a lot of turn-based games, a lot of card-style games. But more importantly, they emphasized the financial components of the gameplay. The idea of play-to-earn, the emergence of play-to-earn. Emphasizing the ability to earn, instead of emphasizing what we feel is most important, which is creating and entertaining an engaging gameplay environment. And so, making a fun game.Michael (07:39):And for us, we're extremely passionate about what we're doing. But a large part of that is we're building the game that we want to play as well. This is essentially living the dream, being able to create the product that we will one day be participating in as well. And we're just extremely excited about it.Michael (07:56):So, the choice at the time was really between Unity and Unreal Engine. Videos were coming out around UE 5, which was not yet released when we started conceptualizing all of this. But there's a couple of pieces of fundamental technology that are coming with UE 5, like Nanite, which is the way that assets are rendered. Polygons are rendered in the game environment. And what is going to be possible in terms of visual fidelity? And so, that was really important, as well as Lumen; is another technology that's new to U E 5, which is the way that light essentially reflects and reacts within the game environment as well.Michael (08:27):And there's a couple of additional pieces there. But what we saw was the potential to create an immersive digital reality, cinematic quality reality. UE 5 is the next generation of gaming, with or without blockchain. Now, what we are doing, adding the fundamentals of blockchain for true asset ownership for a digital asset native economy and for on-chain mechanics that can initiate ecosystem-wide contributions and development to the gaming product itself; we think that is absolutely incredible and will lead to an explosion of growth over time, beyond just the game product itself. But we just saw UE as the best game engine to build within, especially with the opportunities that were present at the time and into the immediate future.Brian (09:08):Yeah. Well, I love that philosophy of building a game that you would want to play and then choosing the right tool for the job there. From the Phantom side, we've definitely seen that interest as well. Just from the metrics that we see of who's using Phantom, what they're connecting to, throughout the last year, Star Atlas is always one of the top projects that people are connecting to. And they're wanting to view their ships, they're super excited about this, and I think you guys have a ton of great momentum into building with Unreal here.Michael (09:31):Big shout out to you guys, if I may just take a moment. Because Phantom came onto the scene. It wasn't the first wallet, but it was, and I think continues to be, the best UI web wallet for the Solana ecosystem. It was already in demand from our users. It was a pretty simple decision for us to integrate. And you guys see the data on your side. We see the data on our analytics. And I think something like 95% of the user base of a couple hundred thousand people across the Star Atlas ecosystem are using Phantom as a wallet. So, big credit to you guys for what you've been able to accomplish there.Brian (10:01):Oh, thanks. Let's keep it going. Let's get gaming on Solana for... I think there's a lot of folks who are really excited about this. I guess, following on that thread, it's been a really busy summer for you guys, across a lot of different aspects. Can you tell us a little bit about some of this events that you guys have had back in June? Specifically, I've seen a lot of noise around 426; maybe what that is, for some folks who are unfamiliar with that?Michael (10:20):Sure. Yeah. I guess just to preface it all, I will mention that we've built a lot, as I've said. We have a lot to continue to build. And we have a community that has been cultivated that is very passionate and enthusiastic, but that also we need to cater to. And so, it's very important for us to interact regularly with our community, engage with our community, keep them informed of the process. And this is truly one of the first times in history, I believe, where a large user base and community is getting the backstage access into the actual process of building a game as complex as Star Atlas.Michael (10:53):And so, a part of that as well is that we're really fostering this ecosystem for collective gameplay. So, guilds: encouraging the gamers to join forces to play across this universe that we're building right now.Michael (11:07):And so, the first event that we hosted this year was called COPA, the Council of Peace Assembly. And this really was a showcase, a place for guilds to highlight the innovation that they're bringing, their recruiting strategies, their intended methods of engaging with a game, of which there are many. We have 28 different career paths in the game that you can take and many different options for player vs. environment, single-player missions that are all scoped out, from deep space PVP with permanent death and destruction of your assets. And so, how you choose to engage is it's really entirely up to the user; there's plentiful options. But doing so with a community and group of other players is probably going to be to the benefit of everyone involved.Michael (11:48):And so, we're really looking to cultivate these relationships between members and help guilds recruit and bring more people in and create strong bonds with their members. And Council of Peace Assembly was an event that was dedicated exclusively to the guilds.Michael (12:01):We sent out a request to all the guilds across our ecosystem. We had 39 submissions from groups that wanted to present their vision for participation in Star Atlas. We had to narrow that down, so we selected 15, based on a set of criteria of presentation materials. And then we hosted an all-day event. We brought in some friends and family and existing partners and some new partners. Relationship with iBUYPOWER, which is one of the largest PC manufacturers in the world, for some custom-branded Star Atlas gear. We actually gave away a top of the line, 3090 Ti-equipped PC to one community member. It was an absolute beast of a machine. I'm kind of jealous, envious that I couldn't win it myself. But-Brian (12:40):Yeah. Yeah, right.Michael (12:42):... great PC. But in any event, the whole point is it was a eight-hour event. 15 different guilds presented, and we had some activities in between and sidetracks that people could participate in. But it was these guilds just presenting, again, their intended approach to Star Atlas, whether that's playing the game, creating a business, creating technology, and how they want to recruit and actually play.Michael (13:02):Moving forward, just towards the end of July, we hosted our first product launch event. And that was called 426 Live. And this is something that is a bit memetic. I won't go too deep into the background of it but in working with the community so closely and trying to provide as much information as possible to them about anticipated timelines for product rollouts, we often refer to the next release coming in four to six weeks. Didn't always or frequently hit those timelines. And so therefore, four to six just became the community meme whenever a projected target date was released.Michael (13:39):And so, we just embraced that. And we've launched the 426 Live. And we think it's really appropriate, just given we had real products coming out. So, on this last one, we rolled out a brand new marketplace program as I described earlier. And one of the biggest releases of the year so far is the official rollout of the Start Atlas Dow. Baseline functionality of the platform with locking in emissions, using the Tribeca framework as part of that overall suite. We launched a Web 3.0 affiliate program; referral program for people that are bringing new members in. We call that Star Path. And then we also, again, solidified the relationship with IBP, iBUYPOWER. And we do have options available now for people to go out and buy Star Atlas-branded PCs, mouse pads, headphones, peripherals. And just really cool to see this Star Atlas-branded gear. And that whole relationship, by the way, just came about because King, the representative there, happened to be a member of our community. And he's just really excited about what's going on across Star Atlas and wanted to get us involved.Brian (14:34):I can't think of another project, I don't think, that has this level of a rabid fan base that wants to be engaged in this key decision-making at this kind of a level. You mentioned a lot here, between all the guilds and the conferences you had around that and the 39 guilds wanting to all present their vision here and the referral programs you guys have; now also, Star Atlas Dow. Let's focus a little bit on the Dow in particular. What is this Dow? What impacts in decision-making do they have on the game as a whole? And who can participate in this? Can I just come in one day and show up? What are the mechanics to this Dow?Michael (15:08):Yeah, I think the concept of Dow's decentralized autonomous organizations, in general, are pretty radical in ideology and what they propose. I would say, even more so in the case of Star Atlas. Here we are, spending enormous time and resources in creating out and building out intellectual property in the form of a gaming product, with the sole intention of taking this ecosystem. And it really does emerge into, as I said earlier, immersive digital environments; the idea of the metaverse. The idea of a place where people can go outside of reality. They can get themselves involved in social aspects and work in education, in commerce; do your shopping there. All things that you can do online today, I think, in some way, are going to live in the metaverse.Michael (15:50):I think it will displace a lot of industry. And I think gaming is one of the core applications there. But we're taking this idea of building the centerpiece of all of that, the gaming product and the ecosystem, and ultimately transitioning control over to the Dow. Which again, in my opinion, very radical proposal to essentially just transfer all of the value that's been created.Michael (16:08):In terms of who can participate, this is, I think, a pretty commonplace model. We have a governance token. It's called POLIS. It's actually a dual token ecosystem. Atlas is our in-game transactional currency, and POLIS is the governance token. But anybody, of course, can acquire POLIS and participate in the Dow. And what I would extend that beyond is, what we've released now is really the universal Dow, the pinnaculum Dow. This is the top level of a hierarchical structure.Michael (16:35):There are elements within the game, within the lore, where political strategy becomes important. And that's at the faction level, it's at the regional level, and it's at the local level. And you can think of this as a county, city, state, federal government, if we were to think of it in modern context of the way that politics is structured. And so, there are gameplay elements that will be influenced. And then there's really the universal Dow, which is just released. And that is to govern the future of Star Atlas itself.Michael (17:03):Now, while I think that this is a paradigm shift and almost antithetical to the way that most companies are built, I also fundamentally embrace fully the idea that significantly more value can be created through these decentralized ecosystems, by opening the pathways to be bidirectional, as opposed to trying to capture all value, retain all value, and create protective walled gardens around it. This is why layer one protocols are succeeding. This is why Solana is succeeding. The idea that you can create primitives in a base layer protocol, that other people can build on top of, is mutually beneficial. It's symbiotic. And we want to do the same thing with the metaverse.Michael (17:43):And so, that's really the idea. That's the vision. We take the idea of the gaming product that attracts people in, it builds this digital society. And then many different functions, features applications, programs, and economies can be built on top of, around it, and tangential to it.Michael (17:58):And so, that's where we're going with this. Now, this is not a short path. America wasn't founded in a day either. So, we have an ethos and a philosophy behind the path to decentralization and how we get from a point where a lot of the content is directed and governed by us, as a more centralized entity at Automata, to one in which Automata is really just a contractor to the Dow. We actually work for the community. We work for the Dow itself. And the Dow is making decisions. Final point I'll make here is that it's specifically because of this philosophy that I think a product like Star Atlas has an indefinite and perpetual life cycle. Because now you're not reliant on the studio to build the 2.0 version and the 3.0 version. It can actually be something that is constantly evolving over time by every contributor around the world that wants to participate in this.Brian (18:49):Yeah. I love that analogy to a layer one blockchain. That opened up my eyes originally, with seeing that anyone from community could just open a GitHub issue and, if they were technical enough, share their vision on how this could improve. And Solana's very open to that. And seeing you guys also position yourself in that way, I think, is really cool, especially as it relates to a AAA game. It's turning the whole industry on its head there.Brian (19:09):So we deep dove a little bit into Dow. You also mentioned a couple other components that you guys have live today, being Star Path. Also your new marketplace. How can end users today interact with the Star Atlas ecosystem, as far as those two respects? And is there anything else that they should be aware of as far as interacting with the Star Atlas ecosystem today?Michael (19:26):Well, first and foremost, I encourage everybody to be informed and educated on what we're doing, what the vision is, what the road ahead looks like. Because I emphasize this all the time. It is a very long journey ahead. We have many years of development. However, our philosophy to development releases is also not conforming to that of a traditional studio. So, we're not building the whole game for 10 years, in isolation, and then rolling that out. We're rolling out components. And I'll speak to one of those in just a moment. But first things first, I would encourage people to read through our white paper, read through our economics paper, read through our quarterly State of the Economy report that was published last month. And also, go check out some of our cinematics, some of our studio trailers, some of our in-engine trailers. It'll really give you a sense of the quality that we're developing too, and what the lore and story behind this is.Michael (20:15):So, that's the first thing. Once people are comfortable with that, options do exist to purchase ships on our marketplace. That's the predominant asset that's out right now, even though land and crew members and components and buildings and structures and all of these things will be available in the future. But for now, the ships are the core asset that people can purchase. They can do that through our marketplace. And it was important for us to get the first, even if simplistic, admittedly simplistic, gaming feature out, which we did on December 17th of last year.Michael (20:42):And we call that SCORE, or Faction Fleet. Score is Ship Commissions on Remote Expeditions. But Faction Fleet. And this is a utility driver for those assets that people have already purchased. It's a way to support your faction through sending or loaning your ships out to the faction, is the story behind it.Michael (20:59):And the player is responsible for managing a set of four different resources. And to the extent that they are keeping those restocked, then the play-to-earn economy is actually activated. So, those players are earning Atlas today. That's one thing you can do.Michael (21:12):I would also encourage everybody to get in Discord because a lot of conversation and strategy and guild formation and guild recruiting, these things are all taking place right now. A lot of speculation around what gameplay mechanics are going to look like, but the Automata team are there as well. And we're interacting frequently and giving guidance and feedback and giving just our current thinking on state of affairs. But going forward, the timing of this podcast is fortuitous. Going forward, very soon, we'll make some announcements around the next 426 Live event for this year.Michael (21:43):And I don't want to reveal exactly what's going to be announced there, but people do know that we have a couple of things in the pipeline, which includes the first Unreal Engine client. And that's called the Showroom. And this is the first time you'll have access to a downloadable client. You can run it on your PC, enter into the Unreal Engine-immersive world, summon your ships, inspect your ships, walk around them, see them at scale. And for anyone that's seen our videos and trailers related to Showroom, I'm sure they can attest to this. But seeing something like a Pure Sex 4, which is a two meter-long air bike, essentially. It's like a hovering motorcycle. Next to some of our largest ships, the Commander class ships that are 300, 400, 700 meters long, you get a real sense of the value of the asset that you've purchased and what it's going to be capable of in-game.Michael (22:30):So, that's up and coming. A new locking mechanism for Atlas, which provides benefits to the marketplace. And last thing I'll add here is, we've also been spending quite a bit of time developing the underlying story behind Star Atlas. And we do have a couple of releases this year, including a graphic novel, which is a comic book format, comic book style, written media that tells the story of Star Atlas before the current era, at least in-game current era, as well as an upcoming podcast sometime this year, which is a storytelling podcast. Not interview style, but it's a storytelling-style podcast that speaks to another aspect, another region in the Star Atlas universe. So, a lot of exciting things up and coming. But I think join the community and read through some of the materials and just have a good time with us in Discord.Brian (23:19):That sounds great. I won't press you for any more spoilers there. We'll wait for the next 426 event. The showroom in particular sounds really exciting. I'm stoked about that. Zooming out now, a little bit longer-term view, you've spoken a little bit about this in your guys' role in merging the AAA gaming and the Web 3.0 worlds, but how do you see these two worlds, that are pretty separate today, converging? And how do you see Star Atlas' place in both of those?Michael (23:44):Well, as a long-time gamer, I see immense value in Web 3.0 gaming, not only for the true asset ownership, not only for the play-to-earn, but again, this idea that you can mutually benefit through co-creation of some idea. I think it's enormous. That, in and of itself, is a paradigm shift that traditional studios would need to get comfortable with. The idea that, "Hey, maybe it makes sense actually for you not to create and retain all of the value, but share in that value and enable a community to co-create that value with you." I think that that is going to be a challenge for almost every traditional business, not just studios, for that matter. Moving into the era of decentralized governance and Dows, and again, Web 3.0, just broadly speaking.Michael (24:28):But again, referring to being a longtime gamer and spending probably tens of thousands of hours in games over my life, it's great to be able to recapture some of that valued, even just through the asset ownership itself or through the account progression, as opposed to being inherently restricted and prohibited from being able to turn around and sell gold that you've farmed or sell a character that you've leveled up. We actually encourage that. We want to facilitate that. You created the value; you get to keep it.Michael (24:57):So, I think Web 3.0 Gaming is absolutely the future. I think that incorporating elements like NFTs and cryptocurrency-based assets into the gameplay add an enormous amount of value. I think for blockchain in general, gaming is going to be a massive contributor to mass adoption of blockchain and cryptocurrency. I think one of the big issues with crypto today is that it's great at attracting the speculator. Anytime you have a high volatility environment, people that have the risk tolerance will enter into the ecosystem to try to capture some portion of that.Michael (25:30):DeFi was a good step, by the way, in more utility-driven functionality, although still a large speculative component. Gaming is different. Gaming is the entertainment value. You cannot overlook the utility. In economic terms, you cannot overlook the utility that is derived by a sense of escapism when joining a game environment. Now, whether or not blockchain was a part of that and whether or not play-to-earn was a part of that, if you create a great product, if you create a great game, people will come to play it. And so now, what we're doing is focusing on that great gameplay and that escapism that people desire out of engaging in video games, but then also enhancing that and saying, "Look, if you want to take it a step further, you can actually derive true financial benefit from this as well. And that's a component that you can layer into your gameplay strategy or not. Play as simple as you want or as complex as you want."Michael (26:20):But I do want to emphasize this idea of, really, development methodology that we use across Star Atlas, which is actually abstracting logic from a game engine and building that logic on the blockchain, using smart contracts. And this exposes the world to the whole idea of permissionless systems and censorship resistance and self-sovereign ownership of assets. The true inception of this philosophy was with the creation of Bitcoin, 12 years ago now, I guess, or 13 years ago. And so, because we're taking game logic, like in the case of Faction Fleet, all of your resource management is done on chain. There are already guilds out there that are creating their own programs, in their own UI, that interfaces with ours and interacts with that and adds more utility to our players. Now, our players can go use a third-party service. And there was no contractual relationship between us and that provider.Michael (27:14):So, the idea that you can initiate this type of innovation, because we're using blockchain as, really, the backend server technology, to me just creates enormous potential for growth. So, I think it's definitely the future. I think the way that we're doing things at Automata, and for Star Atlas, really attempt to capture all of the potential value. Humbly, I feel that we've been leaders in the space, that we have presented a big vision. But I also feel that we've executed well to date. And we will continue to do so. And we will continue to be leaders, not only on Solana, but across blockchain and Web 3.0 in its whole.Brian (27:50):That's awesome. I think that's a great way to wrap things up here. I agree. I think the Solana space is lucky to have you guys as pioneers in pushing forward AAA gaming on Solana. One question we always love to ask anyone, at the end of our discussion here, is: who is a builder that you admire in the Solana ecosystem?Michael (28:09):I almost don't want to answer the question just because picking out one is so difficult. I think, realistically, what we've seen on Solana is, in and of itself, an explosive growth, a Cambrian explosion of innovation. Especially thinking about the early days in the late 2020 and the early '21, where we had to build a lot of the tools that we needed ourselves. And how so many tools are coming online. And you and I were chatting, just before this, about the Solana summer camps and the hackathons and 18,000 submissions to the latest summer camp for project proposals.Brian (28:42):Pretty unreal.Michael (28:43):It is absolutely unreal. So, it's very difficult to isolate one. I think what Metaplex is doing is phenomenal because they're developing some of those same primitives that I'm referring to, that we're actually developing as well, in a different capacity. Magic Eden has done a fantastic job with the marketplace and with the NFT and the PFP drops and cultivating an environment for NFT purchases for industries like gaming as well. So, I think they're doing great. I'd be remiss if I didn't mention Phantom. You guys are awesome. So, maybe I'll just close with that and say I absolutely am thrilled about the Solana ecosystem. Any challenges that we are facing, I am sure, are short-term. And I think Solana's done amazing job, just cultivating a great environment for warm, welcome developers and great innovation.Brian (29:26):I couldn't agree more. Michael Wagner, thanks so much for coming on the show. It's a really great discussion. You mentioned a lot throughout here about how folks could get engaged with Star Atlas. Make sure you join the Discord, join the website. Any closing thoughts here?Michael (29:38):No, that's it. But please do stay tuned. Our 426 Live event is coming up soon. I didn't even mention it, but we have this web client that's coming out this year as well. And we'll probably speak to that at the 426 Live event. We're pretty much @staratlas on any of the socials or staratlas.com. And you can find all the links there. But yeah, I look forward to meeting some new people in our community soon.Brian (29:58):Yeah, we'll have to have you back on to talk about that web-based environ and more exciting announcements for 426. Thanks so much, Michael.Michael (30:05):Thank you, Brian.

Gideon Pt 2, Getting to the Heart of the Matter

heart tales getting to the heart scrypt

Play Episode Listen Later Sep 7, 2022 16:08

Disciple Up # 274 Gideon Pt. 2; Getting to the Heart of the Matter By Louie Marsh, 1-16-2020 Intro. We're taking four weeks to read through six I wrote on the life of Gideon for my radio show, Tales From the Scrypt. Let me know what you think of this short form podcasting ok? Would you like more? Would you like another podcast called Tales from the Scrypt? Or change Disciple Up into this short form scripted format? Let me know, I'm waiting! louie@discipleup.org facebook.com/discipleup

SV pool, Granath v Wright trial & more with Kurt Wuckert | CG Livestream | Episode 34 | Season 2

CoinGeek Weekly Livestream with Kurt Wuckert Jr.

Play Episode Listen Later Sep 3, 2022 60:34

In this installment of CoinGeek Weekly Livestream, host Kurt Wuckert Jr. did an AMA, i.e., Ask Me Anything where he answered questions regarding #SVPool, the mining businesses of Dr. Craig S. Wright, among other topics. Wuckert will be in #Oslo for the court proceedings for the upcoming trial between #Granath and Dr. Wright. Wuckert later revealed the forthcoming launch of Junglebus by #GorillaPool. Tune in for details -Timestamps00:00 - Countdown00:42 - Introduction of Kurt Wuckert Jr.05:52 - CoinGeek Weekly Livestream08:36 - SV node13:12 - BSV18:18 - Solana23:16 - Bitcoin26:58 - Junglebus32:17 - BSV Tulip Trust36:44 - Craig Wright41:56 - CBDC46:14 - Internet as a whole49:59 - BSV blockchain program53:47 - Censorship57:44 - sCrypt & RUN01:00:16 - TeranodeMake sure to like, share, and subscribe, and turn on your notifications, so you never miss the dulcet tones of Mr Wuckert Jr.

internet trial wright pool livestream ama oslo ask me anything sv bsv granath scrypt craig s wright

Gideon Pt 1: Mighty Man of Valor

tales valor mighty man scrypt

Play Episode Listen Later Aug 31, 2022 11:09

Disciple Up # 273 Gideon, Part One: “Mighty Man of Valor: By Louie Marsh, 8-31-2022 Intro. We're taking four weeks to read through six I wrote on the life of Gideon for my radio show, Tales From the Scrypt. Let me know what you think of this short form podcasting ok? Would you like more? Would you like another podcast called Tales from the Scrypt? Or change Disciple Up into this short form scripted format? Let me know, I'm waiting! louie@discipleup.org facebook.com/discipleup

War Stories: Who's In Charge Here?

CoinGeek Weekly Livestream with Kurt Wuckert Jr.

Play Episode Listen Later Aug 24, 2022 53:31

Disciple Up #272 War Stories Pt. 5: Who's In Charge Here? - 2 Chron 20:1-30 By Louie Marsh, 8-24-2022 Intro – Tales From the Scrypt on tap during my trip to Malawi IF I can get it done in time! 2 Some men came and told Jehoshaphat, “A great multitude is coming against you from Edom, from beyond the sea; and, behold, they are in Hazazon-tamar” (that is, Engedi). 2 Chronicles 20:2 (ESV) To Keep Christ 1st in My Life I need too… 1) Go to God and.. 4 And Judah assembled to seek help from the LORD; from all the cities of Judah they came to seek the LORD. 5 And Jehoshaphat stood in the assembly of Judah and Jerusalem, in the house of the LORD, before the new court, 2 Chronicles 20:4-5 (ESV) REMEMBER who God is! 6 and said, “O LORD, God of our fathers, are you not God in heaven? You rule over all the kingdoms of the nations. In your hand are power and might, so that none is able to withstand you. 2 Chronicles 20:6 (ESV) 24 And when they heard it, they lifted their voices together to God and said, “Sovereign Lord, who made the heaven and the earth and the sea and everything in them, Acts 4:24 (ESV) REVIEW my spiritual history. 7 Did you not, our God, drive out the inhabitants of this land before your people Israel, and give it forever to the descendants of Abraham your friend? 8 And they have lived in it and have built for you in it a sanctuary for your name, saying, 2 Chronicles 20:7-8 (ESV) 25 who through the mouth of our father David, your servant, said by the Holy Spirit, “‘Why did the Gentiles rage, and the peoples plot in vain? Acts 4:25 (ESV) RENEW my commitment to Christ! 9 ‘If disaster comes upon us, the sword, judgment, or pestilence, or famine, we will stand before this house and before you—for your name is in this house—and cry out to you in our affliction, and you will hear and save.' 2 Chronicles 20:9 (ESV) Has the heaviness of your old-fashioned church got you weighted down? Try us! We are the New and Improved Lite Church on the River. We feature a 7.5% tithe, a 35-minute worship service with 7 minute sermons. Next Sunday's sermon is on the Feeding of 500. 29 And now, Lord, look upon their threats and grant to your servants to continue to speak your word with all boldness, Acts 4:29 (ESV) 2) ASK & CONFESS at the same time. 12 O our God, will you not execute judgment on them? For we are powerless against this great horde that is coming against us. We do not know what to do, but our eyes are on you.” 2 Chronicles 20:12 (ESV) 3) HEAR & RESPOND to God's Word. 14 And the Spirit of the LORD came upon Jahaziel the son of Zechariah, son of Benaiah, son of Jeiel, son of Mattaniah, a Levite of the sons of Asaph, in the midst of the assembly. 15 And he said, “Listen, all Judah and inhabitants of Jerusalem and King Jehoshaphat: Thus says the LORD to you, ‘Do not be afraid and do not be dismayed at this great horde, for the battle is not yours but God's. 16 Tomorrow go down against them. Behold, they will come up by the ascent of Ziz. You will find them at the end of the valley, east of the wilderness of Jeruel. 17 You will not need to fight in this battle. Stand firm, hold your position, and see the salvation of the LORD on your behalf, O Judah and Jerusalem.' Do not be afraid and do not be dismayed. Tomorrow go out against them, and the LORD will be with you.” 2 Chronicles 20:14-17 (ESV) 4) When the going gets tough, the tough WORSHIP! 18 Then Jehoshaphat bowed his head with his face to the ground, and all Judah and the inhabitants of Jerusalem fell down before the LORD, worshiping the LORD. 19 And the Levites, of the Kohathites and the Korahites, stood up to praise the LORD, the God of Israel, with a very loud voice… 21 And when he had taken counsel with the people, he appointed those who were to sing to the LORD and praise him in holy attire, as they went before the army, and say, “Give thanks to the LORD, for his steadfast love endures forever.” 22 And when they began to sing and praise, the LORD set an ambush against the men of Ammon, Moab, and Mount Seir, who had come against Judah, so that they were routed. 2 Chronicles 20:18-22 (ESV) We were gathered at a little Pentecostal-style church where the preacher had had a difficult time getting the congregation involved.... i.e...amens, etc. This particular Sunday he was preaching on praise and worship. He never noticed his mistake. It was hilarious (but embarrassing we thought) as he yelled out "let everything that hath breasts praise the Lord!" 5) UNDERSTAND that God blesses UNITY. 3 Then Jehoshaphat was afraid and set his face to seek the LORD, and proclaimed a fast throughout all Judah. 4 And Judah assembled to seek help from the LORD; from all the cities of Judah they came to seek the LORD. 5 And Jehoshaphat stood in the assembly of Judah and Jerusalem, in the house of the LORD, before the new court, 2 Chronicles 20:3-5 (ESV) This lyrics to this hymn were written by Isaac Watts in 1777. Robert Lowery wrote the music that we now use in 1867. Watts wrote this hymn as an answer to his critics who had actually split from churches who sang his "human composed" hymns. Prior to this time, churches only sang hymns from the Psalms. Because of the controversy between singing of Psalms and the singing of hymns, the church decided to sing Psalms at the beginning of their service and then after the preaching, they would sing hymns. Many people who were still against the hymns would get up and leave the service at this time. Let those refuse to sing who never knew our God

sCrypt's XiaoHui Liu talks ETH, BSV, on the CoinGeek Weekly Livestream | Episode 20 | Season 2

Play Episode Listen Later Jul 1, 2022 61:59

Streamed live on May 31, 2022 Check out our sponsor: CryptoCraft https://www.cryptocraft.com/?utm_camp... CoinGeek Livestream host Kurt Wuckert Jr. is back from Dubai after attending the first-ever Global Blockchain Convention 2022 and interviewed Xiaohui Liu of #sCrypt this week. The duo discussed the #ETH technology, and how its inability to scale is a hindrance compared to #BitcoinSV. They also revisited moments of the #GBC2022 and appreciated panels and presentations featuring BSV experts. Wuckert gave a shout-out to Liu as one of the smartest developers, encouraging other developers to join the BSV developers' Slack channel.

dubai livestream slack eth liu streamed bsv bitcoin sv scrypt coingeek

192: Xiaohui Liu - sCrypt.io CEO on Bitcoin Smart Contracts, Relationship with Satoshi, BSV

The Friendly Bear

Play Episode Listen Later Jun 30, 2022 44:41

Episode 192: Xiaohui Liu, CEO and Founder of sCrypt.io joins the podcast to discuss his journey into working with smart contracts for Bitcoin SV. Xiaohui also expands on his relationship with Satoshi Nakamoto aka Dr. Craig Wright as well as his experience at the Dubai Bitcoin SV conference in May 2022. Social MediaXiaohui LiuLinkedin: Xiaohui Liu Twitter: sinotrinitysCrypt Blog Class w/ Satoshiwww.scrypt.io

Modernize or Die® - CFML News for March 1st, 2022 - Episode 137

Modernize or Die ® Podcast - CFML News Edition

Play Episode Listen Later Mar 1, 2022 36:57

2022-03-01 Weekly News - Episode 137Watch the video version on YouTube at https://youtu.be/kRi3dMfLPxA Hosts: Gavin Pickin - Senior Developer for Ortus SolutionsDan Card - Senior Developer for Ortus SolutionsThanks to our Sponsor - Ortus SolutionsThe makers of ColdBox, CommandBox, ForgeBox, TestBox and almost every other Box out there. A few ways to say thanks back to Ortus Solutions: Like and subscribe to our videos on YouTube. Help ORTUS reach for the Stars - Star and Fork our Repos https://github.com/coldbox/coldbox-platform https://github.com/Ortus-Solutions/ContentBox/ https://github.com/Ortus-Solutions/commandbox/ https://github.com/ortus-solutions/docker-commandbox https://github.com/Ortus-Solutions/testbox/ https://github.com/coldbox-modules/qb/ https://github.com/coldbox-modules/quick/ https://github.com/coldbox-modules/cbwire https://github.com/Ortus-Solutions/DocBox Star all of your Github Box Dependencies from CommandBox with https://www.forgebox.io/view/commandbox-github Subscribe to our Podcast on your Podcast Apps and leave us a review Sign up for a free or paid account on CFCasts, which is releasing new content every week Buy Ortus's Book - 102 ColdBox HMVC Quick Tips and Tricks on GumRoad (http://gum.co/coldbox-tips) Patreon SupportWe have 36 patreons providing 97% of the funding for our Modernize or Die Podcasts via our Patreon site: https://www.patreon.com/ortussolutions. News and EventsICYMI - Lucee 5.3.9.80 Release Candidate 1 - This release removes all traces of Log4j1With the advent of Lucee 5.3.9 -RC, we now have a build of CommandBox (5.5.0-alpha) which is 100% FREE OF LOG4J 1.x! https://downloads.ortussolutions.com/#/ortussolutions/commandbox/5.5.0-alpha/ Please help us test and use it if you need to get those #infosec monkeys off your back!

Goldshell LT6 3.35Gh/s Profitability reviews Dogecoin and Litecoin miner

Play Episode Listen Later Feb 2, 2022 3:28

BEST PLACE TO BUY CRYPTO MINERS: https://minersdeals.com/ Goldshell KD6: https://youtu.be/Ww9YqQMjdF4 BEST CRYPTO TRADING TRAINING: https://benanalyst.krtra.com/t/Kbmer2... TEENAGERS MAKING $35K MINING CRYPTO: https://youtu.be/QdBAVCr5Xz0 "How much money can you make with Goldshell LT6" "Goldshell LT6 profitability" "Goldshell LT6 reviews" "Goldshell LT6 " "Goldshell LT6 3.35Gh" MAKE $20K/MONTH WITH HIGH TICKET AFFILIATE MARKETING: https://bit.ly/3HmUqBF BECOME BUSINESS ANALYST: https://sfbatraining.com/ BLUEPRINT TO MAKE $20/MONTH ONLINE: https://www.youtube.com/watch?v=dhD8M... HOW TO VISUALIZE: https://youtu.be/J1at4WRuSiM PLAYLISTS: HIGH TICKET AFFILIATE MARKETING TRAINING: https://www.youtube.com/watch?v=sifzx... INSPIRATION & MINDSET: https://www.youtube.com/watch?v=jQOKG... HOW TO MAKE MONEY IN THE US: https://www.youtube.com/watch?v=CilMF... SALESFORCE BUSINESS ANALYST TUTORIAL: https://www.youtube.com/watch?v=tslPG... BUILD BUSINESS CREDIT TO GET FUNDING: https://www.youtube.com/watch?v=qAgKL... HOW TO START A BUSINESS WITH NO MONEY: https://www.youtube.com/watch?v=x7vNr... IMMIGRATION: https://www.youtube.com/watch?v=2R3Bw... Goldshell Lt6 is not on the market yet but it is expected to be released in January 2022, it is another exclusive miner from the manufacturer Goldshell. GoldShell LT6 is a very good option for people looking to mine Litecoin and Dogecoin. It utilizes the Scrypt algorithm with a maximum hash rate of 3.35Gh/s and a maximum power consumption of 3200W. Goldshell LT6 is currently making around $1,500 per month, which means you can earn around $18,000 per year with the device. GoldShell LT6 can be used on major mining pools such as NiceHash, Poolin, AntPool or ViaBTC. GoldShell LT6 uses Scrypt Algorithm and can be used to mine a multitude of coins such as Litecoin, Dogecoin, Verge, Gulden, Viacoin and more. Scrypt algorithm is Less complex compared to other mining algorithms. It has reduced energy consumption compared to other algorithms like SHA-256. Scrypt coins such as Litecoin and dogecoin generally require lower fees for transactions on their blockchains. Scrypt mining is four times faster than mining Bitcoin and it is a great solution for encrypting wallets, files, and passwords. Goldshell LT6 should operate at a low temperature. This will prevent the miner from overheating, which could have a detrimental effect on its lifespan. Ideally, one should operate the miner between temperatures of 5 to 45 degrees Celsius, and amid humidity of 5 to 95%. Goldshell LT6 comes with a PSU and 4 cooling fans. Its size is about 264 x 200 x 290mm and weighs about 12500g. It uses the Ethernet interface to mine, and in standard mining conditions, the noise level is about 80 decibels. The device also comes with a 180-day guarantee. "How much money can you make with Goldshell LT6" "Goldshell LT6 profitability" "Goldshell LT6 reviews" "Goldshell LT6 " "Goldshell LT6 3.35Gh"

mindset inspiration bitcoin immigration verge miners profitability celsius dogecoin sha psu litecoin ethernet gulden nicehash scrypt antpool poolin viabtc

Bitmain Antminer L7 Profitability reviews Most profitable LTC/DOGE Miner

Play Episode Listen Later Feb 1, 2022 3:18

BEST PLACE TO BUY CRYPTO MINERS: https://minersdeals.com/ BEST CRYPTO TRADING TRAINING: https://benanalyst.krtra.com/t/Kbmer2... TEENAGERS MAKING $35K MINING CRYPTO: https://youtu.be/QdBAVCr5Xz0 "How much money can you make with Bitmain Antminer L7" "Bitmain Antminer L7 profitability" "Bitmain Antminer L7 reviews" "Bitmain Antminer L7" "Antminer L7" MAKE $20K/MONTH WITH HIGH TICKET AFFILIATE MARKETING: https://bit.ly/3HmUqBF BECOME BUSINESS ANALYST: https://sfbatraining.com/ BLUEPRINT TO MAKE $20/MONTH ONLINE: https://www.youtube.com/watch?v=dhD8M... HOW TO VISUALIZE: https://youtu.be/J1at4WRuSiM PLAYLISTS: HIGH TICKET AFFILIATE MARKETING TRAINING: https://www.youtube.com/watch?v=sifzx... INSPIRATION & MINDSET: https://www.youtube.com/watch?v=jQOKG... HOW TO MAKE MONEY IN THE US: https://www.youtube.com/watch?v=CilMF... SALESFORCE BUSINESS ANALYST TUTORIAL: https://www.youtube.com/watch?v=tslPG... BUILD BUSINESS CREDIT TO GET FUNDING: https://www.youtube.com/watch?v=qAgKL... HOW TO START A BUSINESS WITH NO MONEY: https://www.youtube.com/watch?v=x7vNr... IMMIGRATION: https://www.youtube.com/watch?v=2R3Bw... Bitmain Antminer L7 (9.5Gh) is among the most profitable miners at the moment. It is not on the market yet but it is supposed to be released anytime soon. Bitmain Antminer L7 is manufactured by Bitmain, mining Scrypt algorithm with a maximum hashrate of 9.5Gh/s for a power consumption of 3425W. Bitmain Antminer L7 can mine up to 35 coins, including litecoin, dogecoin, digibyte, verge and gulden. It is currently making around $160 per day, which means you can earn around $5000 in a single month with this device. and the yearly profits add up to $60,000 The dimensions of the miner are 195 x 290 x 370mm and it weighs 15 kg. Bitmain Antminer L7 operates at a noise level of 75 dB. Through this time, all mining pools are getting together to make hash rate and support available for this particular hardware. The future of the miner looks exceptionally good and this is going to scale the heights of popularity, because to date, Dogecoin is among the most profitable coins. One of the primary advantages that come with using the Scrypt algorithm is the fact that there is less energy or power use as the entire network power is very less. The Scrypt algorithm is here to stay because it reduces the operational costs that the miners require. Similarly, Bitmain Antminer L7 also delivers a much-enhanced performance because of its specs and hardware. Since there are 35 coins to be mined, the manufacturers had no choice but to create a miner whose energy consumption is high. This would, in turn, keep the hash rates high. These specifications will make the miner even more profitable over the months to come. The miner should operate at a low temperature. This will prevent the miner from overheating, which could have a detrimental effect on its lifespan. Ideally, one should operate the miner between temperatures of 5 to 45 degrees Celsius, and amid humidity of 5 to 95%. "How much money can you make with Bitmain Antminer L7" "Bitmain Antminer L7 profitability" "Bitmain Antminer L7 reviews" "Bitmain Antminer L7" "Antminer L7"

mindset inspiration immigration profitable miners profitability db celsius dogecoin doge bitmain scrypt antminer

Bitmain Antminer DR5 Profitability reviews Most profitable Dash Miner

Play Episode Listen Later Feb 1, 2022 4:00

BEST PLACE TO BUY CRYPTO MINERS: https://minersdeals.com/ BEST CRYPTO TRADING TRAINING: https://benanalyst.krtra.com/t/Kbmer2... TEENAGERS MAKING $35K MINING CRYPTO: https://youtu.be/QdBAVCr5Xz0 "How much money can you make with Bitmain Antminer DR5" "Bitmain Antminer DR5 profitability" "Bitmain Antminer DR5 reviews" "Bitmain Antminer DR5" MAKE $20K/MONTH WITH HIGH TICKET AFFILIATE MARKETING: https://bit.ly/3HmUqBF BECOME BUSINESS ANALYST: https://sfbatraining.com/ BLUEPRINT TO MAKE $20/MONTH ONLINE: https://www.youtube.com/watch?v=dhD8M... HOW TO VISUALIZE: https://youtu.be/J1at4WRuSiM PLAYLISTS: HIGH TICKET AFFILIATE MARKETING TRAINING: https://www.youtube.com/watch?v=sifzx... INSPIRATION & MINDSET: https://www.youtube.com/watch?v=jQOKG... HOW TO MAKE MONEY IN THE US: https://www.youtube.com/watch?v=CilMF... SALESFORCE BUSINESS ANALYST TUTORIAL: https://www.youtube.com/watch?v=tslPG... BUILD BUSINESS CREDIT TO GET FUNDING: https://www.youtube.com/watch?v=qAgKL... HOW TO START A BUSINESS WITH NO MONEY: https://www.youtube.com/watch?v=x7vNr... IMMIGRATION: https://www.youtube.com/watch?v=2R3Bw... Bitmain Antminer DR5 was manufactured by Bitmain , The Chinese mining hardware manufacturing leader. The device functions with the same Blake algorithm as the previous version DR3, It has a hash rate of 35TH/S with 1800W power consumption. Bitmain Antminer DR5 is used to mine Decred (DCR). Decred is an excellent community-directed cryptocurrency with built-in governance designed to make it a superior store in the future. Decred's hybrid PoW/PoS consensus mechanism and its continually funded treasury was intended to make the coin secure and adaptable. Currently, on CoinMarketCap, the coin ranks No 62. Antminer Dr5 has a top hash rate of 35Th/s, which means the Antminer Dr5 can make up 34 trillion calculations per second. Bitmain Antminer DR5 is currently making $300 per month, which means you can earn around $3,000 per year using this device. If the price of DCR rises, higher profitability may occur. Antminer Dr5 It comes with a PSU and two cooling fans. Its size is about 175 x 279 x 238 mm and weighs 9.4kg. It uses the Ethernet interface to mine, and in standard mining conditions, the noise level is about 76dB, which is above the noise level of a vacuum cleaner, but it still is ear-friendly. The noise level of 76dB, which is standard for most ASIC miners. The noise level is understandable as miners consume lots of power and require cooling systems, which constitute the noise level. The miner can be heard from a staircase when set up in a residential area. So the owner has to make use of noise isolation techniques, and it is best to set up in mining farms. One advantage of Antminer Dr5 is the potential of its mining algorithm. The Blake-256r 14 was part of the top 5 finalists in the well-known NIST (National Institute of Standards and Technology) competition. According to experts, the Blake 256 is higher than the SHA-256, Scrypt, and Groestl. The recommended ambient temperature should be about 15 to 35 degrees Celsius. To be specific, the miner temperature intake air should fall around this range. Even if the room temperature is cool, the miner's intake temperature might still be high because of dust accumulation or some other reason. You should Clean the miner if needed to regulate the temperature.

technology mindset chinese inspiration immigration standards profitable miners profitability celsius sha psu ethernet asic coinmarketcap bitmain dcr dr3 decred scrypt nist national institute antminer

Goldshell LT5 Pro Profitability reviews Dogecoin and Litecoin miner

Play Episode Listen Later Feb 1, 2022 3:30

BEST PLACE TO BUY CRYPTO MINERS: https://minersdeals.com/ BEST CRYPTO TRADING TRAINING: https://benanalyst.krtra.com/t/Kbmer2... TEENAGERS MAKING $35K MINING CRYPTO: https://youtu.be/QdBAVCr5Xz0 "How much money can you make with Goldshell LT5 Pro" "Goldshell LT5 Pro profitability" "Goldshell LT5 Pro reviews" "Goldshell LT5 Pro " "Goldshell LT5 Pro 2.45 Gh" MAKE $20K/MONTH WITH HIGH TICKET AFFILIATE MARKETING: https://bit.ly/3HmUqBF BECOME BUSINESS ANALYST: https://sfbatraining.com/ BLUEPRINT TO MAKE $20/MONTH ONLINE: https://www.youtube.com/watch?v=dhD8M... HOW TO VISUALIZE: https://youtu.be/J1at4WRuSiM PLAYLISTS: HIGH TICKET AFFILIATE MARKETING TRAINING: https://www.youtube.com/watch?v=sifzx... INSPIRATION & MINDSET: https://www.youtube.com/watch?v=jQOKG... HOW TO MAKE MONEY IN THE US: https://www.youtube.com/watch?v=CilMF... SALESFORCE BUSINESS ANALYST TUTORIAL: https://www.youtube.com/watch?v=tslPG... BUILD BUSINESS CREDIT TO GET FUNDING: https://www.youtube.com/watch?v=qAgKL... HOW TO START A BUSINESS WITH NO MONEY: https://www.youtube.com/watch?v=x7vNr... IMMIGRATION: https://www.youtube.com/watch?v=2R3Bw... GoldShell LT5 pro is a very good option for people looking to mine Litecoin and Dogecoin. It utilizes the Scrypt algorithm with a maximum hash rate of 2.05 GH and a maximum power consumption of 2080 W. The miner was released in March 2021. Looking at the overall design, it looks like other mining products from GoldShell. GoldShell LT5 pro can be used on major mining pools such as NiceHash, Poolin, AntPool or ViaBTC. Dogecoin and Litecoin are quickly becoming profitable coins to mine. GoldShell LT5 pro is currently making around $750 per month, which means you can earn around $9,000 per year with this device. The dimensions of the device are 264 x 200 x 290mm. GoldShell LT5 pro uses Scrypt Algorithm and the greatest advantage of utilizing the Scrypt Algorithm is the speed of transactions. Scrypt Algorithm is best known for quickly confirming Crypto transactions. The reason is that the algorithm was designed to use memory at high speed. This algorithm can generate enough Crypto to handle bulk transactions. It is safe because the speed allows users to get the protection they need against 51% of attacks. For the miner to operate efficiently, it must operate within certain recommended settings. Humidity and temperature play a major role in the lifespan of a miner. Once the miner follows these settings, the device can have a long lifespan. Humidity is set at 5 percent minimum and 95 percent maximum. The optimum temperature levels are set at 35 degrees Celsius maximum and 5 degrees Celsius minimum. The device comes with two fans which facilitate cooling in case of high temperatures Goldshell LT5 also comes with a 180-day warranty. "How much money can you make with Goldshell LT5 Pro" "Goldshell LT5 Pro profitability" "Goldshell LT5 Pro reviews" "Goldshell LT5 Pro " "Goldshell LT5 Pro 2.45 Gh"

mindset inspiration crypto immigration miners profitability celsius dogecoin gh humidity litecoin nicehash scrypt antpool poolin viabtc

60: Basically the Wild West

Code Completion

Play Episode Listen Later Dec 15, 2021 75:44

Welcome to Code Completion, Episode 57! We are a group of iOS developers and educators hoping to share what we love most about development, Apple technology, and completing your code! Follow us @CodeCompletion (https://twitter.com/CodeCompletion) on Twitter to hear about our upcoming livestreams, videos, and other content. Today, we discuss: - Code Completion Club: https://codecompletion.io/jointheclub - Indie App Spotlight, with a new app for you to check out: - DropDMG (https://c-command.com/dropdmg/) by Michael Tsai (https://twitter.com/mjtsai) - NFTs, Blockchains, and Cryptocurrencies - Squidcoin Scam (https://www.wired.com/story/squid-game-coin-crypto-scam/) - Coffeezilla on YouTube (https://www.youtube.com/c/Coffeezilla) - Loot Project (https://www.lootproject.com/) - Steve Mould's Water Computer (https://www.youtube.com/watch?v=IxXaizglscw) - Proof of Stake (https://ethereum.org/en/developers/docs/consensus-mechanisms/pos/) - Mini Review Corner: - Backbone One (https://playbackbone.com/products/backbone-one/) Also, join us for #CompleteTheCode and Compiler Error, two segments that test both your knowledge and our knowledge on Swift, Apple, and all things development! Your hosts for this week: * Fernando Olivares (https://twitter.com/FromJRtoSR) * Spencer Curtis (https://twitter.com/SpencerCCurtis) * Dimitri Bouniol (https://twitter.com/DimitriBouniol) Be sure to also sign up to our monthly newsletter (https://codecompletion.io/), where we will recap the topics we discussed, reveal the answers to #CompleteTheCode, and share even more things we learned in between episodes. You are what makes this show possible, so please be sure to share this with your friends and family who are also interested in any part of the app development process. Sponsor This week's episode of Code Completion is brought to you by Pennant. Go to https://apps.apple.com/app/apple-store/id622463230?pt=1765080&ct=CodeCompletion&mt=8 today to check it out! Complete the Code How can you make sure both load methods run concurrently? ```swift // How can you make sure both load methods run concurrently? func loadItem(_ id: UUID) async { let image = await loadImage(id) let metadata = await loadMetadata(id) presentItem(id, image: image, metadata: metadata) } ``` Be sure to tweet us (https://twitter.com/intent/tweet?text=%23CompleteTheCode%20cc%2F%20%40CodeCompletion&original_referer=https%3A%2F%2Fcodecompletion.io) with hashtag #CompleteTheCode (https://twitter.com/hashtag/CompleteTheCode) if you know the answer! Compiler Error This week's Compiler Error has a theme: Cryptocurrencies! 1 - One of the first cryptocurrencies, Litecoin was created in 2011 based on Scrypt out of concern that GPU-based mining was too high a barrier to entry. 2 - Zcash, founded by Zooko Wilcox, is the first open, permission less financial system employing zero-knowledge security, and employed a “ceremony” to generate the system's private key. 3 - Titcoin was created in 2014 as the first cryptocurrency to be nominated for a major adult industry award, and featured greatly improved transaction speeds over Bitcoin. 4 - iCANhaz was an ill-fated cryptocurrency founded by Burger King in 2018 that could be earned by purchasing cheeseburgers, though most ended up lost since wallets containing the coin were printed on wrappers themselves.

apple development bitcoin nfts ios blockchain cryptocurrency programming swift burger king wild west coding stake gpu litecoin pennant zcash zooko wilcox scrypt steve mould

Minisode 73: Tales From The Scrypt: “Tru Detective, Season 3”

Play Episode Listen Later Dec 3, 2021 38:32

Scryptkeeper Hobert sits down with his friend Will Stagg to talk about Tru Detective, Season 3, a series they conceived to be a third season of the HBO prestige drama True Detective, but not about cops. Hobert and Will review the old notes of their doomed series and talk about the seven episode season and read a part of the pilot. Get ready for pretentious episode titles, an episode that based on the CTA train map, and a destructive finale that never was. Bring out yer dead!!!

312: Spooky Stories

The Bike Shed

Play Episode Listen Later Oct 12, 2021 38:50

Chris evaluates the pros and cons between using Sidekiq or Active Job with Sidekiq. He sees exceptions everywhere. Steph talks about an SSL error that she encountered recently. It's officially spooky season, y'all! sidekiq-symbols (https://github.com/aprescott/sidekiq-symbols) Transcript: CHRIS: Additional radiation just makes Spider-Man more powerful. STEPH: [laughs] Hello and welcome to another episode of The Bike Shed, a weekly podcast from your friends at thoughtbot about developing great software. I'm Steph Viccari. CHRIS: And I'm Chris Toomey. STEPH: And together, we're here to share a bit of what we've learned along the way. Hey, Chris, what's new in your world? CHRIS: Fall is in the air. It's one of those, like, came out of nowhere. I knew it was coming. I knew it was going to happen. But now it's time for pumpkin beer and pumpkin spice lattes, and exclusively watching the movie Hocus Pocus for the next month or so or some variation of those themes. But unrelated to that, I did a thing that I do once, let's call it every year or so, where I had to make the evaluation between Sidekiq or Active Job with Sidekiq, as the actual implementation as the background job engine that is running. And I just keep running through this same cycle. To highlight it, Active Job is the background job system within Rails. It is a nice abstraction that allows you to connect to any of a number of them, so I think Delayed Job is one. Sidekiq is one. Resque is probably another. I'm sure there's a bunch of others. But historically, I've almost always used Sidekiq. Every project I've worked on has used Sidekiq. But the question is do you use Active Job with the adapter set to Sidekiq and then you're sort of living in both worlds, or do you lean in entirely and you use Sidekiq? And so that would mean that your jobs are defined to include Sidekiq::Worker because that's the actual thing that provides the magic as opposed to inheriting from Application Job. And then do you accept all of the trade-offs therein? And every time I go back and forth. And I'm like, well, but I want this feature, but I don't want that feature. But I want these things. So I've made a decision, but I want to talk ever so briefly through the decision points that were part of it. Have you done this back and forth? Are you familiar with the annoying choice that exists here? STEPH: It's been a while since I've had the opportunity to make that choice. I'm usually joining projects where that decision has already been made. So I can't think of a recent time that I've thought through it. And my current project is using that combination of where we are using Active Job and Sidekiq. CHRIS: So I think there's even a middle ground there where that was the configuration that I'd set up on the project that I'm working on. But you can exist in both worlds. And you can selectively opt for certain background jobs to be fully Sidekiq. And if you do that, then instead of saying, "Performlater," You say, "Performasync." And there are a couple of other configurations. It gives you access to the full Sidekiq API. And you can do things like hey, Sidekiq, here's the maximum number of retries or a handful of other things. But then you have to trade away a bunch of the niceties that Active Job gives. So as an example, one thing that Active Job provides that's really nice is the use of GlobalID. So GlobalID is a feature that they added to Rails a while back. And it's a way to uniquely identify a given record within your system such that when you say performlater, you can say, InvitationMailer.performlater and then pass it a user record so like an instance of a user model. And what will happen in the background is that gets serialized, but instead of serializing the whole user object because we don't actually want that, it will do the GlobalID magic. And so it'll turn into, I think it's GID:// so almost like a URL. But then it'll be, I think, your application name/model name down the road. And the Perform method actually gets invoked via the background system. Then you will just get handed that user record back, but it's not the same instance of the user record. It sort of freezes and thaws it. It's really nice. It's a wonderful little feature. Sidekiq wants nothing to do with that. STEPH: I'm so glad that you highlighted that feature because that was on my mind; I think this week where I was reviewing...somebody had made the comment where they were concerned about passing a record to a job and saying how that wouldn't play nicely with Sidekiq. And in the back of my mind, I'm like, yeah, that's right. But then I was also I'm pretty sure this got addressed, though. And I couldn't recall specifically if it was a Sidekiq enhancement or if it was a Rails enhancement. So you just cleared something up for me that I had not had time to confirm myself. So thanks. CHRIS: Well, to be clear, this works if you are using Active Job with Sidekiq as the adapter, but not if you are using a true Sidekiq worker. So if you opt-out of the Active Job flow, then you have to say, "Perform_async," and if you pass it a record, that's not going to work out particularly nicely. The other similar thing is that Sidekiq does not allow the use of keyword args, which, I'm going, to be honest, I really like keyword arguments, especially for background jobs or shuttling data through your system. And there's almost a lazy evaluation. I want some nicety to make sure that when I am putting something into a background job that I'm actually using the correct call signature, essentially passing the correct data in the correct shape. Am I passing a record, or am I passing the ID? Am I passing a list of options or a single option? Those sort of trade-offs that are really easy to subtly get wrong. I came around on this one because I realized although Active Job does support keyword arguments, the way it does that is it just has a JSON serialization format for them. So a keyword argument turns into a positional array with an associated hash that allows for the lookup or whatever. Basically, again, they handle the details. You get to use keyword args, which is great, with the exception that when you're actually calling performlater, that method performlater is a method missing type magic method. So it does not actually check the keyword arguments at that point. You're basically just passing an options hash as opposed to true keyword arguments that would error because they don't match up. And so when I figured that out, I was like, oh, never mind. This doesn't actually do the thing that I care about. It's a little bit nicer in terms of the signature of the method when you're defining your background job itself, but it doesn't actually do any logical checking. It doesn't give me any safety or robustness within my system. So I don't care about that. I did find a project called sidekiq-symbols, which does some things under the hood to how Sidekiq serializes and deserializes jobs, which I think gives largely the same behavior as Active Job. So I can now define my Sidekiq jobs with keyword arguments. Things will work. I can't use GlobalID. That's still out. But that's fine. I can do a little helper method that basically does the same thing as GlobalID or at least close approximation. But sidekiq-symbols lets me have keyword arg-like signatures in my methods; basically, it is. But again, it doesn't actually do any check-in when I'm enqueueing a job, and I am sad about that. STEPH: Yeah, that's another interesting distinction. And I'm unsurprisingly with you that I would favor having keyword args and having that additional safety in place. Okay, so I've been keeping track. And so far, it sounds like we have two points because I'm doing a little scorecard here between Active Job and Sidekiq. And we have two points in favor of Active Job because they offer a GlobalID, which then allows us to pass in a record, and then it takes care of the serialization for us. And then also, keyword args, which I agree with you that's a really nice feature to have in place as well. So I'm curious, so it sounded like you're leaning towards Active Job, but I don't want to spoil the ending. CHRIS: Yes, I could see why that's what you would be taking away from the conversation thus far. So again, just to reiterate, Active Job and Sidekiq with this sidekiq-symbols extension they both support keyword args, kind of. They support defining your job with keyword args and then enqueueing a job passing something that looks like keyword args. But it ends up...nobody's actually checking anything, so it's mostly like a syntactic nicety as opposed to any sort of correctness, which is still nicer, but it's not the thing that I actually want. Either way, nobody supports it, so it is not available to me. Therefore, it is not a consideration point. The GlobalID thing is nice, but it is really, again, it's a nicety more than anything. I have gone, and I'm leaning in the direction of full Sidekiq and Sidekiq everywhere as opposed to Active Job in most cases, but then Sidekiq when we need it. And that's because Sidekiq just has a lot more power and a lot more functionality. So, in particular, Sidekiq has a feature which allows you to say...it's a block that you put at the top of your Sidekiq job that says retries exhausted or something. I think Sidekiq retries exhausted is the actual full name of that at that point, which is really unfortunate in my mind, but anyway, I'll deal. At that point, you know that Sidekiq has exhausted all of the retries, and you can treat it as failed. I'm going, to be honest, I went on a quest to find a way to say, hey, I'm going to put some work into the background. It's really important for me to know if this work succeeds or if it fails. It's very easy to know if it succeeds because that just happens in-line in the method. But we can have an exception raised at basically any point; Sidekiq does a great job of catching those, of retrying, of having fundamental mechanisms there. But this is the best that I can get for this job failed. And so Active Job, as far as I can tell, does not have anything for this in order to say, yep, we are done. We are not going to keep working on this. This work has failed. It is dead. Dead is; actually, I think the more correct term for where we're at because failed is a temporary state, and then you retry after a failure. Whereas dead is, this has gone through all of its retries, and it will never be run again. Therefore, we should treat this as not having run. And in my case, the thing that I want to do is inform the user that this operation that we were trying to do on their behalf has not succeeded, will not succeed. And please reach out or otherwise deal with the fact that we were unable to do the thing that they asked us to do. That feels like a really important thing for me to be able to do, to be able to communicate back to my users. This is one of those situations where I'm looking at the available options, and I'm like, I feel like I can't be the only one who wants to know when something goes wrong. This feels like a thing that's important. But this is the best example that I've found, the Sidekiq retries exhausted block. And unfortunately, when I'm using it, it gets yielded the Sidekiq JSON blob deserialized, so it's like Ruby hash. But it's still like this blob of data. It's not the same data that gets passed into perform. And so, as a result, when I want to look up the record that was associated with it, I have to do this nested dig into the available hash of data. And it just feels like this is not a well-paved path. This is not something that is a deeply thought about or recommended use case. But again, I don't feel like I'm doing something weird here. Am I doing something weird, Steph, wanting to tell my users when I was unable to do the thing they asked me to do? [chuckles] STEPH: That feels like a very rhetorical question. [laughs] CHRIS: It does. I apologize. I'm leading the witness. But in your sincere heart of hearts, what do you think? STEPH: No, that certainly doesn't sound weird. I'm actually thinking back to some of the jobs that cause me stress in regards to knowing when they failed and then having that communication of knowing that we've exhausted all the retries. And, of course, knowing when those retries are exhausted is incredibly helpful. I am intrigued, though,, because you're highlighting that Active Job doesn't have the same option around setting the retry. And I'm trying to recall exactly how it's set. But I feel like I have set the retry count for Active Job. And maybe, as you mentioned before, that's because it's an abstraction, or I'm not sure if Active Job actually has that native support. So I feel a little confused there where I think my default instinct would have been Active Job does have that retry capability. But it sounds like you've discovered otherwise. CHRIS: I'm not actually sure what Active Jobs core retry logic or option looks like. So fundamentally, as far as I understand it, Active Job is an abstraction. And under the hood, you're always connecting an adapter. So it's either going to be Sidekiq, or Resque, or Delayed Job, or other. And each of those systems, whichever system you have as the adapter, is the one that's actually going to be managing retries. And so I know Sidekiq happens to have as a default 25 retries. And that spans, I think it's a two-week exponential back off. And Sidekiq has some very robust logic that they have implemented as the way retries exist within Sidekiq. I'm not sure what that would look like if you're trying to express it abstractly because it is slightly different. I know there was some good work that was done on Sidekiq to allow the Sidekiq options that's a method at the top level of the job, even if it's an Active Job job to express the retries. So that may be what you've seen, or there may be truly an abstraction that exists within Active Job, and then each adapter needs to know how to handle retries. But frankly, the what can Sidekiq do that Active Job can't? There's a whole bunch of stuff around limiting when you would retry limiting, enqueuing a job if there already exists one, when and how do those records get locked. There's a whole bunch of stuff. Sidekiq has a lot of power under the hood. And so if we want to be leaning into that, that's why I'm leaning towards let's just be Sidekiq all the time. Let's become Sidekiq experts. Let's accept that as a deep architectural decision within the app as opposed to just relying on the abstraction. Because fundamentally, if we're just using Active Job, we're not going to have access to the full power of Sidekiq or whatever the underlying system is, so sort of that decision that I'm making, but I don't know specifically around the retries. STEPH: Okay, thanks. That's really helpful. It's been a while since I've had to make this decision. I'm really enjoying you sharing your adventure because I'm trying to think what's the risk? If you don't use Active Job, what are the trade-offs? And you'd mentioned some of them around the GlobalID and keyword args, which are some niceties. But overall, if you don't go with the abstraction, if you lean into Sidekiq, the risk is then you want to migrate to a different enqueuing service. And something that we talk about is mitigating that risk, so then you can swap it out. That's also something I have never done or encountered where we've had to make that change. And it feels like a very low risk in my mind. CHRIS: Sidekiq feels like the thing you would migrate to, not a thing you would migrate from. It feels like it is the most powerful. And if anything, I expect at some point we'll be upgrading to Sidekiq pro or enterprise or whatever the higher versions that you pay for, but you get more features there. So in that sense, that is the calculation. That's the risk trade-off in my mind is that we're leaning into this technology and coupling ourselves more closely to it. But I don't see that as one that will reassess in the same way that people talk about Active Record and it being an ORM. And it's like, oh, we're abstracting the database underneath, and I'm like, no, I'm not. I'm always using Postgres. Please do not take Postgres. I'm not going to switch over to MySQL next week. That's totally fine if you start on MySQL. It's unlikely you're going to port over to Postgres. We may port to an entirely…like it's a Cassandra column store with a Kafka queue, I don't know, something weird down the road. But it's not going to be swapping out Postgres for MySQL or vice versa. Like you said, that's probably not a change that's going to happen. But that I think is the consideration. The other consideration I have in my mind is Active Job is the abstraction that exists within Rails. And so I can treat it as the lowest common denominator, and folks joining the project, it's nice to have that familiarity. So perform_later is the method on the Active Job jobs, and it has a certain shape to it. People may be familiar with that. Mailers will automatically use Active Job just implicitly under the hood. And so there's a familiarity, a discoverability. It's just kind of up the middle choice. And so if I can stick with that, I think there's a nicety there. But in this case, I think I'm choosing I would like the power and consistency on the Sidekiq side, and so I'm leaning into that. STEPH: Yeah, that makes a lot of sense to me. And I liked the other example you provided around things that were not likely to swap out and Postgres, MySQL, your database being one of them. And in favor of an example that I do have for something that...I do enjoy wrapping. It's not something that I adhere to strictly, but I do enjoy it when I have the space to make this choice. So I do enjoy wrapping HTTPClients, not just because then I can swap it out for a different HTTPClient, which frankly, that's also rare that I do that. Once I choose an HTTPClient, I'm probably pretty happy, and I don't need to swap it out. But I really like being able to extend to the API specifically if they don't handle error responses in a way that I would like to or if they raise, and then I want to change the API to have a more thoughtful interface and where I don't have to rescue those errors. But instead, I can interact with this object that then represents an error state. So that was just one example that came to mind for things that I do enjoy having an abstraction around and not just so I can swap it out because that feels like a very low risk, but more frankly, so I can extend the API. CHRIS: I definitely share the I almost always wrap APIs, or I try and hide whatever the implementation detail whether it be HTTPParty, or Faraday or whatever it is that I'm using and trying to hide that deeply within the system. And then I have whatever API client that we define. And that's what we're interacting with. It's interesting that you bring up errors and exceptions there because that's the one other thing that has caused me this...what I'm describing now seems perhaps like, oh, here's just a list of pros and cons, a simple decision was made, and there we are. This represents some real soul searching on my part, if we will. And one of the last things that I ran into that was just so frustrating is that Sidekiq is explicitly built around the idea of exceptions; Sidekiq retries if there is an exception raised in the job, otherwise, it treats it as success, and that's it. That is the entirety of it. That is the story. But if you raise an exception in a job, then you can't test that job because now it's raising an exception. You can't test retries or this retry exhausted block that I'm trying to lean into. I'm like, I want to put that in a feature spec and say, oh, this job goes in the background, but it's in a failure state, and therefore, the user sees the failure message. Sorry, I can't do that because the only way to actually fail a job is via an exception. And I've actually gone to some links in this application to try to introduce more structured data flow. I've talked a bunch about the command objects and the dry-monads and all those things. And I've really loved them where I've gotten to use them. But then I run into one of these edge cases where Sidekiq is like, no, no, no, you can't do that. And so now I have parts of my system that very purposefully return data as opposed to raising an exception. And I just have to turn around and directly raise that failure as an exception, and it just feels less expressive. I actually just ran into the identical thing with Pundit. They have a little bit better control over it; I can choose whether or not I want the raising version or not. But I see exceptions everywhere, and I want a little more discrete data flow. [chuckles] That is my dream. So anyway, I chose Sidekiq is the summary here. And slowly, we're going to migrate entirely to Sidekiq. And I'm going to be totally fine with it. And I'm done griping now. STEPH: This is your own little October Halloween movie, that I see exceptions everywhere. CHRIS: They're so spooky. STEPH: [laughs] That's cool about Pundit. I'm not sure I knew that, that you get to essentially turn on or off that exception flow behavior. On one hand, I'm like, that's nice. You get the option. On the other hand, I'm like, well, let's just not do it. Let's just never raise on people. But at least they give people options; that seems really cool. CHRIS: They do give the option. I think you can choose different strategies there. And also, if we're being honest, I'm newer to Pundit. And I used a different thing, which was to get the Policy Object and ask it a question. I wanted to ask, is this enabled or not? Can a user do this or not? That should not raise an exception. I'm just asking a question. We're just being real chill about this. I just want to know some information. Let's flow some data through our system. We don't need exceptions for that. STEPH: Why are you yelling at me? I just have a question. [laughs] CHRIS: Yeah. I figured out how to be easy on that front. Sidekiq apparently has no be easy mode, but that's fine. You know what? We're going to make it work, and it's going to be fine. But it is interesting deciding which of these facets of the system that I'm building do I really care about? Which are the ones where I'm like, whatever, just pick something, and we'll move forward, it's not a big deal? Versus, we're actually going to be doing a lot of work in the background. This is the thing that I care about deeply. I want to know about failure and success. I want to really understand that and have a robust answer to what our architecture looks like there. Similarly, Pundit for authorization. I believe that authorization will be a critical aspect of our system. It's typically a pretty important thing. But for us, I think we're going to have different types of users who can log in and see different subsets of data and having a consistent and concrete way that we have chosen to implement that we are able to test, that we're able to verify. I think that's another core competency within the app. But you only get to have so many of those. You can only be really good at a couple of things. And so I'm in that place where I'm like, which are our top five when I say are the things that I care a lot about? And then which are the things where I'm like, I don't know, whatever, just run with it? STEPH: Just a little bit ago, I came so close to singing because you said the I want to know phrase again. And that, I'm realizing, [laughs] is a trigger for me and a song where I want to sing. I held it back this time. CHRIS: It's smart. You got to learn anytime you sing on mic that is part of the permanent record. STEPH: Edward Loveall at thoughtbot, since I sang in a recent episode, did the delightful thing where then he grabbed that clip of where you talk a little bit, and then I sing and then encouraged everyone to go listen to it. And in which I responded, like, I would highly recommend that you save your ears and don't listen to it. But yes, singing on the mic is a thing. I do it from time to time. I can't hold it back. CHRIS: We all do. But since it doesn't seem that you're going to sing in this moment, I think I can probably wrap up my Odyssey of choosing between Sidekiq and Active Job. I hope those details were useful to anyone other than me. It was an adventure, so I figured I'd share it. But yeah, that about wraps it up on my side. Mid-roll Ad And now a quick break to hear from today's sponsor, Scout APM. Scout APM is leading-edge application performance monitoring that's designed to help Rails developers quickly find and fix performance issues without having to deal with the headache or overhead of enterprise platform feature bloat. With a developer-centric UI and tracing logic that ties bottlenecks to source code, you can quickly pinpoint and resolve those performance abnormalities like N+1 queries, slow database queries, memory bloat, and much more. Scout's real-time alerting and weekly digest emails let you rest easy knowing Scout's on watch and resolving performance issues before your customers ever see them. Scout has also launched its new error monitoring feature add-on for Python applications. Now you can connect your error reporting and application monitoring data on one platform. See for yourself why developers call Scout their best friend and try our error monitoring and APM free for 14 days; no credit card needed. And as an added-on bonus for Bike Shed listeners, Scout will donate $5 to the open-source project of your choice when you deploy. Learn more at scoutapm.com/bikeshed. That's scoutapm.com/bikeshed. STEPH: So, I would love to talk about an SSL error that I encountered recently. So one of the important processes in our application is sending data to another system. And while sending data to that other system, we started seeing the following error that the read "Certificate verify failed." And then in parens, it states, "Unable to get local issuer certificate." So upon seeing that error, I initially thought, okay, something is wrong with their SSL certificate or their SSL configuration. And that's not something that I have control over and can fix. So we should reach out and let them know to take a look at their SSL config. But it turns out that their team already knew about the issue. They had recently updated or renewed their SSL cert, and they saw our messages were no longer being processed, and they were reaching out to us for help. So at that point, I'm still pretty sure that it's related to something on their end, and it's not something that I can really fix on our end. But we can help them troubleshoot. Maybe there's a workaround that we can add to still get messages processing while they're looking into their SSL config. It seemed like they still just needed help. So it was something that was still worth diving into. So going back to the first error, I want to talk a little bit about it because I realized that I understand SSL just enough, just the surface to get by as a developer. But then, every time that I run into a specific error with it, then I really have to refresh my understanding as to what could be wrong, so then I can troubleshoot more effectively. So for anyone that could use a refresher on that certificate verification process, when your browser or your server is connecting to a site that uses SSL, then your browser server, whichever one you're using, is going to download that site certificate and verify a couple of things. So it's going to check does the certificate contain the domain name of the website? So essentially, you gave us a certificate. Is this your certificate? Does it match the site that we're connecting to? Is this cert issued by a trusted certificate authority? So did someone that we trust give you this certificate? And is the cert still valid, or has it expired? So that part is pretty straightforward. The second part, "Unable to get local issuer certificate," so that's the part I was less certain about. And I took this to mean that they had passed two of those three checks that their cert included the site's name, and it had not expired. But for some reason, we aren't able to determine if their cert was issued by someone that we should trust. So following that journey, my next question was, so what are they giving us? So this is a tool that I don't get to use very often, but I reached for OpenSSL and, specifically, the s_client command, which connects to a specified domain and prints all certificates in the certificate chain. You may already know this, but the certificate chain is basically a fancy way of saying, show me all the certificates necessary to prove your site certificate was authorized by a trusted certificate authority. CHRIS: I did not know that. STEPH: Okay, I honestly didn't either. [laughs] CHRIS: I liked that you thought I would, though. So thank you, but no. [chuckles] STEPH: Yeah, it's one of those areas of SSL where I know just enough. But that was something that was new to me. I thought there was a site certificate, and I didn't realize that there is this chain of certificates that has to be honored. So going back and looking through that output of the certificate chain, that's what highlighted to me that their server was giving us their certificate and saying, hey, you should trust our site certificate. It's legit because it was authorized by, let's say, XYZ certificate. And so if it were a proper certificate chain, then they would give us that XYZ cert. And essentially, we can use this chain of certificates to get back to a trusted authority that then everybody knows that we can trust. However, they weren't actually giving us a reference certificate; they were giving us something else. So essentially, they were saying, "Hey, look at our certificate and look at this very trustworthy reference that we have." But they're actually failing to give us that reference. So to bring it all home, we can download that intermediate certificate that they reference; that is something that is publicly accessible. That's why we're able to then verify each certificate that's provided in that chain. We could go and download that intermediate certificate from that certificate authority. We could combine that with their site-specific certificate, include that in our request to their system, and then complete the certificate chain. And boom, we're back in business. But it was quite a journey. CHRIS: That is quite the journey. And yeah, I definitely knew very little of that, although everything you're saying makes sense. And I have a bunch of cubbyholes in my brain for SSL knowledge. And the words you said all fit into the spaces that I have in my brain, but I didn't know a bunch of those pieces. So thank you for sharing that. SSL and cryptography, more generally or password hashing or things like that, occupy this special place in my brain where I'm both really interested in them. And I will occasionally research them. If I see a blog article, I'll be like, oh yeah, I want to read more about this password hashing. And what's a Salt? And what's a Pepper? And what are we doing there? And what is BCrypt versus SCrypt? What are all these things? This is cool. And almost the arms race on the two sides of how do we demonstrate trust in a secure manner on the internet? But at the same time, I am not allowed to do anything with this information. I outsource this as much as humanly possible because it's one of those things that you just should not do yourself and SSL perhaps even more so. So I have configured aspects of my password hashing. But I 100% just lean on the fact that Let's Encrypt exists in the world. And prior to that, it was a little more work. But frankly, earlier on in my career, I wasn't dealing with the SSL parts of things. But I'm so grateful to Let's Encrypt as a project that exists. And now, on almost every platform that I work with, there's just a checkbox for please do the SSL work for me, make it good, make it work, and then I will be happy. And I'm so glad that that organization exists and really pushed the envelope also. I forget what it was, but it was only like three years ago where SSL was not actually nearly as common as it is now. And now it is pervasive and everywhere. And all of the sites have it, and so that is a wonderful thing. But I don't actually know much. I know that I should have it. I must have it. I should force it. That's true. So I push that out… STEPH: Hello. CHRIS: Are you trying to get me to sing? [chuckles] STEPH: [laughs] No, but I did want to know if you get the reference, the Salt-N-Pepa. CHRIS: Push It Real Good the song? Yeah, okay. STEPH: Yeah, you got it. [chuckles] CHRIS: I will just say the lyrics. I shall not sing the lyrics. I would say that, though, that yes, yes, they do that. STEPH: Thank you for acknowledging my very terrible reference. Circling back just a little bit too in regards to...I'm with you; this is a world that is not one that I am very deeply technical in and something that I learned a fair amount while troubleshooting this particular SSL error. And it was very interesting. But there's also that concern where it's like, that was interesting. And we worked around the issue, but this also feels very fragile. So we still haven't fixed it on their end where they are sending the wrong certificate. So then that's why we had to do more investigative work, and then download the certificate that they meant to send us, and then send back a complete certificate chain so that we don't have this error anymore. But should they change anything about their certificate, should they renew anything like that, then suddenly, we're going to break again. And then, the next developer is going to have to go through the same journey. And this wasn't a light journey. This was a good half-day journey to figure out what was going on and to spend the time, and then to also get that fix out to production. So it's a meaningful task that I don't want anyone else to have to go through. But we are relying on someone else updating their configuration. So, on one hand, we're in a good spot until they are able to update. But on the other hand, I wrote a heck of a commit message for the next person just describing like, friend, just grab some coffee if we're going to chat. It's a very small code change, but you need to know the scoop. So should you need to replicate this because they've changed something, or if this happens…because we work with a number of systems that we send data to. So if someone else should run into a similar issue, they will understand some of the troubleshooting techniques that I used and be able to look up that chain and find out if there's a missing cert or something else they need to provide. So it feels like a win, but I'm also nervous for future selves, future developers. So there's another approach that I haven't mentioned yet, but it was often a top recommendation for when dealing with SSL errors. And specifically, it was turning off SSL verification. And I saw that, and I was like, well, that won't work. I'm definitely sending sensitive, important data. And I need to verify that who I'm sending this to is really the person that I want to send this data to. So that was not an option for me. But it made me very nervous how often that was an approach that people would recommend and be like, oh, it's okay, just turn off SSL. You'll be fine. Like, don't worry about it. CHRIS: I feel like this so perfectly fits into the...some of our work is finding the information and connecting the pieces together and making it work. But some of it is that heuristic sense, that voice in the back of your head that is like, wait, I'm sorry, what? You want me to just turn off the security perimeter and hope that the velociraptors won't come in? That doesn't seem like it's going to end well. I get that that's an easy option that we have available to us right now and will solve the immediate problem but then let's play this out. There are four or five Jurassic Park movies now that tell the story of that. So let's be careful. STEPH: It always ends super well, though, right? Like, it's totally fine. [laughs] CHRIS: [laughs] Exclusively. Although it's funny that you mentioned OpenSSL no verify because just this past week, I used that very same configuration. I think it was okay in my case; I'm pretty sure. But it is interesting because when I saw it, I was like, oh no, can't do that. Certainly not that. Don't turn off the security feature. That's the wrong way to deal with the issue. But in the particular case that I'm working with, I'm using Redis, Heroku Redis, in particular, in a Heroku configuration. And the nature of how Heroku configures the Redis instances and the connectivity to our app into our dyno...I forget why. I read an article. They wrote it; Heroku wrote it. I trust them; they're good. I've outsourced my trust to people that I do trust. The trust chain actually maps really well to the certificate trust chain. I trust that Heroku has taken security deeply seriously. And for some reason, their configuration of Redis requires that I turn on OpenSSL no verify mode. So I'm using this now both in Sidekiq, and then we're using our Redis instance for our Rails cache as well. So in both cases, I said, "It's fine. Don't worry about it." I used the Don't worry about it configuration. And I didn't love it but I think it's okay. And partly, I'm trying to say this into the internet radio right now just in case anyone's listening who's like, no, no, no, you can't do that. That's bad. So I'm willing to be deeply wrong on the internet in favor of someone telling me and then I get to get out in front of it. But I think it's fine. Pretty sure it's fine. It should be fine. STEPH: I love love love that you gave a very visual example of velociraptors, and then you're like, oh, but I turned it off. [laughs] So I'm going to start sending you a velociraptor gif each day. CHRIS: I hope you do. I hope the internet holds you accountable to that. STEPH: [laughs] CHRIS: And I really look forward to [laughs] moving forward because that's a great way to start the day. Well, it doesn't need to start the day, but I look forward to them. STEPH: [laughs] I am really intrigued because I'm with you. Like you said, there are certain entities that are in our trust chain where it's like, hey, you are running this for us, and so I do have faith and trust in you that you wouldn't steer me wrong and provide a bad recommendation. Someone on Stack Overflow telling me to turn off SSL verify uh; that's not my trust chain. Heroku or someone else telling me I'm going to take it a little more seriously. And so I'm also interested in hearing from...what'd you say? You're speaking into the internet phone. [laughs] What'd you say? CHRIS: I think I said internet radio. But yeah, in a way. I mean, we're recording over Skype right now. So in a manner of speaking, we're on the internet phone to make our internet radio show. STEPH: [laughs] Oh goodness, the internet radio. I'm also intrigued to hear if other people are like, oh, no, no, no. Yeah, that sounds like an interesting scenario. Because I would think you'd still want your connection to...you said it's for Redis. So you still want that connection to be verified. But then if Redis itself can't have a specific...yeah, we're testing the boundaries of my SSL knowledge here as to how the heck you would even establish that SSL connection or the verification process. CHRIS: Me too. And it also exists in an interesting space where Heroku is rather clear in their documentation about this. And it was a surprising claim when I saw it. And so, I don't expect them to be flippant about a thing that is important. Like, if they're like, "No, no, no, it is okay. You can turn off the security thing, don't worry." I trust that they're not just like, oh, we didn't think about it too much. But we figured why not? It's not a big deal. I'm sure that they have thought about it deeply because it is an important thing. And so in a weird way, my trust of them and the severity of what this thing represents, I'm like, oh yeah, I super trust that because you're not going to get a major thing wrong. You might get a minor, small, subtle thing wrong. But this is a pretty major configuration change. As I say it, I'm now getting more worried. I'm now like, I feel fine about this. This doesn't seem like a problem at all. But then I keep saying stuff, and I'm like, oh no. That's why I love having a podcast; I find out things about myself as I talk into a microphone to you. STEPH: We come here to share our deep, dark developer secrets. Chris: Spooky developer therapy. STEPH: But just to clarify, even though you've turned off the SSL verify, you're still connecting over SSL. CHRIS: Yes, I believe that's the case. And if I'm remembering, I think the nature of how this works is they're using a self-signed certificate because of shared infrastructure or something, something that made sense when I read it. But it was the idea that they are doing a self-signed certificate. Therefore, to what you were talking about earlier, there isn't the certificate authority in the chain of those because it's self-signed. And so, they are not a trusted certificate authority. Therefore, that certificate that they have generated would not be trusted. But it does still allow for the SSL handshake and then communication to happen over SSL. It's just that fundamental question of trust. I'm saying, in this case, for reasons, it's okay. Trust me that I trust them. We're good. Which, again, I don't feel great about, but I think yes, it is still SSL, but it is a self-signed certificate. So we have to make this configuration change. STEPH: Yeah, all of that makes sense. And it certainly sounds like you have been very thoughtful about that change and put in some investigative work. So on that note, I have a very unrelated bad joke for you. CHRIS: I'm very excited. STEPH: All right, here we go. All right, so what do you call an alligator wearing a vest? CHRIS: I don't know. What do you call an alligator wearing a vest? STEPH: An investigator. [laughter] On that note, shall we wrap up? CHRIS: Oh, let's wrap up. We should also include a link in the show notes to the episode where you told the joke about the elephant hiding in the trees because that's one of my favorite jokes. You slayed me with that one. [laughs] But on that note, yes, let us wrap up. The show notes for this episode can be found at bikeshed.fm. STEPH: This show is produced and edited by Mandy Moore. CHRIS: If you enjoyed listening, one really easy way to support the show is to leave us a quick rating or even a review in iTunes,,as it really helps other folks find the show. STEPH: If you have any feedback for this or any of our other episodes, you can reach us at @_bikeshed or reach me on Twitter @SViccari. CHRIS: And I'm @christoomey STEPH: Or you can reach us at hosts@bikeshed.fm via email. CHRIS: Thanks so much for listening to The Bike Shed, and we'll see you next week. All: Byeeeeeeeeee!!! Announcer: This podcast was brought to you by thoughtbot. thoughtbot is your expert design and development partner. Let's make your product and team a success.

The DEATH of Our Christian Worldview

Modernize or Die ® Podcast - CFML News Edition

Play Episode Listen Later Aug 25, 2021 48:03

Tales From the Scrypt #225 The DEATH of Our Christian Worldview By Louie Marsh, 8-25-2021 Links to Articles: https://www.theblaze.com/news/over-60-percent-christians-jesus-not-only-way-to-heaven https://probe.org/introducing-probes-new-survey-religious-views-and-practices-2020/ “1I charge you in the presence of God and of Christ Jesus, who is to judge the living and the dead, and by his appearing and his kingdom: 2preach the word; be ready in season and out of season; reprove, rebuke, and exhort, with complete patience and teaching. 3For the time is coming when people will not endure sound teaching, but having itching ears they will accumulate for themselves teachers to suit their own passions, 4and will turn away from listening to the truth and wander off into myths. 5As for you, always be sober-minded, endure suffering, do the work of an evangelist, fulfill your ministry.” (2 Timothy 4:1–5, ESV) “3But I am afraid that as the serpent deceived Eve by his cunning, your thoughts will be led astray from a sincere and pure devotion to Christ. 4For if someone comes and proclaims another Jesus than the one we proclaimed, or if you receive a different spirit from the one you received, or if you accept a different gospel from the one you accepted, you put up with it readily enough.” (2 Corinthians 11:3–4, ESV)

god jesus christ death corinthians esv christian worldview 1i 3for 4for 5as scrypt

026: Passwords

Working Code

Play Episode Listen Later Jun 9, 2021 59:05

This week, the crew talks about passwords. Web applications store a great deal of sensitive information. But, there is something categorically different about storing passwords. Because—if compromised—a password from one application may grant a malicious actor access to another application. As such, it is essential that we store our customers' passwords using modern, one-way hashing algorithms that protect the underlying payload against increasingly powerful compute resources. And, that we have a way to evolve our password hashing strategies in order to stay a step ahead of potential attackers.Of course, sometimes the best password hashing strategies is to not store a password at all. Using a "passwordless login" allows you to defer the responsibility of password storage off to another, trusted vendor.Also, we've been doing this podcast for half-a-year! How awesome is that! Yay for us!Triumphs & FailuresAdam's Failure - While Adam has been quite keen on Testing code, he recently ran into a testing scenario that he found very challenging. And, he ended up taking half-a-day to refactor already working code just so that he could add the tests. In the long run, it wasn't a waste of time; but, it was a very humbling experience in the moment.Ben's Triumph - After weeks of struggling to debug an authentication issue within a Sketch plug-in, Ben and his team finally figured out what was going wrong! As fate would often have it, Ben was the engineer that originally wrote the problematic code - so, that was unfortunate. But, at least they figured out how to fix the user experience!Carol's Failure - Carol has been having trouble walking away from problems even when she feels stuck. So, instead of stepping back and clearing her head, she continues to beat it against the wall (often to no avail). She knows this is counterproductive; but, sometimes she gets lost in the details.Tim's Triumph / Failure - Tim finds himself coasting this week. Nothing has been all that note-worthy; either in triumph or in failure.Notes & LinksOWASP Password Cheat Sheet - industry standard best practices for storing passwords - covers Argon2, BCrypt, SCrypt, and PBKDF2.Have I Been Pwned - a service that tells you if your password has been exposed in a data breach.1Password - the world's most-loved password manager.Authy - a user-friendly two-factor authentication app.Shibboleth - an identity provider solution.OAuth - a standard for granting access to a website or application without having to provide it with your password.SAML - a standard for exchanging authentication between parties.Diceware - a method for generation secure, random passwords using playing dice.NIST Password Guidelines - Auth0 explains new passwords guidelines from NIST.Single Sign-On (SSO) - an authentication scheme in which one login grantes access to several, unrelated applications.Netlify Identity Management - a solution for user management in a Netlify app.Firebase Identity Management - a solution for user management in a Firebase app.XKCD: Password Strength - A web comic about how we make passwords hard for people but easy for computers.Follow the show! Our website is workingcode.dev and we're @WorkingCodePod on Twitter and Instagram. Or, leave us a message at (512) 253-2633‬ (that's 512-253-CODE). New episodes drop weekly on Wednesday.And, if you're feeling the love, support us on Patreon.

testing code web passwords triumphs sketch nist 1password firebase oauth netlify have i been pwned saml shibboleth authy scrypt bcrypt pbkdf2 diceware

Modernize or Die® - CFML News for June 1st, 2021 - Episode 106

Play Episode Listen Later Jun 1, 2021 52:08

2021-06-01 Weekly News - Episode 106Watch the video version on YouTube at https://youtu.be/jmA7-rHjomk Hosts: Gavin Pickin - Software Consultant for Ortus SolutionsEric Peterson - Software Consultant for Ortus SolutionsThanks to our Sponsor - Ortus SolutionsThe makers of ColdBox, CommandBox, ForgeBox, TestBox and almost every other Box out there. A few ways to say thanks back to Ortus Solutions: Like and subscribe to our videos on youtube. Sign up for a free or paid account on CFCasts, which is releasing new content every week Buy Ortus's new Book - 102 ColdBox HMVC Quick Tips and Tricks on GumRoad (http://gum.co/coldbox-tips) Patreon SupportWe have 36 patreons providing 84% of the funding for our Modernize or Die Podcasts via our Patreon site: https://www.patreon.com/ortussolutions. If you love our podcasts and all we do for the #coldfusion #cfml community considers chipping in, we are almost there!https://www.ortussolutions.com/blog/we-need-your-help News and EventsLucee 5.3.8.179-RC4 (Final Release Candidate) ReleasedThis will be the Final RC before STABLE, available via your admin or via https://download.lucee.org/There are some improvements for MS SQL users since RC3. There is currently a problem with MS SQL extensions not being available for download, including 7.22, apologies, this will be fixed tomorrow.https://dev.lucee.org/t/lucee-5-3-8-179-rc4-final-release-candidate/8400 Adobe leaking Dev Week Sessions on TwitterAdobe has not added sessions to the Dev Week site yet, but Adobe is tweeting promos with the Session Name, Speaker, date and time on Twitter.https://twitter.com/coldfusionOnline CF Meetup - Getting Started with FusionReactor, with Brad WoodThursday Jun 3rd at 12pm US Eastern Time, UTC-4.New to FusionReactor? Perhaps you have a license but aren't sure how to tap into the features? We'll cover the basics of using FR to profile code, view your running and recent requests, and how to tell what is making a request slow. We'll cover tracking JDBC requests, HTTPS calls, and using the Profiler feature. There are many more features in FR, but we'll cover enough to get you started.https://www.meetup.com/coldfusionmeetup/events/278404050/ Ortus Webinar for June - Eric Peterson - Topic - Build a Blog in 30 minutes with QuickWebinars Page: https://www.ortussolutions.com/events/webinars Registration: coming soonICYMI TestBox v4.3 Released!We are excited to announce a new minor version release of TestBox version 4.3.x. To install just use CommandBox: install testbox --saveDev or to update your TestBox installation update testbox.This update includes several cool new features and improvements that will delight your testing life! For example, we have integrated your favorite code editors to the simple reporter so you can now open the line of code that failed your test or created and exception!https://www.ortussolutions.com/blog/testbox-v43-released Reminder - State of the CF Union SurveyHelp us find out the state of the CF Union – what versions of CFML Engine do people use, what frameworks, tools etc. We will share the summary results with everyone who completes the survey so that you can see how you compare with other CF developers.Spread the news so we can get as many responses as possible.https://teratech.com/state-of-the-cf-union-2021-survey CFCasts Content Updateshttp://www.cfcasts.com New features alert

amazon apple running news speaker explore south blog greek code videos tricks throw released spread survey profile countries adobe tweets conferences blogs stable listing components apis db cf sql coders alb shasta utc gumroad wt modernize profiler invision oop eloquent laravel cold fusion nginx object oriented programming die podcasts itemname regular expressions dockercon swift student challenge rc3 brad wood jdbc scrypt ortus bcrypt c20th adobe coldfusion bad gateway contentbox coldbox

Episode 12: Colin Percival - Developer of Tarsnap and FreeBSD Developer

Open Source Voices

Play Episode Listen Later Mar 30, 2021 57:21

Name Colin Percival is the Developer of Tarsnap and a FreeBSD Developer. Twitter: https://twitter.com/cperciva LinkedIn: https://www.linkedin.com/in/colin-percival-8269672/?originalSubdomain=ca Notes: Colin's Scrypt paper + http://www.tarsnap.com/scrypt/scrypt.pdf Colin's personal website + http://www.daemonology.net Cheri Project + https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/ + https://www.cl.cam.ac.uk/research/security/ctsrd/cheri/cheri-projectideas.html Credits: Music by ikson: https://www.iksonmusic.com Special Guest: Colin Percival.

amazon development security developers programming assembly open source linux percival freebsd scrypt tarsnap

50 Most Dangerous Countries to Follow Jesus In 2021

Play Episode Listen Later Jan 27, 2021 54:06

Tales From the Scrypt # 196 50 Most Dangerous Countries to Follow Jesus In 2021 By Louie Marsh, 1-27-2021 Links to articles read from in show: https://www.christianitytoday.com/news/2021/january/christian-persecution-2021-countries-open-doors-watch-list.html https://www.theguardian.com/world/2021/jan/13/christian-persecution-rises-as-people-refused-aid-in-covid-crisis-report Next Week – Stay Hungry, Disciple's Identity “18“If the world hates you, know that it has hated me before it hated you. 19If you were of the world, the world would love you as its own; but because you are not of the world, but I chose you out of the world, therefore the world hates you. 20Remember the word that I said to you: ‘A servant is not greater than his master.' If they persecuted me, they will also persecute you. If they kept my word, they will also keep yours. 21But all these things they will do to you on account of my name, because they do not know him who sent me. 22If I had not come and spoken to them, they would not have been guilty of sin, but now they have no excuse for their sin. 23Whoever hates me hates my Father also. 24If I had not done among them the works that no one else did, they would not be guilty of sin, but now they have seen and hated both me and my Father. 25But the word that is written in their Law must be fulfilled: ‘They hated me without a cause.'” (John 15:18–25, ESV)

jesus christ father law identity disciples dangerous countries esv 21but scrypt

Slaughter of the Innocent

christmas innocent slaughter real meaning christmas episode scrypt

Play Episode Listen Later Dec 23, 2020 41:47

Disciple Up # 191 Slaughter of the Innocent By Louie Marsh, 12-23-2020 Old Episodes About Christmas: Episode 35: Should Disciples Celebrate Christmas? Episode 36: Tales From the Scrypt – the Christmas Story Episode 87: The Non-Pagan Roots of Christmas Episode 88: Christ IS In X-Mas Episode 139: The Real Meaning of Christmas and Other Christmas Stuff Websites Referenced: https://www.christianpost.com/news/1202-nigerian-christians-killed-in-first-6-months-of-2020-ngo-report.html https://foreignpolicy.com/2020/10/09/christian-victims-in-nigeria-fear-future-attacks/ https://www.christianpost.com/news/nigeria-christian-murdered-fulani-extremists-ambush-attack.html

A tarsnap Special with Colin Percival

Security Headlines

Play Episode Listen Later Aug 25, 2020 63:00

Tarsnap is a backup service running with the slogan "Online backups for the truly paranoid". The service has well earned its slogan as a secure backup option. Created in 2006 by at the time FreeBSD's security officer Dr. Colin Percival, who was responsible for FreeBSD's security advisory. Colin is not only a successful entrepreneur but also a dedicated FreeBSD user. Colin has been getting his hands dirty with FreeBSD in the late 1990'ies when the firewall in his family house running openbsd crashed due to disk failure. After changing the disk he did not manage to figure out how to install OpenBSD so he went with FreeBSD. While studying for his doctrine, he got concern about security, that led him to use freebsd where he later jumped on as FreeBSD security officer. Being the FreeBSD's security officer gave him knowledge of security holes before anyone else did and he needed a secure backup solution for storing his files. After some head scratching, he decided to go the startup route and create his own backup solution. After getting several user requests about having password-protected key storage, Collin created Tarsnap's secure cryptographical solution for protecting keys called "Scrypt", which later got picked up by several opensource projects such as the cryptocurrency project Litecoin. Colin is a very intelligent and trustworthy person, to improve security when connecting and staying connected between machines he creates spiped. Adding a layer of safety on top of just using regular ssh, to mitigate attacks and weaknesses caused by OpenSSL. Because scrypt has a heavy resource need, making it hard for attackers to crack, it became a more secure alternative then the standard hash functions we use in modern systems such as sha1 and md5. The project started to growth and it was soon adopted by various larger companies such as stripe. If you are interested in finding and submitting bugs in Tarsnaps own code base, Colin has put up a Bug bounty rewarding the people that find all kinds of bugs in the code base, a fun fact is that a majority of the security bugs that gets submitted is not found by security researchers looking for holes but by average developers looking at the functions in the code. Today Tarsnap runs on a large set of different systems by a diverse crowd, providing secure storage of data thanks to its stable code base and amazon s3. Colin also donates Tarsnap's December profit to the opensource community sponsoring the FreeBSD foundation, the EuroBSD conference, the bsdcan conference, bsdnow podcast and several other projects. We are super happy to have Colin as a guest on Security Headlines! External links: https://github.com/Tarsnap/spiped https://en.wikipedia.org/wiki/Tarsnap https://en.wikipedia.org/wiki/Scrypt https://www.Tarsnap.com/spiped.html https://www.Tarsnap.com/kivaloo.html https://github.com/Tarsnap/spiped https://www.Tarsnap.com/open-source.html https://github.com/mendsley/bsdiff https://en.wikipedia.org/wiki/Paul_Graham_(programmer) Stay up to date at: https://blog.firosolutions.com

online created external bug litecoin paul graham percival openssl freebsd openbsd scrypt tarsnap

Kiwi Talkz #48 - Robin Rhymes (Battle Rap, Covid-19, Black Lives Matter, Dallas, Donald Trump, New Zealand etc.)

Kiwi Talkz

Play Episode Listen Later Jun 30, 2020 74:05

Robin Rhymes is a battle rapper based out of Dallas, Texas. She was meant to compete at FTH 5 in NZ in late March against Scrypt before Covid-19 hit.SOCIAL MEDIAInstagram - @robinrhymesTwitter - @Robin_RhymesFaceboook - Robin RhymesTIMESTAMPS01:10 - How Robin Is Coping With Covid-1902:12 - Robin Unsure What Kiwis Eat/Indian Food/Netflix04:09 - Black Lives Matter Protests & Riots07:41 - Lockdown Causing People To Go Insane/Marches/Education With Money10:05 - New Zealands Covid-19 Response11:03 - Robin Doesnt Know Dallas Population12:57 - How Robin Got Into Battle Rap15:21 - How Robin Constructs Her Punchlines/Structuring Her Rounds18:38 - Prepping For A Battle/Memory/Offensive Punchlines21:15 - Robin Was Meant To Come To NZ/How The Opportunity Came About22:35 - Robin Hasnt Battled A Guy22:42 - Robins Thoughts On Dizaster24:39 - Robin Wants To Battle DNA26:04 - Charlie Clips Would Make Robin Bring Her A Game/Charlie Clips27:45 - Female Battle Rap29:44 - Switching Into Killer Mode31:07 - Robin Prefers To Battle Early In The Night32:45 - Robin Thinking A Punchline Is Going To Hit And It Doesnt Hit35:00 - NZ Battlers Robin Paid Attention Too35:19 - Talented Steven36:00 - Robin Thinks NZ Crowds Really Support The Battlers37:00 - Female Battle Rappers In America Don't Show Love After A Battle/Ladi Flames39:09 - Robin Wants To Write For Television41:12 - Robin Doesn't Get Stopped On The Street43:00 - Robin Might Relocate To Atlanta At Some Point/NZ Doesnt Have Seafood44:15 - Aucklands House Price Vs Dallas House Price46:49 - HOA(Home Owners Association)48:32 - Tiger King49:15 - Media Sensationalising America50:00 - Donald Trump52:40 - Auckland Black Lives Matter Protest/Dallas Snipers53:50 - Americas Love For Guns/Texas Gun Laws/Robin Doesn92t Have A Gun56:00 - Indians In Dallas & NZ56:40 - Butter Chicken Isnt An Indian Dish57:50 - Hot Wings/Spicy Food/Ghost Pepper59:35 - Robin Gets Annoyed With Her Coworkers/Robin Working Remotely1:01:22 - Kiwis Would Hook Robin Up She Moved To NZ1:01:56 - NZ Has Texas BBQ Food1:02:04 - Raw Thawt1:03:02 - Reece Teaches Robin To Pronounce Maori1:04:00 - Big Polynesian Population In Auckland/2pac Pronounced Wrong By White People1:05:00 - Different American Accents1:06:10 - Robin Adjusting To NZ Battle Rap Terms1:07:30 - Disaster Vs Skolar Battle1:08:35 - Trying To Learn Battle Rap Terms1:09:50 - James Cameron1:10:16 - Americans Underground Bunkers In Queenstown In NZ1:11:17 - Daylyt/Battle Rap Without The Crowd

covid-19 texas donald trump new zealand black lives matter tiger king nz kiwi rhymes battle rap talkz scrypt fth

The Real Meaning of Christmas

christmas meaning of christmas real meaning past shows scrypt

Play Episode Listen Later Dec 18, 2019 49:47

139 Disciple Up Show Notes The Real Meaning of Christmas By Louie Marsh, 12-18-2019 Past Shows on Christmas: Disciple Up #86 – CS Lewis & Christmas Disciple Up #87 – Non-Pagan Roots of Christmas Disciple Up #88 – Christ Is In X-Mas A Christmas Story Part One – written for my radio show, Tales From the Scrypt, which airs each Wednesday on KLPZ, 1380 AM here in Parker. Available at 1380.com on the web. https://www-nytimes-com.cdn.ampproject.org/v/s/www.nytimes.com/2019/12/09/us/nativity-scene-cages-claremont.amp.html?usqp=mq331AQCKAE%3D&_js_v=0.1#aoh=15760221212693&referrer=https%3A%2F%2Fwww.google.com&_tf=From%20%251%24s&share=https%3A%2F%2Fwww.nytimes.com%2F2019%2F12%2F09%2Fus%2Fnativity-scene-cages-claremont.html

Tales from the Scrypt: Untitled Magicians Romantic Comedy (w/ Laura Petro)

Play Episode Listen Later May 24, 2019 26:26

Scyrptkeeper Hobert sits down with new Please Make This host Laura Petro and old host Spencer to discuss Laura’s college-era opus: Untitled Magicians Romantic Comedy. Sure, it never got a title, but it does have mean spirited magicians, romantic heel turns, and one very large rabbit. Abraca-Daring!!!

tales magicians romantic comedies scrypt laura petro

Minisode 24: Tales from the Scrypt: Morning Deliveries (w/ Rob Steinberg)

tales stephen king steinberg deliveries hobert scrypt

Play Episode Listen Later Apr 12, 2019 36:11

Scryptkeeper Hobert sits down with comedian and filmmaker Rob Steinberg to talk about his script for Morning Deliveries, a script he wrote during a rough period of college and later adapted into a short film that was only screened once. Full of 3 week time jumps, inter-dimensional parties, and a the barest of connections to a Stephen King story of the same name, this tale of a little boy with a drug dealing demon (?) crashing in his closet is a jumbled, visually dazzling mess. Rob and Hobert also talk bad screenwriting class memories, mean art teachers, and Rob’s love of setting up chances to fail.

194: My PGP Shame

The Bike Shed

Play Episode Listen Later Apr 12, 2019 47:13

On this week's episode, Chris is joined by Mike Burns, developer in our New York studio, to discuss the ins and outs of application security. Mike recently added a comprehensive Application Security Guide to the thoughtbot guides, and in this chat they discuss some of the high points of the guide, some of the low points of common security holes, and some of the fantastically specific workflows and approaches Mike has for his personal information and security management. Mike Burns on Mastodon Mike Burns on the thoughtbot blog Application Security Guide YAML JSON TOML Bcrypt Scrypt TLS Handshake explained with paint colors NIST - Digital Identity Guidelines Clearance DKIM & SPF for email verification PGP Signing of Emails PGP Signing git Commits Facebook Stored Millions Of Passwords In Plaintext PhishMe (now Cofense) Mutt email client YubiKey Pass pwgen LastPass Perfect Forward Secrecy Tarsnap

new york shame pass forward emails mastodon commits spf lastpass clearance json mutt yubikey yaml dkim mike burns tom l scrypt bcrypt tarsnap phishme perfect forward secrecy

what is Litecoin ?

crypto & cannabis

Play Episode Listen Later Mar 1, 2019 1:25

Litecoin is a peer-to-peer cryptocurrency created by Charlie Lee. It was created based on the Bitcoin protocol but differs in terms of the hashing algorithm used. Litecoin uses the memory intensive Scrypt proof of work mining algorithm. Scrypt allows consumer-grade hardware such as GPU to mine those coins. https://coinmarketcap.com/currencies/litecoin/ --- Support this podcast: https://anchor.fm/joel-aldrich/support

bitcoin gpu litecoin charlie lee scrypt

398: Proper Password Procedures

TechSNAP

Play Episode Listen Later Feb 28, 2019 31:23

We reveal the shady password practices that are all too common at many utility providers, and hash out why salts are essential to proper password storage. Plus the benefits of passphrases, and what you can do to keep your local providers on the up and up.

stand proper procedures passwords utility entropy encryption lastpass cryptography 1password password managers owasp pci dss keepass power company plain text scrypt bcrypt pbkdf2

Minisode 20: Tales from the Scrypt: Doppledemon (w/ Nico Thomas)

Play Episode Listen Later Feb 1, 2019 18:09

Eee-hee-hee! Scryptkeeper Hobert sits down with Nico Thomas to talk about his mirror-murder gore-fest, Doppledemon: the tale of a boy who becomes possessed by a demon every time he looks in a mirror. Full of edge-lord dialogue, fountains of blood and gore, and Jeff Goldblum’s exploding head, can Nico ever make this demonic thriller to life? Or are some scripts better off dead? BRING OUT YER DEAD!

tales jeff goldblum eee scrypt bring out yer dead

Minisode 18: Tales From the Scrypt: Suffragette City (w/ Paula Skaggs)

Play Episode Listen Later Jan 4, 2019 19:48

Eee-hee-hee! Scryptkeeper Hobert sits down with Paula Skaggs to talk about a road trip film about feminist icons Susan B. Anthony and Elizabeth Stanton (or Carry Nation, depending on how exciting you want it to be) traveling the East coast in a horse in buggy. It’s a film that was born as a film, became a sketch, and died in an improv scene. Can Paula and Hobert resurrect the corpse of this love letter to two American icons? And can we make it a rap musical? BRING OUT YER DEAD! Oh btw we are now on Spotify if that floats your boat! Head over there and follow and listen to this ep with your hearts content!

american spotify head tales east suffragettes susan b anthony eee hobert suffragette city carry nation scrypt elizabeth stanton bring out yer dead paula skaggs

Minisode 15: Tales From the Scrypt: Time Neighbors (w/ Mike Scipioni)