If it works like blocking works for users/communities, posts from blocked instances shouldn’t show up in Alexandrite too.

Yep, this is a bug I’m aware of, for what it’s worth there’s also an issue on Github someone reported this in. You can track it here.

Yep, I would like to do that at some point, just haven’t been working on Alexandrite all that much lately, but it’s still on my todo list!

Ooo I like that idea!

Actually it sounds like it might be possible to keep things backwards compatible so I'll attempt to make it work for both versions. The 0.19 announcement post mentions it should be possible to stay backwards compatible.

Oops forgot to post links, I edited the post.

I host Alexandrite at https://alexandrite.app/ and several instances also host Alexandrite on their own domains, like https://a.lemmy.world

This is intentional, but I'll probably be changing it.

When you click a post while in a feed it changes the URL so it's easier for people to share links to posts, as people probably are most used to copying a URL out of the address bar to send to people. It causes a lot of issues though, like the one you mentioned, and the 'back' button on your browser basically doesn't work either. Because of all of that I'm probably going to remove that feature, and make a more prominent "share" button somewhere.

I'll probably end up waiting until one of the popular instances migrates to 0.19, then I'll quickly work on migrating to 0.19 and release a new version. The main alexandrite.app site will use the 0.19 version once lemmy.world updates, because that's its default instance. Exact specifics might change depending on how the rollout goes and how much free time I have around then, so this might change. If Alexandrite updates before your server updates you might just have to use the default UI until your instance updates.

For self-hosters who want to wait on 0.19, Alexandrite's releases have version numbers nowdays so instead of using the latest docker tag, I'd recommend using the last non-0.19 version until you upgrade Lemmy.

There is a lemmy setting to hide read posts fwiw, but it’s probably not exactly what you’re looking for. I’ve been thinking of making a toggle for it more accessible from the feed, but a lemmy feature to hide individual posts like you could on reddit would be nicest.

I’ve been considering something similar to that too, I’ll give it some more thought. Might end up switching those textboxes around. Also when I someday am able to add image uploading I might need to move things around anyway so anything here could change lol

Sweet, thanks for letting me know! This is definitely the kind of bug I like getting fixed ASAP!

Could you give me a little more detail on what problem this solves for you? I’m not opposed to the idea, just want to understand more. What’s inconvenient about the way it works now, and how would you use the site differently if this feature was added?

I went back and forth on this and I’m not sure what’s best. I think I’d prefer doing it automatically, but I also didn’t want stuff on the page to move unexpectedly, because it’s really annoying when you’re trying to click somewhere but miss because stuff moved around. That’s why it only does things when you click.

Also, on the post creation form on Alexandrite I put the “Title” input first, but the official UI has the URL first, which maybe makes it simpler to create a UI to offer these extra options (and the archive links), so maybe I’d need to reorder them and think about stuff a bit more?

If you have any ideas for some other place to put the link’s title and the “use this title” button I’m all ears!

Just to confirm, the issue you’re reporting is that NSFW images in the post list when using Cards are unblurred? I just released a fix for that, so let me know if you were having any other issues.

I totally meant for those to be blurred in the first place, but had run into issues during development and apparently forgot to go back and fix it, so no new setting either!

Oh sorry, I will look into it!

I just put in a change which:

• when you enable that option in the settings, it will open the sidebar right away (or close it if you turn it off)
• if that option is set, on page load it’ll start with it open.

The monkey wrench in this whole thing is that the option doesn’t exactly do what it sounds like. It toggles between two different styles for the sidebar, one (the default) which shows the sidebar as an overlay that closes when you click outside of it or navigate, and the second being a sidebar that actually takes up space in the page as basically another column and doesn’t care if you click on anything.

I could make it just remember if it was open last too, that’s totally doable, but I feel like automatically starting with it open is probably just as good.

Btw, I also just made links in markdown that link to external sites open in new tabs.

sidebar to stay open after refresh

If I made it start open if you have the “Keep navigation sidebar open” when you load the page would that be what you want, or should it actually remember if it was last open or closed?

Thanks!

I generally prefer things to be on Github. I don’t get notifications when people make new posts on here so I just have to check it regularly, but if you make an issue on Github I get an email about it, and it’s easier to track.

If you have a bunch of ideas, it’d be nice if you separated them out into separate Github issues, so I can close the ones I’ve finished if I decide to take on the work!

Thanks for asking!

Lemmy doesn’t have that strong of a “concept” of cross posts. The way it appears to work is that all posts linking to the same URL are all considered cross-posts of each other, so I bet the cross posts Lemmy’s API gives are basically just search results for that URL. When making a cross post there’s nothing that I’m doing to identify that it’s a cross post, but it knows.

I’m not sure what’d be best. Backend would maybe be the least taxing, but at any rate the amount of work to be done to gather all the comments goes up as the number of cross-posts increeases, so 8 cross posts means you have to request 8 times the number of comment lists.

Maybe a good middle ground could be a menu that shows you a bit more of the cross post (because you can completely change the post body for example, or just link to the same thing on a brand new post) and let you select which post’s comments you’d like to see.