<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rohit Kashyap</title>
    <description>The latest articles on DEV Community by Rohit Kashyap (@rohitkashyap).</description>
    <link>https://dev.to/rohitkashyap</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4208312%2F47a38233-f234-43b2-afb6-b6d2d6c5e440.jpeg</url>
      <title>DEV Community: Rohit Kashyap</title>
      <link>https://dev.to/rohitkashyap</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rohitkashyap"/>
    <language>en</language>
    <item>
      <title>Ring the Bell on a Quiet Day</title>
      <dc:creator>Rohit Kashyap</dc:creator>
      <pubDate>Wed, 11 Nov 2026 07:21:42 +0000</pubDate>
      <link>https://dev.to/rohitkashyap/ring-the-bell-on-a-quiet-day-4gni</link>
      <guid>https://dev.to/rohitkashyap/ring-the-bell-on-a-quiet-day-4gni</guid>
      <description>&lt;p&gt;&lt;em&gt;This essay was first published on the &lt;a href="https://zyaku.com/blog/ring-the-bell-on-a-quiet-day" rel="noopener noreferrer"&gt;Zyaku blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Picture a dry afternoon a few weeks before the rains. Someone in a small town pulls the torch out of the drawer and clicks it. Nothing. The batteries died sometime in the winter and nobody noticed, because nobody needed a torch in the winter. So they buy new ones, put the torch back, and forget about it.&lt;/p&gt;

&lt;p&gt;That small, boring moment is the most useful thing anyone in that house will do all season. Not because the torch matters on a dry afternoon. Because the night it matters, there will be no time to find out it doesn't work.&lt;/p&gt;

&lt;p&gt;This week we shipped something built on that idea. If you have disaster alerts switched on for a device in Zyaku's Crisis section, you can now send yourself a test alert, close Zyaku, and watch it arrive on your phone or your computer. Or watch it not arrive, which is the more important half.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feenm80n1cjq27uh78w1p.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feenm80n1cjq27uh78w1p.jpg" alt="The best day to check a torch is a day you don’t need one." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;The best day to check a torch is a day you don’t need one.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  The alert I couldn't see
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwexgfhhs9udodjjsa39g.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwexgfhhs9udodjjsa39g.jpg" alt="A warning nobody receives is only a log entry." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;A warning nobody receives is only a log entry.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I'll start with the uncomfortable part, because it's why this exists.&lt;/p&gt;

&lt;p&gt;A little while ago I noticed that alerts weren't showing up on my own devices when Zyaku was closed. So I went looking. On our side, everything looked fine. Every alert went out. The services that carry notifications to phones and browsers kept saying yes, we've got it.&lt;/p&gt;

&lt;p&gt;But "we've got it" from a delivery service is not "it reached your phone". It means the message was accepted into a queue. Whether it was ever handed over to the device was a separate answer that came back later, and we weren't reading that answer at all. A phone that had uninstalled the app, or a missing setting somewhere in the chain, looked exactly the same to us as an alert that had landed. Our records said sent. The phone said nothing, because it never heard anything.&lt;/p&gt;

&lt;p&gt;That's a quiet kind of failure, and quiet failures are the dangerous ones. Nothing breaks. No error appears. Everyone involved believes the warning system works, right up until the night it's needed.&lt;/p&gt;

&lt;p&gt;So we fixed it from both ends. On our side, we now go back and read the answer that says whether a phone really took the alert, and we treat a refusal as a refusal instead of a success. And on your side, we gave you a button.&lt;/p&gt;

&lt;h3&gt;
  
  
  What a test is for
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2j3wkdvfntao2zawujov.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F2j3wkdvfntao2zawujov.jpg" alt="A bell nobody has rung is a guess about a bell." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;A bell nobody has rung is a guess about a bell.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The test alert is simple on purpose. Switch on alerts for the device you're holding, press Send a test alert, close Zyaku, and wait. If it shows up, you know that this device, with these settings, can be reached when the app isn't open. If it doesn't, you've learned that on a calm day, with time to fix it.&lt;/p&gt;

&lt;p&gt;I think about this as the difference between a promise and a check. Every app with notifications makes the same promise: we'll tell you. Very few let you check that promise yourself, on your own phone, without waiting for something bad to happen. And the person holding the phone is the only one who can really check it. We can see what left our servers. We can't see your battery saver, your browser settings, or the switch you turned off last year and forgot about.&lt;/p&gt;

&lt;p&gt;We kept the test deliberately small. It goes only to your own devices. You can't send it to anyone else, and you can't fire it over and over, because a warning that cries wolf trains people to ignore it. And when it arrives, it says plainly that it's a test, so nobody's heart jumps.&lt;/p&gt;

&lt;h3&gt;
  
  
  A backup nobody has restored
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fa950ge0obioif0c0cbdq.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fa950ge0obioif0c0cbdq.jpg" alt="A copy you’ve never opened is a hope, not a backup." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;A copy you’ve never opened is a hope, not a backup.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Before Zyaku, I worked in finance for years. One habit from that world has followed me into software more than any other. You don't trust anything that has only been tested on paper.&lt;/p&gt;

&lt;p&gt;In finance, a transaction either happened or it didn't. I've written that before. The quieter lesson underneath it is that you only know which one by checking. A backup you've never restored from is not a backup. It's a hope with a filename. A procedure nobody has walked through is a document, not a procedure. The people I learned the most from were the ones who insisted on running the drill even when everyone in the room was sure it would pass, because that certainty was exactly what they didn't trust.&lt;/p&gt;

&lt;p&gt;Disaster alerts are the same kind of thing. The whole point of them is that they work on a day nobody can predict. That means the only fair time to test them is a day when nothing is happening. If the first real test of a warning system is the warning itself, it isn't really a system yet.&lt;/p&gt;

&lt;h3&gt;
  
  
  Small rehearsals everywhere
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faxobvb1iz1x14dbrb9oo.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Faxobvb1iz1x14dbrb9oo.jpg" alt="If something is slow, say so, and show the way out." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;If something is slow, say so, and show the way out.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Once I started looking for this pattern, I saw it in a few other changes we made this week and last.&lt;/p&gt;

&lt;p&gt;On the web, Zyaku used to show a plain black page while it was opening. On a slow connection that black page could sit there long enough to make you wonder if anything was happening at all. Now Zyaku shows its logo while it opens. And if opening takes unusually long, it says so, and offers two ways forward: reload, or go straight to emergency help, which works without an account. Someone on one bar of signal in a bad hour shouldn't have to wait for the whole app to load before they can reach the part that might help them.&lt;/p&gt;

&lt;p&gt;The editors got a smaller version of the same honesty. While you write an article or a post, one quiet line underneath now says where your words are: saved on this device, saved to Zyaku, waiting for signal, being sent, or published. Reports filed without signal show it too, and say when they need you. It's not a test button, but it does the same job. It lets you check the state of something you care about while you still have time to act on it.&lt;/p&gt;

&lt;p&gt;None of these are big features. They're the software version of clicking the torch.&lt;/p&gt;

&lt;h3&gt;
  
  
  What a test can't do
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuifkq41lm20ghvb7pjs8.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuifkq41lm20ghvb7pjs8.jpg" alt="A test proves one moment. It doesn’t promise the next." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;A test proves one moment. It doesn’t promise the next.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I want to be careful here, because a test button can create its own kind of false confidence.&lt;/p&gt;

&lt;p&gt;A test that arrives today proves that one device could be reached at one moment. It doesn't promise that the next storm will find your phone charged, your settings unchanged, or a network still standing. It's worth running again when you change phones, change browsers or change settings.&lt;/p&gt;

&lt;p&gt;There are limits I can't engineer away. On a computer, a browser that has been fully quit can't receive a notification at all. That's how browsers work, not something we chose. The test doesn't fix that. It makes it visible, which I think is the honest thing to do with a limit you can't remove.&lt;/p&gt;

&lt;p&gt;Some of our own work isn't finished either. The phone apps aren't public yet, so everything here is about Zyaku in your browser. For emergency messages you write without signal, the rule is still the same: the first one sends by itself when signal returns, even with Zyaku closed, only in Chrome on Android or in Chrome or Edge on a computer. Any message written after that waits for you to press Send or Send all, and they go in the order you wrote them. Mesh, where phones pass messages to each other without a network, is still in testing.&lt;/p&gt;

&lt;p&gt;And the most important line, which I'll keep repeating as long as I write these: Zyaku is not an emergency service. If you're in danger, call your local emergency number first. An alert from us is meant to be one more way to hear something, never the only one.&lt;/p&gt;

&lt;h3&gt;
  
  
  Ring it on a quiet day
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj5oq96hj1vx8yah64uxm.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fj5oq96hj1vx8yah64uxm.jpg" alt="Quiet days are for checking. Loud ones are for acting." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Quiet days are for checking. Loud ones are for acting.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;When I look back at the last few weeks of building, the work I'm proudest of isn't the work that looks impressive in a demo. It's the work that lets ordinary people check things for themselves. Where is my draft. Did my message go. Will this warning actually reach me.&lt;/p&gt;

&lt;p&gt;Software usually asks for trust. I'd rather it earned it in front of you, on an ordinary afternoon, with nothing at stake.&lt;/p&gt;

&lt;p&gt;So if you use Zyaku, try it once. Switch on alerts for your device in Crisis, send yourself the test, close the app and wait. If it arrives, good. If it doesn't, you've found out on the right day, and I'd like to hear what got in the way.&lt;/p&gt;

&lt;p&gt;And a question for everyone, whether you use Zyaku or not. What's the one thing in your life you're sure works but have never actually tested? A smoke alarm, a spare key, a backup, an emergency contact who changed their number? I'm curious which one you went and checked after reading this.&lt;/p&gt;

&lt;p&gt;Rohit Kashyap&lt;br&gt;&lt;br&gt;
Founder &amp;amp; CEO, Zyaku · Founder, TAMVEL  &lt;/p&gt;

&lt;p&gt;&lt;a href="https://zyaku.com/safety" rel="noopener noreferrer"&gt;Safety on Zyaku&lt;/a&gt; · &lt;a href="https://zyaku.com/founder" rel="noopener noreferrer"&gt;About the founder&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>pwa</category>
      <category>ux</category>
      <category>startup</category>
    </item>
    <item>
      <title>Every Song Has a Name</title>
      <dc:creator>Rohit Kashyap</dc:creator>
      <pubDate>Wed, 04 Nov 2026 06:58:51 +0000</pubDate>
      <link>https://dev.to/rohitkashyap/every-song-has-a-name-3lj3</link>
      <guid>https://dev.to/rohitkashyap/every-song-has-a-name-3lj3</guid>
      <description>&lt;p&gt;&lt;em&gt;This essay was first published on the &lt;a href="https://zyaku.com/blog/every-song-has-a-name" rel="noopener noreferrer"&gt;Zyaku blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Say you've just filmed a short clip of your mother's kitchen on a festival morning. Steam off the pan, her hands moving faster than the camera can follow, a radio somewhere in the back. You want a song under it. Not any song. The one that sounds like that morning.&lt;/p&gt;

&lt;p&gt;You open the music picker, find a track, and post. Your cousin in another city watches it on her phone. The song plays. Under the clip, in small letters, is the name of the song and the name of the person who made it.&lt;/p&gt;

&lt;p&gt;That last line is the part I want to write about. This week, music started playing under clips, stories and live broadcasts on Zyaku. Every track you can choose carries its artist's name, its licence, and a link back to where it came from. Viewers see the name. They can also turn the music off.&lt;/p&gt;

&lt;p&gt;It sounds like a small thing. It took us longer to get right than the part where the music plays.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcv982xzoen3myq45jm70.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcv982xzoen3myq45jm70.jpeg" alt="A small clip deserves the right song, and the song deserves its maker's name." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;A small clip deserves the right song, and the song deserves its maker's name.&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  The name under the clip
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcbr44ha1uh9wngv9z0by.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fcbr44ha1uh9wngv9z0by.jpeg" alt="Somebody made every track you hear." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Somebody made every track you hear.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Most of the music you hear under short videos on the internet arrives without a name. Someone heard it somewhere, added it, and it travelled. By the time it reaches you, the person who wrote it has fallen off the end of the chain.&lt;/p&gt;

&lt;p&gt;I didn't want Zyaku to work like that. Zyaku is meant to be a place where people get paid for what they make, readers pay for the chapter they unlock, and the work carries its maker with it. It would be a strange kind of platform that asked you to respect a comic artist and then let a musician vanish from the bottom of every clip.&lt;/p&gt;

&lt;p&gt;So our music library holds only openly licensed tracks, the kind whose licence lets you put the song under a picture and share the result, as long as you credit the person who made it. Songs whose licence says no to that are left out, even when they're good. Every track keeps four things wherever it goes: its title, its artist, its licence, and a link to the original page.&lt;/p&gt;

&lt;p&gt;When I explain this to people, the usual question is why we didn't just license a big catalogue of famous songs. The honest answer is that we're a young company and we don't buy what we can't pay for. The better answer is that I'd rather offer fewer songs that are really yours to use than more songs that might be taken down from under you later.&lt;/p&gt;

&lt;h3&gt;
  
  
  What an auditor taught me
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkol5qrr4cfyyjfciwg8k.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkol5qrr4cfyyjfciwg8k.jpeg" alt="Every line in the books points back to a piece of paper." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Every line in the books points back to a piece of paper.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Before I built software, I spent years in finance. The lesson that comes back to me most often this week isn't about money moving. It's about where a number comes from.&lt;/p&gt;

&lt;p&gt;An auditor doesn't start by asking whether a figure looks right. They ask for the voucher. Show me the invoice behind this line, the receipt, the contract. A number with a document behind it is a fact. A number without one is a question, however confident it looks on the page.&lt;/p&gt;

&lt;p&gt;I think about content the same way now. A song under a clip is a line in a ledger. The credit is its voucher. Strip the credit off and the song is still there, still playing, still pleasant, but nobody can say where it came from or who should be thanked for it.&lt;/p&gt;

&lt;p&gt;That idea has been quietly spreading through Zyaku for a while. The technology section of News now includes top stories from Hacker News, and each one links to the original article rather than a copy of it. Discover shows a story's picture only where the publisher provides one. And an article on Zyaku can show Independently checked only after a Zyaku reviewer, never the author, confirms it against a public source. Readers can open that source and read what was checked. Different features, same rule. If we show you something, you should be able to follow it back to where it started.&lt;/p&gt;

&lt;h3&gt;
  
  
  Songs people actually play
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fikvnxk2295jlonpiih9c.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fikvnxk2295jlonpiih9c.jpeg" alt="The shelf should sound like the people using it." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;The shelf should sound like the people using it.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I'll admit something that isn't flattering. For a while, our music picker was searching a place that didn't exist. Every shelf was empty, and nobody outside the team would have known why. We rebuilt it around our own catalogue, and the picker finally opened on a shelf of real tracks.&lt;/p&gt;

&lt;p&gt;Then we looked at what people would actually search for. Hindi. Punjabi. Workout. The shelves came back nearly bare. A music library that can't answer "Punjabi" isn't much use to a creator in Ludhiana, or to anyone in the diaspora making a clip for a wedding.&lt;/p&gt;

&lt;p&gt;So this week the library started bringing in Hindi, Punjabi, Bollywood, devotional and workout tracks, and Trending gained Workout, Romantic, Happy and Devotional rows. It's still openly licensed music, so you won't find the latest film hit there. You will find people playing the harmonium, the dhol and the flute who chose to let others build on their work, with their names attached.&lt;/p&gt;

&lt;p&gt;This matters to me beyond music. Zyaku already tries to meet people in the language they think in: our Offline Emergency Assistant speaks Hindi and Hinglish because in a frightening moment nobody should have to translate in their head. A creator choosing a song for their sister's sangeet deserves the same respect, even if the stakes are lower.&lt;/p&gt;

&lt;h3&gt;
  
  
  When we get it wrong
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdowa2pj1lswdl48qvose.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fdowa2pj1lswdl48qvose.jpeg" alt="If we take something down, you should be able to answer." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;If we take something down, you should be able to answer.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Credit has another side. Sometimes the trouble runs the other way: someone says a piece of work belongs to them when it doesn't, or a platform removes the wrong thing.&lt;/p&gt;

&lt;p&gt;Since last week, if something you posted is removed after a copyright notice, you can read that notice yourself and send a counter-notice from Settings, under Privacy, then Copyright notices. You don't need to find an email address or write a letter in legal English from scratch. If the person who sent the notice doesn't take it to court within the legal waiting period, your work comes back on its own. There's also a public page, &lt;a href="https://zyaku.com/dmca" rel="noopener noreferrer"&gt;zyaku.com/dmca&lt;/a&gt;, that explains how notices work, who receives them, and how to answer one if your own work was taken down by mistake.&lt;/p&gt;

&lt;p&gt;I care about this because takedowns are where platforms tend to be least transparent. A post disappears, a vague email arrives, and the creator is left guessing. Zyaku already puts moderation decisions on a public ledger with a real window to appeal. Copyright deserves the same thing: if we remove your work, you should see why, and you should have a clear way to say we were wrong.&lt;/p&gt;

&lt;h3&gt;
  
  
  What isn't finished
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsje4yveqkhgav0vcjbr7.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fsje4yveqkhgav0vcjbr7.jpeg" alt="Some of this works in the browser first. The apps are next." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;Some of this works in the browser first. The apps are next.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;There's plenty left.&lt;/p&gt;

&lt;p&gt;The music plays in the browser today. Our phone apps don't play it yet; that comes with their next build, and I won't say it's there until it is. The catalogue is also smaller than anyone would like. It grows a little each day, but a creator looking for one particular sound will sometimes come up empty.&lt;/p&gt;

&lt;p&gt;There's a harder question too. Openly licensed music is only as honest as the people who uploaded it. If someone shares a track they had no right to share, the licence label on it is wrong, and we would be passing that mistake along. The counter-notice flow helps when things go wrong. It doesn't stop them going wrong in the first place, and I don't have a perfect answer for that yet.&lt;/p&gt;

&lt;p&gt;And credit isn't payment. Putting an artist's name under a clip is the least we can do, not the most. I'd like to get to a place where the people behind the music can be paid on Zyaku the way comic artists and journalists already can. We're not there, and I'd rather say so than dress up a credit line as something it isn't.&lt;/p&gt;

&lt;h3&gt;
  
  
  Pointing back
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fl6urtxgs5paifru963n4.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fl6urtxgs5paifru963n4.jpeg" alt="A name is the least a song is owed." width="799" height="450"&gt;&lt;/a&gt;&lt;br&gt;
&lt;em&gt;A name is the least a song is owed.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;When I line up this week's changes, I see one stubborn habit. Every borrowed thing on Zyaku should point back to where it came from: a song to its artist, a headline to its publisher, a fact check to its source, a removed post to the notice that removed it.&lt;/p&gt;

&lt;p&gt;It isn't the flashiest work we do. Nobody downloads an app because its credits are accurate. But I think trust gets built in exactly these places, in the small print people almost never read, and notice straight away when it's missing.&lt;/p&gt;

&lt;p&gt;Back in that kitchen clip, the song plays, your cousin smiles, and somewhere a musician you'll never meet has their name on a screen in a city they've never visited. That seems like the right way round.&lt;/p&gt;

&lt;p&gt;So here's my question for you. Is there a song, a drawing or a piece of writing you loved for years and never knew who made? I'd like to hear how you finally found out, or whether you're still looking.&lt;/p&gt;

&lt;p&gt;Rohit Kashyap&lt;br&gt;&lt;br&gt;
Founder &amp;amp; CEO, Zyaku · Founder, TAMVEL  &lt;/p&gt;

&lt;p&gt;&lt;a href="https://zyaku.com/developers/changelog" rel="noopener noreferrer"&gt;What's new on Zyaku&lt;/a&gt; · &lt;a href="https://zyaku.com/founder" rel="noopener noreferrer"&gt;About the founder&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>music</category>
      <category>startup</category>
      <category>ux</category>
    </item>
    <item>
      <title>The Honest Middle</title>
      <dc:creator>Rohit Kashyap</dc:creator>
      <pubDate>Wed, 28 Oct 2026 06:49:51 +0000</pubDate>
      <link>https://dev.to/rohitkashyap/the-honest-middle-24a8</link>
      <guid>https://dev.to/rohitkashyap/the-honest-middle-24a8</guid>
      <description>&lt;p&gt;&lt;em&gt;This essay was first published on the &lt;a href="https://zyaku.com/blog/the-honest-middle" rel="noopener noreferrer"&gt;Zyaku blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Imagine a reporter on a bus climbing out of a valley. She has just finished a short piece about a road that washed out. She presses Publish. Somewhere around the next bend, the signal goes.&lt;/p&gt;

&lt;p&gt;Now look at her screen and ask a simple question: what does the phone actually know?&lt;/p&gt;

&lt;p&gt;It knows she pressed the button. It might know the request left the phone. It does not know whether Zyaku received it. Maybe the post went through a second before the tower dropped. Maybe it never left. From inside the phone, both look the same.&lt;/p&gt;

&lt;p&gt;Most apps answer that question with a guess. A spinner that never stops. A tick that appears too early. Or, worst of all, a cheerful "Posted!" that turns out to be wrong much later, when her editor asks where the story is.&lt;/p&gt;

&lt;p&gt;This week we shipped a small change to Zyaku that I think about more than most big features. Every item waiting in your outbox now says how sure it is.&lt;/p&gt;

&lt;h3&gt;
  
  
  Half right
&lt;/h3&gt;

&lt;p&gt;In my first essay here, I wrote that in finance a transaction either happened or it didn't, and that "probably sent" is not a state. I still believe the first half. I've had to rethink the second.&lt;/p&gt;

&lt;p&gt;Anyone who has worked near payments knows the word pending. Money has left one place and hasn't been confirmed in the other. Banks don't hide that. They don't round it up to "done" or down to "failed". They show it as what it is: a middle state, with a name, that everyone agrees to watch until it settles. Reconciliation, the dull work that keeps the whole system honest, is mostly about refusing to pretend the middle isn't there.&lt;/p&gt;

&lt;p&gt;Software for ordinary people rarely gets that courtesy. We flatten everything into two states because two states are easier to design. Sent or not sent. Green or red. And the truth, which is often "we don't know yet", gets painted over with whichever colour makes the screen look calmer.&lt;/p&gt;

&lt;p&gt;So "probably sent" still isn't a state. But "sent, no answer yet" is. So is "we tried and never heard back". Admitting uncertainty was never the mistake. Hiding it was.&lt;/p&gt;

&lt;h3&gt;
  
  
  What the outbox says now
&lt;/h3&gt;

&lt;p&gt;Every row in the Zyaku outbox now carries one of a few plain answers.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;On this device only.&lt;/strong&gt; You wrote it, it's safe on your phone, and it hasn't been sent anywhere yet.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Sending, with no answer yet.&lt;/strong&gt; It has gone out, and Zyaku hasn't replied.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Tried, without a reply.&lt;/strong&gt; We made an attempt and the network swallowed the answer. We can't tell you it arrived, and we won't.&lt;/p&gt;

&lt;p&gt;What the outbox never says is "published". That word belongs to Zyaku itself, not to the queue on your phone. A queue finishing its job is not the same as the server saying "I have it". Since last week, a post's own page tells you whether it has reached Zyaku, and that's where the confirmation lives. The outbox only ever describes what your phone can honestly see.&lt;/p&gt;

&lt;p&gt;That sounds like a wording change. It took a surprising amount of discipline. The temptation, every single time, is to let a row slide into "done" because the request finished without an error. But finishing without an error and arriving are different things, and anyone who has lost a message on a train knows it.&lt;/p&gt;

&lt;p&gt;We changed something else on the same screen. The buttons that remove what you wrote now look different from the ones that send it. Cancel and Discard are drawn one way, because once you press them your words are gone. Try again and Send are drawn another way. We did the same on the offline emergency screen: buttons that send a message, buttons that remove something for good, and buttons that only check or go back each have their own shape. When you're tired, scared or squinting at a cracked screen, you shouldn't have to read a label to know which button can't be undone.&lt;/p&gt;

&lt;h3&gt;
  
  
  Nothing moves by itself
&lt;/h3&gt;

&lt;p&gt;The same idea showed up somewhere I didn't expect: the marketplace.&lt;/p&gt;

&lt;p&gt;Creators on Zyaku sell their work there. Until this week, if you opened the marketplace without a connection, you saw nothing. If you pressed Buy, you got a raw network error that didn't tell you the one thing you wanted to know. Did money move?&lt;/p&gt;

&lt;p&gt;Now the marketplace opens offline, with the items you saw before and your own library. If you press Buy while offline, Zyaku tells you nothing has been charged. It can keep the item for you, and when you're back online it shows Continue to checkout. The payment page opens only when you press that button. Never on reconnect, never by itself.&lt;/p&gt;

&lt;p&gt;This is where the finance years come back hardest. An offline queue for posts is a kindness. An offline queue for payments is a trap. Picture tapping Buy on a train, losing signal, forgetting about it, and getting charged much later when your phone finds a tower. Even if you wanted it at the time, you didn't agree to it now. So we made a rule with no exceptions: nothing is bought offline, and no payment ever starts on its own later. A payment needs a connection and your own tap. Every time.&lt;/p&gt;

&lt;p&gt;It's a strange thing to be proud of, a button that refuses to do something. But I'd rather lose a sale than take money from someone who wasn't looking.&lt;/p&gt;

&lt;h3&gt;
  
  
  Two versions of the truth
&lt;/h3&gt;

&lt;p&gt;The third change this week is for journalists, and it's the hardest one to explain without sounding technical, so here's a scene.&lt;/p&gt;

&lt;p&gt;An editor fixes a mistake in a published story from her laptop. At the same time a reporter, offline on a hillside, is rewriting the same paragraph on his phone. Until this week, whichever edit arrived last simply won. His signal comes back, his version lands, and her fix disappears without anyone being told.&lt;/p&gt;

&lt;p&gt;Now, if you edit an article offline and someone changed it somewhere else in the meantime, Zyaku asks which version to keep instead of quietly replacing the newer one. We also stopped a few quieter problems. Saving offline no longer makes extra copies of a new article. An open editor no longer turns a published article back into a draft. And a deleted article stays deleted.&lt;/p&gt;

&lt;p&gt;None of that is glamorous. But news depends on people trusting that what they read is what the newsroom meant to publish. Living Story already keeps the earlier text of a story visible when it's updated, along with the reason for the change. Making sure one person's edit can't silently erase another's is the same promise, one level down.&lt;/p&gt;

&lt;h3&gt;
  
  
  Saying "not yet" out loud
&lt;/h3&gt;

&lt;p&gt;Then there's the offline page itself. When you open a page on Zyaku that you haven't saved and there's no connection, you used to get one bare line telling you that you were offline. Now the page explains what happened, offers Try again and a way back to the saved home screen, and reloads by itself when the connection returns. Nothing clever. Just a screen that tells you where you stand and what you can do next.&lt;/p&gt;

&lt;p&gt;When I line these changes up, I see one idea. Software should say what it knows, say what it doesn't, and never make a decision with your words or your money while you aren't looking.&lt;/p&gt;

&lt;p&gt;That idea also sits at the centre of HoldSend, the open-source library we put on GitHub a few days ago. Its core is a small state machine that holds what you wrote and moves it from your device to the server one step at a time, without claiming a step it can't prove. It's public under the Apache license, and it's early. Only that core and its tests are there. The storage pieces, the server side and the emergency module are still being built, and the README says plainly that nothing is ready for production. I'd rather say that in public than find out later that someone trusted it too soon.&lt;/p&gt;

&lt;h3&gt;
  
  
  What isn't finished
&lt;/h3&gt;

&lt;p&gt;"Tried, without a reply" is an honest answer, but not a satisfying one. The next job is to find out more often, so fewer things sit in the middle for long.&lt;/p&gt;

&lt;p&gt;Some of that depends on the phone. Our native apps don't send in the background yet. For now, the first emergency message you write without signal sends by itself when signal returns, even with Zyaku closed, only in Chrome on Android or in Chrome or Edge on a computer. Any message you write after that waits for you to press Send or Send all, and they go in the order you wrote them. I want to close the gap on the native apps, and I won't claim it's closed before it is.&lt;/p&gt;

&lt;p&gt;None of this replaces emergency services, either. If you're in danger, call your local emergency number first.&lt;/p&gt;

&lt;h3&gt;
  
  
  The comforting lie
&lt;/h3&gt;

&lt;p&gt;I used to think the kindest thing an app could do was make you feel everything was fine. I don't anymore. The kindest thing is to tell you the truth in words you can act on, even when the truth is "not yet".&lt;/p&gt;

&lt;p&gt;A reporter on a bus doesn't need a green tick. She needs to know whether to tell her editor the story is in, or to try again at the next town.&lt;/p&gt;

&lt;p&gt;Everything we ship goes on our &lt;a href="https://zyaku.com/developers/changelog" rel="noopener noreferrer"&gt;public changelog&lt;/a&gt;, including the small, unglamorous fixes like these.&lt;/p&gt;

&lt;p&gt;So here's my question for you. Where has a piece of software told you something was done when it wasn't, and what did it cost you? I read every reply, and more than one thing we've built started as a stranger's question.&lt;/p&gt;

&lt;p&gt;Rohit Kashyap&lt;br&gt;&lt;br&gt;
Founder &amp;amp; CEO, Zyaku · Founder, TAMVEL  &lt;/p&gt;

&lt;p&gt;&lt;a href="https://zyaku.com/developers/changelog" rel="noopener noreferrer"&gt;What's new on Zyaku&lt;/a&gt; · &lt;a href="https://zyaku.com/founder" rel="noopener noreferrer"&gt;About the founder&lt;/a&gt; · &lt;a href="https://github.com/zyakuhq/holdsend" rel="noopener noreferrer"&gt;HoldSend on GitHub&lt;/a&gt;&lt;/p&gt;

</description>
      <category>offlinefirst</category>
      <category>ux</category>
      <category>webdev</category>
      <category>startup</category>
    </item>
    <item>
      <title>The Hour the Internet Goes Quiet</title>
      <dc:creator>Rohit Kashyap</dc:creator>
      <pubDate>Mon, 26 Oct 2026 09:43:19 +0000</pubDate>
      <link>https://dev.to/rohitkashyap/the-hour-the-internet-goes-quiet-3d53</link>
      <guid>https://dev.to/rohitkashyap/the-hour-the-internet-goes-quiet-3d53</guid>
      <description>&lt;p&gt;&lt;em&gt;This essay was first published on the &lt;a href="https://zyaku.com/blog/the-hour-the-internet-goes-quiet" rel="noopener noreferrer"&gt;Zyaku blog&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;I keep coming back to one picture.&lt;/p&gt;

&lt;p&gt;A phone on a kitchen table, screen on, one bar of signal that keeps disappearing. Water is already in the street. Someone is trying to tell their mother they're fine. The message sits there with a little clock icon next to it, and nobody knows if it went.&lt;/p&gt;

&lt;p&gt;Most of the internet was never built for that moment. It was built for good Wi-Fi, a charged battery and a calm afternoon. When the network goes, apps don't slow down gracefully. They just stop. The phone still works. Your words are still there. But the software decides that without a connection, nothing you do counts.&lt;/p&gt;

&lt;p&gt;That idea bothered me enough that I started building something about it. It's called Zyaku.&lt;/p&gt;

&lt;h3&gt;
  
  
  I didn't come from software
&lt;/h3&gt;

&lt;p&gt;I spent most of my working life in finance: investment, wealth management, and eventually my own firm. I wasn't an engineer. I taught myself to build because the thing I wanted didn't exist, and waiting for someone else to make it felt worse than learning.&lt;/p&gt;

&lt;p&gt;I'm telling you this because it explains the way Zyaku is built. In finance you learn one rule early: a transaction either happened or it didn't. "Probably sent" is not a state. So when I started on the offline side of Zyaku, that was the first rule I wrote down. Nothing gets called sent until it has actually arrived.&lt;/p&gt;

&lt;h3&gt;
  
  
  Write now, publish when the world lets you
&lt;/h3&gt;

&lt;p&gt;The first thing Zyaku had to do was simple to say and hard to get right. You can write while you're offline, whether it's a post, a story or a news report. Zyaku keeps it safely on your device. When the connection comes back, it goes out once. Not zero times, not twice.&lt;/p&gt;

&lt;p&gt;That "once" took more work than anything else. Phones lose signal halfway through a send. People tap the button again. Apps get killed in the background. Every one of those moments is a chance for a post to vanish or show up twice. A few weeks ago I posted a demo of this on X, phone in airplane mode, and engineers I'd never met started asking hard questions. How long do you keep the keys that stop duplicates? What happens if I force-close the app? Does a post keep the time it was written? Those questions were a gift. Building in public meant a stranger could look at my work and push it further, and that's exactly what happened.&lt;/p&gt;

&lt;h3&gt;
  
  
  Then the floods
&lt;/h3&gt;

&lt;p&gt;Zyaku's Disaster Alert came out of the floods in Nepal. Networks failed exactly when people most needed to reach each other. Watching that from the outside, I realised that a platform which works offline for creators can also work offline for families.&lt;/p&gt;

&lt;p&gt;So the safety side of Zyaku grew from there. Today it has:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Official warnings, turned into Crisis alerts.&lt;/strong&gt; Zyaku draws on official warning services around the world, including in India, Japan, Nepal, Europe, Canada and Brazil. When one of them issues a serious warning for an earthquake, flood, cyclone, wildfire or severe weather, Zyaku sends it first to people in that area, in its own Crisis feed so it doesn't get lost between memes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An Offline Emergency Assistant.&lt;/strong&gt; Step-by-step guidance for earthquakes, floods, fire, first aid and CPR, with no internet at all. It speaks English, Hindi and Hinglish, because in a crisis people should get help in the language they think in.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A Medical ID with a QR code.&lt;/strong&gt; You add your blood group, allergies, medicines and emergency contacts. Zyaku turns the details you choose into a QR code that a rescuer can read with any phone camera. No app, no internet. It stays encrypted on your own phone, and we keep no copy.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;I'm Safe.&lt;/strong&gt; One tap tells the people you trust most that you're okay. Nobody can add you to a circle without your say, and your location is shared only when you choose, every time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;An offline map of hospitals and shelters.&lt;/strong&gt; Save your area while you're online. Later, with no connection, your phone's GPS shows the nearest hospitals, clinics, shelters, police and fire stations, with distance and direction. The place data comes from OpenStreetMap, built by volunteers, which feels right.&lt;/p&gt;

&lt;p&gt;I want to be careful here, because safety is the one area where overpromising is unforgivable. Zyaku is not an emergency service. If you're in danger, call your local emergency number first. What we can do is make sure that when the network is gone, the little things that help are still on your phone.&lt;/p&gt;

&lt;h3&gt;
  
  
  Creators shouldn't need a big audience to get paid
&lt;/h3&gt;

&lt;p&gt;Safety is the part of Zyaku that gets attention, but the everyday part matters just as much.&lt;/p&gt;

&lt;p&gt;Zyaku is a home for creators and independent journalists. Comics, motion comics made in our AI Studio, short video, podcasts, long reporting. There's no follower minimum to start earning. Readers pay for the chapter they unlock, not for how famous you are. And creators get paid wherever they live, including in countries where the usual payment rails don't reach.&lt;/p&gt;

&lt;p&gt;Creators can also make Offline Packs: bundles of comic chapters or videos that a reader downloads once on Wi-Fi and enjoys anywhere, on a train, on a flight, in a village with one weak tower.&lt;/p&gt;

&lt;p&gt;For journalists, one line matters more than any feature list: journalists can publish anonymously. Their identity is stored encrypted and is never shown to readers.&lt;/p&gt;

&lt;p&gt;And every moderation decision on Zyaku goes on a public ledger, with a real window to appeal. If we take something down, you can see that we did, and you can argue with us.&lt;/p&gt;

&lt;h3&gt;
  
  
  Where I'm being honest about what isn't done
&lt;/h3&gt;

&lt;p&gt;There's a part of Zyaku I care about a lot that isn't live yet. We're working on a mesh, where phones talk to each other directly when there's no network at all. It's in testing. I'm not going to call it finished until it works in the field, at real distances, with real people. If you've read startup announcements before, you know how rare that sentence is. I'd rather be slow and right.&lt;/p&gt;

&lt;h3&gt;
  
  
  Why the core is going open source
&lt;/h3&gt;

&lt;p&gt;This is the part I'm most excited to write about.&lt;/p&gt;

&lt;p&gt;The engine that lets you compose offline and publish safely during an outage shouldn't belong only to Zyaku. Newsrooms need it. Aid groups need it. Small apps in places with bad connectivity need it. Every team that builds this alone makes the same mistakes I made, losing posts, duplicating posts, and lying to users with a "sent" that wasn't true.&lt;/p&gt;

&lt;p&gt;So we're going to open-source it. The idea is simple: a piece of software that holds your work safely while you're offline, sends it exactly once when the connection returns, and never pretends something arrived when it didn't. Anyone should be able to use it, inspect it and improve it. When it's public, I'll write about it here first.&lt;/p&gt;

&lt;p&gt;I've also started a second company, TAMVEL, around the same belief applied to money: financial apps shouldn't stop working the moment the network does. Different problem, same stubborn idea.&lt;/p&gt;

&lt;h3&gt;
  
  
  What I believe
&lt;/h3&gt;

&lt;p&gt;I don't think the next internet will be defined by who has the biggest model or the most users. I think it will be defined by what still works on the worst day.&lt;/p&gt;

&lt;p&gt;A journalist in a shutdown who can still file. A creator in a small town who gets paid. A family that knows everyone is safe before the towers come back.&lt;/p&gt;

&lt;p&gt;That's what I'm building. It's not finished, and I'm doing a lot of it in public, mistakes included. If you build software, report the news, make things, or just live somewhere the signal drops, I'd really like to hear what you'd want from it.&lt;/p&gt;

&lt;p&gt;You can see everything that has shipped at &lt;a href="https://zyaku.com" rel="noopener noreferrer"&gt;zyaku.com&lt;/a&gt;, and every update goes on our &lt;a href="https://zyaku.com/developers/changelog" rel="noopener noreferrer"&gt;public changelog&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Rohit Kashyap&lt;br&gt;&lt;br&gt;
Founder &amp;amp; CEO, Zyaku · Founder, TAMVEL&lt;/p&gt;

&lt;p&gt;&lt;a href="https://zyaku.com/safety" rel="noopener noreferrer"&gt;Safety features&lt;/a&gt; · &lt;a href="https://zyaku.com/founder" rel="noopener noreferrer"&gt;About the founder&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://medium.com/@rohit.kashyap_53123/the-hour-the-internet-goes-quiet-9cb1621f9b00" rel="noopener noreferrer"&gt;Also published on Medium.&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Update: the open-source part is now public as &lt;a href="https://github.com/zyakuhq/holdsend" rel="noopener noreferrer"&gt;HoldSend&lt;/a&gt;, an early open-source outbox for apps that must never lose or double-post what people write. It is not production-ready yet.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>offlinefirst</category>
      <category>opensource</category>
      <category>startup</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
