Hacker News new | past | comments | ask | show | jobs | submit | kossnocorp's comments login

Discovered the app on Twitter, it's amazingly good at recording product demos


Hey, after I learned that Twitter acquired Revue, I decided to build a mashup app that converts Revue newsletters to Twitter threads.

I used an algorithm that splits along text into tweets from another project that ensures that the sentences never slice and the thread is easy to read.

I've built it using Preact, CSS, Firebase (Firestore/Functions).


Congrats with the launch! Proud to see that https://chirr.app inspired you!


Made this before discovering Chirr. But very happy to see another great product in this space from a fellow maker!


You're right, and I suppose that's why Twitter doesn't add it. But when you write a thread and then spot a typo right in the middle, it's a disaster. You don't have to deal with clunky Twitter UI but also have to recreate the content (images, text).

Chirr does not update the content but removes the edited part of the thread and republishes it, so it's impossible to abuse.

Another thing I working on is delayed publishing ala Gmail.


Thanks! ฅ^•ﻌ•^ฅ


Threads is an excellent and unique medium that is easy to consume and share, take a look at these examples:

- https://twitter.com/dannypostmaa/status/1282952961857970176

- https://twitter.com/robhope/status/1265278107088347136

Of course, you can make a blog post from such threads (and probably should, if the thread got traction), but it would look and read differently.


Can you explain why? Your reply is "it's better because it's better".


From my personal experience, people are more likely to read and share threads for a number of reasons:

* They don't have to go off platform.

* the base tweet can be much more eye catching that a link, even with social cards set up

* People may be desensitised to links that lead off-platform, because that's how Ads generally appear on Twitter

Then there are other advantages, like the fact that it tends to encourage you to write in a concise and direct way, with each tweet in the thread being like a bullet point. I often see people retweeting and engaging with a specific tweet from the thread; it's harder (relative term) to do that with a section from a blog post.


Depending on what you are doing(!) users stuck on a platform OR users who don't do links might or might not be the desired audience.


Maybe, but the question is: who are they going to share it to?


I never said that threads are better than blog posts. It's a different format and provides its advantages.

- First of all, threads are often long-living i.e., authors update it over time. It allows them to surface the content every time they update it.

- Secondly, often every tweet's a self-containing idea. Blog posts usually are worried and need more time to grasp.

- Also, it's not only easy to consume but also to share.

I like, write and consume both Twitter threads and blog posts.


I think it's primarily because you put actual content right in front of them, increasing the chances of them getting hooked by quite a bit. Before your blog post has any chance of hooking people, they have to first take the plunge of clicking on it. Threads eliminate that friction.


Those look terrible, like powerpoint presentations that you fall asleep in the middle of. And in any case, the link here was to a tool that was basically using blog-like editing tools to write blog-like threads. So, why not just blog?


Agreed, what would be better would to maybe put the engagement stats(faves,replies, etc) to the right, expand replies to each tweet when clicked on pop from the right and then descend, but the thread itself a contiguous block of text/tweets all the way to the authors last tweet in the thread.


Hey, the Chirr App author here!

I released the initial version of the app in 2017 as a free and open-source tool (https://github.com/kossnocorp/chirrapp) even before Twitter threads become a thing.

Later that year, Twitter gave me a lot of trouble when they added 280-chars support but didn't update API and the twitter-text library. I was about to close it, but thanks to Firebase, the running cost was $0, so I fixed the issues and kept it alive.

With time, the app accumulated authority and users. Since 2017 when I first launched the app, it has been used by 9.5K people to publish 22K threads and 330K tweets! Happy users started coming to me with thanks and features requests more and more so I decided to rewrite the app and added tons of new features, like:

- Drag-n-drop images

- Editing published threads (yes, the edit button!)

- Drafts

- Scheduling

- And much more!

In case if anyone curious, the app is built with TypeScript, Preact, on top Firebase platform.


How does editing work given Twitter doesn't support editing tweets?

Looking at the demo (https://twitter.com/chirrapp/status/1282608419321643009) I think it removes the tweet you edited AND any later tweet in the same thread, and republishes those - the first with updated text, and the rest with the same content as before. Is that right?


Yes, you got it right!

I'm also working on adding a delayed publishing like in GMail, so you can edit typos even before the thread got published.


Have you considered adding a very short link into each tweet (or into the first/second tweet), whose contents (as a Twitter card) could be later updated to provide corrections?


I didn't. It sounds like a fun idea but not sure if the content consumers would understand it, and also Twitter caches the card content (not sure for how long though), so it might just not work.


So it does lose the likes and retweets of the tweets after the edited tweet?


Good point, thank you!


Right! But I'm afraid I can't fix that. When I receive an email, I associate it with the address that GMail reports to me,, and when you sign in as something+something@gmail.com, the email address differs (as you might already guess). I know that I can safely remove +something but I can't be sure that it will work the same for every email service and ensure security. Please use something@gmail.com, I won't send you anything unless you explicitly ask for it.


Sorry, there are no settings for that yet. Please mail me to koss@nocorp.me, and I'll do it for you.


Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: