<?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 Semih Erdogan on Medium]]></title>
        <description><![CDATA[Stories by Semih Erdogan on Medium]]></description>
        <link>https://medium.com/@semiherdogan?source=rss-ee449aacf0b7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*o4vaSy-aNwyntfzKx6JYPg.jpeg</url>
            <title>Stories by Semih Erdogan on Medium</title>
            <link>https://medium.com/@semiherdogan?source=rss-ee449aacf0b7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 22:18:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@semiherdogan/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[handoff: Keeping AI Coding Sessions on Track]]></title>
            <link>https://semiherdogan.medium.com/handoff-a-better-way-to-run-autonomous-development-loops-00e97e62d470?source=rss-ee449aacf0b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/00e97e62d470</guid>
            <category><![CDATA[claude]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[github-copilot]]></category>
            <category><![CDATA[spec-driven-development]]></category>
            <dc:creator><![CDATA[Semih Erdogan]]></dc:creator>
            <pubDate>Fri, 20 Feb 2026 11:39:01 GMT</pubDate>
            <atom:updated>2026-06-01T16:23:05.540Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LlDrPpk2VhTilowi1cROQA.jpeg" /></figure><p>AI coding tools are very good at helping with the next step.</p><p>They are much worse at reliably carrying the full thread of a feature across multiple sessions.</p><p>That was the first problem I kept running into.</p><p>I would start a feature with Claude, ChatGPT, Copilot, or another assistant, make real progress, then step away. When I came back, I had the same questions again:</p><ul><li>What exactly was I building?</li><li>What decisions had already been made?</li><li>What was the current step?</li><li>What should happen next?</li></ul><p>The model had no memory. I had partial memory. The repo had some memory. None of it was structured enough.</p><p>But continuity was only part of the issue.</p><p>The deeper problem was that intent, requirements, decisions, current progress, and validation evidence were scattered across chat history and code changes.</p><p>So I built handoff.</p><h3>What handoff is</h3><p>handoff is a local-first CLI for structured AI coding workflows.</p><p>It creates a small workspace inside your repository under .handoff/ and uses plain Markdown files as the source of truth for the feature you are working on.</p><p>The core workflow now revolves around six files:</p><ul><li>FEATURE.md: raw feature intent</li><li>SPEC.md: normalized requirements and acceptance criteria</li><li>DESIGN.md: optional technical design</li><li>DECISIONS.md: durable product and architecture decisions</li><li>STATE.md: execution plan, progress, and evidence</li><li>SESSION.md: continuation-safe session summary</li></ul><p>No cloud sync. No provider lock-in. No hidden agent runtime.</p><p>Just files, prompts, and a deterministic workflow from intent to execution.</p><h3>The real problem was not only memory</h3><p>At first, I thought continuation was the only missing piece.</p><p>After enough AI-assisted coding sessions, I realized there were actually several different problems:</p><ul><li>the assistant forgets where the work stopped</li><li>the assistant starts implementation before the work is decomposed well enough</li><li>important decisions lose their reasoning</li><li>completed work lacks evidence</li><li>implementation quietly drifts away from the spec</li></ul><p>Those later problems matter just as much.</p><p>If the feature is vague, the assistant tends to improvise. Sometimes that works. Sometimes it creates drift, partial implementation, or too much code too early.</p><p>That is why handoff is intent-aware, planning-aware, decision-aware, and continuation-aware.</p><h3>The workflow I wanted</h3><p>I wanted something with the strengths of structured decomposition, but without forcing people into one IDE or one proprietary workflow.</p><p>I also did not want a system where users had to manually juggle several tools just to start a feature.</p><p>So the result became a hybrid workflow:</p><ul><li>simple when you want speed</li><li>explicit when you want control</li></ul><h3>The default path</h3><p>For most features, the flow starts like this:</p><pre>handoff init payment-integration</pre><p>Then you edit .handoff/current/FEATURE.md with the feature request, requirements, and constraints.</p><p>After that:</p><pre>handoff run --copy</pre><p>That is now the default entry point.</p><p>handoff run looks at the saved workspace state and decides what prompt should come next:</p><ul><li>if planning is incomplete, it emits a planning prompt</li><li>if the execution plan is ready, it emits an execution prompt</li><li>if execution is already underway, it emits a continuation prompt</li></ul><p>That keeps the simple path simple.</p><p>You can also use:</p><pre>handoff next<br>handoff status</pre><p>to inspect what the tool thinks should happen next without generating another prompt.</p><h3>The advanced path</h3><p>Sometimes you want to review the planning before any code is written.</p><p>For that, handoff also has:</p><pre>handoff spec --copy<br>handoff design --copy<br>handoff tasks --copy</pre><p>Those commands let you inspect the work in stages:</p><ul><li>spec: turn feature intent into clear requirements</li><li>design: map those requirements to a practical implementation approach</li><li>tasks: generate an execution-ready task list in STATE.md</li></ul><p>Then you can run:</p><pre>handoff start --copy</pre><p>and begin implementation from a cleaner plan.</p><p>That distinction matters:</p><ul><li>run is the default state-aware entry point</li><li>start is for direct execution when a valid plan already exists</li></ul><p>There is also a closing-loop command:</p><pre>handoff drift --copy</pre><p>handoff drift does not modify code. It generates a structured audit prompt that asks an assistant to compare the saved intent, spec, design, decision log, state, session summary, and implementation.</p><p>That gives you a final check before you call the feature done.</p><h3>Why the file split matters</h3><p>The value is not just “more files.”</p><p>The value is that each file has one job:</p><ul><li>FEATURE.md captures intent</li><li>SPEC.md captures what must be true</li><li>DESIGN.md captures how to approach it</li><li>DECISIONS.md captures why durable choices were made</li><li>STATE.md captures what is being done right now</li><li>STATE.md also captures evidence for completed steps</li><li>SESSION.md captures what the next session must know</li></ul><p>That separation gives the assistant better footing.</p><p>It also gives you better reviewability. You can inspect the spec before implementation, challenge the design before code, review decisions later, and check whether the task list actually matches the feature.</p><h3>Decisions are part of the memory</h3><p>Requirements are not the only thing worth preserving.</p><p>In long-running work, the more expensive loss is often decision history:</p><ul><li>Why did we choose this approach?</li><li>What alternatives did we reject?</li><li>Is this decision still valid?</li><li>Should a future assistant re-open this topic?</li></ul><p>That is why new feature workspaces include DECISIONS.md.</p><p>It is intentionally lightweight. It is not for every small implementation detail. It is for durable product or architecture choices that future sessions should not re-litigate without new evidence.</p><h3>Evidence changes the execution loop</h3><p>AI-assisted coding often ends with a vague claim that work is done.</p><p>That is not enough.</p><p>The default execution prompts now ask the assistant to record evidence in STATE.md after completed micro-steps:</p><ul><li>changed files</li><li>commands or tests run</li><li>result</li><li>notes or remaining risks</li></ul><p>That turns the loop from:</p><pre>Task -&gt; &quot;done&quot;</pre><p>into:</p><pre>Task -&gt; code -&gt; evidence</pre><p>It is still simple Markdown, but it gives you something concrete to review.</p><h3>Drift audit before closing</h3><p>The last failure mode is silent drift.</p><p>A feature can have a good spec, a reasonable plan, and passing tests while still missing part of the original intent.</p><p>handoff drift --copy exists for that moment.</p><p>It emits a prompt for an audit, not an automatic verdict. That distinction is important. The CLI stays deterministic and provider-agnostic; the assistant does the code inspection using the saved artifacts as the checklist.</p><p>The goal is to catch mismatches like:</p><ul><li>a requirement in SPEC.md that never reached implementation</li><li>an accepted decision in DECISIONS.md that code ignored</li><li>a completed task in STATE.md without matching evidence</li><li>a session summary that no longer reflects the repo</li></ul><h3>Why determinism matters</h3><p>One of the design goals of handoff is determinism.</p><p>That is why handoff continue is guarded.</p><p>If the execution plan is invalid, the command fails with a deterministic error instead of pretending everything is fine.</p><p>Examples:</p><ul><li>no execution plan initialized</li><li>multiple current [&gt;] steps</li><li>no remaining steps</li></ul><p>That behavior is deliberate.</p><p>I do not want a workflow that silently fixes state by guessing. I want the handoff to be inspectable and stable.</p><h3>A concrete example</h3><p>Imagine I am adding a payment flow.</p><p>I might start with:</p><pre>handoff init payment-flow</pre><p>Then in FEATURE.md:</p><ul><li>support Stripe checkout</li><li>keep existing order flow intact</li><li>show clear errors</li><li>do not refactor unrelated modules</li></ul><p>From there I have two options.</p><p>Fast path:</p><pre>handoff run --copy<br>handoff next</pre><p>Reviewable path:</p><pre>handoff spec --copy<br>handoff design --copy<br>handoff tasks --copy<br>handoff start --copy</pre><p>Once work is in motion, I can continue with:</p><pre>handoff continue --copy</pre><p>The next session gets a prompt grounded in the existing state, not a vague memory of yesterday.</p><p>Before closing the work, I can ask for a drift audit:</p><pre>handoff drift --copy</pre><p>That prompt checks whether the implementation still matches the saved intent.</p><h3>Better continuity is not only about prompts</h3><p>One thing I like about the current shape of handoff is that it is not only a prompt generator anymore.</p><p>It also helps surface state, decisions, evidence, and drift.</p><p>That is why commands like these matter:</p><ul><li>handoff status</li><li>handoff next</li><li>handoff validate</li></ul><p>They make the saved workflow visible instead of burying it inside one long prompt.</p><p>That is important when you are trying to answer simple questions like:</p><ul><li>Is this feature ready for execution?</li><li>What is the current step?</li><li>Why is the workflow blocked?</li><li>What evidence exists for completed work?</li><li>Did implementation drift from the spec or decisions?</li><li>What command should I run next?</li></ul><h3>Why local-first still matters</h3><p>I wanted this to work with any coding assistant.</p><p>That meant the core could not depend on one provider, one editor, or one hosted workflow system.</p><p>So handoff stays local-first:</p><ul><li>Markdown files in your repository</li><li>prompt generation from a CLI</li><li>no provider dependency in the core flow</li><li>no cloud requirement</li></ul><p>You can use it with ChatGPT today, Claude tomorrow, Copilot later, or another tool entirely.</p><p>The workflow stays yours.</p><h3>Why repository context matters too</h3><p>Feature state is only part of the story.</p><p>Repository context matters too.</p><p>If your README.md and AGENTS.md are missing, stale, or too thin, AI sessions still waste time rediscovering the same project facts.</p><p>That is why handoff init can flag missing high-value context, and why there is also a handoff prompt context flow for improving repo-level guidance without writing application code.</p><p>That may sound small, but it matters in practice.</p><p>A feature plan works much better when the surrounding repository is legible.</p><h3>Why I still like the CLI model</h3><p>There is a lot of value in editor-native workflows, and I may support more of them over time.</p><p>But the CLI model has one major strength: portability.</p><p>The moment a workflow depends too heavily on one IDE, it becomes harder to reuse across tools, harder to debug, and harder to trust.</p><p>handoff keeps the source of truth in files you can inspect directly.</p><p>That makes it easier to reason about, easier to version, and easier to carry across environments.</p><h3>Who this is for</h3><p>handoff is a good fit if:</p><ul><li>you build features across multiple AI sessions</li><li>you switch between assistants or editors</li><li>you want better task decomposition before coding</li><li>you want decision history outside chat</li><li>you want evidence attached to completed work</li><li>you want drift checks before closing features</li><li>you care about deterministic state and inspectable workflow</li><li>you prefer local tools over hosted orchestration</li></ul><p>It is probably not for you if you want a full IDE platform with built-in visual workflow management and heavy automation everywhere.</p><p>That is fine. The tool is intentionally narrower than that.</p><h3>The short version</h3><p>handoff gives AI coding workflows intent, memory, decisions, evidence, and a deterministic continuation path without taking ownership of your editor or your repository.</p><p>That is the whole idea.</p><h3>Try it</h3><p>If you want to try the current default flow:</p><pre>handoff init my-feature<br># edit .handoff/current/FEATURE.md<br>handoff run --copy<br>handoff next<br>handoff status<br>handoff drift --copy</pre><p>If you want to inspect planning in stages first:</p><pre>handoff init my-feature<br># edit .handoff/current/FEATURE.md<br>handoff spec --copy<br>handoff design --copy<br>handoff tasks --copy<br>handoff start --copy<br>handoff continue --copy<br>handoff drift --copy</pre><p>Project link:</p><ul><li><a href="https://github.com/semiherdogan/handoff">handoff on GitHub</a></li></ul><p>If you are building with AI every day, you already know the pain this solves.</p><p>The interesting part is not that the model needs context.</p><p>It is that context needs structure.</p><p>This post may not reflect the latest version. For the updated version, see: <a href="https://semiherdogan.net/posts/handoff-keeping-ai-coding-sessions-on-track/">https://semiherdogan.net/posts/handoff-keeping-ai-coding-sessions-on-track/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=00e97e62d470" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simplifying EC2 Connections with AWS SSH: A CLI Tool for Developers]]></title>
            <link>https://semiherdogan.medium.com/simplifying-ec2-connections-with-aws-ssh-a-cli-tool-for-developers-e723691c2e50?source=rss-ee449aacf0b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/e723691c2e50</guid>
            <category><![CDATA[aws-cli]]></category>
            <category><![CDATA[aws-ssh]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[aws-ssm]]></category>
            <category><![CDATA[aws-ec2]]></category>
            <dc:creator><![CDATA[Semih Erdogan]]></dc:creator>
            <pubDate>Mon, 26 May 2025 14:29:02 GMT</pubDate>
            <atom:updated>2025-05-26T14:29:02.235Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*1nE19dK3BPrDmlF8" /><figcaption>Photo by <a href="https://unsplash.com/@tvick?utm_source=medium&amp;utm_medium=referral">Taylor Vick</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As a developer working with AWS, I often found myself juggling between multiple EC2 instances. Connecting to these instances securely and efficiently was a repetitive task that required navigating through the AWS CLI and Session Manager Plugin. <br>While these tools are powerful, I wanted a simpler, more intuitive way to manage EC2 connections. That’s why I built <strong>AWS SSH</strong>, a CLI tool with a TUI (Text User Interface) that streamlines the process of connecting to EC2 instances.</p><h3>Why I Built AWS SSH</h3><p>The AWS CLI and Session Manager Plugin are excellent tools for managing EC2 instances, but they can be cumbersome for developers who frequently switch between instances. Here are some of the challenges I faced:</p><ul><li><strong>Manual Effort</strong>: Searching for instance IDs and typing long commands to connect.</li><li><strong>Lack of Intuitive UI</strong>: The AWS CLI lacks a user-friendly interface for selecting instances.</li><li><strong>Region Management</strong>: Switching between regions required additional configuration or commands.</li></ul><p>I wanted a tool that could address these pain points by providing a simple, interactive interface for managing EC2 connections. AWS SSH was born out of this need.</p><h3>How AWS SSH Works</h3><p>AWS SSH is a wrapper around the AWS CLI and Session Manager Plugin. It leverages these tools to provide a seamless experience for connecting to EC2 instances. Here’s how it works:</p><ol><li><strong>Instance Discovery</strong>: The tool fetches a list of EC2 instances from your AWS account.</li><li><strong>Interactive UI</strong>: It displays the instances in a TUI, allowing you to search and select the one you want to connect to.</li><li><strong>Secure Connection</strong>: Once you select an instance, the tool uses the AWS Session Manager to establish a secure connection.</li></ol><p>The tool also supports region configuration, so you can specify the regions you want to search in your .aws/credentials file. If no regions are specified, it will prompt you to select one.</p><h3>How to Use AWS SSH</h3><h3>Prerequisites</h3><p>Before using AWS SSH, ensure you have the following installed:</p><ul><li><strong>AWS CLI</strong>: <a href="https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html">Installation Guide</a></li><li><strong>Session Manager Plugin</strong>: <a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html">Installation Guide</a></li></ul><p>You can verify the installation by running:</p><pre>$ aws --version<br>$ session-manager-plugin --version</pre><h3>Installation</h3><p>Download the latest release of AWS SSH from the <a href="https://github.com/semiherdogan/aws-ssh/releases">GitHub releases page</a>. Move the binary to a directory in your $PATH.</p><h3>Usage</h3><p>To launch the tool, run:</p><pre>aws-ssh [ — profile|-p] [ — region|-r] searchparam1 searchparam2 …</pre><p>This will open a TUI where you can search for and select an EC2 instance. Once selected, the tool will automatically connect to the instance using the AWS Session Manager.</p><h3>Key Features</h3><p>Here’s what makes AWS SSH stand out:</p><ul><li><strong>User-Friendly TUI</strong>: A simple interface for selecting EC2 instances.</li><li><strong>Search Functionality</strong>: Quickly find instances by name</li><li><strong>Region Configuration</strong>: Automatically search in specified regions or select one at runtime.</li><li><strong>Profile Selection: </strong>With — profile argument you may select another profile, instead of default.</li></ul><h3>Configuring Regions</h3><p>To streamline your workflow, you can specify regions in your .aws/credentials file. For example:</p><pre>[default]<br>aws_access_key_id = YOUR_ACCESS_KEY<br>aws_secret_access_key = YOUR_SECRET_KEY<br>regions = us-east-1,us-west-2</pre><p>With this configuration, AWS SSH will automatically search for instances in the specified regions.</p><h3>Required AWS Permissions</h3><p>To run this application, you need the following AWS Identity and Access Management (IAM) permissions:</p><h3>Minimum Required Permissions</h3><p><strong>Describe Instances</strong>:</p><ul><li>ec2:DescribeInstances</li></ul><p><strong>SSM Session Start</strong> (for SSH commands via SSM):</p><ul><li>ssm:StartSession</li></ul><h3>Example IAM Policy</h3><p>Here’s an example of an IAM policy that grants the necessary permissions:</p><pre>{<br>  &quot;Version&quot;: &quot;2012-10-17&quot;,<br>  &quot;Statement&quot;: [<br>    {<br>      &quot;Effect&quot;: &quot;Allow&quot;,<br>      &quot;Action&quot;: [<br>        &quot;ec2:DescribeInstances&quot;,<br>        &quot;ssm:StartSession&quot;<br>      ],<br>      &quot;Resource&quot;: &quot;*&quot;<br>    }<br>  ]<br>}</pre><h3>Notes</h3><ul><li>If you want to restrict access further, you can limit the Resource field to specific EC2 instances or tags.</li><li>Ensure the IAM user or role also has permissions to use the AWS Systems Manager (SSM) agent if required for SSH sessions.</li><li><strong>SSM must be enabled for the EC2 instance</strong> to use this tool. Ensure that the instance has the necessary IAM role attached and the SSM agent is installed and running. You can follow the steps to enable SSM for your instance in the <a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-prerequisites.html">AWS documentation</a>.</li></ul><h3>Why You Should Try AWS SSH</h3><p>AWS SSH is designed to save time and reduce friction for developers managing EC2 instances. Whether you’re working with a single instance or dozens, this tool simplifies the process.</p><h3>Links</h3><p><strong>Project repository</strong>: <a href="https://github.com/semiherdogan/aws-ssh">https://github.com/semiherdogan/aws-ssh</a><br><strong>AWS CLI:</strong> <a href="https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html">https://docs.aws.amazon.com/cli/latest/userguide/getting-started-install.html</a><br><strong>Session Manager plugin for the AWS CLI</strong>: <a href="https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html">https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-working-with-install-plugin.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e723691c2e50" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WhatsApp Business Platform New Pricing Model]]></title>
            <link>https://medium.com/teknasyon-engineering/whatsapp-business-platform-new-pricing-model-56fda91ef8df?source=rss-ee449aacf0b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/56fda91ef8df</guid>
            <category><![CDATA[whatsapp-pricing]]></category>
            <category><![CDATA[whatsapp-privacy-feature]]></category>
            <category><![CDATA[whatsapp]]></category>
            <category><![CDATA[whatsapp-business]]></category>
            <category><![CDATA[desk360]]></category>
            <dc:creator><![CDATA[Semih Erdogan]]></dc:creator>
            <pubDate>Tue, 07 Jan 2025 06:37:32 GMT</pubDate>
            <atom:updated>2025-01-07T06:37:32.102Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HyvaCsB3gJQobJewnC-7Sw.jpeg" /></figure><h3><strong>Meta Announces New Pricing Model for WhatsApp Business API</strong></h3><p>Meta has announced its new pricing model for businesses using the WhatsApp Business Platform (API). These changes could significantly impact costs and business processes, especially for businesses. As a messaging platform with billions of users worldwide, WhatsApp has become a critical tool for businesses’ customer service and marketing strategies. Meta’s new pricing structure will change the cost of services that businesses offer on WhatsApp.</p><h3><strong>New Pricing Model: Based on Template Message, Not Conversation</strong></h3><p>Meta will change pricing on the WhatsApp Business API from per conversation to per template message. With this change, businesses will no longer pay per conversation, but per template message. Currently, for many businesses, template messages and the cost of a conversation are generally the same, but with the new model, each template message will have a clearer cost per message.</p><h3><strong>Per-Message Pricing</strong></h3><p>With per-message pricing, businesses on the Meta platform will be charged as follows:</p><ul><li>Per delivered marketing template message</li><li>Per delivered authentication template message</li><li>Per delivered utility template message (if delivered outside of a customer service window)</li></ul><p>For example, if you send a marketing template message followed by two utility template messages, this results in 3 charges (1 for marketing, and 2 for utility). However, if these 2 utility template messages are sent within a customer service window between you and the user, then only one charge will be made (1 for marketing).</p><h3><strong>A new pricing_analytics analysis field</strong></h3><p>A new pricing_analytics analytics field will be released on April 1, 2025, that allows you to get per-message pricing breakdowns for any messages you have sent.</p><h3><strong>Cloud API Webhooks</strong></h3><p>Starting April 2025, status messages webhooks containing pricing information will have the following changes to reflect the new pricing model:</p><h4><strong>Conversation object</strong></h4><p>If per-message pricing applies to you, the conversation object will have the following changes:</p><p>· For webhooks version 22.0 and older, a unique ID will be set per-message, instead of per-conversation-unless the webhook is for a free-entry point conversation.</p><p>· For webhooks version 23.0 and newer, the entire conversation object will only be included for messages that are part of a free-entry point conversation.</p><p>You can adjust webhook version subscriptions using the <strong>App Dashboard &gt; WhatsApp &gt; Configuration</strong> panel’s <strong>Version</strong> dropdown menu for each webhook field.</p><h4><strong>Pricing object</strong></h4><p>Changes to the pricing object in the status messages webhook:</p><ul><li><strong><em>pricing_model</em></strong> property will support a new PMP value. The property will be set to PMP (per-message pricing) if per-message pricing applies to you, otherwise it will be set to CBP (conversation-based pricing).</li><li>A new <strong>type</strong> property will be included, which can have the following possible values:</li><li><strong>regular</strong> — Indicates that the message is billable.</li><li><strong>free_customer_service</strong> — Indicates that the message is free because it was either a utility template message or a non-template message, sent within a customer service window.</li><li><strong>free_entry_point</strong> — Indicates that the message is free because it is part of a free-entry point conversation.</li></ul><p>Under the conversation-based pricing model, the category value in pricing objects indicated which conversation rate was applied. Under the per-message pricing model, these values will not change, but can be interpreted as follows:</p><ul><li><strong>authentication</strong> — Indicates an authentication template message.</li><li><strong>authentication-international</strong> — Indicates that an authentication template message is sent to a WhatsApp user in a country or region that has authentication-international rates.</li><li><strong>marketing</strong> — Indicates a marketing template message.</li><li><strong>utility</strong> — Indicates a utility template message.</li><li><strong>service</strong> — Indicates a non-template message.</li><li><strong>referral_conversion</strong> — Indicates that the message is part of a free entry point conversation.</li></ul><p>The <strong>type</strong> value can be used in conjunction with the category value to determine if the webhook describes a message that was billable, and if so, which rate was applied.</p><pre>+=======================+===========+=====================+==================================================================================================+<br>| Type                  | Category  | Rate          | Reason                                                                                                 |<br>+=======================+===========+===============+========================================================================================================+<br>| regular               | marketing | Marketing     | All marketing template messages are billable.                                                          |<br>+-----------------------+-----------+---------------+--------------------------------------------------------------------------------------------------------+<br>| regular               | utility   | Utility.      | Utility template messages sent outside of a customer service window are billable.                      |<br>+-----------------------+-----------+---------------+--------------------------------------------------------------------------------------------------------+<br>| free_customer_service | utility   | n/a           | Utility template messages sent inside of a customer service window are free.                           |<br>+-----------------------+-----------+---------------+--------------------------------------------------------------------------------------------------------+<br>| free_customer_service | service   | n/a           | Non-templates messages are free.                                                                       |<br>+-----------------------+-----------+---------------+--------------------------------------------------------------------------------------------------------+</pre><h3><strong>Timeline</strong></h3><p>Here are some important dates when the new pricing model will be implemented:</p><ul><li><strong>November 1, 2024</strong>: <em>User-initiated </em>service conversations will be free of charge.</li><li><strong>April 1, 2025</strong>: The new per-template message pricing will be applied to the first API user group.</li><li><strong>April 1, 2025</strong>: Utility templates sent within a customer service window will be free of charge for everyone.</li><li><strong>July 1, 2025</strong>: The new per-template message pricing will be applied to the second (and final) API user group</li></ul><h3><strong>Strategic Decisions and Cost Management</strong></h3><p>While the opportunities that the new pricing model presents to businesses are great, it will also require meticulous cost management. Being able to better analyze the cost of messaging and interactions on WhatsApp will allow businesses to adopt a more strategic approach.</p><h3><strong>At Desk360, we are ready to make sure our customers are not affected by these changes</strong></h3><p>At <a href="https://desk360.com/en">Desk360</a>, we are closely monitoring Meta’s transition to the new pricing model for the WhatsApp Business API and have already started implementing all the necessary updates to ensure that our customers are not affected by these changes. By fully adapting to the new pricing structure, we offer our customers an uninterrupted and seamless experience.</p><h3><strong>Links</strong></h3><ul><li><a href="https://developers.facebook.com/docs/whatsapp/pricing/updates-to-pricing">https://developers.facebook.com/docs/whatsapp/pricing/updates-to-pricing</a></li><li><a href="https://desk360.com/en">https://desk360.com</a></li><li><a href="https://whatsapp.desk360.com/">https://whatsapp.desk360.com</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56fda91ef8df" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teknasyon-engineering/whatsapp-business-platform-new-pricing-model-56fda91ef8df">WhatsApp Business Platform New Pricing Model</a> was originally published in <a href="https://medium.com/teknasyon-engineering">Teknasyon Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WhatsApp Business Platform Yeni Fiyatlandırma Modeli]]></title>
            <link>https://medium.com/teknasyon-engineering/whatsapp-business-platform-yeni-fiyatland%C4%B1rma-modeli-0d08ca3d8016?source=rss-ee449aacf0b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/0d08ca3d8016</guid>
            <category><![CDATA[desk360]]></category>
            <category><![CDATA[whatsapp]]></category>
            <category><![CDATA[whatsapp-business]]></category>
            <category><![CDATA[whatsapp-pricing]]></category>
            <category><![CDATA[business-whatsapp-price]]></category>
            <dc:creator><![CDATA[Semih Erdogan]]></dc:creator>
            <pubDate>Tue, 07 Jan 2025 06:36:38 GMT</pubDate>
            <atom:updated>2025-01-07T06:36:38.061Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O1YZ9oM_UtevcNHL4LWA_Q.jpeg" /></figure><h3><strong>Meta, WhatsApp Business API için Yeni Fiyatlandırma Modelini Açıkladı</strong></h3><p>Meta, WhatsApp Business Platform (API) kullanan işletmeler için yeni fiyatlandırma modelini duyurdu. Bu değişiklikler, özellikle işletmelerin maliyetlerini ve iş süreçlerini önemli ölçüde etkileyebilir. WhatsApp; dünya çapında milyarlarca kullanıcısı olan bir mesajlaşma platformu olarak, işletmelerin müşteri hizmetleri ve pazarlama stratejileri için kritik bir araç hâline geldi. Meta’nın bu yeni fiyatlandırma yapısıyla, işletmelerin WhatsApp üzerinden sunduğu hizmetlerin maliyetleri yeniden şekillenecek.</p><h3><strong>Yeni Fiyatlandırma Modeli: Konuşma Bazlı Değil, Şablon Mesajı Bazlı</strong></h3><p>Meta, WhatsApp Business API üzerindeki fiyatlandırmayı; konuşma başına ücretlendirmeden, şablon mesajı başına ücretlendirmeye geçirecek. Bu değişiklikle birlikte, işletmeler artık konuşma başına değil; her bir şablon mesajı için ücret ödeyecek. Mevcut durumda, birçok işletme için şablon mesajları ve bir konuşmanın maliyeti genellikle eş değer seviyedeydi; ancak yeni modelle birlikte her bir şablon mesajı, mesaj başına daha net bir maliyet oluşturacak.</p><h3><strong>Mesaj Başı Fiyatlandırma</strong></h3><p>Mesaj başına fiyatlandırma ile, Meta platformundaki işletmeler şu şekilde ücretlendirilecektir:</p><ul><li>Teslim edilen pazarlama şablonu mesajı başına</li><li>Teslim edilen kimlik doğrulama şablonu mesajı başına</li><li>Teslim edilen yardımcı hizmet şablonu mesajı başına (Eğer müşteri hizmetleri penceresi dışında teslim edilmişse.)</li></ul><p>Örneğin; bir pazarlama şablonu mesajı ve ardından iki yardımcı hizmet şablonu mesajı gönderdiğinizde bu durum 3 ücretle sonuçlanır (1 pazarlama, 2 yardımcı hizmet). <br> Ancak; eğer bu 2 yardımcı hizmet şablonu mesajı, sizinle kullanıcı arasındaki bir müşteri hizmetleri penceresi sırasında gönderilmişse yalnızca tek bir ücret alınır (1 pazarlama).</p><h3><strong>Yeni bir pricing_analytics analiz alanı</strong></h3><p>1 Nisan 2025 tarihinde yayımlanacak olan bu alan, gönderdiğimiz her mesaj başına fiyatlandırma dökümü almamıza olanak tanıyacaktır.</p><h3><strong>Cloud API Webhooks</strong></h3><p>2025 nisan ayı itibarıyla; fiyatlandırma bilgisi içeren durum mesajı webhook’larında, yeni fiyatlandırma modelini yansıtacak şekilde aşağıdaki değişiklikler yapılacaktır:</p><h4><strong>Conversation object</strong></h4><p>Eğer mesaj başına fiyatlandırma sizin için geçerliyse konuşma nesnesinde aşağıdaki değişiklikler olacaktır:</p><ul><li>Webhook’lar sürüm 22.0 ve öncesi versiyonda; her mesaj için benzersiz bir ID ayarlanacaktır (konuşma başına değil). Bununla birlikte, webhook bir ücretsiz giriş noktasına ait konuşma içinse de bu durum değişmez.</li><li>Webhook’lar sürüm 23.0 ve sonrasındaki versiyonlarda; tüm konuşma nesnesi, yalnızca bir ücretsiz giriş noktasına ait konuşmaların parçası olan mesajlar için dâhil edilecektir.</li></ul><p>Webhook sürüm aboneliklerinizi, her webhook alanı için <strong>Uygulama Gösterge Paneli</strong> &gt; <strong>WhatsApp</strong> &gt; <strong>Yapılandırma</strong> panelindeki <strong>Sürüm</strong> açılır menüsünden ayarlayabilirsiniz.</p><h4><strong>Pricing object</strong></h4><p>Durum mesajları webhook’unda fiyatlandırma nesnesindeki değişiklikler:</p><ul><li><strong><em>pricing_model</em></strong> özelliği, yeni bir PMP değerini destekleyecektir. Eğer mesaj başına fiyatlandırma uygulanıyorsa, bu özellik PMP (mesaj başına fiyatlandırma) olarak; aksi takdirde CBP (konuşma başına fiyatlandırma) olarak ayarlanacaktır.</li><li>Yeni bir <strong>type</strong> (tip) özelliği eklenecektir ve aşağıdaki olası değerleri alabilir:</li><li><strong>regular</strong> — mesajın ücretlendirilebilir olduğunu belirtir.</li><li><strong>free_customer_service</strong> — mesajın ücretsiz olduğunu belirtir; çünkü bu mesaj bir yardımcı hizmet şablonu mesajı ya da müşteri hizmetleri penceresi içinde gönderilen bir şablon dışı mesajdır.</li><li><strong>free_entry_point</strong> — mesajın ücretsiz olduğunu belirtir; çünkü bu mesaj, ücretsiz bir giriş noktasına ait konuşmanın parçasıdır.</li></ul><p>Konuşma başına fiyatlandırma modelinde, fiyatlandırma nesnelerindeki category (kategori) değeri, hangi konuşma oranının uygulandığını gösterir. Mesaj başına fiyatlandırma modelinde ise bu değerler değişmez; ancak aşağıdaki şekilde yorumlanabilir:</p><ul><li><strong>authentication</strong> — kimlik doğrulama şablonu mesajını belirtir.</li><li><strong>authentication-international</strong> — kimlik doğrulama şablonu mesajının, kimlik doğrulama uluslararası oranlarının geçerli olduğu bir ülke veya bölgedeki bir WhatsApp kullanıcısına gönderildiğini belirtir.</li><li><strong>marketing</strong> — pazarlama şablonu mesajını belirtir.</li><li><strong>utility</strong> — yardımcı hizmet şablonu mesajını belirtir.</li><li><strong>service</strong> — şablon dışı mesajı belirtir.</li><li><strong>referral_conversion</strong> — mesajın, ücretsiz bir giriş noktasına ait konuşmanın parçası olduğunu belirtir.</li></ul><p><strong>type</strong> değeri, category değeriyle birlikte kullanılabilir; böylece webhook’un, ücretlendirilebilir bir mesajı tanımlayıp tanımlamadığını belirleyebiliriz ve eğer ücretlendirilmişse hangi oranın uygulandığını öğrenebiliriz.</p><pre><br>+=======================+===========+=====================+========================================================================================================+<br>| Tür                   | Kategori  | Oran                | Sebep                                                                                                  |<br>+=======================+===========+=====================+========================================================================================================+<br>| regular               | marketing | Pazarlama           | Tüm pazarlama şablonu mesajları ücretlendirilebilir.                                                   |<br>+-----------------------+-----------+---------------------+--------------------------------------------------------------------------------------------------------+<br>| regular               | utility   | Yardımcı hizmet     | Müşteri hizmetleri penceresi dışında gönderilen yardımcı hizmet şablonu mesajları ücretlendirilebilir. |<br>+-----------------------+-----------+---------------------+--------------------------------------------------------------------------------------------------------+<br>| free_customer_service | utility   | n/a (geçerli değil) | Müşteri hizmetleri penceresi içinde gönderilen yardımcı hizmet şablonu mesajları ücretsizdir.          |<br>+-----------------------+-----------+---------------------+--------------------------------------------------------------------------------------------------------+<br>| free_customer_service | service   | n/a (geçerli değil) | Şablon dışı mesajlar ücretsizdir.                                                                      |<br>+-----------------------+-----------+---------------------+--------------------------------------------------------------------------------------------------------+</pre><h3><strong>Tarihler</strong></h3><p>Yeni fiyatlandırma modelinin uygulanacağı bazı önemli tarihler şunlardır:</p><ul><li><strong>1 Kasım 2024</strong>: <em>Kullanıcı tarafından başlatılan</em> hizmet konuşmaları ücretsiz olacak.</li><li><strong>1 Nisan 2025</strong>: İlk API kullanıcı grubuna, yeni şablon mesajı başına fiyatlandırma uygulanacak.</li><li><strong>1 Nisan 2025</strong>: 24 saatlik müşteri hizmetleri penceresi içinde kullanılan yardımcı şablon mesajları ücretsiz olacak.</li><li><strong>1 Temmuz 2025</strong>: İkinci (ve son) API kullanıcı grubuna, yeni şablon mesajı başına fiyatlandırma uygulanacak.</li></ul><h3><strong>Stratejik Kararlar ve Maliyet Yönetimi</strong></h3><p>Yeni fiyatlandırma modelinin işletmelere sunduğu fırsatlar büyük olsa da aynı zamanda dikkatli bir maliyet yönetimini gerektirecek. WhatsApp üzerinden yapılan mesajlaşmaların ve etkileşimlerin maliyetini daha iyi analiz edebilmek, işletmelerin daha stratejik bir yaklaşım benimsemesine olanak tanıyacak.</p><h3><strong>Desk360 olarak, bu değişikliklerden müşterilerimizin etkilenmemesi için hazırız</strong></h3><p><a href="https://desk360.com/">Desk360</a> olarak, Meta’nın WhatsApp Business API’deki yeni fiyatlandırma modeline geçiş sürecini yakından takip ediyor ve müşterilerimizin bu değişikliklerden etkilenmemesi için gerekli tüm güncellemeleri şimdiden tamamlıyoruz. Yeni fiyatlandırma yapısına tam uyum sağlayarak müşterilerimize kesintisiz ve sorunsuz bir deneyim sunuyoruz.</p><h3>Linkler</h3><ul><li><a href="https://developers.facebook.com/docs/whatsapp/pricing/updates-to-pricing">https://developers.facebook.com/docs/whatsapp/pricing/updates-to-pricing</a></li><li><a href="https://desk360.com/tr">https://desk360.com</a></li><li><a href="https://whatsapp.desk360.com/">https://whatsapp.desk360.com</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0d08ca3d8016" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teknasyon-engineering/whatsapp-business-platform-yeni-fiyatland%C4%B1rma-modeli-0d08ca3d8016">WhatsApp Business Platform Yeni Fiyatlandırma Modeli</a> was originally published in <a href="https://medium.com/teknasyon-engineering">Teknasyon Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building laravel documentation locally]]></title>
            <link>https://semiherdogan.medium.com/building-laravel-documentation-locally-62758b7a6a38?source=rss-ee449aacf0b7------2</link>
            <guid isPermaLink="false">https://medium.com/p/62758b7a6a38</guid>
            <category><![CDATA[laravel-documentation]]></category>
            <category><![CDATA[laravel-development]]></category>
            <category><![CDATA[laravel]]></category>
            <dc:creator><![CDATA[Semih Erdogan]]></dc:creator>
            <pubDate>Mon, 21 Dec 2020 08:59:22 GMT</pubDate>
            <atom:updated>2020-12-21T08:59:22.929Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2aWQlLY6B7UDytDt" /><figcaption>Photo by <a href="https://unsplash.com/@richtervet?utm_source=medium&amp;utm_medium=referral">Rich Tervet</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Laravel documentation website is great and i can find whatever i needed. <br>But this document pages updating almost everyday and keeping track of those changes became almost impossible for me.</p><p>For solving this issue i build laravel documentation website on my local computer and used git for getting differences between my local and remote documentation repository.</p><p><strong>Let’s start!</strong></p><p>Head over to github laravel docs repository <a href="https://github.com/laravel/docs">https://github.com/laravel/docs</a>.<br>In this repository you can see branches are the same with laravel versions (8.x, 7.x, 6.x etc.). <br>And also you can see all pages in “.md” format (artisan.md, blade.md etc.)</p><p>What we are going to do is, we will clone this repo and checkout branches into another folders.</p><ul><li>Create and cd into new documentation folder <br>$ mkdir laravel-docs &amp; cd laravel-docs .</li><li>Clone branch which you want to keep track of changes. <br>$ git clone <a href="https://github.com/laravel/docs.git">https://github.com/laravel/docs.git</a> -b 8.x --single-branch 8.x</li><li>For seeing changes first you need to get latest changes from github.<br>$ git pull</li><li>After pulling changes from remote you may see these changes with <br>$ git diff HEAD@{1}`</li></ul><p>Example output will be like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*raJGjxi6Bjy9go376cdeIg.png" /></figure><p>After this steps i was able to know latest changes about laravel documentation but after some time i’ve realised that i need changes from another branches too and checking those changes manually will take too much time.</p><p>For this reason i’ve created a script that gets all branches. With this script checking this changes got much easier. And i also add basic html page to see .md files locally.</p><p>For learning more about the script you can check github repository <a href="https://github.com/laratoolbox/laravel-local-documentation">https://github.com/laratoolbox/laravel-local-documentation</a> .</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62758b7a6a38" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>