First of all I am super happy that such alternative exists but it’s far from perfect due to many reasons and this is why I think it’s not ready yet to absorb the influx of reddit users because many of them will just bounce off when they realize it.

My biggest gripes so far:

  • Users are unable to block whole instances hence you either need to register with instance that already blocks unwanted instances (which is not perfect because it might block also those that you don’t want to be blocked) or you need to block manually every single community there or you will be exposed to lemmygrad or other tankie instances. That’s so basic feature I can’t find any logical reasons that was not a thing since day 1.

  • Lemmy is one of the least privacy friendly (unless you just use throwaways and disposable mail like you should) service I have ever stumbled upon and while it’s partially due to how federation works it’s just a fact that even reddit did that better because it was way easier to nuke your account and all traces (including nicknames in deleted comments, which is not a case on lemmy).

  • There is no possibility to migrate or backup your subscribed/favorited stuff or even move it to another instance (which somehow is possible on Mastodon), so you basically have to trust that your instance won’t disappear overnight. Obviously any site can disappear, centralized or not but there are bigger chances that some random Joe will decide to close instance without saying anything than reddit closing down overnight without letting you copy your stuff. That’s even more annyoing if you consider that instance admin can restrict you from viewing instances they don’t like, hence you would need to create account on another instance and resubscribe to anything manually which is far from perfect.

What are your views on that for the time being?

  • Faceman🇦🇺
    1·
    1 year ago

    the link is correct, but the current limitation is that if your particular instance has not yet federated with the linked instance, it;s not a huge issue between large instances and popular communities as they sync pretty quickly, but on smaller instances you will get a 404.

    In that case, you either need to wait for more people to connect, or manually enter the full URL into the search bar of your instance to force it to be synced, sometimes it takes a minute.

    This is something being discussed on github as it is a weakness of the federated approach, it can be solved by having the instance check first, then instead of showing a 404, it would say please wait then refresh once federated.