Thanks to @WeirdWriter for sharing Zocial, a modern Enafore fork. #accessibility remains good, and I was able to set it up for my local instance with two commands and five minutes. Much easier than Enafore. git.ztfr.eu/Dome/Zocial
@fastfinge Only thing I'd say so far, which might not even be specific to zocial, is that I liked when I could make FastSM collapse reply threads, especially my own replies, from the home timeline. This convo is showing up fully on it but not on FastSM except for that one post about its deployment for some reason. @WeirdWriter
@fastfinge Well damn. Will have to wait until the cave deploys then probably. I'm not throwing docker on my tiny server just for this when I haven't a clue how to route/use it.
@x0 Oh, interesting. He's running his own infra (git, etc) so I assumed that meant he was more experienced than average. Most vibecoders just use github.
@fastfinge I just logged in with my akkoma-account. Can't see much of a difference to Pinafore or Enafore, though.
E.g. "On mobile, @handles are hidden to let display names breathe." Doesn't seem to work, do I have to activate a setting? Screenshot with an example, where on mobile handles are written.
The same goes for "automatically-collapsed threads, doesn't work either.
@fasnix@WeirdWriter I have no idea how Synology works, sorry. But you have to have the env files set correctly, and you have to store the docker-compose in the docker directory of the repo you cloned. Otherwise it can't find locales and things correctly.
@fasnix@WeirdWriter The dude is actively committing code it looks like. And has no staging environment; just deploy to production. And the docker and public deploy are wildly out of sync. Not just "one is newer". They have different features entirely! So...yeah. I'm hoping these are just "new project weirdness" rather than a sign of bigger problems.
@fastfinge CC @admin Looks like a modern fork of enafore actually optimized for glitch as well, if you guys still deploy your own URLs to accessible web clients give this one a look.
@x0@admin I'd say this isn't ready for public use, yet. Still actively under development. The public instance and the dockerized version are wildly out of sync. Worth watching, but still needs to finish cooking.
