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).
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.
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.
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.
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 [email protected], 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 [email protected], I won't send you anything unless you explicitly ask for it.
My goal wasn't to create a 100% secure diary. If you need that, you probably should not store your data in the cloud. That's unlikely that I will ever try to make it happen. But even if I would, there're so many ways to screw it over anyway, so I won't ever try to make this promise.
> But once the data leaves the browser there is no way to know, wouldn't you consider to partner with Gmail(or others) and appear as an addon to an already trusted company in order to start off the business ?
Also, I understand the concern and that Paul most likely will not trust their secrets to anyone. The problem is that's not a business, but a beautiful hobby project that I honestly love, so it's unlikely that I will ever spend time rewriting it and then paying Google $15K (https://www.gmass.co/blog/google-oauth-verification-security...) so they could vet me.