While I internally debate on the 20 million names we could assign to this new front end. Let’s lay out what you can expect from this initial release and what it means for the older TTI front end for GPT and NAI. First things first: Your old webpages are going NOWHERE! This means that through the release of this front end the play pages for GPT and NAI will remain as they are. There’s no need to migrate anywhere you don’t want to. So, you might be asking why we’d choose to do this.<\/p>\n\n\n\n
Over the last year the framework from which we’ve built TTI on has steadily been slipping into decay, and while I am so very grateful for the start it gave us, it’s important to recognize when things no longer server the purpose they once did. AI and roleplying has a lot of current demands our front end is not currently meeting. But we’re going to change that very soon.<\/p>\n\n\n\n
So while we’re building, let me temper some expectations for our initial alpha release:<\/p>\n\n\n\n
Things this new front end needs (Remember, these things already functionality exist and now just need to be translated for this new system):<\/p>\n\n\n\n
While I internally debate on the 20 million names we could assign to this new front end. Let’s lay out what you can expect from this initial release and what it means for the older TTI front end for GPT and NAI. First things first: Your old webpages are going NOWHERE! This means that through […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1979","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"yoast_head":"\n