Good idea!

Oh yeah, I added a few hotkeys too, forgot to mention that! You can find them documented on the hotkey help page.

Woo! :D Thanks!

Hey, just wanted to let you know this should be fixed now!

There are a few moving parts here: instances have a list of all languages it knows about, admins can restrict what can be used on the site (“discussion languages”), and communities can further restrict what languages they allow (if no mods speak Swedish, no use allowing it because you can’t moderate it), and on top of that you can select which languages you use in Lemmy’s settings. Alexandrite now respects all these settings/restrictions.

Some communities only allow posting in “Undetermined”, and Alexandrite defaults to selecting “English”, so if it was in one of those communities that’s why you were having issues. Should be good now though.

I didn’t see anything about it, but I wish they would change how typing a message works. When my keyboard is open it’s so big it covers the chat and I can’t see the message I’m typing so I just have to hope I’m typing what I think I am.

I think this UI looks neat, totally room out there for both of them! :) I think it actually looks a bit closer to Photon. I’m always down for more apps because we all benefit from new ideas.

Some communities can restrict which languages you’re allowed to post in, and I haven’t yet made Alexandrite respect that list, I imagine that’s what you’re running into. Fixing this is on my todo list!

I’m planning on adding alternate post styles in the (hopefully near) future. A more compact style is one of the styles I want to add.

There’s an option in the settings that makes the left sidebar not auto-hide if you just want to always be able to see them.

I assume there’s an API to allow individuals to develop their own front end if they wanted? Is there any documentation to this end?

Yes there’s an API (docs here), but the docs are little more than type definitions right now so it takes a bit of digging to figure out what you’re meant to do. You can look through all the methods on the LemmyHttp section of the docs, and watch the network tab in your browser’s dev tools to figure out which APIs are called.

Did you sign in on there? The login session on lemmy.world and a.lemmy.world isn’t shared, so you’ll need to login on a.lemmy.world to post/comment on there.

Thanks! :)

I do definitely want to make it work on mobile at some point! It’ll probably be a while though.

Yep, I’m actually working on making those changes now.

There’s a slider in the settings for the hue used for all the background/borders/text etc, so you can change it from purple to other colors, like:

Eventually I plan on adding more customization so you can change the colors of links/votes, and I need to make a light theme because so many people want that too.

(dev here) Sorry! The post forgot to mention Alexandrite is meant to be a alternate UI for desktop. There are a lot of issues if you try using it on mobile at the moment, because I haven’t done the work to support it yet. I would keep using whatever you’ve been using on mobile.

Another random reply to an old comment! I’ve got a branch out for self hosting Alexandrite if you happened to be interested in trying it out at all, more info on this post.

(dev here) I had an idea for how I’d build a profile switcher recently, it’s something I want to implement soon.

Thanks!

See my other comment about self hosting, as it’s probably not super easy right now.

The site uses Sveltekit and so far every interaction with Lemmy happens server side, so it’s probably not as easy to host as WefWef. I got partway through implementing image uploading yesterday until I hit a bug (fix just got merged today!) that prevented that, but image uploading is going to happen client side so it doesn’t cause extra server load.

Thanks!

The username/password are just used once to login and get an auth token and that auth token is stored in a cookie. The username is also stored in a cookie, but the password is not. Here’s the login code

Yes you can! However the production version currently uses Sveltekit’s adapter-auto which just runs on various cloud platforms, so it might not be that easy to self host without changes. You can run the dev version of the site by cloning it, running npm install and npm run dev and viewing it at http://localhost:5173/ but that won’t be as optimized so your page load would be slower.

If you want to self host, would a docker image make it easier?