Remember when Twitter was inaccessible and you had to use specific clients to interact with it? pinafore.social is that client for Mastodon at the moment.

@dark@xarxa.cloud @ada It's pretty neat for self-hosting.

@dark@xarxa.cloud @ada Yes, that can make some sense. It's very hard to moderate content you can't understand, and automatic translation can only do so much. Still, I'll need to find some other instance...

@marcozehe It does have a more intimate feel, like a tea shop with quiet conversation rather than a bustling, loud trains station in rush hour. Though I suspect some of it is what each of us makes of it.

@guenther My similar experience is, that with Rust I will dare to do much more aggressive optimisations, or try for lower level things that I'm a little scared to try in other languages because I'm afraid I will mess something up, but the static checks typically keep things correct. People may call it bondage and discipline, but it's more of a security harness that lets you climb to places you wouldn't have, at least for me.

Vaya, esto me pasa por no leer las reglas de la instancia antes de meterme a hacer una cuenta. fosstodon requiere que los toots públicos sean en inglés, así que no me vale.

Alright, going to be using #TweseCake while the situation with #Pinafore remains unresolved. At least it updates.

Buenos días desde la Administración Pública.
Sigo teletrabajando.
Por cierto, Pinafore no me actualiza bien, así que no seguiré Mastodon demasiado de cerca hasta que se corrija el problema. Lo he estado investigando pero no lo consigo arreglar.

Thinking of migrating this account to @modulux@node.isonomia.net which is a #GoToSocial instance. Not sure if that will sort out my #Pinafore woes, but I may as well try it.

@lights_rage I think I'll try downloading it again and see if it sorts it out.

@lights_rage I'm blind so it's not that odd, but for some reason Twesecake isn't working for me today, doesn't start and doesn't leave logs.

Ok, giving up. Maybe it will work another day. Bye.

And, so far, it does not. Sigh.

So, testing out the dev version of Pinafore to see if that solves the problem...

Right, so in short:
1. #Pinafore doesn't update home stream except with my own toots.
2. Browser console gives a websocket error. The response is 301, permanent redirect.
3. Tried with two different Pinafore instances. Firefox 106 and Edge.
4. Tootstream gets to stream the home timeline.

No idea how to fix this or what else to try. Hints?

Ok, doesn't work from here either... Very puzzled.

Ok, testing from Microsoft Edge now.

Ok, I suppose I should try another browser... Ugh, what the fuck...

Frustration level rising...