

Found it now, crosspost detection actually happens in the frontend. It only works if posts have the same url and are shown on the same page.
Opened an issue, but it will likely take a while to fix.
Lemmy Lead Developer and father of two children.
I also develop Ibis, a federated wiki.


Found it now, crosspost detection actually happens in the frontend. It only works if posts have the same url and are shown on the same page.
Opened an issue, but it will likely take a while to fix.


So the problem only occurs after you use “Hide Post”? That might be part of the problem, I suppose that deduplication only considers posts that are visible to you. Though I cant find the corressponding code right now to confirm it. Best if you open an issue in the lemmy repo.


Yes I don’t doubt that you were having this problem, another post was also complaining about it a few days ago. It’s just that I cant think of any reason why this would happen if the image urls are identical.


Here are the posts on lemmy.ca, they both have the same image url and are also shown as crossposts:
So these should be grouped together without any problem, not sure why it would fail.


Yes but apparently its not working for some reason. My first guess is that these posts have identical looking images, but they are actually loaded from different urls.


I cant find these duplicate posts, can you share the URLs that you were viewing? Is it possible that these identical images actually have different URLs?


No problem, this is my job after all. And I got lucky to end up with a job like this :)


Thanks for letting me know! I made a fix, it should be deployed within half an hour.


Im not a designer, so for me its very difficult to make such changes. I prefer making a small adjustment rather than messing the whole thing up.


Thanks for your feedback! I made the theme colors a bit darker, what do you think? https://github.com/LemmyNet/joinlemmy-site/pull/597
Now that you mention it, I also notice the problem with scroll performance, hard to say what might cause it.


Its a difficult decision to send people to the homepage or the registration page. Homepage makes sense to explore like you say, but then someone might not find the registration button or dislike the frontpage posts and close the page. Registration page makes sense because with an account you can actually start voting, posting and following so you get the full experience. Its also what joinmastodon.org or pixelfed.org do.
I can see how that warning is a turnoff, but the registration approval is necessary to prevent spam bots. And its better to make users aware of that than having them think something is broken. In 1.0 there will be estimated approval time shown, and it will also be possible to use a plugin for automatic approval based on keywords.


No you cannot post to a multi-community, they are only for browsing/viewing.


Follow these steps:
nightly Docker image for Lemmy and lemmy-uiDANGER_PLUGIN_SKIP_HASH_CHECK (not merged yet, part of the PR above)Let me know if this works, then I will add it to the documentation. Or better yet, make a PR yourself ;)
Edit: Config from the test server:
plugins: [{
file: "https://github.com/LemmyNet/lemmy-plugins/releases/download/0.1.3/rust_lingua.wasm",
hash: "e1f58029f2ecca5127a4584609494120683b691fc63a543979ea071f32cf690f",
allowed_hosts: ["0.0.0.0"]
}]


There is also enterprise.lemmy.ml which runs the stable version. And ds9.lemmy.ml but that is currently not active.


What exactly do you like about Alexandrite compared to the default? From what I can see:


And private communities. As mod you need to approve every follower manually. Others cannot see any posts/comments in the community.


Completely agree about this, we are currently discussing it. One possible solution would be a label for the dropdown.
We need to make some uncommon buttons (eg. show hidden posts) more hidden in the UI. While others such as switching sort type and feed type should be very prominent. So that a new user can figure out intuitively how to find good content. If any of you know about design and UX, please tell us your suggestions!


We already have server location based on the IP shown on join-lemmy.org, and this can also be used for filtering. There are a few ideas to improve it further, most importantly Regional Instances for Quick Join.


Good point, I renamed it to “hosted in” and also added a filter by continent ath the same time (https://github.com/LemmyNet/joinlemmy-site/pull/567). Translations are contributed by people like you via Weblate, contributions welcome!
Multiple language selection would be both complicated to implement and also complicated to use. Not even joinmastodon.org has it. I would simply select the language which is less common, for French there is only a single instance.
That was a fun achievement, and not really that difficult. Only way you could fail was if you forgot the gnome somewhere.