<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jiri Zdvomka on Medium]]></title>
        <description><![CDATA[Stories by Jiri Zdvomka on Medium]]></description>
        <link>https://medium.com/@zdvomka.j?source=rss-911448969c64------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*iqXpTyDjmjf9hulghx0JXw.jpeg</url>
            <title>Stories by Jiri Zdvomka on Medium</title>
            <link>https://medium.com/@zdvomka.j?source=rss-911448969c64------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:32:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@zdvomka.j/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Apple iOS 26 Call Screening: What Apple Missed in Personalization]]></title>
            <link>https://medium.com/@zdvomka.j/apple-ios-26-call-screening-what-apple-missed-in-personalization-ca7ef20fae5a?source=rss-911448969c64------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca7ef20fae5a</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[indiehackers]]></category>
            <dc:creator><![CDATA[Jiri Zdvomka]]></dc:creator>
            <pubDate>Fri, 05 Sep 2025 14:41:26 GMT</pubDate>
            <atom:updated>2025-09-07T16:58:49.179Z</atom:updated>
            <content:encoded><![CDATA[<p>Apple’s new <strong>Call Screening</strong> in iOS 26 is a game-changer for blocking spam calls, but it’s a bit <em>sterile</em> out of the box. Meanwhile, <a href="https://ihatecalling.ai/ghosty/app-store?utm_source=medium-compare-en"><strong>Ghosty</strong></a> — an AI-powered call screener app — brings fun and personalization to the mix. In this article, we’ll break down how Apple’s call screening works, what it <em>doesn’t</em> do, and how Ghosty fills in the gaps with custom voices, greetings, and more. Let’s dive into the future of phone call management and see why a personal touch matters.</p><p><em>Original article was published on </em><a href="https://ihatecalling.ai/en/ghosty/blog/apple-ios-26-call-screening-what-apple-missed-in-personalization"><em>the author&#39;s website</em></a><em>.</em></p><h3>Apple’s Call Screening in iOS 26: A Quick Overview</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F4yFDvqEjciQ%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4yFDvqEjciQ&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4yFDvqEjciQ%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6c0dfe2e30276a84f5f11362e14ab69c/href">https://medium.com/media/6c0dfe2e30276a84f5f11362e14ab69c/href</a></iframe><h4>How Does iOS 26 Call Screening Work?</h4><ul><li><strong>Automated Call Answering:</strong> When an unknown number calls, your iPhone can automatically answer on your behalf, <strong>politely asking the caller who they are and why they’re calling</strong> <a href="https://nevtis.com/ios-26-call-screening-apples-answer-to-spam-calls/#:~:text=Imagine%20this%3A%20an%20unknown%20number,on">[nevtis.com]</a>. You’ll see a live transcription of the caller’s answer on your screen, almost like magic.</li><li><strong>Real-Time Transcription:</strong> As the caller responds, their words are converted to text instantly. You can glance at the on-screen transcript and decide whether to pick up, ignore, or block the call — all while the caller is still talking.</li><li><strong>Built-In Privacy:</strong> Apple processes all call screening on-device, keeping your call data private and secure. There’s no cloud processing needed, which means your information stays with you.</li></ul><h4>Key Features of Apple’s Call Screening</h4><ul><li><strong>Spam Blocking Upgrade:</strong> This feature builds upon iOS 17’s Live Voicemail, taking it a step further by screening calls <em>before</em> they hit your voicemail. It’s designed to tackle the spam call epidemic by intercepting robocalls and scams proactively.</li><li><strong>Simple User Experience:</strong> The interface is seamless and integrated into the Phone app. If the transcript looks important (say, a doctor’s appointment reminder), your phone will ring so you can answer. If it’s a spammy “free cruise” offer, you can silently decline.</li><li><strong>One-Size-Fits-All Prompt:</strong> The screening uses a <strong>standard Apple prompt</strong> — essentially Siri asking <strong>“Please state the reason for your call…”</strong> — and transcribing the reply. It’s straightforward and effective for basic filtering.</li></ul><h4>Limitations of Apple’s Approach</h4><ul><li><strong>No Personalization:</strong> Apple’s call screening uses a <strong>sterile, generic greeting</strong> for everyone. You can’t change the voice or phrasing of the prompt — it’s the same for your grandma as it is for a telemarketer.</li><li><strong>No Contextual Conversations:</strong> Unlike more advanced systems (like Google’s Call Screen or third-party apps), Apple’s version doesn’t have back-and-forth dialogue with the caller. It asks one question and that’s it — no follow-up queries or customized responses to different scenarios.</li><li><strong>Basic Control Only:</strong> While you can decide on the spot to take the call or block it, you <strong>can’t pre-set any rules</strong> for how different call types should be handled beyond silencing unknown callers. This is where users might start wishing for more control — which is exactly what our next section is about.</li></ul><h3>Ghosty App — Personalized Call Screening for iPhone</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UOcy4gt2LZWSrcQBf4uPeA.png" /></figure><h4>How Ghosty Works as an AI Call Screener</h4><ul><li><strong>AI Voicemail on Steroids:</strong> Ghosty is an iOS app that acts like your personal receptionist. If you’re busy or hit “decline”, <strong>Ghosty answers the call for you</strong> — just like Apple’s screening, but with its own flair. In seconds, it generates a summary of who’s calling and why, so you’re never left guessing.</li><li><strong>Instant Summaries:</strong> While the caller speaks to Ghosty, the app transcribes or analyzes the conversation. You’ll quickly get a notification or text summary of the call’s purpose. It’s like having an assistant take a message, but way faster.</li><li><strong>Seamless Integration:</strong> Ghosty uses call forwarding to work its magic (by routing unanswered calls to its AI service). It works on your iPhone alongside the default Phone app, and you can easily return calls or reply with a text once you see what the caller wanted.</li></ul><h4>Personalization Features in Ghosty</h4><ul><li><strong>Tone of Voice Options:</strong> Ghosty shines with its <strong>voice personalization</strong>. You can choose a tone that fits <em>you</em> — whether that’s a casual Gen-Z vibe, a professional Millennial, or a polite Boomer style, with male, female, or even neutral voice options. This means the AI can answer your calls sounding youthful and upbeat or formal and courteous, as you prefer.</li><li><strong>Custom Greetings:</strong> Tired of Apple’s robotic script? With Ghosty, you can write your own greeting for the AI to use. Want it to say “Hey, you’ve reached John’s phone. I’m using Ghosty to screen my calls — how can I help you?” in a friendly tone? No problem. You have full control to make the greeting warm, funny, or totally personalized to reflect your personality (or even seasonal holiday greetings if you’re feeling festive!).</li><li><strong>AI Call Instructions:</strong> Ghosty lets you set <strong>custom AI instructions</strong> for common situations. For example, you can instruct it to <strong>automatically reject telemarketers</strong> or sales calls politely (“Sorry, not interested, please remove me from your list”), or to inform personal callers of your availability (“If this is about scheduling a meeting, let them know I’m free on Wednesdays”). The app comes with scenario templates (like “decline financial offers” for spam) that you can tweak. Essentially, you’re training your AI assistant how to handle different types of calls exactly the way you want.</li></ul><h4>User Experience and Benefits</h4><ul><li><strong>Personal Touch:</strong> Because Ghosty speaks in a style you choose, callers get a sense they’re still interacting with <em>your</em> personality (and not a cold robot). This personal touch can be more pleasant for friends or clients who reach your Ghosty voicemail versus the generic Apple screening.</li><li><strong>Peace of Mind:</strong> Ghosty is perfect for those moments when you can’t or don’t want to pick up. Whether you’re in a meeting, driving, or just need downtime, Ghosty’s got your back. You’ll know immediately if the call was important without the guilt of wondering what you missed.</li><li><strong>Control and Customization:</strong> The app’s smart settings let you decide exactly when Ghosty intervenes — you can have it screen all unknown numbers, or even known contacts if you’re ultra busy. You’re in the driver’s seat. As a result, phone anxiety goes down and productivity goes up, because random calls no longer derail your focus.</li></ul><h3>Apple vs. Ghosty — What Did Apple’s Call Screening Miss?</h3><h4>Voice and Tone Personalization</h4><ul><li><strong>Apple’s Single Voice:</strong> Apple’s call screening uses a standard Siri-like voice to address all callers. It’s efficient, but it comes off as one-size-fits-all — basically the same tone whether it’s a spammer or your spouse calling.</li><li><strong>Ghosty’s Variety of Voices:</strong> Ghosty offers a <strong>range of voices and tones</strong> to match different vibes. You can have the AI sound youthful and slangy for a light-hearted touch or more mature and formal for business calls. The ability to select <strong>Gen Z, Millennial, or Boomer-style voices</strong> means the call screener can represent you in a way that resonates with different callers or just matches your personal brand. This is something Apple’s built-in feature simply doesn’t do — it missed the memo on personalization here.</li></ul><h4>Custom Greetings vs. Apple’s Sterile Default</h4><ul><li><strong>Apple’s Sterile Greeting:</strong> Apple’s call screening prompt is polite but generic: essentially “Please state the reason for your call?” in the same monotone for everyone. There’s no way to change the wording or add personality. Some might find it a bit <em>sterile</em> or impersonal.</li><li><strong>Ghosty’s Personalized Greeting:</strong> Ghosty lets you craft your very own greeting message. This means you can add your personal flair or important info. For instance, you could have Ghosty introduce itself by name (“Ghosty here, screening John’s calls!”) or mention your status (“John’s driving right now”). This custom touch can make even a screened call feel more friendly and less like talking to a machine. Apple’s feature missed this opportunity to let users customize the experience.</li></ul><h4>User-Defined Call Handling Rules</h4><ul><li><strong>Apple’s Basic Approach:</strong> With iOS 26, every unknown caller gets treated the same way — they’re asked for info, and you decide to take it or not. There’s no built-in way to automatically handle specific types of calls differently (beyond silencing all unknowns).</li><li><strong>Ghosty’s Smart Instructions:</strong> <strong>Ghosty allows advanced rules</strong>. You can pre-set how the AI should respond to certain callers or keywords. For example, if Ghosty detects the call is from a telemarketer or contains phrases like “free offer” or “limited time deal,” you can have it politely decline right then and there. Or if a call seems to be about scheduling, Ghosty could automatically respond with your availability (“She’s busy now, but is usually free on Wednesdays after 2 PM”). This level of customization — basically teaching your AI assistant how to behave — is absent in Apple’s current offering. Apple missed out on giving users this kind of granular control.</li></ul><h4>Language and Voice Variety</h4><ul><li><strong>Apple’s Limited Customization:</strong> Apple’s system will use your device’s default language and Siri voice settings. It doesn’t let you choose a different language on the fly for screening or switch voices per caller. If you have bilingual needs or just prefer a certain accent or gender for the voice, you’re out of luck with Apple’s call screening as it stands.</li><li><strong>Ghosty’s Multi-Language Support:</strong> Ghosty speaks <strong>31+ languages</strong> and can switch as needed. This is huge for international users or anyone who gets calls in different languages. Plus, Ghosty offers male, female, or gender-neutral voice options. Essentially, Ghosty missed no opportunity in letting you fine-tune how the AI sounds to callers, whereas Apple kept it simple and uniform.</li></ul><h4>Future Features: Voice Cloning &amp; Outbound Calls</h4><ul><li><strong>Apple’s Unknown Path:</strong> As of iOS 26, Apple hasn’t announced any wild features like voice cloning or making calls for you. They tend to roll things out carefully and haven’t hinted at these capabilities in call screening yet.</li><li><strong>Ghosty’s Ambitious Plans:</strong> The Ghosty developer, <a href="https://x.com/jstorm31">Jiri</a>, is already looking ahead. In the near future, he plans to introduce <strong>AI voice cloning</strong>, so the call screener could use <em>your own voice</em> to interact with callers — how cool (and slightly spooky) is that? Imagine the AI speaking so naturally the caller thinks they’re talking to you. Additionally, Ghosty is exploring <strong>outbound call features</strong>, meaning the AI could potentially <strong>make calls on your behalf</strong> (for example, to return a call and gather info, or to hold your spot in a customer service queue). These forward-looking features highlight a key difference: Ghosty is all-in on pushing AI boundaries in telephony, while Apple’s feature is currently more conservative. Apple’s call screening, as helpful as it is, missed out on these cutting-edge ideas — at least for now.</li></ul><h3>Why Personalization Matters in Call Screening</h3><p>Personalization isn’t just a fancy add-on — it’s the future of how we interact with technology. When it comes to call screening, a personal touch can make a huge difference:</p><ul><li><strong>Better Caller Experience:</strong> If a friend or client reaches your call screener, hearing a friendly custom greeting or even your cloned voice can make them feel acknowledged, not brushed off by a robot. It softens the impersonal nature of being screened.</li><li><strong>Improved Communication:</strong> Tailored instructions mean important information gets through even if you don’t answer. For example, your Ghosty can let a caller know when you’ll call back or direct them to email for quicker replies. This kind of customization can lead to less frustration all around.</li><li><strong>User Empowerment:</strong> Being able to set the tone and rules for your call handling gives <strong>you control</strong> over your phone, rather than your phone controlling you. You decide who gets through and how, based on your priorities. For many iPhone users (from busy professionals to those with phone anxiety), that’s a game-changer.</li><li><strong>Reflecting Your Identity:</strong> The way we answer the phone can be part of our personal or business brand. Apple’s single scripted approach doesn’t reflect <em>you</em>, it reflects Apple. Ghosty’s approach allows your unique style (or your company’s tone) to shine through, even when you’re not the one picking up. In an era of AI, keeping that human or humorous element in the loop makes tech work <em>for</em> us, not against us.</li></ul><p>In short, Apple’s iOS 26 Call Screening is a big step forward for filtering unwanted calls, but personalization brings it to the next level. As we demand more from our devices, features like Ghosty’s show that people value having a say in how their calls are handled. It’s not just about blocking spam — it’s about doing it <em>your</em> way.</p><h3>Frequently Asked Questions (FAQ)</h3><h4>What is Call Screening in iOS 26?</h4><p>Apple’s call screening in iOS 26 is a new feature that automatically answers unknown calls for you. It asks the caller who they are and why they’re calling, then shows you a live transcript of their answer. This lets you decide if you want to pick up the call, ignore it, or block it — all without talking to the caller directly.</p><h4>How does Ghosty differ from Apple’s Call Screening?</h4><p>Ghosty is a third-party AI voicemail app that goes beyond Apple’s built-in call screening. While Apple uses a generic prompt and voice, Ghosty lets you personalize the greeting, choose different voice styles (even by generation or gender), and set custom rules for handling calls. Essentially, Ghosty offers a more customizable and feature-rich call screening experience compared to Apple’s one-size-fits-all approach.</p><h4>Can I personalize Apple’s call screening responses or voice?</h4><p>Not at the moment. Apple’s iOS 26 call screening doesn’t provide options to change the greeting or voice — it uses Apple’s default assistant voice and script for all calls. If you want personalized greetings or different voice options on iPhone, you’d need to use an app like Ghosty, since Apple’s built-in feature doesn’t support that level of customization yet.</p><h4>Why is personalization important in call screening?</h4><p>Personalization makes call screening feel less robotic and more user-friendly. When you tailor the greeting or set specific rules (like auto-declining telemarketing calls), you ensure that callers are handled in a way that fits your needs and style. It improves the experience for the caller (they get a relevant response or a friendly tone) and for you as the user (you have control and peace of mind). Overall, it turns a basic spam-blocking tool into a smarter personal assistant.</p><h4>Does Ghosty plan to add any new features that Apple’s screening doesn’t have?</h4><p>Yes, Ghosty’s developers are working on some cutting-edge features. They’ve mentioned plans for an <strong>outbound call feature</strong>, meaning Ghosty’s AI could potentially make calls on your behalf (imagine an AI calling a number and gathering info for you). They’re also exploring <strong>AI voice cloning</strong>, which could let the AI speak in a voice that sounds like you. These are forward-looking features that Apple’s call screening doesn’t offer at this time.</p><h4>Is Ghosty safe to use and does it protect my privacy?</h4><p>Ghosty is designed to be secure — it uses call forwarding and AI to handle calls, and it should follow privacy best practices (like any app, you should check what data it collects). Apple’s solution keeps everything on-device, which is a strong privacy approach. With Ghosty, some data (like the call audio for AI processing) may be handled on servers to generate the transcript and response. At the moment, the app doesn’t keep audio or full transcript, only summary. However, reputable apps will encrypt data and not store anything unnecessarily. If privacy is a top concern, it’s worth reading Ghosty’s privacy policy. Many users find the added personalization worth it, but you should use the solution you’re most comfortable with.</p><h3>Related Articles</h3><ul><li><a href="https://support.apple.com/en-us/105066"><strong>How to Use Live Voicemail on iOS 17</strong></a> — <em>A look at Apple’s first step toward call screening and how to make the most of it.</em></li><li><a href="https://www.theverge.com/24325270/iphone-apple-spam-calls-screen-how-to"><strong>5 Tips to Block and Reduce Spam Calls on iPhone</strong></a> — <em>From built-in features to apps like Ghosty, learn how to keep annoying callers at bay.</em></li><li><a href="https://www.tomsguide.com/phones/iphones/ios-26-call-screening-promises-to-keep-spam-callers-at-bay-heres-how-to-set-it-up"><strong>Google Call Screen vs Apple Call Screening</strong></a> — <em>Comparing Android’s call screening capabilities with Apple’s iOS 26 feature (and where third-party apps still lead).</em></li><li><a href="https://serviceagent.ai/blog/ai-call-assistant/"><strong>The Future of AI in Phone Calls</strong></a> — <em>Explore how AI voice assistants and call bots (like Ghosty’s planned features) are changing the way we handle phone calls.</em></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca7ef20fae5a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 principles for efficient debugging]]></title>
            <link>https://medium.com/@zdvomka.j/5-principles-for-efficient-debugging-549a4902972d?source=rss-911448969c64------2</link>
            <guid isPermaLink="false">https://medium.com/p/549a4902972d</guid>
            <category><![CDATA[logging]]></category>
            <category><![CDATA[error-handling]]></category>
            <category><![CDATA[debugging]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Jiri Zdvomka]]></dc:creator>
            <pubDate>Sat, 09 Sep 2023 15:38:10 GMT</pubDate>
            <atom:updated>2023-09-09T15:38:49.863Z</atom:updated>
            <content:encoded><![CDATA[<h3>🐛 5 principles for efficient debugging</h3><p>1. <strong>Fail fast &amp; loud</strong> — the sooner you know about the error, the faster you can fix it. There’s nothing more annoying than a silent error that cannot be reproduced.</p><p>2. <strong>Error metadata</strong> — instead of throwing textual generic errors, add metadata to your errors (record Id, input data,..). Ideally, you want to identify the context only from the error message combined with the stack trace. Catch your errors locally.</p><p>3. <strong>Structured logging</strong> — using a structured format instead of plaintext enables advanced search capabilities in logs. Use <a href="https://betterstack.com/logs">BetterStack Logs</a> for searching text logs with SQL.</p><p>4. <strong>Correlation ID</strong> — correlate related log entries (e.g. for an HTTP request) so you know the context and can find the pain point.</p><p>5. <strong>Test-driven development (TDD)</strong> — make the test first with real bug data, then make it green by fixing the bug. You know when you have fixed the bug and are safe from regressions.</p><p><strong>Bonus principle</strong>: use binary search to find the pain point.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=549a4902972d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Should I store access tokens in browser storage?]]></title>
            <link>https://medium.com/ackee/should-i-store-access-tokens-in-browser-storage-6492b1c6ce41?source=rss-911448969c64------2</link>
            <guid isPermaLink="false">https://medium.com/p/6492b1c6ce41</guid>
            <category><![CDATA[xss-attack]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-security]]></category>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[csrf]]></category>
            <dc:creator><![CDATA[Jiri Zdvomka]]></dc:creator>
            <pubDate>Thu, 27 Oct 2022 17:56:00 GMT</pubDate>
            <atom:updated>2022-10-27T17:56:00.849Z</atom:updated>
            <content:encoded><![CDATA[<h4>Security discussion, alternatives, and scalability</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ZfApYGSdLW75JY6FEtRlg.png" /></figure><p>The popularization of Single Page Applications in recent years required new ways of authentication compared to traditional server-client websites. With the rise of frameworks like Next or Remix, we&#39;ve been slowly moving forward to the original architecture with some enhancements. It could be confusing, especially to front-end development newcomers, what are the authentication options and their security and scalability tradeoffs. I have sometimes struggled to understand these concepts, therefore I&#39;d like to summarize and discuss them in this post.</p><h3>Means of authentication on the web</h3><p>There are two common ways of authenticating a front-end client with a server.</p><h4>Authorization HTTP header</h4><p>The frontend sends the secret in Authorizationheader (or query parameter/request body) with every request to the server but needs to store the secret token somewhere after the user signs in. With the widespread Single Page Application(SPA) architecture, the typical solution is to store the secret in <strong>browser storage</strong>, be it local / session storage or IndexedDB, which <strong>all have</strong> <strong>the same properties security-wise</strong>. There is also an option to store the secret only <strong>in memory</strong>, but the user loses the session after a page refresh.</p><p>Another progressive approach suggests <a href="https://auth0.com/blog/secure-browser-storage-the-facts/#Web-Workers-Help-Maintain-Secure-Browser-Storage">storing the secret in a Web Worker</a> to isolate the context for the secret. A popular authentication library Auth0<a href="https://auth0.com/docs/secure/security-guidance/data-security/token-storage#browser-in-memory-scenarios"> implements this pattern in its SDK</a>, and <a href="https://firebase.google.com/docs/auth/web/service-worker-sessions">Firebase also suggests managing client-side authentication in Service Workers</a>.</p><h4>HTTP cookies</h4><p>In a traditional server-client web architecture, the server can set a cookie in the HTTP response header, and the browser automatically attaches it with every request, creating a session between the client and server. There is no need to store the secret locally in the browser. Furthermore, there is <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#restrict_access_to_cookies">HttpOnly</a> flag, which blocks accessing the cookie from JavaScript. Combined with the<a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite">SameSite</a>attribute, only the target server will have access to the cookie, effectively isolating it. There is also the<a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#restrict_access_to_cookies">Secure</a> attribute which is only sent to the server over the HTTPS protocol.</p><h3>Session hijacking attacks</h3><p>Let&#39;s briefly look at the possible attack vectors for compromising secrets. I&#39;ll discuss possible defenses later in the article.</p><h4>Cross-site scripting (XSS)</h4><p>This is a whole class of attacks in which a malicious script is injected into the web app. There are many ways to execute XSS. For example, unsanitized user input or <a href="https://thehackernews.com/2021/10/popular-npm-package-hijacked-to-publish.html">installing a popular NPM library that gets hacked and mines crypto</a> (or sends our secret to an untrusted server). I&#39;d recommend reading <a href="https://owasp.org/www-community/attacks/xss/">OWASP materials</a> for more information or watching these great <a href="https://www.youtube.com/watch?v=5JJrJGZ_LjM&amp;list=PL1y1iaEtjSYiiSGVlL1cHsXN_kvJOOhu-">Web Security lectures</a>.</p><h4>Cross-site request forgery (CSRF)</h4><p>The general idea is to trick the user into performing an unwanted action. For instance, the user is authenticated with bank.com by a cookie. The attacker uses a phishing email to send the user a malicious link to a web page with a form sending request to bank.com. The user either clicks on the submit button or the form is submitted by JavaScript. Because the user is authenticated with bank.com, the server accepts this unwanted request. Again, <a href="https://owasp.org/www-community/attacks/csrf">OWASP materials</a> do an excellent job of explaining it.</p><h3>Security aspects</h3><p>So, an easy question, what is the correct secure solution? Unfortunately, not an easy answer, and more importantly, the wrong question. In security, you can never be sure. You can only mitigate specific attack vectors. How can I protect my frontend against compromising a secret through an XSS vulnerability? That&#39;s better.</p><p>Storing a secret in the browser <strong>is susceptible to XSS</strong> because any JavaScript on the page can access it. Storing it in memory might be better, but the secret can still be compromised. Web Workers effectively isolate the storage context, though the secret is indirectly accessible by messaging with the worker.</p><p>One way to mitigate some forms of XSS is to <strong>configure </strong><a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/CSP"><strong>Content Security Policy</strong></a>, including all essential directives. <strong>It is critical to use nonces</strong> or hashes for inline scripts. Otherwise, there is not a big difference from not having CSP as most attacks use inline scripts. CSP restricts target origins which the frontend can send requests and load data from, including Fetch API / XHR requests. With the policy set only to trusted servers, the potential attacker can never send the compromised token to his server. I must give credit to my friend <a href="https://github.com/Tomas2D">Tomáš</a> for pointing CSP out in our discussion about web security.</p><pre>Content-Security-Policy:<br>   default-src &#39;self&#39; data:;<br>   img-src *;<br>   object-src &#39;none&#39;;<br>   script-src &#39;strict-dynamic&#39; &#39;nonce-VALUE_HERE&#39; &#39;unsafe-inline&#39;;<br>   style-src &#39;self&#39; &#39;unsafe-inline&#39;;<br>   base-uri &#39;none&#39;;<br>   frame-ancestors &#39;none&#39;;<br>   form-action &#39;self&#39;;</pre><p>Cookies are generally considered the more secure approach (XSS is on the 3rd place in <a href="https://owasp.org/www-project-top-ten/">OWASP Top Ten list</a>), but only with HttpOnly, SameSite and Secureattributes. That way, the cookie cannot be accessed by JavaScript or sent from/to an unauthorized origin. To add another level of protection against CSRF attacks, we can set CSRF tokens to all forms on the web and verify them on the server (frameworks should usually do this automatically).</p><p>Another advantage is that a browser automatically <strong>sends cookies with all requests</strong>, so there is no need for additional client-side implementation. Cookies can be only 4 KB large, which might not be enough for some forms of secrets (e.g., enormous JWT token). Also note that all requests from the front-end must be proxied through our backend server, which can be a performance bottleneck in some architectures.</p><h3>Scalability</h3><p>The usage of cookies is a stateful solution in terms of communication with the server, because it needs to remember client sessions. This could be a performance bottleneck for higher traffic loads. Scaling server instances, adding a load balancer, and using sticky sessions solves the issue but add complexity.</p><p>Compared to cookies, using Authorization header is a stateless approach and scales well without additional complexity as the clients call backend APIs directly (in some architectures). That&#39;s the reason SPAs have become popular in the first place.</p><p>With the growth of edge computing architecture like Cloudflare Workers or Next.js middleware, usage of cookies may scale well without infrastructural complexity.</p><h3>Takeaways</h3><p>There is no silver bullet in security, and both authentication options have tradeoffs. HTTP-only same-site cookies are considered the more secure approach though. Browser / in-memory storage with correct CSP configuration may also be a suitable approach that scales well for some use cases. You should also look at the system as a whole. There can be other more severe security issues than a front-end vulnerable to session hijacking with XSS (e.g., hacked NPM library printing .env at the backend).</p><p><a href="https://www.ackee.cz/blog/web3">The rise of Web 3</a> has brought a new architecture concept employing a wallet in the form of a browser extension, which signs blockchain transactions. Could this be a security progression from the current authentication methods in the future?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6492b1c6ce41" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ackee/should-i-store-access-tokens-in-browser-storage-6492b1c6ce41">Should I store access tokens in browser storage?</a> was originally published in <a href="https://medium.com/ackee">Ackee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Best Web Dev Accounts to Follow on Twitter]]></title>
            <link>https://medium.com/ackee/the-best-web-dev-accounts-to-follow-on-twitter-cec13a78366c?source=rss-911448969c64------2</link>
            <guid isPermaLink="false">https://medium.com/p/cec13a78366c</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[remix]]></category>
            <category><![CDATA[twitter]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Jiri Zdvomka]]></dc:creator>
            <pubDate>Wed, 30 Mar 2022 07:38:30 GMT</pubDate>
            <atom:updated>2022-06-06T07:48:08.591Z</atom:updated>
            <content:encoded><![CDATA[<p>Do you seek inspiration and want to be up to date in the web bubble? Twitter is packed full of tips and insights for/from <a href="https://www.ackee.agency/blog/the-best-ios-accounts-on-twitter">mobile</a> as well as web developers. Check out these people and never miss the latest tech info.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c7XEnnAtipQFIMxMngmqPg.png" /></figure><h3>International web pros</h3><h4><a href="https://twitter.com/dan_abramov">Dan Abramov</a></h4><p>Dan is a member of the core <a href="https://www.ackee.agency/blog/glossary/react">React</a> team and is a must-follow for any <a href="https://www.ackee.agency/blog/glossary/react">React</a> <a href="https://www.ackee.agency/blog/glossary/developer">developer</a>. Apart from <a href="https://www.ackee.agency/blog/glossary/react">React</a> he tweets about web development in general.</p><h4><a href="https://twitter.com/housecor">Cory House</a></h4><p>I find Cory the most valuable source of JS and <a href="https://www.ackee.agency/blog/glossary/react">React</a> development tips, which he shares on a daily basis.</p><h4><a href="https://twitter.com/kentcdodds">Kent C. Dodds</a></h4><p>Kent is another <a href="https://www.ackee.agency/blog/glossary/javascript">JavaScript</a> expert who created excellent and very thorough courses including <a href="https://epicreact.dev/">Epic </a><a href="https://www.ackee.agency/blog/glossary/react">React</a> Dev. He has recently joined the <a href="https://remix.run/">Remix</a> team and tweets about the framework as well.</p><h4><a href="https://twitter.com/leeerob">Lee Robinson</a></h4><p>Lee is a Director of <a href="https://www.ackee.agency/blog/glossary/developer">Developer</a> Relations at Vercel, a company behind <a href="https://nextjs.org/">Next.js</a> web framework. He tweets about web development, serverless and <a href="https://www.ackee.agency/blog/glossary/react">React</a> / Next.js.</p><h4><a href="https://twitter.com/ryanflorence">Ryan Florence</a></h4><p>Another framework representative is Ryan Florence, co-founder of <a href="https://remix.run/">Remix</a>.</p><h4><a href="https://twitter.com/wesbos">Wes Bos</a></h4><p>Wes is an author of many great courses focused on JS, backend and frontend, worth following.</p><h3>Czech web developers</h3><h4><a href="https://twitter.com/robinpokorny">Robin Pokorný</a></h4><p>A representative from the Czech Republic tweeting about <a href="https://www.ackee.agency/blog/glossary/javascript">JavaScript</a> and TypeScript, also having interesting talks at Frontendisti meetups from time to time.</p><h4><a href="https://twitter.com/machal">Martin Michálek</a></h4><p>Martin was one of the first people I have gained inspiration from in my early days of web development. He usually tweets about CSS, writes the blog <a href="https://www.vzhurudolu.cz/">vzhurudolu.cz</a> and has published several books. Martin is also focused on web performance and founded the service <a href="https://pagespeed.cz/">pagespeed.cz</a>.</p><h4><a href="https://twitter.com/johny_cache">Johny Cache</a></h4><p>The best account to follow is definitely Johny Cache! A funny guy from <a href="https://www.reactboys.com/">Ackee frontend team</a> tweeting about web development stuff and caching problems.</p><h3>Other dev accounts</h3><h4><a href="https://twitter.com/programmingart">Robin Marx</a></h4><p>A security, performance and networking researcher I started following after reading his excellent <a href="https://www.smashingmagazine.com/2021/08/http3-core-concepts-part1/">series of blog posts</a> about the new HTTP/3 protocol.</p><h4><a href="https://twitter.com/moxie">Moxie Marlinspike</a></h4><p>A security expert, <a href="https://www.ackee.agency/blog/glossary/developer">developer</a> and founder of the Signal messenger app, who has recently <a href="https://moxie.org/2022/01/07/web3-first-impressions.html">questioned</a> Web3 phenomena.</p><h4><a href="https://twitter.com/iamdevloper">I Am </a><a href="https://www.ackee.agency/blog/glossary/developer">Developer</a></h4><p>Let’s have some fun at the end. This account tweets funny stuff and memes about development. Enjoy!</p><p>What are your favourite web developers you follow on Twitter? Let us know in the comments!</p><p><em>Originally published at </em><a href="https://www.ackee.agency/blog/the-best-web-dev-accounts-to-follow-on-twitter"><em>https://www.ackee.agency</em></a><em> on March 30, 2022.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cec13a78366c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ackee/the-best-web-dev-accounts-to-follow-on-twitter-cec13a78366c">The Best Web Dev Accounts to Follow on Twitter</a> was originally published in <a href="https://medium.com/ackee">Ackee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our web frontend tech-stack]]></title>
            <link>https://medium.com/@zdvomka.j/our-web-frontend-tech-stack-24819ea03819?source=rss-911448969c64------2</link>
            <guid isPermaLink="false">https://medium.com/p/24819ea03819</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[redux]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Jiri Zdvomka]]></dc:creator>
            <pubDate>Wed, 12 Aug 2020 13:18:13 GMT</pubDate>
            <atom:updated>2020-08-12T13:18:13.988Z</atom:updated>
            <content:encoded><![CDATA[<p>In this post, I present the technological stack we use at Ackee frontend team for building modern web applications. We have a few different stacks for concrete use cases, but almost all of them are derived from JAMstack architecture, which has gained popularity in recent years.</p><p><a href="https://jamstack.org/"><strong>JAMstack</strong></a> stands for Javascript, API and Markup. It is a way of developing client web applications in Javascript without a server, communicating with a backend server through HTTP protocol and serving static files (often pre-build) though a CDN network.¹</p><p>We have been using these concepts for over five years now. Though we constantly update and modernize it. Our base stack can be divided into three categories based on the size and use-case of a project. I am going through all of them briefly.</p><h3>Single-page web apps</h3><p>A great part of our portfolio are enterprise and highly interactive web applications. We develop them as Single Page Applications (SPA) in <strong>React </strong>in combination with <strong>Redux </strong>for state management on <a href="https://github.com/AckeeCZ/create-react-app">a customized fork of Create React App</a> (CRA) as a base skeleton for our projects. The CRA skeleton is ready to enable <a href="https://www.ackee.cz/blog/proc-a-jak-psat-progresivni-webove-aplikace/"><strong>Progressive Web Apps</strong></a><strong> (PWA) </strong>features like content caching or browser push notifications. Communication with a backend server, usually REST API, goes directly from Javascript through HTTP protocol. We have <a href="https://github.com/AckeeCZ/antonio">a small library</a> called Antonio for that purpose.</p><p>The main advantage of this approach is web frontend <strong>decoupled</strong> <strong>from backend</strong>, which leads to independent and scalable development. We like principles and mental models of React as it often provides elegant solutions to complicated tasks and is fully customizable.</p><h3>Microsites and static websites</h3><p><a href="https://www.gatsbyjs.org/"><strong>Gatsby.js</strong></a> is the main choice for microsites and more static websites. We really like it, because we can develop a website in React like any other web app and it is then <strong>automatically</strong> <strong>converted into static HTML markup</strong> at build time. We can even stick to <strong>JS-in-CSS</strong> approach with <a href="https://fela.js.org/">Fela library</a> which has proven itself for a state-driven styling and atomic CSS generation. Another good feature is data querying at build time from many sources (e.g. Google Docs/Sheets). Last but not least, Gatsby site can be easily converted into PWA. That&#39;s what we have done with <a href="https://wtfisackee.dev/">our website for open-source projects</a>.</p><h3>Isomorphic web apps</h3><p>Both previous categories are compliant with the JAMstack principles, but when there is a need for better SEO, isomorphic web apps perform better. When we develop such a project, we keep our CRA skeleton and <strong>enhance it with a Node.js server</strong> for serving rendered HTML pages. This setup is usually a little harder to maintain and it has some pitfalls compared to the previous two.</p><h3>Deploy</h3><p>Continuous Integration/Delivery and deployment from GIT is a standard for us. Web applications and microsites are <strong>deployed as static files</strong> to Google Cloud Bucket. Content from the Bucket is served through Cloudflare Content Delivery Network (CDN) so <strong>fast delivery is guaranteed</strong>. Find out more info in our <a href="https://www.ackee.cz/blog/hosting-react-aplikaci-v-google-storage-bucket-a-cloudflare/">other blog post</a>.</p><h3>Conclusion</h3><p>I showed you the technologies we use for web apps development and the way how we deploy. We frequently discuss new options and regularly update our tools to keep pace with fast development in the frontend field and to provide the best services.</p><p>[1] <a href="https://jamstack.org/">Jamstack.org</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24819ea03819" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cypress — testing web applications with ease]]></title>
            <link>https://medium.com/ackee/cypress-testing-web-applications-with-ease-99fcfe107fc4?source=rss-911448969c64------2</link>
            <guid isPermaLink="false">https://medium.com/p/99fcfe107fc4</guid>
            <category><![CDATA[cypress]]></category>
            <category><![CDATA[testing-tools]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Jiri Zdvomka]]></dc:creator>
            <pubDate>Tue, 22 Jan 2019 15:56:38 GMT</pubDate>
            <atom:updated>2019-01-23T08:14:28.475Z</atom:updated>
            <content:encoded><![CDATA[<h3>Cypress — testing web applications with ease</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1eo849p2Qn2JsSkkAG6QYg.jpeg" /></figure><p>Jest, Mocha and Chai are among the most known tools for React testing (and Javascript in general) of applications. In <a href="https://www.ackee.cz/en">Ackee</a> we use <a href="https://jestjs.io/">Jest</a> for unit test and integration testing. However, when it comes to testing more complex functionalities, working with Jest is not always easy. When integrating many application parts in your tests you must often deal with complex setup of a test environment, mocking modules/functions and handling of asynchronous events. That is the reason I decided to try the testing tool <strong>Cypress</strong> which our colleague Lukáš heard about at the Reactive Meetup in Pardubice and I would like to share my experience in this article.</p><h3>Introduction</h3><p><a href="https://www.cypress.io/">Cypress</a> is a tool for testing web application in the real environment of the browser which makes writing and setup of e2e/integration tests easier. Or to be more specific, those that test a complete part of an application, not only stand-alone functions or components. Among other things, it offers <a href="https://docs.cypress.io/api/commands/stub.html#Syntax">stubbing</a> (mocking) of functions and <a href="https://docs.cypress.io/guides/guides/network-requests.html#Testing-Strategies">network requests</a>, asserting by mere finding of an HTML element, built-in handling of the asynchronous nature of web applications or inclusion of test into Continuous Integration.</p><p>The tool can also be used for unit testing. It is not its primarily purpose though and the tests will run more slowly. There is a <a href="https://github.com/bahmutov/cypress-react-unit-test">plugin</a> for unit testing of React applications.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oeq8SHmP0yCOdlTjn5rKuA.jpeg" /><figcaption>Cypress test progress window</figcaption></figure><p>One of the things that is very well thought-through in Cypress is the UI testing environment and debugging of the tests. In the UI testing environment lets you see everything that is happening in the application during the test and you can switch to any moment of the performed test. Moreover, you have a lot of debugging information available, so <strong>finding an error in the test is easy</strong>. There is no need to read between the lines in the console and be frustrated that the test is not working. It is of course possible <a href="https://docs.cypress.io/guides/guides/command-line.html#Installation">to run Cypress in the console</a>, where it runs in the Electron browser. How it all works is very nicely <a href="https://docs.cypress.io/guides/core-concepts/introduction-to-cypress.html#Cypress-Is-Simple">described in their documentation</a>.</p><h3>Example</h3><p>I demonstrate how Cypress works and how test are written in it on an easy example of a web form for adding recipes, using the public <a href="https://cookbook3.docs.apiary.io/#">Ackee cookbook API</a>.</p><h4>Tested form</h4><p>For the sake of simplicity the form will only include 3 fields — the recipe name, preparation time and description. After clicking on the button “Add”, a POST request will be sent to the API. If the recipe is successfully added, there will be a message about the success under the form, in the opposite case, there will be a message about the failure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/326/1*nEeVdT88fcwsSQVXD2ZSUg.jpeg" /><figcaption>Form for adding a recipe</figcaption></figure><h4>Installation</h4><p>In case you are using NPM or YARN in your project, the installation is really simple:</p><ol><li>The package is installed as a dev dependency: npm i-D cypress.</li><li>Into the section scripts of the package.json file, we add a command for running the package: &quot;cypress:open&quot;: &quot;cypress open&quot;.</li></ol><p>The tool will be run by the added npm script npm run cypess:open, a window with the list of template tests will open. In the project, there is a cypress folder generated with several sub-folders, whose structure and purpose <a href="https://docs.cypress.io/guides/core-concepts/writing-and-organizing-tests.html#Folder-Structure">is described in the documentation</a>, where you can also find <a href="https://docs.cypress.io/guides/getting-started/installing-cypress.html#System-requirements">other ways of installation and a thorough manual</a>. The tests are located in the integrations folder.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*0yVruqcQovddBIC94nMuBA.jpeg" /><figcaption>Window with a list of template tests</figcaption></figure><h4>Writing a test</h4><p>The test case for our form is following:</p><ol><li>We navigate to the page with the form.</li><li>We fill out the fields with values — <em>name, duration of preparation and description</em>.</li><li>We click on the <em>Add</em> button.</li><li>We check whether the request to the API has been sent and we return a simulated response (using stub).</li><li>We verify that the message about success is displayed.</li></ol><p>Before the code of the test itself, it is necessary to add the URL address where the web is running to the file cypress.json, which ensures a relative address usage within Cypress. In our case localhost:</p><pre>{ <br>   &quot;baseUrl&quot;: &quot;http://localhost:3000&quot; <br>}</pre><p>Now everything is ready and we can go ahead and write our test which will look almost the same as the test case thanks to the simplicity of the tool.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8337038c77a5aed4c489dc1e2c076cd6/href">https://medium.com/media/8337038c77a5aed4c489dc1e2c076cd6/href</a></iframe><p>First, before each test, we run cy.server() and after that cy.route(). These two commands check the behavior of the network request and allow their “stubbing”. Thanks to the cy.route({...}) we define that POST request to the defined URL reacts by the response {} with the default status code 200. Our <em>route</em> has been added an alias postAddRecipe, so that we can later wait for the execution and finishing of the request using cy.wait(&#39;@postAddRecipe&#39;) after submitting the form. This is a very useful functionality which allow our tests to be <strong>independent on an external API</strong> . We could also define all scenarios of responses including the unsuccessful ones (404, 500,…).</p><p>The rest of the testing code is simple. First, we go to the requested page, after that we fill out the values into the form, submit it, wait for a response and check the display of the message about success.</p><p>Here, I will point out that even though the code of the test seems to be synchronous, it is not. Cypress adds commands to the queue internally and in case of failure, it can run several times with a defined timeout. That is why the result of the command cannot be saved to a variable const button = cy.get(‘button’) and be later used, but we have to use an alias cy.get(&#39;button&#39;).as(&#39;myButton&#39;). You can find more about aliases and how it works under the surface <a href="https://docs.cypress.io/guides/core-concepts/introduction-to-cypress.html#Cypress-Is-Simple">in the section Core Concepts of the documentation</a>.</p><h4>Running the test</h4><p>That&#39;s all! 💪 And how does the test progress looks like?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/537/1*PdMPFieMOSBJcAwHpn727w.gif" /><figcaption>Receipt form test progress</figcaption></figure><p>A browser window is opened and the whole test is played there. In the left column, we can see all operations that have taken place and by clicking on them, we can return to the given moment to inspect it. Debugging of the test is therefore very easy. There is also other detailed information added to the console, which is very useful when dealing with API requests.</p><h3>Trouble with Fetch API</h3><p>Cypress unfortunately does not support <a href="https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API">Fetch API</a> so far, which is replacing <a href="https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest">XHR</a> in many modern web applications (for more info visit <a href="https://docs.cypress.io/guides/references/known-issues.html#window-fetch-routing-and-stubbing">known issues</a>). If you use it in your projects, stubbing of network requests will not work for you. There is a temporary solution for this missing functionality, which constitutes of replacing Fetch API by a polyfill. This issue is further discussed by the community in the <a href="https://github.com/cypress-io/cypress/issues/95">GitHub project</a>.</p><h3>To Sum Up</h3><p>In comparison with other existing solutions, Cypress <strong>presents a simple and fast way of automatically testing more complex flow of web applications</strong> and therefore saving our work with repetitive manual testing. Thanks to the elegant handling of asynchronous requests, you can use it to write test code as if it were synchronous. It allows testing different responses from external APIs and therefore thoroughly verify the functionality from end to end.</p><p>For unit testing (not only of components, but selectors as well), Cypress is less suitable and it is better to use Jest or similar tools where the running of tests will be faster among other things.</p><p>You <a href="https://frontend-cookbook.ack.ee/pages/libraries/Cypress.html">can read about some tips &amp; tricks</a> we find useful in Ackee in our frontend cookbook 👨‍🍳.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99fcfe107fc4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ackee/cypress-testing-web-applications-with-ease-99fcfe107fc4">Cypress — testing web applications with ease</a> was originally published in <a href="https://medium.com/ackee">Ackee</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>