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.
I felt slightly frustrated when I tried some Lemmy apps and they only offer a few largest instances in the initial setup and leave people to discover/find smaller instances by themselves.
It is understandable that they don't want to present a thousand choices and confuse people, or get people to sign up for an instance that disappears a week later. Also, larger instances tend to get a snowball effect by receiving more donations / volunteers and scale better, other nodes are also more likely to help them if there are e.g. federation problems.
However this effectively promotes an centralized ecosystem that both depends on and burdens a small number of key instances.
It didn't log me out but when I submit a thread or comment sometimes the "Add comment" button doesn't "catch" the first time and I have to press it again. It gives me anxiety that it's being submitted twice, fortunately so far that has not happened yet.
XFX is good too, no personal experience with Asrock GPU.
Sapphire is a good brand but pcpartpicker tells me that you can save 20-40+ bucks getting an XFX or Asrock 6700xt.
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.
Would there be any benefit to lemmy.world admins running a lemmy2.world and redirecting new users to sign up there? It would spread the load and federation between the two should be easier due to proximity and having the same admins.
Please take good care Ernest.