Comment on posts blackholed on the onion instance
Sal@mander.xyz 4 weeks ago
Thanks for pointing this out… I am very sorry that this happened. I have not tested the .onion front-end much.
Sorry for missing this post, I was traveling during holidays last month.
The server that is serving the .onion front-end is running only that service, and so I doubt it is ever under heavy load. I am not sure if this was a problem with the onion network itself, with the front-end, or the instance. When I looked into options I could not find examples of Lemmy instances using .onion front-ends and I picked the one I did because it does not require JavaScript.
I will make an effort to use the .onion site myself more often and I will look for other options.
plantteacher@mander.xyz 4 weeks ago
One problem with all Lemmy instances running later version than 0.19.3 is the front-ends are broken with Ungoogled Chromium. Lemmy instances running 0.19.5 essentially force me to use Tor Browser (firefox). This is unrelated to the onion problem but one of my other workarounds is to use a non-stock front-end with ungoogled chromium. So for example slrpnk.net has alexandrite.slrpnk.net, which is an alternative FE. The landing page of slrpnk.net lists a few other alternative front ends as well.
I don’t know if there is a way for users to run alexandrite and then specify another backend of choice. But if not, it could be useful to make other front-ends available on the onion.