@Depoetic Getting there. At the point where I just need to tidy a few things up, then it will be a soft launch without open sign up (so invitation only) for a while just to iron out any bugs.
In a shock to everyone, including and especially myself, I made good progress on getting things moving again.
Please cross your fingers the momentum continues.
So, yeah, completely missed my (self-imposed) deadline for new version. Real Job™ was very hectic the last month.
Resolved to get time over the next couple of weeks to get on top of this.
@sukoshi_kaze Eventually. The focus right now is getting the new version up and running, then working out the best option to host the several hundred gigabytes that is legacy posts.
Currently looking for a regularly updated list of AI scraper bots to disallow in the robots.txt file, because that’s a thing we have to worry about now, while also trying not to block useful bots 🙃
For the avoidance of doubt, the “new” TwitLonger isn't some company that takes over abandoned apps and “relaunches” them to suck up personal data for advertising and AI training. It's still just the same single person, doing this as a (sometimes) fun side project.
Quick update on where development of new TwitLonger is on my local development system:
✅ Create new account
✅ Sign in
✅ Sign out
✅ Update account details
✅ Create a new post
✅ View public posts
✅ View legacy public posts
And still to be done…
🚫View your post history
🚫 Add additional passkeys
🚫 Account recovery
🚫 Account deletion
🚫 Post deletion
🚫 Security hardening
🚫 Beta server deployment
At that point of development where the hard bits are done, and it’s mostly filling out the functionality and polishing the roughest edges.
Of course, the deployment and dealing with servers bit still has to come 🤢
@BorisRobloxian By all means do for your own peace of mind, but the very first thing I built for the new version was making sure old posts will still be available at their original URLs.