How about a way to request the bot to create a post if it stopped (e.g. due to no one participating in previous episodes)? It would both lower the barrier of entry for people who want to talk about an episode and keep the post format consistent.
I'm surprised that she found a real chest for once!
Somehow the same content become appropriate just because some people know how to download an app.
Still somewhat annoyed that there is no seat belt on the shuttle, even if it is to maintain continuity with TOS. M'Benga looked like he was going to bang his head and get a concussion when they were landing.
La'an: They won't see us coming.
Zac: We totally saw you from the other side of the planet a hemisphere away.
What was Zac trying to accomplish? He lured them there with the Starfleet Delta, but he was not going to hitch a ride home. He expected whatever ship that comes to inspect to... forget and go away, or suffer some disastrous result when the crew become unable to function? Why not just stay low and be king if he wasn't planning to leave?
Currently there are (is?) content-only servers like https://lemmit.online/ .
I have been thinking perhaps the idea can be carried further and we can separate the user-facing front end and the back end.
Imagine having multiple front end servers (e.g. fe1.site, fe2.site, ... fe5.site) all connecting to the same user database and the same back end server which serves the communities and contents etc (call it be.site for example). A user signs up once and can login to any front end server with the same account, create a community /c/whatever on e.g. fe3 and it will be accessible automatically on fe1-fe5.
This is in addition to the back end federating with outside servers. Outside sees the community as be.site/c/whatever and users there as be.site/u/whoever. (or maybe make an alias like www.site/c/whatever www.site/u/whoever).
Additional front end servers can be added to spread the load if there are many users. If done right the users shouldn't even need to choose (or be aware of) which front end server they log on to, it can be automatically load-balanced. Another idea would be that special front end servers can be created to only serve API calls for apps.
I'm not sure if this will have bottleneck somewhere else, but I think this is an interesting idea to explore.
It does not make sense to me why the API charge have to be calculated by total traffic of all users of an app either. I've decided to think it is just an excuse to get rid of third party apps until convinced otherwise.
So Putin thinking Zelensky would flee Ukraine at the first sign of trouble when he invaded is just self-projection?
Also, mouseover is not an easily doable action on mobile / touch-based interfaces.
This is the right approach. Create the mascot with some uniquely identifying features (looks, shape, color scheme etc) first and then make a logo / icon out of it. The OP is a generic looking white parrot head on a purple background. Better to make the mascot purple to fit the purple folder logo.
Please take good care Ernest.