I am also partial to “lemmings”

Scrolling through the linked instances and noticed Lemmygrad was banned? Is it their politics or are they just annoying or smth.

The lemmy.ml instance federates with lemmygrad.ml, the collection of Marxist communities. It blocks lemmygrad.com, which currently redirects to the forum of choice for President Donald J. Trump. The latter does not seem to be hosted using lemmy and I think could not be federated with in any case? But presumably this was once the domain of a similarly-minded lemmy instance.

Some instances other than lemmy.ml do block lemmygrad.ml. Besides being a place for Marxist communities, the instance is also home to some very radical and very hostile users. I haven’t been around long enough to really know the situation for myself, but I have seen mentions of lemmygrad.ml communities engaging in brigading in the past.

It feels like user accounts need to be abstracted away from instances somehow. Federation means it’s almost meaningless which instance you register with, and as integration between instances and other Fediverse apps gets better it will just become more and more meaningless. It should be possible to just “Join Lemmy” and have the servers behind the scenes handle spreading the load. You should be able to login to Lemmy from Beehaw.org or Lemmy.ml or any other Lemmy instance. The way it works at the moment is kind of like content is global but accounts aren’t and it feels like it should be the other way around?

User accounts can be independent of anyone else’s instance. You just have to host your own.

But it’s always going to be much more convenient to register your account on someone else’s instance, than to set up your own. Even if instance setup was made to be as effortless as possible, and single-user instances were made to be as lightweight as possible, say you download and run a single binary onto your computer that runs a lemmy instance and everything is automatic from there, most people still wouldn’t want to do that.

The idea that you should be able to log in to your account from any instance is…less practical than you might think.

The technical reasons why are hard to boil down into an easy explanation. But the very short version is that everything comes with pros and cons. Doing it this way makes it a little less convenient for users, and a little harder to make a good UX for. Doing it another way could make it more convenient, at the cost of making it very easy for a bad actor to do things like post fake content under another user’s name, or could add inconvenience somewhere else, like making it so that users have to manage a private key instead of or in addition to their username and password.

I do think there’s room for improvement, but I think the overall idea of logging in and interacting with content specifically via the instance you’re registered with is ultimately very unlikely to change.

Does the gmail SMTP server have a limit on how many emails can be sent per day?

I think it does, yes. The kinsta.com link says the limit is 500 per day. If you’re expecting a higher volume than that, or if the unpredictability of relying on a free Google service for anything is not acceptable, then you would probably want to pay for an inbox service.

But if you’re running a small instance and just need the occasional email to go through without a lot of effort or fees, then it ought to be fine.

Currently yes. If you wanted to be in full control of which instances you can see, then you will need to administrate your own instance.

Hopefully this will change in the future!

If email isn’t working, then you’ll have to turn off email verification in your instance’s settings before anyone is able to log in without encountering that spinner.

To get email to work, you’ll need to provide SMTP credentials in lemmy.hjson on the server you’re using to host lemmy. An example SMTP configuration is shown in the docs here: https://join-lemmy.org/docs/en/administration/configuration.html

You may also have to restart lemmy after you update the configuration, in order for it to take effect. (I do this on my server via docker-compose restart.)

When I set up lemmy on my server with lemmy-ansible, the config file was initially set up with a valid-looking SMTP config. But when emails weren’t working I looked more closely, and it turned out that there is something broken with the SMTP service that lemmy is integrated with by default. It seems that you will need to provide your own credentials.

I’m using an SMTP service provided by a web hosting service I pay for, but you can also use gmail in a pinch: https://kinsta.com/blog/gmail-smtp-server/