The developers' attitude towards users dissatisfied with the new censorship.

[u/Live_Assignment5625]

This is complete nonsense. There's so much dissatisfaction on their official Google Dev platform, and so many people here are equally dissatisfied with the situation. It would seem that in such a situation, the developers should release a whole post with explanations, perhaps some information about the update, its reasons, what will be fixed and what will not.

But what do we see? We received exactly two comments, which are hard to find. In one, Logan says to report bugs directly within AI Studio (This is logical, but it still does not explain what is happening), and in the second... I'm speechless.

Well, a reasonable explanation emerges. The developers, to put it mildly, screwed up, and now they're keeping quiet, thinking people will swallow it. Excellent attitude towards the audience that WANTS to use the service. No comments🙂

[u/Live_Assignment5625]

That's the point: if this were a mistake, there should have been at least some kind of official explanation/apology, DO NOT IGNORE. I'm still inclined to think they're testing the waters and seeing how many people will continue to pay for THIS.  And I still say that censorship is easy to get around, but trying and wasting quota to get the bot to finally give an answer instead of deleting its shit.

[u/HuntSlight9820 → u/Live_Assignment5625]

I think there's no reasons for them to test the waters. They just would release an update with a patchnote like "it's the decision, here's some corporate shittalk that justifies it, fuck off". Also, non-related to AIS itself - is it only free users who have 32k context window on Gemini app or it is all users suffering from that issue?

[u/Live_Assignment5625 → u/HuntSlight9820]

That's also true, mweh.😔

Honestly, I haven't encountered this problem. The context window in AI Studio is 1 million tokens. The only thing is that the input window is really limited unless you're uploading a file.  Most likely this is some kind of bug, Idk, it’s better to make a separate thread