The higher a barrier to entry the less people you are going to get.

And that’s ok. MOST redditors are lurkers who don’t interact with the platform and/or bot accounts. Nothing good will come to this platform if these accounts move over.

Give the platform 2 minutes to figure out how it works and all is ok. This on its own is a great screening process.

Not that the platform is hard. It’s just different.

people are going to go back to reddit.

Realistically, there is no reddit to go back to. After the company goes public, Reddit as we knew it, will cease to exist.

The shareholders will want to be make maximum profit. This means that ads are going to be everywhere. They are going to outsource hosting services to horrible companies, in order to cut down hosting costs like video hosting and image hosting. Features that existed in 3rd party apps are going to be paid features in the official app/webapp, etc.

Reddit is gone. It’s lost. It will not be there as you knew it to go back to. It’s now a case of where to next and for the time being, lemmy and feddiverse looks the best.

Guys, what are you on about.

It’s very clear that Lemmy is dead on arrival.

Redditors told me so.

Don’t you see it?

/s

You are logging into lemmy ml instance which is at capacity so it’s struggling. I created another account on another instance and now all is fine while previously I couldn’t login either.

edit: as @PriorProject@lemmy.world correctly mentioned, OP asked about the lemmy.click instance which is a mistake on my part. That still doesn’t completely solve the issue as the Reddit exodus is putting a massive strain on all instances as more and more are getting removed from the suggestion list due to being at capacity. This along with the platform being not mature enough is going to cause issues. Best way to resolve these, is to place them in the github issues with descriptions.

Oh, ok, I didn’t know that this was the intended usage of that particular instance. Good to know.

Because lemmy.ml is the official instance meaning it was created by the developers of the people who created the backend for lemmy as well so people assume it would be the correct one to join.

Thankfully fediverse doesn’t work like that and in a few days I expect users to be spread around in instances more evenly.

Not that I know of but here’s 2 lists you might be interested in:

• Github issues, including enhancements for the lemmy backend.
• Github issues, including `enhancements for the lemmy frontend which is the look that all instances use.

The first one shouldn’t be used as a directory. The second one, can be used.

The reason the first one can’t, is because it is just the search directory of one instance. Each instance knows/shows a community only AFTER some user has indexed it manually by putting the full url of that federated community in the search bar and submitted it. Only after this, does lemmy.directory will be able to show it.

Good to have you and looking forward to seeing this ecosystem as a whole grow.

I am now trying to go into the advanced stuff in Nuxt 3 but it I bummed out by its support unfortunately.

Nuxt 3 is waaaay better in terms of Dev Experience than Nuxt 2 but even though it released in Nov 2022 it still lacks official modules like Auth and PWA.

Especially Auth is kind of unacceptable to not exist for a framework build in 2023.

and they don’t show up in the lemmy community browser

Communities are not visible to other instances until some user manually adds them.

If you are on one instance and you have the link for a community of another instance, that does show in the first, just copy the entire url of the unknown community, paste it in the search field of the instance that doesn’t know about it and search for it. It will NOT show up the result, but you can then delete the url and search again by its name. You will see the community now appear because you just indexed it.

I just learned this today, so I am going to spread it wherever possible.