We offer machine driven closing programs to facilitate your real estate business

Doma

doma

This paper is available on arxiv under CC 4.0 license.
Authors:
(1) Oded Blumenthal, Software and Information Systems Engineering, Ben Gurion University, Israel;
(2) Guy Shani, Software and Information Systems Engineering, Ben Gurion University, Israel. Table of Links Introduction
Background
Related Work
POMCP for Stochastic Contingent Planning
Domain Independent Heuristics for POMCP
Empirical Evaluation
Conclusion and References 5 Domain Independent Heuristics for POMCP We now describe the main contribution of this paper — two domain independent rollout heuristics that leverage methods developed in the automated planning community, using the structure specified in the stochastic contingent planning problem. 5.1 Delete Relaxation Heuristics Delete relaxation heuristics are built upon the notion that if actions have only positive effects, then the number of actions that can be executed before the state becomes fixed is finite, and in many cases, small. Also, as actions cannot destroy the precondition of other actions, one can execute actions in parallel. Algorithm 2 portrays a delete relaxation heuristic. Delete relaxation heuristics create a layered graph, interleaving action and fact layers. The first layer, which is a fact layer, contains all the facts that hold in the state for which the heuristic is computed (line 2). The second layer, which is an action layer, contains all the actions whose preconditions hold given the facts in the first layer (line 5). The next layer, which is again a fact layer, contains all the positive effects of the actions in the previous layer, as well as all facts from the previous layer (line 6), and so forth. We stop developing the graph once no new facts can be obtained (line 8). 5.2 Heuristics in Belief Space A major disadvantage of the above heuristics is that they focus on a single state. When the agent is aware of the true state of the system, observations have no value. Hence, the above heuristics, as well as any heuristic that is based on a single state, do not provide an estimate for the value of information, which is a key advantage of POMDPs. We hence suggest now a heuristic that is computed over a set B of possible states (Algorithm 3). We compute again the delete relaxation graph, with a few modifications. We compute for each state in B a separate fact layer. An action can be applied only if its preconditions are satisfied in the fact layers of all agents (line 7). This is equivalent to the requirement in contingent planning where an action is applicable only if it is applicable in all states in the current belief, where B is served as an approximation of the true belief state. Second, our method leverages the deterministic observations, that allow us to filter out states that are inconsistent with the received observation (lines 8-14). When a sensing action can be applied, all states that do not agree with the value of s on the observation are discarded from B (lines 10-14). That is, we remove the fact layers corresponding to these states, and no longer consider them when computing which actions can be applied. We stop when both no states were discarded, and no new facts were obtained (line 17). This process must take into account sensing actions to remove states that are incompatible with s, which would allow, at the next iteration, that action preconditions would be satisfied for less states, and hence additional actions can be executed. This paper is available on arxiv under CC 4.0 license. Authors: (1) Oded Blumenthal, Software and Information Systems Engineering, Ben Gurion University, Israel; (2) Guy Shani, Software and Information Systems Engineering, Ben Gurion University, Israel. This paper is available on arxiv under CC 4.0 license. Authors: Authors: (1) Oded Blumenthal, Software and Information Systems Engineering, Ben Gurion University, Israel; (2) Guy Shani, Software and Information Systems Engineering, Ben Gurion University, Israel. Table of Links Introduction Background Related Work POMCP for Stochastic Contingent Planning Domain Independent Heuristics for POMCP Empirical Evaluation Conclusion and References Introduction Introduction Background Background Related Work Related Work POMCP for Stochastic Contingent Planning POMCP for Stochastic Contingent Planning Domain Independent Heuristics for POMCP Domain Independent Heuristics for POMCP Empirical Evaluation Empirical Evaluation Conclusion and References Conclusion and References 5 Domain Independent Heuristics for POMCP We now describe the main contribution of this paper — two domain independent rollout heuristics that leverage methods developed in the automated planning community, using the structure specified in the stochastic contingent planning problem. 5.1 Delete Relaxation Heuristics Delete relaxation heuristics are built upon the notion that if actions have only positive effects, then the number of actions that can be executed before the state becomes fixed is finite, and in many cases, small. Also, as actions cannot destroy the precondition of other actions, one can execute actions in parallel. Algorithm 2 portrays a delete relaxation heuristic. Delete relaxation heuristics create a layered graph, interleaving action and fact layers. The first layer, which is a fact layer, contains all the facts that hold in the state for which the heuristic is computed (line 2). The second layer, which is an action layer, contains all the actions whose preconditions hold given the facts in the first layer (line 5). The next layer, which is again a fact layer, contains all the positive effects of the actions in the previous layer, as well as all facts from the previous layer (line 6), and so forth. We stop developing the graph once no new facts can be obtained (line 8). 5.2 Heuristics in Belief Space A major disadvantage of the above heuristics is that they focus on a single state. When the agent is aware of the true state of the system, observations have no value. Hence, the above heuristics, as well as any heuristic that is based on a single state, do not provide an estimate for the value of information, which is a key advantage of POMDPs. We hence suggest now a heuristic that is computed over a set B of possible states (Algorithm 3). B We compute again the delete relaxation graph, with a few modifications. We compute for each state in B a separate fact layer. An action can be applied only if its preconditions are satisfied in the fact layers of all agents (line 7). This is equivalent to the requirement in contingent planning where an action is applicable only if it is applicable in all states in the current belief, where B is served as an approximation of the true belief state. B B Second, our method leverages the deterministic observations, that allow us to filter out states that are inconsistent with the received observation (lines 8-14). When a sensing action can be applied, all states that do not agree with the value of s on the observation are discarded from B (lines 10-14). That is, we remove the fact layers corresponding to these states, and no longer consider them when computing which actions can be applied. B We stop when both no states were discarded, and no new facts were obtained (line 17). This process must take into account sensing actions to remove states that are incompatible with s , which would allow, at the next iteration, that action preconditions would be satisfied for less states, and hence additional actions can be executed. s

Rollout Heuristics: Domain Independent Heuristics for POMCP

How to secure your apps with SSL certificates for custom domains If you’re building an application that needs to go toward production, you’ll undoubtedly need to serve it up securely with SSL. What that entails varies from provider to provider, and you’ll encounter differing levels of complexity (and cost) in getting it all setup. Fortunately, if you’re using Heroku to run your application, this is pretty straightforward. Recently, I've been exploring Heroku again, and in this article, I'll delve into what you'll require to enable SSL on the platform and explore the reasons behind choosing certain features over others. What does Heroku provide for SSL right out of the box? Heroku focuses on ease of use, and I love that. Whether it’s the one-click deploy straight from my GitHub repo or the plugin ecosystem that lets me drop all kinds of great things into my app from the command line, I always appreciate the out-of-the-box options I have at my fingertips. Likewise, SSL on Heroku provides some great default options. Heroku offers two main ways of working with SSL certificates on their platform: Automated Certificate Management (ACM) Heroku SSL For most apps, ACM will give you a really simple, automated certificate management experience—that is the name, after all. But there may be times when you’ll need the more robust Heroku SSL option. We’ll take a look at ACM first. Then, we’ll investigate why you might need Heroku SSL and how you’d use it. Automated Certificate Management and how it works ACM is built on top of —a free, automated certificate authority, run by a nonprofit organization committed to enhancing the security of the web in general. While organizations can sponsor the Let’s Encrypt project, there is no cost for using Let’s Encrypt-issued SSL certificates. Because the certificates are free, Heroku provides Automated Certificate Management with any of their basic plans at no additional charge. Let’s Encrypt While Let’s Encrypt automates the process of requesting and issuing certificates, ACM automates the process of installing those certificates on the relevant apps for the domains they’re issued for. Other methods exist for automated management of certificates, but they’re paid add-ons, so I won’t be looking at them here. Instead, let’s show you how to add ACM to a demo app I’ve already deployed to Heroku. To be clear, there isn’t a whole lot you need to configure for ACM. In fact, if you haven’t added a custom domain to your app, the Heroku-generated URL (on the herokuapp.com domain) for your app already has SSL. Step 1: Enable ACM Your first step is to turn on ACM. The easiest way to do this for any deployed app is with . Assuming you’re logged into the Heroku CLI Heroku via the CLI, all you need to do is run a single command to turn on ACM: $ heroku certs:auto:enable
Enabling Automatic Certificate Management... starting.
See status with heroku certs:auto or wait until active with
heroku certs:auto --wait=== Your certificate will now be managed by Heroku.
Check the status by running heroku certs:auto. If you enable ACM setting up a custom domain on your app, you’ll get a message like this: before $ heroku certs:auto
=== Automatic Certificate Management is enabled on pure-brushlands-82324
=== Add a custom domain to your app by running: heroku domains:add <yourdomain.com> Step 2: Add a custom domain At this point, you simply need to do what the Heroku CLI says and add a domain to your app. You can do this in the CLI too. $ heroku domains:add really-cool-stuff.app
Configure your app's DNS provider to point to the DNS Target lively-basin-0v9xkh99iaz1yc0xldmakla5.herokudns.com.
    For help, see https://devcenter.heroku.com/articles/custom-domains

The domain really-cool-stuff.app has been enqueued for addition
Run heroku domains:wait 'really-cool-stuff.app' to wait for completion
Adding really-cool-stuff.app to ⬢ pure-brushlands-82324... done Step 3: Configure DNS At this point, you need to update your DNS records on your domain to point to the DNS target provided by Heroku. The are detailed and clear. Typically, this means adding a CNAME record that directs to the new location provided by Heroku. instructions in the help documentation it links to Once you have your DNS configured properly, you can check on the status of your certificates. You should see output like this: $ heroku certs:auto
=== Automatic Certificate Management is enabled on pure-brushlands-82324

Certificate details:
Common Name(s): really-cool-stuff.app
Domain(s):      fe6ab605-91f9-4261-974c-ee85c043dbf7
Expires At:     2024-05-27 17:08 UTC
Issuer:         /CN=R3/O=Let's Encrypt/C=US
Starts At:      2024-02-27 17:09 UTC
Subject:        /CN=really-cool-stuff.app
SSL certificate is verified by a root authority.

Domain                       Status       Last Updated
───────────────────────────  ───────────  ────────────
really-cool-stuff.app        Cert issued  4 minutes If you’re like me and you made a mistake when setting up the DNS records 🤦🏻, then you might see some warnings on the app dashboard in the web interface like this: Or this one: Fortunately, ACM repeats its validation attempts regularly for an entire hour. So, I was able to fix my issues quickly. I got to a green status pretty easily. If you’ve ever had to set up SSL on another platform before, you’re probably painfully aware that it usually isn’t this simple (and that’s putting it mildly). That said, Let’s Encrypt has some limitations that may require you to use the more robust offering: Heroku SSL. Heroku SSL and why you might want it While ACM gives you a really simple experience, with that simplicity also comes somewhat limited functionality. Let’s consider two examples where ACM might not meet your unique needs. Example 1: When you need wildcard certificates Let’s Encrypt is restricted to providing certificates on only one single domain name zone at a time. Sometimes, you might actually want to have a wildcard certificate; this is the type of functionality you might need if you have a multi-tenant application that switches between tenants at the subdomain level. ACM doesn’t support this. But Heroku SSL does. common name Example 2: When you need Organizational or Extended Validation (OV/EV) Let’s Encrypt also doesn’t guarantee that you are who you say you are. What I mean is that the type of certificate issued by Let’s Encrypt only attests that the entity requesting the certificate also controls the domain name that it’s securing. There are some scenarios when you need to ensure more than just that your domain traffic is encrypted in transit. You might need to verify that your application is actually associated with your company. In this case, you’d want to purchase an SSL certificate with either Organizational Validation (OV) or Extended Validation (EV). Those usually require checks that can’t be simply automated by a product like Let’s Encrypt. really Using Heroku SSL In the above cases, you’ll need to manually upload your own certificate. As usual, this process has been beautifully simplified by Heroku (but it’s still more work than just telling the platform to start issuing certificates with ACM). To add or update the certificate for your Heroku app, and to use a certificate provide, you need to run a single command: you $ heroku certs:add server.crt server.key
Adding SSL to example... done
exampleapp now served by exemplary-sushi-4gr7rb6h8djkvo9j5zf16mfp.herokudns.com.
Certificate details:
Expires At: 2022-08-18 21:53:18 GMT
Issuer: C=US; ST=CA; L=SF; O=Heroku; CN=www.example.com
Starts At: 2021-08-18 21:53:18 GMT
... Ok, so it’s not much more work than using ACM. that Note that you can’t add multiple intermediate certificates to make a valid chain toward whatever root certificate has signed your new certificate. However, you can into one file so they can be uploaded as a single file. merge your intermediate certificates After uploading your certificate through Heroku SSL, you’ll be able to see your application protected by the SSL certificate you provided on your own. While Heroku SSL still keeps things pretty simple, keep in mind that You’ll also need knowledge of how to work with certificates. While these might not be deal-breakers for you, they’re important points to remember—especially when you consider that ACM takes care of automatic renewals of SSL certificates. With ACM, the simple commands to set it up really are “set it and forget it.” That said, Heroku designed their entire certificate management system in such a way that even if you need the most advanced options, it’s still quite simple and manageable, even if you don’t have extensive certificate experience. you’re responsible for keeping your certificates up to date . Conclusion While there is more you can do with SSL on Heroku, both the ACM and Heroku SSL options can provide the functionality to fit most use cases. Heroku’s also provides enough detail to point you in the right direction. If you haven’t secured your app with SSL (shame on you!), then the simplicity of ACM should remove any excuse you have to secure your site properly. If your use case is more complicated, then Heroku SSL should give you what you need. documentation in this space

How to Secure your Heroku Apps with SSL Certificates for Custom Domains

Authors: (1) Michael Sorochan Armstrong, Computational Data Science (CoDaS) Lab in the Department of Signal Theory, Telematics, and Communications at the University of Granada; (2) Jose Carlos P´erez-Gir´on, part of the Interuniversity Institute for Research on the Earth System in Andalucia through the University of Granada; (3) Jos´e Camacho, Computational Data Science (CoDaS) Lab in the Department of Signal Theory, Telematics, and Communications at the University of Granada; (4) Regino Zamora, part of the Interuniversity Institute for Research on the Earth System in Andalucia through the University of Granada. Table of Links Abstract & Introduction Optimization of the Optical Interpolation Materials and Methods Results and Discussion Conclusion Appendix A: Proof of Hermitian Self-Adjoint product identity for Equidistant Time-Domain Measurements Appendix B: AAH ̸= MIN I in the Non-Equidistant Case Acknowledgments & References APPENDIX A: PROOF OF HERMITIAN SELF-ADJOINT PRODUCT IDENTITY FOR EQUIDISTANT TIME-DOMAIN MEASUREMENTS Consider the case of an NFFT matrix and its hermitian, where: Equation 44 simplifies to: This paper is under CC 4.0 license. available on arxiv

Proof of Hermitian Self-Adjoint Product Identity for Equidistant Time-Domain Measurements

Authors: (1) Michael Sorochan Armstrong, Computational Data Science (CoDaS) Lab in the Department of Signal Theory, Telematics, and Communications at the University of Granada; (2) Jose Carlos P´erez-Gir´on, part of the Interuniversity Institute for Research on the Earth System in Andalucia through the University of Granada; (3) Jos´e Camacho, Computational Data Science (CoDaS) Lab in the Department of Signal Theory, Telematics, and Communications at the University of Granada; (4) Regino Zamora, part of the Interuniversity Institute for Research on the Earth System in Andalucia through the University of Granada. Table of Links Abstract & Introduction Optimization of the Optical Interpolation Materials and Methods Results and Discussion Conclusion Appendix A: Proof of Hermitian Self-Adjoint product identity for Equidistant Time-Domain Measurements Appendix B: AAH ̸= MIN I in the Non-Equidistant Case Acknowledgments & References since it is obvious that when θ = 0, the only possible evaluation for z is 1, consider only when θ ̸= 0, which we can write as: to evaluate for z for some constant integer θ, consider the finite geometric series: This paper is under CC 4.0 license. available on arxiv

Exploring Advanced Time-Domain Measurement Techniques

উন্নত সময়-ডোমেন পরিমাপ কৌশল অন্বেষণ

Erkundung fortschrittlicher Zeitbereichsmesstechniken

Explorando técnicas avanzadas de medición en el dominio del tiempo

Explorer les techniques avancées de mesure du domaine temporel

उन्नत समय-डोमेन मापन तकनीकों की खोज

高度な時間領域測定技術の探索

고급 시간 영역 측정 기술 탐색

Explorando técnicas avançadas de medição no domínio do tempo

Изучение передовых методов измерения во временной области

Gelişmiş Zaman Alanı Ölçüm Tekniklerini Keşfetmek

Khám phá các kỹ thuật đo lường miền thời gian nâng cao

探索先进的时域测量技术

In the ever-evolving world of cryptocurrencies and decentralized technologies, the Shiba Inu project is making waves with its ambitious plans to introduce a '.shib' internet domain. This move is part of a broader push towards the creation of a decentralized identity ecosystem, offering a glimpse into the future of digital identities and online interactions. As the internet continues to shape our lives, the need for secure and transparent identity solutions becomes increasingly paramount, and the '.shib' domain could be a game-changer in this realm. The Rise of Decentralized Identities Decentralized identities have emerged as a revolutionary concept, challenging the traditional centralized models of identity management. In a world where data breaches and privacy concerns are rampant, the idea of giving individuals control over their personal information has garnered significant attention. By leveraging blockchain technology and decentralized systems, these identities aim to provide a secure and transparent way for users to manage their digital footprint, while minimizing the risks associated with centralized data storage. Understanding Decentralized Domains At the core of the Shiba Inu project's plans lies the concept of decentralized domains. These domains operate on decentralized systems, rather than being controlled by centralized authorities like traditional domain registrars. By applying for the '.shib' top-level domain, Shiba Inu aims to create a unique namespace that can be used to establish digital identities within its ecosystem, fostering a sense of community and ownership among its users. The Shiba Inu Ecosystem and Shibarium Shiba Inu, the popular meme-inspired cryptocurrency, has ambitious plans beyond just being a digital asset. The project has developed its own decentralized ecosystem, which includes the Shib Name Service (SNS) and the upcoming Shibarium layer 2 network. The SNS serves as a means to introduce digital identity verification for all products built on the Shiba Inu blockchain, while Shibarium aims to provide scalability and faster transaction times. Challenges and Controversies While the concept of decentralized identities and domains holds immense potential, it is not without its challenges and controversies. Issues such as user adoption, regulatory hurdles, and interoperability with existing systems are just a few of the obstacles that projects like Shiba Inu may face. Additionally, concerns around the security and privacy of these decentralized systems continue to be debated within the broader community. Real-world Applications and Use Cases Decentralized identities and domains have a wide range of potential applications across various industries and sectors. In the realm of finance, they could revolutionize know-your-customer (KYC) processes and anti-money laundering (AML) compliance, providing a secure and transparent way to verify identities. In e-commerce and online transactions, decentralized identities could enhance consumer trust and reduce the risk of fraud. Furthermore, they could play a crucial role in protecting user privacy and data sovereignty in the digital age. The Future of Digital Identities and Shiba Inu's Impact As the world becomes increasingly digitized, the need for robust and secure digital identity solutions will only continue to grow. The Shiba Inu project's foray into the realm of decentralized identities and domains could be a significant step towards a future where individuals have greater control over their online presence and personal data. If successful, the '.shib' domain could pave the way for other blockchain projects and decentralized ecosystems to explore similar avenues, fostering innovation and pushing the boundaries of what is possible in the world of digital identities. Final Thoughts The Shiba Inu project's plans to introduce a '.shib' internet domain and delve into the realm of decentralized identities represent a bold and ambitious step towards a more secure and transparent digital future. While challenges and uncertainties remain, the potential impact of this endeavor cannot be ignored. As the world grapples with the complexities of online identities and data privacy, projects like Shiba Inu offer a glimpse into the possibilities that decentralized technologies can unlock. Whether the '.shib' domain becomes a widespread success or not, it serves as a reminder that the pursuit of innovative solutions in the realm of digital identities is crucial for navigating the ever-changing digital landscape. Don’t forget to like and share the story! This author is an independent contributor publishing via our brand-as-author program. Be it through direct compensation, media partnerships, or networking, the author has a vested interest in the company/ies mentioned in this story. HackerNoon has reviewed the report for quality, but the claims herein belong to the author. #DYOR Vested Interest Disclosure:

The Rise of Decentralized Identities: Shiba Inu's Move Towards a '.shib' Domain

বিকেন্দ্রীভূত পরিচয়ের উত্থান: শিবা ইনু একটি '.শিব' ডোমেনের দিকে অগ্রসর হচ্ছে

Der Aufstieg dezentraler Identitäten: Shiba Inus Schritt hin zu einer „.shib“-Domain

El auge de las identidades descentralizadas: el movimiento de Shiba Inu hacia un dominio '.shib'

La montée des identités décentralisées : l'évolution de Shiba Inu vers un domaine « .shib »

विकेंद्रीकृत पहचान का उदय: शीबा इनु का '.शिब' डोमेन की ओर कदम

分散型アイデンティティの台頭: 「.shib」ドメインに向けた柴犬の動き

분산형 ID의 부상: '.shib' 도메인을 향한 Shiba Inu의 움직임

A ascensão das identidades descentralizadas: o movimento de Shiba Inu em direção a um domínio '.shib'

Рост децентрализованной идентичности: переход сиба-ину к домену .shib

Merkezi Olmayan Kimliklerin Yükselişi: Shiba Inu'nun '.shib' Etki Alanına Doğru Hareketi

Sự trỗi dậy của danh tính phi tập trung: Động thái của Shiba Inu hướng tới miền '.shib'

去中心化身份的兴起：柴犬走向“.shib”域名

LAS VEGAS, Nevada, February 8th, 2024/Chainwire/-- The , the Swiss non-profit organization fostering the growth and decentralization of the NEAR Protocol and ecosystem, today announced it has exclusively partnered with , a next-generation domain name company developing interoperable digital identities, to apply for and obtain the .near Top-Level Domain (TLD) during ICANN’s upcoming application window. NEAR Foundation D3 Global D3 is developing future-proof, interoperable digital identities with the Domain Name System (DNS) at the foundation, ensuring native resolution across all forms of the ‘web.’ The company will enable partner ecosystems to expand their reach beyond their existing communities and provide universal access to their services in a trusted manner. Bridging the gap between the Internet and Web3 will allow the NEAR ecosystem to provide seamless access to over 5.3 billion Internet users worldwide. Through these interoperable digital identities, users will be able to use a single domain as a website, email, or wallet address, cross-platform username, and serve verified credentials. Projects and developers will be able to develop dApps and services with enhanced utility, tapping into existing Internet infrastructure while offering new identity and verification solutions catered to the NEAR ecosystem, which currently boasts over 88 million unique accounts. "We're excited to work with D3 to secure the .near top-level domain and extend the power of NEAR accounts across the entire internet. As the functionality of NEAR accounts expands with Chain Abstraction, combining Web3 identity with existing internet infrastructure will help drive mainstream adoption,” said Illia Polosukhin, Co-Founder of NEAR Protocol and Chief Executive Officer of the NEAR Foundation. “In order for Web3 to accelerate its growth, it will require interoperability with existing Internet infrastructure. We’re pleased to welcome NEAR on our journey to redefine digital identity, while offering NEAR users and projects alike more utility by bringing the ‘web’ to Web3,” Said Fred Hsu, Chief Executive Officer at D3. D3’s patent-pending platform is set to integrate traditional Internet and Web3 ecosystems to deliver enhanced utility, security, and universal access for what the company calls ‘real Web3 domains.’ The D3 team boasts over three decades of combined industry experience across DNS and Web3 technologies. About NEAR NEAR Protocol is a fully sharded, proof-of-stake blockchain designed to scale Web3 to a billion users. Performant, hyper-scalable, and secure, NEAR is the gateway to the open web, achieving the highest number of active accounts in Web3 via easy user onboarding & retention and excellent developer experience with the lowest fees of any blockchain. Learn more about NEAR at https://www.near.org About D3 Global D3 Global is a digital infrastructure provider that delivers secure, decentralized, and interoperable identities on the root layer of the internet - the Domain Name System (DNS). D3’s patent-pending platform will be the first to deliver real domain names that seamlessly bridge the gap between traditional Internet infrastructure and Web3 ecosystems. The D3 team consists of industry veterans with over three decades of collective experience, known for leading domain name monetization, internet protocols, and various TLD operations, including .xyz, .inc, .tv, and .link. Learn more about D3 at https://www.d3.app/ Contact Dan Edelstein PR@marketacross.com This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here.

NEAR Protocol Partners With D3 To Apply For .Near Top-Level Domain

.box is bridging Web3 and Web2 TORONTO, Ontario, January 18th, 2024/Chainwire/-- Breaking new ground in the domain name industry, My.box Inc. announces the upcoming launch of its Public Beta on January 18th, 2024 at 12:00 PM ET. This kicks off public availability of the first ever domain name system supported natively by browsers, email, and wallets. The Future Of Digital Identity .box domains offer secure and seamless identity on Web3 and Web2. The holder of ‘example.box’ is empowered with decentralized ownership and access to DNS record management, ENS integration, payments, Web3 authentication, Web3 messaging, websites, and email. Founder of .box, Josh Brandley states, “There are many great things happening at the intersection of Web3, decentralized identity, and domain names – we are the first to tie it all together with a powerful, easy to use product”. .box solves the major problem with blockchain domains .box sets a new standard in the world of blockchain-based top-level domains. While other new blockchain domain systems generate excitement, they ultimately fall short because they do not work with traditional browsers and email services. In contrast, .box is ICANN-accredited, recognized by the global Domain Name System (DNS), and supported by the Ethereum Name Service (ENS). Both DNS and ENS have established substantial network effects, solidifying their positions as core infrastructure. .box is pioneering an approach that natively integrates the features of both systems, thus delivering a better experience for users. The Team Behind .box The .box TLD is owned and operated by Intercap Registry, an ICANN Accredited Registry Operator. Intercap has dedicated over a decade to the development of .box. Core partners include 3DNS and ENS Labs, whose leaders share the vision of bringing the benefits of Web3 to the domain industry. Nick Johnson, Founder of ENS, states: “We have always had a deep respect for the DNS and are very excited to witness this unique .box implementation that supports seamless interoperability between the two systems”. Paul Gauvreau, CEO of 3DNS adds, “Bringing real world domain assets onchain improves almost every use case there is – we anticipate that this product will be widely adopted by Web3 enthusiasts and newcomers alike.” Launch Pricing During launch, .box domains will run through a premium pricing phase, ensuring fair access for everyone. Prices start at $7,680 USDC and then decay exponentially for 6 days until stopping at a fixed rate of $120 USDC. All domains will renew at $120 USDC per year. Domains are minted and managed using the dApp hosted at my.box. Payment is made with ETH or USDC. Join the .box community Secure your .box domain now at http://www.my.box Follow .box at https://x.com/boxdomains Join the .box to: Discord server Learn how to buy a .box and take control of your decentralized identity. Qualify for your referral link to earn $18 for each successful referral. Receive support, updates, and connect with the team. For More Information: Visit our website at  __ __or contact Omar Hamed, omar@intercap.com http://www.my.box Contact Community Manager Omar Hamed My.box contact@omar.box This story was distributed as a release by Chainwire under HackerNoon’s Business Blogging Program. Learn more about the program here.

Introducing .box – The World’s First Blockchain Native DNS Routable Domain

Authors: (1) Dominic Petrak, UKP Lab, Department of Computer Science, Technical University of Darmstadt, Germany; (2) Nafise Sadat Moosavi, Department of Computer Science, The University of Sheffield, United Kingdom; (3) Ye Tian, Wluper, London, United Kingdom; (4) Nikolai Rozanov, Wluper, London, United Kingdom; (5) Iryna Gurevych, UKP Lab, Department of Computer Science, Technical University of Darmstadt, Germany. Table of Links Abstract & Introduction Related Work Datasets Examined Manual Error Type Analysis and Taxonomies Automatic Filtering for Potentially Relevant Dialogs Statistical Analysis Evaluation and Experiments Discussion Conclusion, Limitation, Acknowledgments, and References A Integrated Error Taxonomy – Details B Error-Indicating Sentences And Phrases C Automatic Filtering – Implementation D Automatic Filtering – Sentence-Level Analysis E Task-Oriented Dialogs – Examples F Effectiveness Of Automatic Filtering – A Detailed Analysis G Inter-Annotator Agreement – Detailed Analysis H Annotation Guidelines I Hyperparameters and Baseline Experiments J Human-Human Dialogs – Examples 3 Datasets Examined Table 1 gives an overview of the datasets examined in this work. Overall, we consider six datasets with dialogs of various types, including task-oriented, open-domain, and knowledge-grounded dialogs, as well as human-human and human-bot dialogs. For task-oriented dialog datasets, we consider MultiWoZ (Budzianowski et al., 2018) (MWoZ), SGD (Rastogi et al., 2020), and BABI (Bordes et al., 2017). They mainly differ in the number of domains included in the dialogs. MWoZ includes seven different domains, SGD 16, and BABI only one (but with dialogs of increasing difficulty). In contrast to MWoZ and SGD, BABI consists of human-bot dialogs. For open-domain dialogs, we consider PersonaChat (Zhang et al., 2018) (PC) and the human-bot split of the SelfFeeding Chatbot (Hancock et al., 2019) (SFC). While PC consists of dialogs between two people who are trying to get to know each other, SFC consists of human-bot open-domain dialogs2 . For knowledge-grounded dialogs, we focus on Wizardsof-Wikipedia (Dinan et al., 2019) (WoW), which consists of human-human dialogs. For simplicity, we do not distinguish between human or bot in the following. We always refer to the utterance of the partner as a system utterance. This paper is under CC BY-NC-SA 4.0 DEED license. available on arxiv

Dialog Datasets: Navigating Task-Oriented, Open-Domain, and Knowledge-Grounded Conversations

The Noonification: How I Came Up With a Telegram Bot for Domain Monitoring and Got 700 Users (12/5/2023)

I want to share a story from my life, explaining how I came up with and launched my pet project. How did creating a bot for domain tracking come to me? Telegram Why did I believe it would be in demand? How does employment and working in a team contribute to generating new project ideas? Let’s get straight to the answers. Employment and working in a team After several unsuccessful attempts to build a profitable and successful web studio, our team dispersed, and each of us had to find our paths for further development. The choice of a company was not a question for me at that time; my immediate concern was paying the rent for the next month and having something to eat. I didn’t pass the first interview, but I immediately received an offer from the second one and gladly accepted it. I joined a fantastic team. Imagine a team of professionals where everyone is open and always willing to help, there is no toxicity within the team, and every initiative from the bottom is heard at the top. Our team served both product and service roles. In the product team, we developed new features, tested hypotheses, and improved the product. In the service team, we supported the service and its users, fixed bugs, rolled out fixes, and solved customer problems that technical support couldn’t handle without our assistance. Generating ideas for the future Every day in the service team, we received feedback reports from users. If the reports for the month showed many user complaints about a particular feature in the user account or users complained about a part of the interface, the project manager took the issue for further improvement in NPS (Net Promoter Score). NPS, Net Promoter Score, indicates customer loyalty to a product or company. Measurements are based on whether the customer would recommend the company to their friends, with a score from 0 to 10 points. Usually, this survey pops up in the user’s account once every three months. As I immersed myself in processes and the product, I noticed user pains and needs that could be addressed. In large companies, project owners and managers often overlook minor user issues, chasing prominent hypotheses whose implementation will profit the company. I think there’s no argument here; they are doing it right. Therefore, I documented all ideas and issues that came to mind during work in a separate document, briefly describing the user problems it could solve, how often it occurred, whether there were analogs, and the possibility of technical implementation. Then, I sat down and thoroughly worked through the list to identify a more viable idea. Choosing an idea for product implementation One of these problems was the adverse user reaction to emails that registrars send to them. These emails notify users that the registration date of their domain is expiring and needs to be renewed. Registrars are required to send at least two notifications reminding users to renew the domain approximately a month and a week before the domain registration expires, as well as within five days after the expiration of this period. The frequency may depend on the domain zone and the requirements of the managing company. Some countries may have legislative requirements regarding customer notifications about registration deadlines. In such cases, companies must comply with these laws. The registrar’s website should specify the methods of sending such notifications. It seemed to me that users psychologically dislike receiving a notification suggesting renewing the domain a month before the actual expiration date. Users get the impression that they have been deprived of one month of paid service. For this reason, users usually wait until a few days before the domain registration expiration date and only then renew the domain. Another problem is that there are registrars that send more than two emails and start doing so 60 days in advance. If you have only one domain, you can tolerate it, but if you have five or more domains, the user’s email becomes inundated with emails. These emails annoy users, and some end up in the spam folder. I’m not talking about all users; most users feel fine. I encountered users who genuinely felt discomfort in my field of view. Developing the idea and possible use cases Is this even possible? Can users set when to receive notifications themselves? What if users don’t want to be bombarded with emails? I thought, what if there’s a proxy in the form of a Telegram bot between the user and the registrar? Then, it struck me that sending notifications via messenger would be better than email. We use messengers several times a day; most of us work in messengers to communicate with colleagues and friends. It’s almost impossible not to see a notification about the need to renew a domain in a messenger, unlike an email inbox that we may not check for weeks. Can the user control the notification date themselves? Why can’t users decide when to receive notifications? Why can’t users choose where it’s more convenient for them to receive notifications? Whether it’s Discord, Telegram, or Viber? In the Telegram bot, functionality can be implemented to set up notifications for each domain, indicating how many days before the domain registration expires the notification should be sent. What if I have many domains, and they’re all registered on different emails? If you add all your domains to the Telegram bot, they will be in one place, and notifications for them will come to your messenger, even if they are registered with different registrars and on different emails even if they belong to different people. Monitoring competitors’ domains Why would one want to keep an eye on competitors’ domains? I later explored this scenario in various ways. Webmaster or web-studio A webmaster with numerous clients for technical support or SEO optimization may face an issue if a domain owner fails to renew. The webmaster might discover one morning that a client’s domain has expired, and they weren’t actively monitoring it, leading to an unpleasant situation. Domain collection In another situation, a desired domain for a project or company might be taken, or a site with errors might occupy it. Anticipating its release in a couple of years, one could buy and redirect it to their domain, potentially gaining traffic. Acquiring domains in a related theme Similar to the second situation, if one owns an online store for children’s toys, one might add all domains related to children’s toys to the bot for monitoring. By possibly acquiring an expiring domain, they could tap into its existing traffic by redirecting it to their main domain. Does auto-renewal solve the problem? In my opinion, enabling auto-payment doesn’t solve the problem. I’ve seen emails from frustrated users who did not intend to renew certain domains, yet auto-renewal charged their cards for 60 or 30 days. Most registrars do not offer refunds in such cases. Attempting to refund and relinquish the domain while it’s still in the registry might be an option. Dismissal from work So, everything was already decided; it was time to start developing the bot and plan its further promotion. There was just one thing holding me back — my job. After three years in this wonderful domain registrar company, my dreams became a bureaucratic state entity after a corporation takeover. How is the Telegram Bot doing now? After leaving, I spent several months developing the , creating a website for SEO traffic, and working on promotion. I filled the site with content, adding around 1200 pages, performed SEO optimization, attracted initial users, and tested my hypotheses. Telegram bot I spent about three months on website development, content creation, translation into English, and SEO optimization. A piece of advice I’d give myself for the future is to start with an SEO-friendly website before developing the product. By the time the project is in development, SEO will already be working and bringing in initial users. As of now, I can confidently say that the bot is in demand, with around 700 users and 2000 domains being tracked. The bot sends daily notifications to users on Telegram; in return, users add new domains for tracking. Conclusion If facing a creative crisis or experiencing setbacks in launching projects, it’s beneficial to work in a good company for a few years, immersing oneself in its processes and products. You’ll undoubtedly identify problems that your future product can solve. Record all ideas in a separate document, briefly describing the solution, target audience, and potential. During this time, you can relax, improve your financial situation, and gather resources for your next launch. Learn the techniques and tools used in the company for marketing. Never give up, and keep moving forward.

How I Came Up With a Telegram Bot for Domain Monitoring and Got 700 Users

আমি কীভাবে ডোমেন মনিটরিংয়ের জন্য একটি টেলিগ্রাম বট নিয়ে এসেছি এবং 700 ব্যবহারকারী পেয়েছি

Wie ich einen Telegram-Bot für die Domain-Überwachung entwickelte und 700 Benutzer bekam

Cómo se me ocurrió un bot de Telegram para monitorear dominios y obtuve 700 usuarios

Comment j'ai créé un robot Telegram pour la surveillance de domaine et j'ai obtenu 700 utilisateurs

मैं डोमेन मॉनिटरिंग के लिए टेलीग्राम बॉट के साथ कैसे आया और मुझे 700 उपयोगकर्ता मिले

ドメイン監視用の Telegram ボットを思いつき、700 人のユーザーを獲得した方法

도메인 모니터링을 위한 텔레그램 봇을 생각해내고 700명의 사용자를 확보한 방법

Como criei um bot de telegrama para monitoramento de domínio e consegui 700 usuários

Как я придумал Telegram-бота для мониторинга доменов и набрал 700 пользователей

Etki Alanı İzleme için Telegram Botunu Nasıl Geliştirdim ve 700 Kullanıcıya Nasıl Sahip Oldum?

Làm thế nào tôi nghĩ ra Bot Telegram để theo dõi tên miền và có 700 người dùng

我如何想出一个用于域监控的 Telegram 机器人并获得 700 个用户

As part of , I have been battling for quite some time with certificates. I was so upset at one point that I even blocked port at fw --firewall level and stopped all traffic on . berrynews.org :80 http But that is not the way things should be handled, and even though it took me about 3 days to figure it out, now, I can proudly say that I have the recipe for success. Here is the specific situation the article will tackle: 1x web-server apache2 1x domain: primary berrynews.org 2x : subdomains edu.berrynews.org crypto.berrynews.org certificates are generated using -- free SSL certificate generator certbot DNS provider is GoDaddy certificate is for www.berrynews.org invalid www.edu.berrynews.org and www.crypto.berrynews.org and when you try to access them you get an do not exist error Outcome: www and non-www will have valid SSL certificates HTTP requests will be redirected at the web server level to HTTPS You Can Configure SSL Certificates in 3 Steps Domain and DNS Setup Web Server Configuration Obtain SSL Certificates To configure SSL certificates for both and non- versions of a domain, as well as for subdomains, see below for detailed steps: www www : Domain and DNS Setup Ensure that your domain and subdomains are properly set up in your DNS settings. You should have records pointing to both the root domain ( ) and the version to your server's IP address. A @ www For subdomains, you should have or records pointing each subdomain to the server's IP address or the main domain, respectively. A CNAME DNS setup example with emphasis on: 2xA → server IP, 2x for each subdomain CNAME ; Domain: berrynews.org
; Exported (y-m-d hh:mm:ss): 2023-11-08 13:03:00
;
; This file is intended for use for informational and archival
; purposes ONLY and MUST be edited before use on a production
; DNS server.
;
; In particular, you must update the SOA record with the correct
; authoritative name server and contact e-mail address information,
; and add the correct NS records for the name servers which will
; be authoritative for this domain.
;
; For further information, please consult the BIND documentation
; located on the following website:
;
; http://www.isc.org/
;
; And RFC 1035:
;
; http://www.ietf.org/rfc/rfc1035.txt
;
; Please note that we do NOT offer technical support for any use
; of this zone data, the BIND name server, or any other third-
; party DNS software.
;
; Use at your own risk.


$ORIGIN berrynews.org.

; SOA Record
@	3600	 IN 	SOA	ns35.domaincontrol.com.	dns.jomax.net. (
					2023110806
					28800
					7200
					604800
					3600
					) 

; A Record
@	600	 IN 	A	94.211.67.63
www	600	 IN 	A	94.211.67.63

; NS Record
@	3600	 IN 	NS	ns35.domaincontrol.com.
@	3600	 IN 	NS	ns36.domaincontrol.com.


; CNAME Record
crypto	3600	 IN 	CNAME	@
edu	3600	 IN 	CNAME	@
www.crypto	3600	 IN 	CNAME	crypto.berrynews.org.
www.edu	3600	 IN 	CNAME	edu.berrynews.org. : Web Server Configuration Configure your web server (Apache, Nginx, etc.) to serve both the and non- versions of your domain, as well as any subdomains. This usually involves setting up server blocks or virtual hosts for each. www www Here is how should look like, with emphasis on , and /etc/apache2/sites-enabled/000-default.conf ServerName ServerAlias Rewrite* <VirtualHost *:80>
        # The ServerName directive sets the request scheme, hostname and port that
        # the server uses to identify itself. This is used when creating
        # redirection URLs. In the context of virtual hosts, the ServerName
        # specifies what hostname must appear in the request's Host: header to
        # match this virtual host. For the default virtual host (this file) this
        # value is not decisive as it is used as a last resort host regardless.
        # However, you must set it for any further virtual host explicitly.
        
        ServerName berrynews.org
        ServerAlias www.berrynews.org
        DocumentRoot /var/www/html/

        # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
        # error, crit, alert, emerg.
        # It is also possible to configure the loglevel for particular
        # modules, e.g.
        #LogLevel info ssl:warn

        ErrorLog ${APACHE_LOG_DIR}/error.log
        CustomLog ${APACHE_LOG_DIR}/access.log combined

        # For most configuration files from conf-available/, which are
        # enabled or disabled at a global level, it is possible to
        # include a line for only one particular virtual host. For example the
        # following line enables the CGI configuration for this host only
        # after it has been globally disabled with "a2disconf".
        #Include conf-available/serve-cgi-bin.conf

	RewriteEngine on
    RewriteCond %{HTTP_HOST} ^www\.berrynews\.org [NC,OR]
    RewriteCond %{HTTP_HOST} ^berrynews\.org [NC]
    RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

</VirtualHost>

<VirtualHost *:80>
    ServerName edu.berrynews.org
    ServerAlias www.edu.berrynews.org
    DocumentRoot /var/www/html/edu
    <Directory /var/www/html/edu>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride all
        Order allow,deny
        allow from all
        Require all granted
    </Directory>
    ErrorLog ${APACHE_LOG_DIR}/error.edu.log
    CustomLog ${APACHE_LOG_DIR}/access.edu.log combined
</VirtualHost>

<VirtualHost *:80>
    ServerName crypto.berrynews.org
    ServerAlias www.crypto.berrynews.org
    DocumentRoot /var/www/html/crypto
    <Directory /var/www/html/crypto>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride all
        Order allow,deny
        allow from all
        Require all granted
    </Directory>
    ErrorLog ${APACHE_LOG_DIR}/error.crypto.log
    CustomLog ${APACHE_LOG_DIR}/access.crypto.log combined


 # Add Rewrite rules here if you want to force HTTPS for the crypto subdomain
    RewriteEngine on
RewriteCond %{SERVER_NAME} =crypto.berrynews.org [OR]
RewriteCond %{SERVER_NAME} =www.crypto.berrynews.org
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost> Here is how should look like, with emphasis on , and /etc/apache2/sites-enabled/000-default-le-ssl.conf ServerName ServerAlias SSLCert* Replace berrynews.org with your own domain ++ you can skip the SSLCert; it will automatically be added by certbot. <IfModule mod_ssl.c>
<VirtualHost *:443>
#Header set Content-Security-Policy "default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self'; font-src 'self';"

        # The ServerName directive sets the request scheme, hostname and port that
        # the server uses to identify itself. This is used when creating
        # redirection URLs. In the context of virtual hosts, the ServerName
        # specifies what hostname must appear in the request's Host: header to
        # match this virtual host. For the default virtual host (this file) this
        # value is not decisive as it is used as a last resort host regardless.
        # However, you must set it for any further virtual host explicitly.
        
	    ServerName berrynews.org
        ServerAlias www.berrynews.org        
        DocumentRoot /var/www/html

        # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
        # error, crit, alert, emerg.
        # It is also possible to configure the loglevel for particular
        # modules, e.g.
        #LogLevel info ssl:warn

        ErrorLog ${APACHE_LOG_DIR}/error.log
        CustomLog ${APACHE_LOG_DIR}/access.log combined

        # For most configuration files from conf-available/, which are
        # enabled or disabled at a global level, it is possible to
        # include a line for only one particular virtual host. For example the
        # following line enables the CGI configuration for this host only
        # after it has been globally disabled with "a2disconf".
        #Include conf-available/serve-cgi-bin.conf


Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/berrynews.org/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/berrynews.org/privkey.pem
</VirtualHost>
</IfModule>
<IfModule mod_ssl.c>
<VirtualHost *:443>
    ServerName edu.berrynews.org
    ServerAlias www.edu.berrynews.org
    DocumentRoot /var/www/html/edu
    <Directory /var/www/html/edu>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride all
        Order allow,deny
        allow from all
        Require all granted
    </Directory>
    ErrorLog /var/log/apache2/error.edu.log
    CustomLog /var/log/apache2/access.edu.log combined

Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/edu.berrynews.org/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/edu.berrynews.org/privkey.pem
</VirtualHost>
</IfModule>

<IfModule mod_ssl.c>
<VirtualHost *:443>
    ServerName crypto.berrynews.org
    ServerAlias www.crypto.berrynews.org
    DocumentRoot /var/www/html/crypto
    <Directory /var/www/html/crypto>
        Options Indexes FollowSymLinks MultiViews
        AllowOverride all
        Order allow,deny
        allow from all
        Require all granted
    </Directory>
    ErrorLog /var/log/apache2/error.crypto.log
    CustomLog /var/log/apache2/access.crypto.log combined

Include /etc/letsencrypt/options-ssl-apache.conf
SSLCertificateFile /etc/letsencrypt/live/crypto.berrynews.org/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/crypto.berrynews.org/privkey.pem
</VirtualHost>
</IfModule> : Obtain SSL Certificates Use a tool like Let's Encrypt's Certbot to obtain SSL certificates. You can include multiple domains and subdomains in a single certificate by using the flag multiple times, like so: -d sudo certbot --apache -d example.com -d www.example.com -d subdomain.example.com Follow the Certbot prompts to complete the validation process and install the certificates. Here’s a snippet from my in-hash: history 1144  sudo certbot --apache -d berrynews.org -d www.berrynews.org
 1150  sudo certbot --apache -d berrynews.org -d www.berrynews.org
 1176  sudo certbot --apache -d crypto.berrynews.org -d www.crypto.berrynews.org
 1190  sudo certbot --apache -d crypto.berrynews.org -d www.crypto.berrynews.org
 1197  sudo certbot --apache -d edu.berrynews.org -d www.edu.berrynews.org
 1202  sudo certbot --apache -d edu.berrynews.org -d www.edu.berrynews.org : Web Server SSL Configuration For each virtual host or server block, configure the paths to the SSL certificate and private key provided by Let's Encrypt. Ensure you have the directive for Apache or the equivalent for other web servers. SSLEngine on Include a directive for the non- version and a directive for the version. For subdomains, set up a separate virtual host or server block with its . ServerName www ServerAlias www ServerName This has been tackled at point 2, if point 3 fails remove SSL certificates from ssl.conf : Redirection Rules Implement redirection rules in your server configuration to redirect HTTP traffic to HTTPS, and optionally redirect to non- or vice versa, based on your preference. www www This has been tackled at point 2, use the example from .conf file : Test Configuration After making changes to your web server configuration, always test to make sure there are no syntax errors. For Apache, you can use: sudo apachectl configtest If the syntax is OK, restart your web server to apply the changes. # example output
root@berrynews:/home/ubuntu# sudo apachectl configtest
Syntax OK : Verification Verify that your domains and subdomains are correctly serving content over HTTPS by using or by visiting them in a web browser. curl You can also use online tools to test your SSL setup, such as SSL Labs' SSL Test. curl -Iv https://berrynews.org
 curl -Iv https://www.berrynews.org
 curl -Iv https://edu.berrynews.org
 curl -Iv https://www.edu.berrynews.org
 curl -Iv https://crypto.berrynews.org
 curl -Iv https://www.crypto.berrynews.org The response should return 200! curl curl -Iv https://www.crypto.berrynews.org
*   Trying 94.211.67.63:443...
* Connected to www.crypto.berrynews.org (94.211.67.63) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS header, Certificate Status (22):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS header, Finished (20):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Finished (20):
* TLSv1.2 (OUT), TLS header, Finished (20):
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
* TLSv1.3 (OUT), TLS handshake, Finished (20):
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: CN=crypto.berrynews.org
*  start date: Nov  8 18:47:08 2023 GMT
*  expire date: Feb  6 18:47:07 2024 GMT
*  subjectAltName: host "www.crypto.berrynews.org" matched cert's "www.crypto.berrynews.org"
*  issuer: C=US; O=Let's Encrypt; CN=R3
*  SSL certificate verify ok.
* TLSv1.2 (OUT), TLS header, Supplemental data (23):
> HEAD / HTTP/1.1
> Host: www.crypto.berrynews.org
> User-Agent: curl/7.81.0
> Accept: */*
> 
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* old SSL session ID is stale, removing
* TLSv1.2 (IN), TLS header, Supplemental data (23):
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
HTTP/1.1 200 OK
< Date: Wed, 08 Nov 2023 20:43:39 GMT
Date: Wed, 08 Nov 2023 20:43:39 GMT
< Server: Apache/2.4.52 (Ubuntu)
Server: Apache/2.4.52 (Ubuntu)
< Last-Modified: Wed, 08 Nov 2023 20:38:01 GMT
Last-Modified: Wed, 08 Nov 2023 20:38:01 GMT
< ETag: "14585-609aa103f57f4"
ETag: "14585-609aa103f57f4"
< Accept-Ranges: bytes
Accept-Ranges: bytes
< Content-Length: 83333
Content-Length: 83333
< Vary: Accept-Encoding
Vary: Accept-Encoding
< Content-Type: text/html
Content-Type: text/html

< 
* Connection #0 to host www.crypto.berrynews.org left intact : Renewal Setup Ensure that automatic renewal of certificates is set up. Certbot usually does this for you by creating a cron job or systemd timer. : Firewall Configuration Make sure your firewall is configured to allow HTTPS traffic on port 443. : Monitor and Maintain Regularly check your websites to ensure that SSL certificates are being renewed and that there are no security warnings. It's also good practice to stay informed about any updates to your web server software or the Certbot tool. By point 3 with certificate generation, you should already be done. Hope this helped, and feel free to reach out if you have any questions. If you liked the article & would like to support content creators such as myself, Make sure to: 🔔 Follow me Bogdan Tudorache 🔔 Connect w/ me: | LinkedIn Reddit

SSL Certificates for Both www and non-www versions of a Domain

In this article, I’ll show you how to deploy a app and associate it with a domain. Node.js Let’s get right to it! 1. Buying everything we need: Server (VPS): I bought it on Digital Ocean because I have 200$ free on this service, and I can also , but you can also buy a VPS on sites such as: give you 200$ hostinger.com contabo.com Domain: I got a free one on namecheap.com, but you can also buy a domain on sites such as: hostinger.com godaddy.com domain.com 2. Setting up a VPS: Server settings: The server settings depend on the load your site will be under and the complexity of the project. Since I will be deploying a simple site, I chose the most minimal settings. For the authentication method, I chose a password. Once our server is up and running, we can start connecting to it. Copy the IPv4 or IPv6 address, then open a terminal and enter the following command: Ssh root@164.90.218.8(instead of 164.90.218.8 put your IPv4) After this, it will ask you to enter the password that you set when creating the VPS: When you successfully log in, you will see something similar to this: From there, we have two ways to transfer our project folder. If you have it in a zip file on your local computer, you can use these commands to transfer the zip file with your project to the server. #if you have authentication method thought password
scp your-archive.zip root@164.90.218.8:~/
#if you have authentication method thought ssh key
scp -i ~/.ssh your-archive.zip root@164.90.218.8:~/ However, I suggest that you use GitHub. Log in to and use “git clone” to put your project in the global directory. For example, I will use my Node.js project called “ ”. GitHub qr_code_hunt_challenge Then, we need to install packages. Use the following commands on our VPS: #to update everything
sudo apt update
#after it shows us that we have packages that we can upgrade
sudo apt upgrade
#when you get Do you want to continue? [Y/n], you just write Y After this, go to the git repository using this link and choose the version of Node.js you need. In my case, I will use the latest LTS version. Press the copy button next to the commands and insert them in our VPS: If you encounter any errors: sudo apt-get update
sudo apt-get install -f
sudo apt-get clean
sudo apt-get install -y nodejs
sudo apt Then: #to install vim, zip, nginx
sudo apt install vim zip nginx Now, we need to make some changes in the firewall settings: sudo ufw allow 'OpenSSH'
sudo ufw allow 'Nginx HTTP'
sudo ufw enable 
#after all this commands you need to write
sudo ufw status
#and you will get something like this
Status: active

To                         Action      From
--                         ------      ----
OpenSSH                    ALLOW       Anywhere                  
Nginx HTTP                 ALLOW       Anywhere                  
OpenSSH (v6)               ALLOW       Anywhere (v6)             
Nginx HTTP (v6)            ALLOW       Anywhere (v6) 3. Setting up a domain: First, we need to input our domain on the VPS hosting service. In my case, it is DigitalOcean. Go to the dashboard where you can check your VPS and start: When you insert the domain name and click “Add Domain,” you need to point to DigitalOcean in your nameservers. You can follow the guide from DigitalOcean using this . link In my case, I go to my dashboard in Namecheap and add everything as instructed in the guide: Second, we need to create a directory: sudo mkdir /var/www/your_domain.com
sudo chown -R $USER:$USER /var/www/your_domain.com/
sudo vim /etc/nginx/sites-available/your_domain.com The last command will open Vim, and here we need to insert this Nginx configuration: server {
    server_name your_domain.com www.your_domain.com;

    location / {
        proxy_pass http://localhost:3000;#here you need to change to your port
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
    }
} Then, use these commands: rm -rf /etc/nginx/sites-available/default
rm -rf /etc/nginx/sites-enabled/default
sudo ln -s /etc/nginx/sites-available/your_domain.com /etc/nginx/sites-enabled/your_domain.com
#by next command you can check if everything okay
nginx -t
#now we need to reload our nginx
nginx -s reload Now, we need to move our Node.js project to another directory: cd /var/www/your_domain.com
mv ~/name_of_your_project_folder After using “ls,” you will see the folder or “.zip” file in your directory. If you just moved the “.zip” file, you need to unzip it using the command “unzip your_file.zip.” Now, we need to move all files from this directory: mv name_of_your_project_folder/* .
#and now we can delete this directory
rm -rf name_of_your_project_folder After that, use these commands: npm install
#and if you need some packages you can install now, in my case i will use:
npm init
npm install express
npm install ejs
npm install path
#and when you installed everything that you need, you can start your node.js
node server.js To make this site work without stopping: sudo npm install pm2@latest -g

pm2 startup systemd

pm2 start /var/www/your_domain.com/server.js

pm2 save

pm2 status
#after last command you should see If everything is okay, start using these commands: sudo systemctl start pm2-root

sudo systemctl reboot 4. Setting up HTTPS: To use HTTPS on our app, use these commands: sudo ufw allow 'Nginx Full'

sudo apt install certbot python3-certbot-nginx

sudo certbot --nginx -d your_domain.com -d www.your_domain.com

sudo systemctl status certbot.timer

sudo certbot renew --dry-run

sudo ufw delete allow 'Nginx HTTP'

#and if you upload some file on your app
sudo vim /etc/nginx/nginx.conf
#and here you need to insert in http {}
client_max_body_size 1000M; #here you can input any amout of megabytes

#and after all this
 nginx -t && nginx -s reload Now, our Node.js app is deployed and reachable through our domain, and everything is working. Finishing Up I hope you understood the instructions correctly. If you have any thoughts on this article, I will be waiting for your comments. If I really helped you, I kindly ask you to subscribe to my and provide feedback on this article. LinkedIn Also published here.

Deploying a Node.js App with an Associated Domain

Hi guys! In the article today, we'll discuss, and I'll also show you how to set up NextJS 13 (with app folder), , and sub-domains. Auth0 I'm currently working on a web multi-tenancy app. So, we need multiple sub-domains. For security reasons, we decided to use Auth0. We did follow the basic setup for Auth0, which can be found . And everything worked smoothly and fine. But, we figured out that we need multiple sub-domains. So, I started researching, and I got into a lot of trouble with this because every time I entered I got an error. Something about etc. I can't reproduce the error now, but the status code was 400. here subdomain.domain.com err callback, grant_type, Anyway, after a lot of research, a colleague of mine has found that we need to create our SDK. If you followed the basic quickstart from Auth0, you should have something like // src/api/auth/[auth0]/route.ts
import { NextResponse, NextRequest } from 'next/server';
import { handleAuth } from '@auth0/nextjs-auth0';

export const GET = (req: NextRequest, res: NextResponse) => {
  return handleAuth()(req, res); // not neccesary to have (req, res)
}; And beside of that, in our case, we had a middleware to set the user token from Auth0 You can ignore the first if statement for as we needed it for other checks in deployments. It is the only route on the application which doesn't require authentification. /api/status // src/middleware.ts

import { NextRequest, NextResponse } from ‘next/server’;
import {
  withMiddlewareAuthRequired,
  getSession,
} from ‘@auth0/nextjs-auth0/edge’;

export default withMiddlewareAuthRequired(async (req: NextRequest) => {
  if (req.nextUrl.pathname === ‘/api/status’) {
    return NextResponse.next();
  }

  const res = NextResponse.next();
  const user = await getSession(req, res);
  if (user) {
    // set your user.token whenever you want, db, cookies, localStorage etc
    return res;
  }
  return res;
});
export const config = {
  matcher: ‘/’,
}; So basically, with this setup, the login/logout was working fine. domain.com Now, as I mentioned earlier, my colleague found out we have to create our own and we have to simulate a domain name. , Auth0 SDK The following configuration is for macOS and Linux. If you use Windows, use a Google search such as: how to add sub domains local windows So, open your terminal and run: $ sudo nano /etc/host Here, you have to add a root domain and a few subdomains the name will not matter, but the extension, yes. So they can be anything but need to end with . .local 127.0.0.1    cloudstar.local
127.0.0.1    apple.cloudstar.local
127.0.0.1    microsoft.cloudstar.local
127.0.0.1    github.cloudstar.local After you finish, click then press and CTRL + X Y enter Now you need to flush it in the terminal run $ sudo killall -HUP mDNSResponder So now, in Auth0 Dashboard at your application settings, you'll have to set the: * Please note that before Cloudstar.local there's a (dot) . Allowed callbacks urls to: http://.cloudstar.local:3000/api/auth/callback Allowed logout urls to: http://.cloudstar.local:3000 // src/lib/auth0.ts
import { initAuth0 } from '@auth0/nextjs-auth0';

export const initializeAuth0 = (req): ReturnType<typeof initAuth0> => {
  return initAuth0({
    baseURL: `http://${req.headers.get('host')}`, 
    secret: process.env.AUTH0_SECRET,
    issuerBaseURL: process.env.AUTH0_ISSUER_BASE_URL,
    clientID: process.env.AUTH0_CLIENT_ID,
    clientSecret: process.env.AUTH0_CLIENT_SECRET,
    session: {
      cookie: {
        domain: `.${req.headers
          .get('host')
          .split(':')[0]
          .split('.')
          .slice(-2)
          .join('.')}`,
      },
    },
  });
}; will return or etc. The req.headers.get('host') myapp.com apple.myapp.com And at the we want to set up the domain. But without a port, we need to make sure the cookie will be set for . So, basically, we want to be sure we set the cookie at the very top-level domain. session.cookie.domain .myapp.com A small tip: If you want to set HTTP or HTTPS based on development or production, you can pass this to the base. baseURL: `${
      process.env.NODE_ENV === 'development' ? 'http' : 'https'
    }://${req.headers.get('host')}` We need to modify the API route as well to use the custom Sdk. // src/api/auth/[auth0]/route.ts
import type { NextApiRequest, NextApiResponse } from 'next'
import { initializeAuth0 } from '@/lib/auth0';

export const GET = (req: NextApiRequest, res: NextApiResponse) => { 
  const auth0 = initializeAuth0(req); 
  return auth0.handleAuth()(req, res); 
} Now, if you're trying to access your instance, it has to work to log in but will not work to log out. Why, you wonder? So, if you open the dev tools from your browser and go to application -> cookies. You'll see two cookies: with the name appSesion, value, and the and the second with . That's normal for how the project is configured right now. First domain: myapp.com one domain: .myapp.com But if you want to log out, I will do the refresh I was saying at the start of the article and will log you back in. And now comes the fix: The issue is middleware . This middleware is setting the domain cookie, aka . Honestly, I don't know if whoever from Auth0 wrote the docs forgot to add that, or it was just ignorance, or maybe it is writing somewhere that if you use at the root level, it creates a new cookie. I saw a lot of examples using and I don't know if that formula is still creating the cookie, but at the root level, sure it is. Maybe Auth0 guys didn't know about it; who knows, I'm not here to point any fingers at anyone. withMiddlewareAuthRequired myapp.com withMiddlewareAuthRequired withMiddlewareAuthRequired(PageName), Let's get back at the fix. So, you just have to change the name of middleware from to anything else, let's say, and it will work perfectly fine. withMiddlewareAuthRequired middleware, I'm also providing a GitHub repo for the final code to be more concise because here, I mostly explained what was the issues and so on, and we didn't focus too much on the code itself. https://github.com/alexcloudstar/nextjs13-auth0-sub-domains End note: I'm pretty sad that most of the discussions on Auth0 are open; there are a few responses or no responses at all, and then the topic is closed. Or, in some discussions, folks came and said: "Oh yeah, I had the same issue, but I managed to fix it" - Yes, I'm glad you did, but how? Because I need a fix as well at that very moment. Anyway, that's it for today, guys! Many thanks to my colleagues for help, the internet, and you guys for reading. If you have any queries, please let me know at or on my social media. alexcloudstar@gmail.com Until next time! Cheers! 🍻 Also published . here

Setting Up NextJS 13 with Auth0 and Sub-Domains: A Guide to Multi-Tenancy Web Apps

This one is personal. It was a random Friday evening and I had a ‘simple’ goal: host a static website on with my domain. I mean, how difficult can it be, right? Apparently quite, considering it took 10 articles, 4 tutorials, 2 videos, and an entire day of trying everything the internet had to offer. AWS S3 GoDaddy But fret not! Your journey will be far smoother. Let’s embark on this adventure together, starting with the first and fundamental step: snagging yourself a catchy domain. Content Overview GoDaddy: Securing Your Slice of the Internet Pie! Amazon Web Services: Where Websites Fly First Class Migrating GoDaddy Domain to AWS S3 Bucket Webmaster: Smooth Updates for Your Shiny, New Site Celebration Time: You’re Live! GoDaddy: Securing Your Slice of the Internet Pie! (Learn how to acquire and set up a personal domain with GoDaddy.) So, you’ve decided to establish your own little corner on the web. Exciting times ahead! Let’s begin with the basics: . acquiring a domain Step 1: Choose Your Domain Start by brainstorming a unique and memorable domain name that represents you or your project well. Keep it short, sweet, and easy to spell. Once you have a few options in mind, it’s time to head over to GoDaddy’s website. Step 2: Search and Select On GoDaddy’s homepage, enter your desired domain name into the search bar. If your first choice is taken, don’t despair! GoDaddy will offer alternative suggestions, or you can try a variation of your initial idea. Once you find an available domain that you love, add it to your cart by clicking on the button. Make it Yours Step 3: Customize and Checkout GoDaddy will offer various add-ons and options, like privacy protection and professional email addresses (<username>@yourdomain). Review these offerings, select the ones that fit your needs, and proceed to checkout. Complete the transaction, and voila, the domain is yours! Step 4: Setup and Configuration Now, with the domain in your possession, there might be a few setup steps and changes before it shows up on your desired URL. Configure your domain settings, connect it to your hosting (which we’ll dive into next), and ensure everything is in tip-top shape for launch. For this part of the setup we’ll be visiting your domain’s DNS Records and Forwarding rules. And just like that, you’ve successfully secured your slice of the internet pie with GoDaddy! Stay tuned as we navigate through the next phase of our digital journey: hosting with AWS S3. Amazon Web Services: Where Websites Fly First Class (Introduction to hosting your website on Amazon Web Services’ S3.) Welcome to the powerhouse of the internet: . If the web were an ocean, AWS would be its mightiest vessel, and today, you’re coming aboard to host your website in style. Amazon Web Services (AWS) Step 1: Navigating the AWS Landscape AWS is vast, with a myriad of services that can be overwhelming for first-timers. Either log-in to your existing AWS account or create a new one. : Upon first login to AWS, you’ll encounter the AWS Management Console. It’s your control center for AWS services, so take a moment to explore its layout. Notice the ‘Services’ dropdown at the top left, your go-to hub for all AWS offerings. Familiarizing Yourself : Under the ‘Services’ dropdown, you’ll find ‘S3’ listed under the ‘Storage’ category. Click on ‘S3’ to enter the S3 console, where you’ll be managing your static website hosting. Finding S3 Step 2: Creating an S3 Bucket Think of a bucket as a storage unit for your website. Click on the ‘Create Bucket’ button. Here, you’ll name your bucket (usually, this should match your domain name for simplicity but its fine to name it anything you like), select a region closest to your target audience, and follow through with the default settings for now. : Under the S3 console, click the blue ‘Create bucket’ button. A window appears prompting you for a bucket name. Select a name closely matching your domain for consistency. Naming Your Bucket : Pick a region close to your audience to minimize latency. Each region corresponds to a specific geographical area. For me personally, I always prefer using US East regions since I am based in the US and also because it helps with SSL certification process on AWS (more on this in the next section). Selecting Regions : While many settings are fine at default, glance through each option and get acquainted. You’ll likely not need to adjust much here, but familiarity is key for future troubleshooting and adjustments. Reviewing Settings Step 3: Configuring the Bucket Once your bucket is ready, it’s time for some configurations. Set the properties and permissions to make your bucket public (as it is private by default), enabling people to view your website. You’ll also set up static website hosting here by enabling the feature and designating your index and error documents. : Uncheck “Block all public access” to allow users to access the bucket files. This is what it should look like post allowing access. Public Access Settings Step 4: Uploading Content and Making it Public With everything set up, you’re ready to upload your website’s files to the bucket. Simply drag and drop, or manually upload your HTML, CSS, and other files into your S3 bucket. : Upload your static website files to the new bucket. You can do this using the AWS CLI or by selecting the “Upload” option under the “Objects” tab. Personally I always use the upload option. Uploading Website Files : Navigate to the “Properties” tab of your bucket and scroll to “Static website hosting”. Click “Edit”, enable static website hosting, and input your default page name (typically ‘index.html’) in the “index” text field. Don’t forget to save your changes! Enabling Static Website Hosting : Head to the “Permissions” tab and add a bucket policy to grant public read access to your bucket (change YOUR-BUCKET-NAME and add the code provided below). This policy allows anyone on the internet to read the objects in your bucket, so ensure you want your data to be publicly accessible. Be sure to review and understand the policy’s permissions before saving it along with your other changes. Granting Public Access {
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "PublicReadGetObject",
            "Effect": "Allow",
            "Principal": "*",
            "Action": [
                "s3:GetObject"
            ],
            "Resource": [
                "arn:aws:s3:::YOUR-BUCKET-NAME/*"
            ]
        }
    ]
} Step 5: Testing Your Live Site AWS provides a unique endpoint for your hosted content. Click on this link, and if all is well, you’ll see your static website alive and kicking! And there you have it! The initial descent into AWS might seem daunting, but with these steps, you’ve not only landed but set up base. Ready for the next adventure? We’ll delve into going live in the upcoming section. Finally Done: Your Site is Live! (A walkthrough of successfully hosting your website and seeing it go live.) Congratulations, you’re almost there! Now, let’s bind everything together by pointing your shiny new GoDaddy domain to the AWS S3 bucket you’ve meticulously set up. Migrating GoDaddy Domain to AWS S3 Bucket Step 1: Getting an SSL Certificate with AWS ACM Open AWS Certificate Manager (ACM). Click “Request” to initiate a new certificate and select “Request a public certificate”. Add your domain names — & . www.your-domain.com your-domain.com Choose “DNS Validation”. After certificate creation, two CNAME records will be generated by ACM. Copy both the “CNAME name” and “CNAME value” for later use. Step 2: Updating DNS Records in GoDaddy Login to your GoDaddy account and navigate to the domain settings of your chosen domain. Go to “Manage DNS” under “Additional Settings”. Add the CNAME records provided by ACM. Repeat this step for both sets of values provided. Set “Type” to “CNAME”. “Name” is the “CNAME name” from ACM (in this case making it _95c3d23b4c008dfcadeed5b518ed3d1d.www & _2bb2bfda7c66af8c036422465b415a8c). omitting the . part from the CNAME name your-domain.com “Value” is the “CNAME value” from ACM (copy as is). Set “TTL” to “Default”. Allow some time for these changes to propagate and the certificate to be validated. Step 3: Creating AWS CloudFront Distribution Open the CloudFront console on AWS. Click “ ”. Create Distribution Enter the S3 bucket website URL as the “ ” (avoid using the auto-suggested link). Origin Domain Under “ ”, select “Redirect HTTP to HTTPS”. Viewer Protocol Policy Under “ , select “Enable security protection”. Web Application Firewall (WAF)” Add “ ” for both your preferred website URLs ( and ) under “ ”. Alternative Domain names (CNAME) www.your-domain.com your-domain.com Settings Choose the previously created ACM certificate under “ ”. Custom SSL Certificate Complete the distribution creation process and wait for it to deploy (usually 5–10 minutes). Step 4: Pointing Domain to CloudFront and Final Adjustments Unfortunately, GoDaddy’s standard DNS service does not support direct ALIAS or ANAME records to CloudFront. Therefore, the best practice is to set up a CNAME for the www subdomain and then redirect the root domain to the www subdomain. You already have a CNAME for www, so let’s modify that. Take note of the CloudFront domain name provided upon creating your distribution, resembling . CloudFront Domain Retrieval: dxxxxxxxxxxxxx.cloudfront.net GoDaddy’s standard DNS doesn’t support ALIAS or ANAME records pointing directly to CloudFront for root domains. To address this, set up a CNAME for your subdomain and redirect the root to . Updating Root Domain Record: www www Modify the existing CNAME record for subdomain: Adjusting CNAME for www: www Type: CNAME Name: www Data: [Your CloudFront domain name] TTL: 1 Hour (adjust as preferred) Implement forwarding to redirect traffic from your root domain to the subdomain: Setting Up Root Domain Forwarding: www Go to DNS management for your domain in GoDaddy’s dashboard. Locate the “Forwarding” section and add “Domain” forwarding. Forward to: www.your-domain.com Redirect type: 301 (Permanent) Settings: Forward only Maintain the existing NS, SOA, and records without changes. Handling Other Records: _domainconnect Following these DNS adjustments, propagation might require some time, potentially ranging from immediate to several hours. Utilize tools like to monitor propagation status globally. Propagation Time Consideration: DNS Checker Once propagation concludes, accessing or should direct users to your site hosted on CloudFront securely via HTTPS. your-domain.com www.your-domain.com Webmaster: Smooth Updates for Your Shiny, New Site (Guidance on updating and maintaining your newly hosted website.) Updating your static website hosted on AWS S3 is a straightforward process. Follow these steps to ensure your site stays fresh and up-to-date: Step 1: Accessing AWS S3 Log in to your AWS Console. Navigate to the S3 service. Open the bucket hosting your website. Step 2: Updating Website Files To update existing files: Navigate to the file you wish to replace. Either overwrite this file by uploading a file with the same name or delete the existing file and upload the new version. To add new files, simply upload them to the relevant directory within your bucket. Step 3: File Permissions (if necessary) When uploading new files, ensure their permissions are set correctly. If your bucket is public, new files should typically be set to ‘public read’ to be accessible to visitors. Step 4: Clearing Cache (if using CloudFront) If you’re utilizing AWS CloudFront for content delivery, remember that updates might not reflect immediately due to caching. You may need to create an invalidation to clear the cache for updated content to appear. Navigate to your CloudFront distribution, go to the ‘Invalidations’ tab, and create an invalidation by entering the path of your updated files (use to invalidate all files). /* Step 5: Testing After updating files and settings, visit your website to confirm that changes are live and functioning as expected. Test on different devices and browsers to ensure compatibility and proper display. Celebration Time: You’re Live! Congratulations on successfully navigating the digital waves to launch your shiny, new website! Your virtual real estate is now up, running, and ready to welcome visitors from around the globe, securely and swiftly. This journey, while seemingly daunting, has brought you from domain registration with GoDaddy to secure, static website hosting on AWS S3, all the way to deploying with CloudFront for that extra speed and security layer. Cheers to your success! 🚀🎉

Bridging Domains:How to Migrate From GoDaddy to AWS S3 in Style!

ব্রিজিং ডোমেন: GoDaddy থেকে AWS S3-এ স্টাইলে কীভাবে স্থানান্তর করা যায়!

Überbrückung von Domänen: So migrieren Sie stilvoll von GoDaddy zu AWS S3!

Puente de dominios: ¡Cómo migrar de GoDaddy a AWS S3 con estilo!

Pontage de domaines : comment migrer de GoDaddy vers AWS S3 avec style !

ब्रिजिंग डोमेन: स्टाइल में GoDaddy से AWS S3 पर कैसे माइग्रेट करें!

ドメインのブリッジング:GoDaddy から AWS S3 にスタイリッシュに移行する方法!

도메인 브리징:GoDaddy에서 AWS S3로 스타일리쉬하게 마이그레이션하는 방법!

Bridging Domains:Como migrar do GoDaddy para o AWS S3 com estilo!

Соединение доменов: как стильно перейти с GoDaddy на AWS S3!

Etki Alanları Arasında Köprü Oluşturma: GoDaddy'den AWS S3'e Şık Bir Şekilde Nasıl Geçiş Yapılır?

Kết nối miền: Cách di chuyển từ GoDaddy sang AWS S3 thật phong cách!

桥接域：如何时尚地从 GoDaddy 迁移到 AWS S3！

Do you know what takes the most time when building a ? Finding the freaking name an available domain. Startup and A year ago, I hired some amazing designers and engineers and we brainstormed around a financial product with the code name . Fire stands for inancial ndependence - etire arly. HelloFire F I R E I loved that name and I even got the domain - the .com was crazy expensive and I'll never pay tons of money for a domain. hellofire.co But the story doesn't end here. I got distracted by another project of mine - (come on, admit it, it is a great name) and I paused HelloFire. OMGDrops OMGDrops got acquired after 15 months (based on the last git commit), I decided to continue playing around with HelloFire but it seems I never renewed my domain. That means that now, I have to find a new name - and to tell you the truth, HelloFire wasn't very descriptive of what I was building. Five Steps for Picking a Great Domain Name Here are the steps I always follow when I am picking a new name for a product and domain (name reveal in the end!): I will never pay a premium for a domain. I will add some words like "hello, hq, awesome" etc. Example: basecamphq.com I am a positive person (check my to see for yourself) and I always try to make my products positive and fun. YouTube The more serious the sector, the funnier the name I pick. This is a double-edged sword of course but I love marketing that is contrarian and I hate boring products. Do not pick a "smart" name that relies on a pun. My first company (that got acquired by Splunk) was first called Sfalma (DO NOT ASK WHY OR WHAT IT MEANS) and we rebranded it to BugSense (we were an error reporting product). Make marketing's life easier by picking a name that could create a lot of interesting scenarios. Maybe all these instructions seem too generic so below is my thought process when I try to find a new product name. Finding a new domain name Any domains that contain the word , are immediately disqualified. Same with the following: invest Wealth Portfolio All of them are too boring. To get some inspiration, I started looking at titles of famous investment books. Example: I could play around with but it is a very long word. Let's find intelligent synonyms online! and draw my attention but is a bit tame and I don't like the in the end. But I like the vibe. I decide to follow Whiz and I end with: Wise whiz wise whiz z wonder star There are a lot of products with in their name so I decided to research a bit more. Wonder Star Star has some color in it and some movement and it is a bit playful. Let's save it for now and head back to looking at book titles. I like where this is going. It is descriptive and most of our audience has heard about it. By the way, your domain name doesn't have to be exactly the name of your product! While I kept looking around books, I saw this and it took me in a different direction. Your product name and especially your domain to evoke something about your brand. In my case, I am building a product that helps people create wealth by following strategies that are suited to their case. has I remember also another book from the same author: which is even close to the vibe I like. My product has a lot of community involved so misfits, underdogs are not bad ideas. David and Goliath: Underdogs, Misfits, and the Art of Battling Giants But, I want to remove a little bit of the anger that these words carry. Let's save outliers and misfits and keep looking for inspiration in book titles. Now that we have some ideas, let's try to imagine our product as a person. Customer persona My ideal customer is someone that cares a lot about their financials and they are always on the lookout for new opportunities to build wealth. They might have gotten burnt in the past by listening to people who have NO idea what are they talking about (hint: people with money usually don't know how to manage their wealth) and they hope that they can add a little bit of in their decisions. They are explorers. They are hustlers. Builders. data The full product is going to cost $499 per year (accurate price pending) so I assume that my customers have a considerable amount in investable assets. Expanding the search I am stuck and I decided to expand my search to memes - taking it even further from how traditional financial products approach their audience. I google: money memes and some golden results come up: Fuck you money (a saying from the FIRE community) Show me the money Make it rain Memes are a great part of my growth strategy and it fits in my customer persona. Ok, is a fantastic domain but not available. What if we change it to Show me money? ShowMeTheMoney YOUR Bingo. The following domains are available: showmeyourmoney.app showmeyourmoney.co I like it. It is playful (show me your money) and people get that it is about a wealth-tracking app. Now the question is to use the .app as the main domain or the .co? What do you think? If you want to read more about how I am building HelloFire (oh sorry) ShowMeYourMoney then follow my devlog! PS: A lot of my process comes from the amazing book . Hello, My Name Is Awesome Check it out Also published here.

Choosing an Exceptional Domain Name for Your Startup: Five Tested Steps

Welcome to HackerNoon’s Writing Prompts! Would you like to take a stab at answering some of these questions? The link for the template is . HERE It’s no secret that today, our email inboxes have become a storage of tons of phishing emails competing with one another with their creativity, perfect impersonation, and the amount of damage they can cause. In fact, begin with a phishing email. That is $500 million lost to phishing attacks every year: fake invoices, an email from the CEO, a kind request for credit card details, etc. 93% of successful cyberattacks Anyways, it’s not stats like this that come to prove the rise of cyberattacks and phishing in general, as dozens of such cases happen around us daily. Such email security breaches cost billions of dollars to business owners who are turning to DMARC for a more robust and reliable layer of security. Now, let’s delve into the mounting demand for DMARC, the main implementation challenges IT departments face, and the as the go-to resource for mastering email security. EasyDMARC Academy Why are More and More Businesses Implementing DMARC? DMARC has become a must-have for businesses looking to protect their domains. It takes SPF and DKIM solutions to the next level by ensuring that emails meet those standards before letting them through. It’s essential for the safety of any organization and its customers as it: DMARC confirms the authenticity of the emails sent from your domain by granting you full control over your email senders and volumes. Prevents phishing and spoofing: Such a level-up in your domain security will make sure your emails don’t end up in spam or junk folders and get delivered. Enhances your email deliverability: By blocking any attempt of impersonation, DMARC protects your brand, stopping unverified parties from sending emails from your domain. Protects your brand reputation: The list of DMARC benefits extends far beyond what we’ve covered, making it clear that implementing this protocol is a huge investment in email security and your brand image. The Rising Need for DMARC: Market Trends and Adoption Insights Now, let’s take a look at the DMARC trends, its rising need in the market, and the reasons behind it. of the growing adoption of this email authentication standard perfectly shows the increasing number of valid DMARC records confirmed via DNS. Here are the results: DMARC.org’s analysis As mentioned earlier, this graph shows the total number of valid DMARC policies published from late 2016 through the first half of 2022. This analysis, of course, doesn’t cover the entire Internet but is based on certain datasets still being enough to show the trends and rising demand of DMARC. There are a number of reasons why the need for DMARC has increased in recent years, and here are several of them: In the first half of 2022, our platform EasyDMARC alone blocked over 90 million phishing attacks. This number is quite disturbing considering the low percentage of domains worldwide being protected by any authentication standard. The rise of cyberattacks: Some countries have taken serious steps to protect their citizens by making DMARC implementation mandatory/highly recommended for government domains or providing . However, these policies and enforcement mechanisms vary from country to country, including The Netherlands, Canada, the UK, Australia, The US, etc. Government regulations: guidance to organizations The availability of tools such as , an all-in-one DMARC management system, have made it easier for business to implement and adopt it. The Availability of DMARC tools: EasyDMARC Together, these have resulted in a growing awareness of DMARC, with more and more organizations using this authentication standard. The Implementation Challenges Faced by IT Departments and MSPs With such a growing need for DMARC, IT departments and MSPs (Managed Service Providers) are actively implementing this policy to ensure emails sent from their or their clients’ domains are authenticated and legitimate. However, DMARC implementation is quite challenging. Your IT team needs knowledge and expert guidance to solve the problems that arise during DMARC deployment. In fact, 70% of organizations trying to deploy DMARC by themselves fail, with still stuck in the monitoring stage (p= “none”). 68.2% of global active domains Let’s go through some of the current challenges and see what can go wrong when deploying this protocol. - Insights From IT Departments First things first, configuring DMARC records causes a big problem for IT administrators, especially for organizations with diverse email infrastructures. Complex Configuration: A minor mistake can lead to an authentication error, and to avoid such issues, you need to generate a record according to all the required specifications. As mentioned above, in the case of many domains, the DMARC record has been left at p=none for years, which basically means that these domains are not protected and fraudulent emails are still delivered. Being Stuck on “Policy None”: On the other hand, you need to review all your sources, make them compliant one by one, and then go through p=none or quarantine. Understanding the reporting is another significant challenge if you are not using DMARC software. ISPs (i.e., Google, Outlook, Yahoo, Zoho, etc.) directly send you those reports that contain compressed flat XML text with a lot of valuable data. Incomprehensible Reporting: You should constantly review them to authenticate your legitimate sources and ensure email deliverability. - Insights From MSPs Surely, all the challenges mentioned above refer to MSPs as well. But here are two more: MSPs often work with various clients, each with unique email infrastructures. They all require adaptable strategies for DMARC implementation, thus making it harder for MSPs to manage the whole process. Navigating Diverse Infrastructures: They also need to make sure their clients understand the importance of DMARC and are actively engaged in the implementation processes. Educating Clients for smooth implementation: In light of these challenges, it is crucial for both IT departments and MSPs to have access to comprehensive resources and expert guidance to facilitate the smooth implementation of DMARC protocols. Your Free Professional Guide to Domain Protection: Become DMARC-Certified Now that we've explored the challenges of DMARC implementation, it's time to introduce our , which will equip you with the right tools and knowledge you need to level up your domain security. EasyDMARC Academy So far, we have prepared two detailed courses designed to elevate your understanding of DMARC and overall email authentication standards. We're proud to share that over 1,500 professionals have already been certified. By enrolling, you'll dive into creating, checking, and implementing SPF, DKIM, DMARC, and BIMI records, learn how to get it to a strict “reject” policy, and become DMARC certified. Choose the right one for you and start your DMARC journey. Mastering DMARC is essential for protecting your domain, brand, and customers. It’s the only reliable way to prevent phishing and spoofing and take responsibility for your outgoing emails. But proper implementation is even more important as it demands knowledge and expertise to achieve peace of mind and ensure your recipients have full confidence in your communications.

The Rise of DMARC: Level Up Your Domain Security Knowledge With EasyDMARC Academy

El auge de DMARC: mejore sus conocimientos sobre seguridad de dominios con EasyDMARC Academy

L'essor de DMARC : améliorez vos connaissances en matière de sécurité de domaine avec EasyDMARC Academy

DMARC का उदय: EasyDMARC अकादमी के साथ अपने डोमेन सुरक्षा ज्ञान का स्तर बढ़ाएं

DMARC の台頭: EasyDMARC アカデミーでドメイン セキュリティの知識をレベルアップ

A ascensão do DMARC: aprimore seu conhecimento sobre segurança de domínio com a EasyDMARC Academy

Sự trỗi dậy của DMARC: Nâng cao kiến thức về bảo mật tên miền của bạn với Học viện EasyDMARC

DMARC 的崛起：通过 EasyDMARC Academy 提升您的域安全知识

Creating a Domain Expert LLM: A Guide to Fine-Tuning

Since the early days of Svix, we supported letting our customers of the event types they send. The schemas are used in a few places throughout the Svix product, but one of the main things they are used for is the event catalog. define the schemas The event catalog is essentially an automatically generated documentation page for the event types that you support. The event catalog was originally only accessible from the , though we have since added the ability so that you can link to it directly from your docs. application portal to make it public While this works great, one of the most common requests we got since launching this feature was to make it possible to host it on a custom domain so that it's served from rather than . We have now made it possible! webhooks.example.com www.svix.com By default, your event types are only accessible to users from within an authenticated session on the Application Portal. To make them publicly accessible, please first enable the "Make Public" setting from the Event Catalog configuration screen in the Dashboard settings. Once you have made the event catalog public, please set the following record on your DNS provider: Type: CNAME Name: (or whatever subdomain you would like to use) webhooks Value: event-types.svix.com And once you do so that we can activate it on our end. let us know Once activated, you will be able to serve the Event Catalog from our custom domain for all of your environments! For more content like this, make sure to follow us on , or for the latest updates for the , or join the discussion on . Twitter , GitHub RSS Svix webhook service our community Slack Also published here

Event Catalog on a Custom Domain: A Quick Guide

Stories, News & Mentions about DOMA

Doma’s Stories on HackerNoon