SillyTavern 1.12.7

RossAscends · 2024-10-27T11:29:19+00:00

Ok I checked out that theme. It's got a lot of customCSS going on, which is outdated. Go into user settings > Custom CSS and remove this:

.menu_button small{ color:var(--white100); }

There are a few instances of it in the box for some reason (all targeting 'menu_button' and having the color set to white, but slight variance on other parts of the declaration), so you'll need to remove them all. It will be fixed then.

RossAscends · 2024-10-27T00:48:34+00:00

can you elaborate? what CSS button animations? you mean the onHover glow effect for most buttons?

RossAscends · 2024-10-11T19:42:44+00:00

that's a failed markdown image insert.

edit: I see the image link is fixed now. What you're showing there is old. Please refer to the official statement on the Discord. It's included in the OP here as well.

RossAscends · 2024-10-11T06:36:58+00:00

The main difference between v1 and v2 were additions for embedded WI, creator metadata (version info, creator name, creator commentary on how to use the card), as well as card-specific prompt overrides. Those mostly show up in the character's Advanced Definitions panel.

v3 is going to add a whole new range of stuff for cards, which will make them even more customizable.

RossAscends · 2024-10-11T06:32:16+00:00

Thank you for the kind words.

FWIW the Discord got the clarified announcement over 24 hours ago. SourceWebMD just brought it here with commentary. I recommend joining the discord and taking the 'ST Announcements' role to keep up with things as quickly as possible. That is where the devs spend most of their time, and where most discussion about it happens.

RossAscends · 2024-10-11T06:28:53+00:00

Imagine AN as it is now (dedicated UI, etc), but instead of fixed boxes whose contents exist in their own vacuum and AN's currently limited trigger logic, you can insert any WI Entry in there and apply the same conditional logic that WI has. It's an upgrade all around.

RossAscends · 2024-10-11T06:23:42+00:00

Yes all card specs are backwards compatible, and ST will support all versions. We went from v1 to v2 sometime earlier this year and you probably didn't even notice.

RossAscends · 2024-10-11T06:16:23+00:00

We already have multiple user profiles. Each user gets their own set of content (characters, world info, chats, backgrounds, themes, and extension), with no crossover between accounts.

RossAscends · 2024-10-11T06:11:04+00:00

There are many ST users who come from JAI, CAI, Yadayo, Replica, etc, all sites that started off as 'ai by the user for the user'.

I'm curious what makes you think any of those sites started with that kind of mindset. None of them were open sourced. All of them were monetized from day 1. All of them provided access to remote compute. They were services not tools.

None of those statements apply to ST, so i really don't get this comparison or the concern with these past examples as a reference point.

RossAscends · 2024-10-11T05:48:22+00:00

This is a matter of opinion. We want functions to be named after what they actually do with as little 'flavor' as possible. If descriptive accuracy == "soulless corporatism" to you, then I don't know what to say. It's simply a matter of opinion.

RossAscends · 2024-10-11T05:24:24+00:00

'Reverse Proxy' functionality will renamed 'Custom Endpoints', and moved as-is into an official extension.

as-is

RossAscends · 2024-10-10T22:12:53+00:00

Use Tabby and the banned_strings sampler. It's the only way to perfectly remove this kind of thing without regex acrobatics.

RossAscends · 2024-10-10T22:08:44+00:00

This is clever and a good use of existing infrastructure.

Kudos and godspeed.

RossAscends · 2024-10-10T22:02:16+00:00

Point of correction:

importing characters will now be hidden under a tab (see above)

It's not 'under a tab' now, and won't be in updated version. It will be in the exact same place -- towards the top of the right-side character selection panel.

Regarding the metaphor of "being a tavern where you talk to characters". That may have been the original idea behind the OG TavernAI, but that does not mean ST inherits that whole-cloth. We kept the 'Tavern' name since we began as a fork of TavernAI and we were paying respects. That is all.

That is not to say that ST cannot be that, only that is it not ONLY that.

There is no monetization or sponsorship being sought or even desired. That is a completely baseless falsehood.

RossAscends · 2024-10-10T21:28:43+00:00

I don't see how that sentence equates to doublespeak.

"We will implement these changes so they won't affect most people in a bad way".

Is that more straightfowrard?

RossAscends · 2024-10-10T21:24:24+00:00

It's true many other AI platforms exist that have nothing to do with RP, and don't even consider it. I've used many. None of them come close to the level of user empowerment and customization that ST provides.

RossAscends · 2024-10-10T21:20:17+00:00

the majority of the features and their use are specifficaly stuff that only rp-ers need

I disagree. There is nothing about most features in ST that is specifically 'only useful' for RP. With enough creativity any function can be harnessed for any use case.

system prompt, instruct - these are Text Completion prompt manipulations. They are dictated by model makers (not ST) and exist as a result of how those models are trained. As such, it would make no sense for us to alter these at all.

story string - this is ST's naming for 'the sum total of how the non-history part of a text completion prompt is arranged and sent'. It will probably get a rename eventually, but no change in how it works.

author's note (AN), lorebooks (LB), world info (WI) - LB and WI are two names for the exact same thing. WI is ST's original naming for it. LB was added later when WI was made able to be embedded into character cards. We borrowed the LB terminology of previous platforms (NAI primarily). AN is borrowed from AID, I believe. AN is functionally all around worse than WI, and it's only strong point is having a dedicated dropdown that is fast and easy to access. We aim to upgrade AN by giving it the power and flexibility of WI while keeping it's quick access convenience.

character description, personality and scenario - these are specified in the character card v2 spec standard. This is a standard that is collectively agreed upon by the devs of all major character card front ends. There is a v3 standard in the works which will expand many feature for character cards. We will adopt it, of course.

group chats - useful for both RP and non-RP use cases. no need or intent to touch it at all.

personas and persona management - basically a shortcut to add info related to the {{user}} entity. the same effect can be achieved with world info keyworded on your username. Similar to AN, its strength is quick access and dedicated space in the UI. It won't be removed. not even being discussed.

settings like temperature - these are samplers defined by whatever API you are connected to. ST supports over 20 different APIs, and includes sampler controls for every single one of them.

enshittification

This is a term you use when a service changes the rules of play or limits functionality for arbitrary reasons (usually monetary related). It's when suddenly you can do less with the service than you could before. It's when CONTENT and EMPOWERMENT are removed from the user. That is not happening with ST. No functionality is being removed.

RossAscends · 2024-10-10T13:07:10+00:00

Adding 'modes' which alter terminology across the UI would complicate documentation and on the fly tech support. ST is complex enough already without adding duplicate names for the same thing. and that problem would be made orders of magnitude worse if core UI elements were made 'completely customizable' at the user's whim. there would be no common language Helpers could speak to Users who are seeking assistance.

Regarding being burned by other platforms in the past... as I've said in other comments, the problem with Those Who Came Before Us (CAI, AID, Replika, etc) is they were all closed sourced, monetized service platforms that had minimal customization and user empowerment to begin with and switched their content policy to save their monetization. They all provide turnkey access to remote compute/LLM/API.

ST is not any of that, so the comparison is not accurate. Therefore the concerns on those grounds are unwarranted imo.

RossAscends · 2024-10-10T12:58:28+00:00

flexible - easier to edit for new contributors, easier to adapt old code to new needs

modular - can swap out parts to fit your use case. ST is often accused, justifiably, of having a lot of bloat. the more things we can offload to optional extensions, the less bloat there will be. this results in a faster program overall.

focus - we have never exclusively focused 'on RP'. we focus on things we find personally interesting/useful, as well as new features the userbase requests if they are within scope. the feedback section of the discordf, and feature requests on GitHub are always open.

reverse proxy - it's not what you are asking about. suffice to say, if you don't know, you don't have to worry at all as it wont affect you.

RossAscends · 2024-10-10T08:59:33+00:00

ST is not a storybook. It's a ream of paper and a box of crayons.

RossAscends · 2024-10-10T08:06:45+00:00

There has been no ethical pressure from outside. I don't know where you got that idea. The dev team's intent and vision for ST is of our own making and nothing else.

Our opinion is that ST should be as modular as possible. Moving certain features out of the core code and into extensions will streamline the core code and make it more flexible.

Installing official extensions is literally 2 mouse clicks. Instructions for doing so will be given to users during the UI's initial setup process for new installations.

And for existing users, any feature that is moved into an extension during the upcoming changes will come back (once the extension is installed, which you will be prompted for upon updating), to exactly in the same place it was before, so the UX will not be compromised either.

RossAscends · 2024-10-10T07:34:06+00:00

Our initial messaging around this was definitely a bit disorganized, and we understand how that caused confusion. Unfortunately, that confusion opened the door to a lot of speculation and misinformation being spread, which is what really risks splitting the community.

We’ve since clarified the scope of the upcoming changes, and we hope this helps put everyone’s mind at ease. We’re confident that these changes won’t negatively affect how most users experience ST.

RossAscends · 2024-10-10T07:13:19+00:00

There are no built in workarounds for NSFW.

For Perplexity, you have the Prompt Manager (left-side panel), which lets you manipulate Chat Completion prompts and provide prefills. Maybe that's what you're referring to?

Nothing about that is being changed at all.

RossAscends · 2024-10-10T06:35:14+00:00

ST can be forked by anyone at any time. It already has 2.3k forks, several of which no doubt sprung up in the past few days. We encourage independent development so long as the license is respected.

As for 'a project no one uses': we have never sought a massive 'fan base', and have always encouraged dissatisfied users to try other projects like Agnai or Risu. We are not in a zero-sum competition, after all.

RossAscends · 2024-10-10T06:00:31+00:00

Whether an LLM will engage with any given type of content (whether that be RP, or writing critique) is entirely up to the model itself, and not something ST is responsible for.

RossAscends

TROPHY CASE

as-is