In this interview, we sit down with Pauline Shangett. She is the\u00a0Chief Strategy Officer at ChangeNOW and strategic advisor at NOWNodes, to discuss her recent talk at WebX titled \u201cHead in the Clouds: Is Hardware the Key to Sustainable Web3 Infrastructure?\u201d.<\/p>\n
Pauline<\/a> shares her perspective on the changing landscape of Web3 infrastructure, the myths around cloud vs. hardware, and why true resilience is more about people, processes, and strategy than technology alone.<\/p>\n <\/a><\/p>\n In the following, the CSO at ChangeNOW<\/a> shares her insights on some of the most pressing matters for Web3 and beyond.<\/p>\n Pauline, in your WebX keynote you started with a striking line: \u201cWhat\u2019s the scariest thing for a CTO? The hack? No, it\u2019s when everything fails without warning.\u201d Can you explain what you meant by that?<\/strong><\/p>\n Absolutely. When we talk about \u201cscary scenarios\u201d in Web3, most people\u2019s minds go straight to hacks, exploits, or malicious actors. And yes, those are terrifying. But in reality, the situations that shake teams to their core are often much simpler and more mundane: one fire, one missed update, one overloaded endpoint, and suddenly your entire product is offline.<\/p>\n This isn\u2019t a theoretical concern. We\u2019ve seen major platforms brought down not because of sophisticated cyberattacks, but because of a power outage, a faulty cable, or a misconfigured failover system. And when that happens, you\u2019re not just losing uptime. You\u2019re losing user trust, transaction volume, and in some cases, your reputation.<\/p>\n That\u2019s why I framed my keynote as a \u201creality check.\u201d I\u2019m not a CTO, I don\u2019t write code every day, but I talk to teams, founders, infrastructure leads, and chain developers constantly. And what I\u2019ve learned is this: in Web3, your biggest vulnerability is often the one you never expected, the one outside your attack surface but inside your operational risk model. Infrastructure isn\u2019t interesting until it fails. And then it\u2019s the only thing that matters.<\/p>\n Let\u2019s talk about cloud. Everyone knows the benefits like scalability, speed, ease of use. But in your talk, you argued that people overlook the security angle. What did you mean?<\/strong><\/p>\n The narrative around the cloud has always been, \u201cIt\u2019s easy, it\u2019s fast, and it scales.\u201d And that\u2019s true. But when people move away from cloud, the most common justification is security. They\u2019ll say, \u201cI don\u2019t want my nodes or my infrastructure controlled by a centralized provider that could censor me, cut me off, or expose me to surveillance.\u201d<\/p>\n There\u2019s truth in that concern. Centralization at the infrastructure layer introduces risks. But ironically, what I see is that when people ditch the cloud for \u201csafety,\u201d they underestimate another type of risk entirely: physical risk.<\/p>\n Think about it: the cloud\u2019s biggest strength isn\u2019t just elasticity, it\u2019s redundancy. If an AWS region goes down, there are multiple layers of fallback. When you self-host your hardware in a single facility, you don\u2019t have that safety net. And that\u2019s where people can get blindsided.<\/p>\n You gave the example of the KakaoTalk data center fire in South Korea, which paralyzed entire services, including Upbit. Why is that case so important for the Web3 industry?<\/strong><\/p>\n Because it demonstrates something fundamental: failure doesn\u2019t have to be malicious to be catastrophic. When a fire broke out in just one data center in 2022, services across the country froze.<\/p>\n It wasn\u2019t a hack. It wasn\u2019t ransomware. It was smoke. Yet the consequences were massive, users couldn\u2019t log in, transactions were blocked, and the government had to step in. That\u2019s a national-level disruption caused by a single point of failure.<\/p>\n In crypto, we often talk about \u201ccrypto winters\u201d in terms of market downturns. But I think the more pressing crypto winter is operational: wars, floods, fires, cut cables, rolling blackouts. Those aren\u2019t \u201cedge cases.\u201d They\u2019re part of the world we live in. And if you\u2019re not planning for them, you\u2019re essentially gambling with your infrastructure.<\/p>\n So how does NOWNodes approach resilience differently? What does \u201cplanning for failure\u201d look like in practice?<\/strong><\/p>\n At NOWNodes<\/a>, our philosophy is very simple: don\u2019t ask if something will go wrong \u2013 ask when. Because it will. That\u2019s the only certainty in infrastructure.<\/p>\n Our systems are deliberately distributed across multiple regions: the EU, the US, and Asia, with physical presence in countries like Germany, Finland, the Netherlands, the United States, and Singapore. That\u2019s not just a checkbox for compliance. It\u2019s a strategy of survivability: placing nodes where they can withstand political, geographical, and technical risks.<\/p>\n We also operate on a 2N+1 architecture. That means for every critical component like power, compute, network, we don\u2019t just have one backup. We have two, plus a spare. So if one system fails, traffic shifts instantly. If the backup also fails, the spare takes over. It\u2019s a layered safety net.<\/p>\n And we don\u2019t just trust the system blindly. We run regular failover simulations. We intentionally shut down systems in mirrored environments to see what breaks. We do stress tests, region tests, even attack simulations. Because you don\u2019t want the first time you test resilience to be the moment a real crisis happens.<\/p>\n For years, cloud was considered the cheaper option. But you\u2019ve suggested that equation is changing. Can you walk us through that?<\/strong><\/p>\n Five years ago, cloud was the obvious choice. You avoided massive upfront CAPEX, you only paid for what you used, and scaling felt effortless. But that narrative has shifted dramatically.<\/p>\n Today, the \u201cBig Three\u201d cloud providers, like AWS, Google Cloud, Azure, dominate the market. And as happens in any near-monopoly, pricing trends upward. AWS compute costs, for example, rose by more than 20% in just a single year. Almost 40% of companies reported cloud bills spiking by over 25% in the last 12 months.<\/p>\n Meanwhile, hardware has become more predictable. Yes, you pay more on day one \u2013 servers, racks, power. But when you spread that investment over 7 \u2013 10 years, the economics flip. One engineer famously calculated that an $1,100 server costs about $110 per month over a decade. Compare that with $2,000 \u2013 $7,000 per month for equivalent resources in the cloud, and the math speaks for itself.<\/p>\n And beyond cost, hardware gives you freedom. You\u2019re not limited to the features and configurations your cloud provider offers. You can patch, tweak, and deploy exactly how you need to. That level of control can be the difference between smooth scaling and bottlenecked growth.<\/p>\n But even with great hardware or a strong cloud setup, what if your provider simply fails you at a critical moment?<\/strong><\/p>\n That\u2019s exactly the point. Neither cloud nor hardware will save you if your provider ghosts you at 3AM. Infrastructure is only as reliable as the people behind it.<\/p>\n At NOWNodes, when we ask our clients why they choose us, their answers rarely have to do with the specifics of our servers or our architecture. Instead, they talk about the human side, the fact that we respond within minutes, that we scale seamlessly without hidden billing surprises, that we support more than 115 blockchains including the less obvious ones, and that when their RPC crashed at two in the morning, our team was there fixing it in real time.<\/p>\n That\u2019s the reality: infrastructure is as much about trust and responsiveness as it is about technology.<\/p>\n Let\u2019s get into the specifics: backups, multichain reach, and support. What makes your model different?<\/strong><\/p>\n Backups first. Nodes fail. Chains freeze. Updates break compatibility. The real question is: when disaster strikes, what state do you restore? Last week\u2019s? Last month\u2019s? We run geo-distributed backups so that your \u201cworst day\u201d becomes a small bump, not a total blackout.<\/p>\n On multichain reach, most providers top out at 50\u201370 blockchains. Only a handful, maybe 3-5, support 100+. We support 115+ chains, and we\u2019re constantly adding more. Importantly, we don\u2019t just support the trendy chains. For example, we\u2019re the only provider offering shared-node infrastructure for some of the most complex and overlooked blockchains: Monero, eCash, Nano, and more. Because your users won\u2019t wait for you to \u201cmaybe\u201d support their asset. They\u2019ll leave.<\/p>\n Finally, support. We don\u2019t believe in chatbots or endless ticket escalations. So our clients get real engineers in their Telegram or Slack. Average response time: under three minutes. Resolution time: hours, not days, even for deep technical bugs. And that\u2019s not a premium upsell. That\u2019s our baseline.<\/p>\n Pricing models in infrastructure can be notoriously opaque. How do you approach transparency?<\/strong><\/p>\n Most RPC providers rely on complex tiering, hidden throttles, and surprise charges. One day everything looks fine, the next day you\u2019ve crossed some invisible threshold because a botnet spiked your traffic, and suddenly your bill triples. Or worse, they just cut you off mid-transaction.<\/p>\n We took a very different approach. Our pricing is clear, subscription-based, and predictable. You always know exactly what you\u2019re paying for. When you need more capacity, scaling is fast, fairly priced, and transparent. There\u2019s no hostage negotiation.<\/p>\n That predictability is one of the main reasons our clients stay with us. Because in Web3, uncertainty is everywhere \u2013 in the markets, in regulation, in adoption. The last thing you want is uncertainty in your infrastructure bill.<\/p>\n So back to your original question: is hardware the key to sustainable Web3 infrastructure?<\/strong><\/p>\n No. And neither is cloud. The real key is resilience.<\/p>\n Resilience comes from smart backups, distributed systems, human-centric support, transparent pricing, and true multichain reach. It\u2019s not something you rent. It\u2019s something you build.<\/p>\n Infrastructure is boring until it\u2019s not. Until your endpoint falls, your TVL disappears, your users rage quit, and your logs say nothing. That\u2019s when you realize infrastructure is more than servers. It\u2019s trust. It\u2019s the silent contract between your product and the people who keep it alive.<\/p>\n Final thoughts? What should Web3 teams take away from your message?<\/strong><\/p>\n I\u2019d say this: stop treating infrastructure as an afterthought. It\u2019s the bedrock of your product. You can have the best UI, the smartest tokenomics, and the most loyal community, but if your infrastructure fails, none of that matters.<\/p>\n Don\u2019t ask, \u201cHow do I save money this month?\u201d Ask, \u201cHow do I survive the crisis I haven\u2019t seen yet?\u201d Because it\u2019s coming. The teams that will still be here in five years aren\u2019t the ones who cut corners. They\u2019re the ones who build resilience from day one.<\/p>\n The post Beyond the Cloud: Building Resilient Web3 Infrastructure, Interview with Pauline Shangett, Chief Strategy Officer at ChangeNOW<\/a> appeared first on CryptoPotato<\/a>.<\/p>","protected":false},"excerpt":{"rendered":" In this interview, we sit down with Pauline Shangett. She is the\u00a0Chief Strategy Officer at ChangeNOW and strategic advisor at NOWNodes, to discuss her recent talk at WebX titled \u201cHead in the Clouds: Is Hardware the Key to Sustainable Web3 Infrastructure?\u201d. Pauline shares her perspective on the changing landscape of Web3 infrastructure, the myths around […]<\/p>\n","protected":false},"author":0,"featured_media":92123,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-92122","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-discovery"],"_links":{"self":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/92122"}],"collection":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=92122"}],"version-history":[{"count":0,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/92122\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/media\/92123"}],"wp:attachment":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=92122"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=92122"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=92122"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
![<\/a><\/p>\nIn the following, the CSO at ChangeNOW<\/a> shares her insights on some of the most pressing matters for Web3 and beyond.<\/p>\nPauline, in your WebX keynote you started with a striking line: \u201cWhat\u2019s the scariest thing for a CTO? The hack? No, it\u2019s when everything fails without warning.\u201d Can you explain what you meant by that?<\/strong><\/p>\nAbsolutely. When we talk about \u201cscary scenarios\u201d in Web3, most people\u2019s minds go straight to hacks, exploits, or malicious actors. And yes, those are terrifying. But in reality, the situations that shake teams to their core are often much simpler and more mundane: one fire, one missed update, one overloaded endpoint, and suddenly your entire product is offline.<\/p>\nThis isn\u2019t a theoretical concern. We\u2019ve seen major platforms brought down not because of sophisticated cyberattacks, but because of a power outage, a faulty cable, or a misconfigured failover system. And when that happens, you\u2019re not just losing uptime. You\u2019re losing user trust, transaction volume, and in some cases, your reputation.<\/p>\nThat\u2019s why I framed my keynote as a \u201creality check.\u201d I\u2019m not a CTO, I don\u2019t write code every day, but I talk to teams, founders, infrastructure leads, and chain developers constantly. And what I\u2019ve learned is this: in Web3, your biggest vulnerability is often the one you never expected, the one outside your attack surface but inside your operational risk model. Infrastructure isn\u2019t interesting until it fails. And then it\u2019s the only thing that matters.<\/p>\nLet\u2019s talk about cloud. Everyone knows the benefits like scalability, speed, ease of use. But in your talk, you argued that people overlook the security angle. What did you mean?<\/strong><\/p>\nThe narrative around the cloud has always been, \u201cIt\u2019s easy, it\u2019s fast, and it scales.\u201d And that\u2019s true. But when people move away from cloud, the most common justification is security. They\u2019ll say, \u201cI don\u2019t want my nodes or my infrastructure controlled by a centralized provider that could censor me, cut me off, or expose me to surveillance.\u201d<\/p>\nThere\u2019s truth in that concern. Centralization at the infrastructure layer introduces risks. But ironically, what I see is that when people ditch the cloud for \u201csafety,\u201d they underestimate another type of risk entirely: physical risk.<\/p>\nThink about it: the cloud\u2019s biggest strength isn\u2019t just elasticity, it\u2019s redundancy. If an AWS region goes down, there are multiple layers of fallback. When you self-host your hardware in a single facility, you don\u2019t have that safety net. And that\u2019s where people can get blindsided.<\/p>\nYou gave the example of the KakaoTalk data center fire in South Korea, which paralyzed entire services, including Upbit. Why is that case so important for the Web3 industry?<\/strong><\/p>\nBecause it demonstrates something fundamental: failure doesn\u2019t have to be malicious to be catastrophic. When a fire broke out in just one data center in 2022, services across the country froze.<\/p>\nIt wasn\u2019t a hack. It wasn\u2019t ransomware. It was smoke. Yet the consequences were massive, users couldn\u2019t log in, transactions were blocked, and the government had to step in. That\u2019s a national-level disruption caused by a single point of failure.<\/p>\nIn crypto, we often talk about \u201ccrypto winters\u201d in terms of market downturns. But I think the more pressing crypto winter is operational: wars, floods, fires, cut cables, rolling blackouts. Those aren\u2019t \u201cedge cases.\u201d They\u2019re part of the world we live in. And if you\u2019re not planning for them, you\u2019re essentially gambling with your infrastructure.<\/p>\nSo how does NOWNodes approach resilience differently? What does \u201cplanning for failure\u201d look like in practice?<\/strong><\/p>\nAt NOWNodes<\/a>, our philosophy is very simple: don\u2019t ask if something will go wrong \u2013 ask when. Because it will. That\u2019s the only certainty in infrastructure.<\/p>\nOur systems are deliberately distributed across multiple regions: the EU, the US, and Asia, with physical presence in countries like Germany, Finland, the Netherlands, the United States, and Singapore. That\u2019s not just a checkbox for compliance. It\u2019s a strategy of survivability: placing nodes where they can withstand political, geographical, and technical risks.<\/p>\nWe also operate on a 2N+1 architecture. That means for every critical component like power, compute, network, we don\u2019t just have one backup. We have two, plus a spare. So if one system fails, traffic shifts instantly. If the backup also fails, the spare takes over. It\u2019s a layered safety net.<\/p>\nAnd we don\u2019t just trust the system blindly. We run regular failover simulations. We intentionally shut down systems in mirrored environments to see what breaks. We do stress tests, region tests, even attack simulations. Because you don\u2019t want the first time you test resilience to be the moment a real crisis happens.<\/p>\nFor years, cloud was considered the cheaper option. But you\u2019ve suggested that equation is changing. Can you walk us through that?<\/strong><\/p>\nFive years ago, cloud was the obvious choice. You avoided massive upfront CAPEX, you only paid for what you used, and scaling felt effortless. But that narrative has shifted dramatically.<\/p>\nToday, the \u201cBig Three\u201d cloud providers, like AWS, Google Cloud, Azure, dominate the market. And as happens in any near-monopoly, pricing trends upward. AWS compute costs, for example, rose by more than 20% in just a single year. Almost 40% of companies reported cloud bills spiking by over 25% in the last 12 months.<\/p>\nMeanwhile, hardware has become more predictable. Yes, you pay more on day one \u2013 servers, racks, power. But when you spread that investment over 7 \u2013 10 years, the economics flip. One engineer famously calculated that an $1,100 server costs about $110 per month over a decade. Compare that with $2,000 \u2013 $7,000 per month for equivalent resources in the cloud, and the math speaks for itself.<\/p>\nAnd beyond cost, hardware gives you freedom. You\u2019re not limited to the features and configurations your cloud provider offers. You can patch, tweak, and deploy exactly how you need to. That level of control can be the difference between smooth scaling and bottlenecked growth.<\/p>\nBut even with great hardware or a strong cloud setup, what if your provider simply fails you at a critical moment?<\/strong><\/p>\nThat\u2019s exactly the point. Neither cloud nor hardware will save you if your provider ghosts you at 3AM. Infrastructure is only as reliable as the people behind it.<\/p>\nAt NOWNodes, when we ask our clients why they choose us, their answers rarely have to do with the specifics of our servers or our architecture. Instead, they talk about the human side, the fact that we respond within minutes, that we scale seamlessly without hidden billing surprises, that we support more than 115 blockchains including the less obvious ones, and that when their RPC crashed at two in the morning, our team was there fixing it in real time.<\/p>\nThat\u2019s the reality: infrastructure is as much about trust and responsiveness as it is about technology.<\/p>\nLet\u2019s get into the specifics: backups, multichain reach, and support. What makes your model different?<\/strong><\/p>\nBackups first. Nodes fail. Chains freeze. Updates break compatibility. The real question is: when disaster strikes, what state do you restore? Last week\u2019s? Last month\u2019s? We run geo-distributed backups so that your \u201cworst day\u201d becomes a small bump, not a total blackout.<\/p>\nOn multichain reach, most providers top out at 50\u201370 blockchains. Only a handful, maybe 3-5, support 100+. We support 115+ chains, and we\u2019re constantly adding more. Importantly, we don\u2019t just support the trendy chains. For example, we\u2019re the only provider offering shared-node infrastructure for some of the most complex and overlooked blockchains: Monero, eCash, Nano, and more. Because your users won\u2019t wait for you to \u201cmaybe\u201d support their asset. They\u2019ll leave.<\/p>\nFinally, support. We don\u2019t believe in chatbots or endless ticket escalations. So our clients get real engineers in their Telegram or Slack. Average response time: under three minutes. Resolution time: hours, not days, even for deep technical bugs. And that\u2019s not a premium upsell. That\u2019s our baseline.<\/p>\nPricing models in infrastructure can be notoriously opaque. How do you approach transparency?<\/strong><\/p>\nMost RPC providers rely on complex tiering, hidden throttles, and surprise charges. One day everything looks fine, the next day you\u2019ve crossed some invisible threshold because a botnet spiked your traffic, and suddenly your bill triples. Or worse, they just cut you off mid-transaction.<\/p>\nWe took a very different approach. Our pricing is clear, subscription-based, and predictable. You always know exactly what you\u2019re paying for. When you need more capacity, scaling is fast, fairly priced, and transparent. There\u2019s no hostage negotiation.<\/p>\nThat predictability is one of the main reasons our clients stay with us. Because in Web3, uncertainty is everywhere \u2013 in the markets, in regulation, in adoption. The last thing you want is uncertainty in your infrastructure bill.<\/p>\nSo back to your original question: is hardware the key to sustainable Web3 infrastructure?<\/strong><\/p>\nNo. And neither is cloud. The real key is resilience.<\/p>\nResilience comes from smart backups, distributed systems, human-centric support, transparent pricing, and true multichain reach. It\u2019s not something you rent. It\u2019s something you build.<\/p>\nInfrastructure is boring until it\u2019s not. Until your endpoint falls, your TVL disappears, your users rage quit, and your logs say nothing. That\u2019s when you realize infrastructure is more than servers. It\u2019s trust. It\u2019s the silent contract between your product and the people who keep it alive.<\/p>\nFinal thoughts? What should Web3 teams take away from your message?<\/strong><\/p>\nI\u2019d say this: stop treating infrastructure as an afterthought. It\u2019s the bedrock of your product. You can have the best UI, the smartest tokenomics, and the most loyal community, but if your infrastructure fails, none of that matters.<\/p>\nDon\u2019t ask, \u201cHow do I save money this month?\u201d Ask, \u201cHow do I survive the crisis I haven\u2019t seen yet?\u201d Because it\u2019s coming. The teams that will still be here in five years aren\u2019t the ones who cut corners. They\u2019re the ones who build resilience from day one.<\/p>\nThe post Beyond the Cloud: Building Resilient Web3 Infrastructure, Interview with Pauline Shangett, Chief Strategy Officer at ChangeNOW<\/a> appeared first on CryptoPotato<\/a>.<\/p>","protected":false},"excerpt":{"rendered":"In this interview, we sit down with Pauline Shangett. She is the\u00a0Chief Strategy Officer at ChangeNOW and strategic advisor at NOWNodes, to discuss her recent talk at WebX titled \u201cHead in the Clouds: Is Hardware the Key to Sustainable Web3 Infrastructure?\u201d. Pauline shares her perspective on the changing landscape of Web3 infrastructure, the myths around […]<\/p>\n","protected":false},"author":0,"featured_media":92123,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-92122","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-discovery"],"_links":{"self":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/92122"}],"collection":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=92122"}],"version-history":[{"count":0,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/posts\/92122\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=\/wp\/v2\/media\/92123"}],"wp:attachment":[{"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=92122"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=92122"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mycryptomania.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=92122"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}](\"http:\/\/cryptopotato.com\/wp-content\/uploads\/2025\/08\/Screenshot-2025-08-28-at-22.43.26.png\"){kind=link}