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.

It looks like Lemmy itself is not fully translated into your language yet:

https://weblate.join-lemmy.org/projects/lemmy/lemmy/pt_BR/

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.

How does the json for a batched vote activity look like?

Working on Lemmy, instead of selling my soul to a company.

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

Good job! I wonder why some of these are missing from fediverse.observer. There is an add instance page, and entering for example aussie.zone says it already exists, but the search doesnt find it. Lemmy.cafe, fosscad.io are included in the statistics (file instances/full.json.gz in the git repo), but not currently shown on the website.

Thanks to your comment I realized that we are only showing instances with registration application on the official site, as there was concern that others would be overrun by spam bots. I had a look at it now, and instances with captcha are actually fine. Here you can see all that are newly listed on joinlemmy.

The instance list is sorted by monthly active users with slight randomization. As these instances you mention are among the larger ones, it is expected that they show near the top. Is there a better sort method that you would suggest?

Follow these steps:

• Use the nightly Docker image for Lemmy and lemmy-ui
• Setup postgres, pictrs and nginx according to the usual 0.19 instructions
• Specify plugins in Lemmy config (docs, example)
• You need to specify the hash for each wasm file (check logfile for error message), or set DANGER_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:

• Full-page layout while lemmy-ui is more centered
• Posts open in overlay
• Comment search, neat!
• Card view (you can also try that on our test instance with Lemmy)
• Anything else?

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!

Yes there is something strange going on, because blocked instances shouldnt be in the linked list.

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.

The instance is blocked, I suppose thats why the link is rendered wrong. Why it was blocked I dont know.

Good idea, I just implemented this.

https://github.com/LemmyNet/lemmy-ui/pull/3846

You’re in luck, I just modified the instance crawler on join-lemmy.org to collect statistics for all Lemmy instances. You can find them in this repo in JSON format. Now we need someone to build a tool that can visualize it. The stats could even be shown directly on join-lemmy.org.

Lemmy also has an admin setting like that. Additionally there will be private, federated communities available in version 1.0.

I made a couple of “Help Design Lemmy” posts in [email protected] recently to get feedback and ideas, which was very helpful. I will continue to make such posts to improve join-lemmy.org, and also Lemmy itself.

Had a look at the Piefed signup now, choosing categories like that is a good idea. But the question is how these categories get curated. We have something similar with the instance topics on join-lemmy.org but no one is really helping to maintain them. So for community categories it would probably similar. In 1.0 we will have some improvements for discovery, like multi-communities and a “suggested communities” collection which can be set by local admins.

For the Mastodon recommendation there isnt any good alternative software that I can see. So its probably best to recommend a single Mastodon instance, depending on the target audience.

Not everyone likes infinite scroll, but some apps such as vger.app offer it.