(dev here) I hadn't really considered it as a full replacement before, but hosting it alongside the instance like a desktop version of m.lemmy.world is something I think would be neat (at least one instance is doing that, with a custom Dockerfile because I haven't made one yet). I'd need to add some mobile support (which I'm not against doing in the future) and some admin tools probably before it could be a full replacement, both would probably not be for a bit still because I'm still working on feature parity for normal users. Also still waiting on a Lemmy issue to be fixed before I can add image uploading which is the most basic feature the site lacks at the moment.
Wefwef/voyager works well as a mobile interface. It only has an iOS style interface now, but it’s really good, and they’re working on an Android skin if that’s a dealbreaker
This is something I'd really love to see, as well. While I'd say that the default UI on Lemmy is "functional", in that it gets the job done...I would love if the backend could support alternative bundled frontends. This is something that Pleroma supports, and it's a great feature. It's something I wish more Fediverse software could officially support.
You know what's funny? I would never use something like this (my own Lemmy client is absolutely terrible in comparison!).
But I'm so happy that Alexandrite exists: it's proof that programming and web development can still be experimental and loads of fun. Congrats to the developers!
Honestly, I think this is the real selling point of the fediverse, at least for developers. There's no incentive to force people to use Official Mobile Clients™. You can literally spin up something (meaning a fediverse server) locally, if you want, and test against that until you have something that works. And as long as you stick to the API, you can build whatever you want.
Yes - well, almost! I made a read-only filesystem interface to Lemmy then wrote a small program for one of the Plan 9 text editors/programming environments to access it.
The real thing would be to serve that filesystem interface over the Plan 9 file protocol (9P).
Not quite there yet!
This is really good feedback. I wonder what that would take? 🤔 Is this something where the app needs to be updated with some property, or does this need to be fixed on HoverZoom+'s side?
I use Imagus and it doesn't work well with Alexandrite, I was trying to find some documentation on if I could support Imagus from the website side somehow, like attributes to provide non-thumbnail image URL hints but I hadn't found documentation yet.
I've been meaning to try building something similar into Alexandrite at some point otherwise.
I don't know, I know it works in a lot of places automatically, but I'm not sure how it works. Maybe if the thumbnail has some sort of pointer to the real image?
As good as wefwef/Voyager is (particularly in helping to transition from using Apollo to access Reddit), it kinda falls apart on a desktop browser because it's built around swipe gestures, and lives squarely in the middle of the screen. So Alexandrite for desktop, Voyager for mobile seems pretty sound.