title pretty much I saw that FMHY was rebuilt to fmhy.net but currently I cant sub to it and it. Even tried /c/[email protected] is something wrong with their end or mine or ours here? xD
You must log in or register to comment.
Lemmy.net is not their domain name. Its lemmy.fmhy.net so the community would be /c/[email protected] but that community doesn’t exist, it’s /c/[email protected]
Your link ([email protected]) is working for me, and I can subscribe from another instance (dbzer0.com in this case), and so does /c/[email protected] since they both seem to resolve to the same community.
I think for the link to work across Lemmy it should be: [email protected] Might have to edit if that is incorrect.
Edit: that link doesn’t work, maybe for a different community on that instance: [email protected]
That works, not sure if you can link directly to an instance rather than a community.
deleted by creator
Unrelated, but I was looking forward to see if FMHY would implement a solution for migrating a Lemmy instance to another domain. Looks like they starting from scratch instead and everyone have to create a new account.
Seems like something wrong on the lemmy.net end.
I can’t even visit them from this instance but I can create a new tab and visit them. https://lemmy.fmhy.net/. Seems like you have to create a separate account for their instance.
You don’t have to create a separate account for their instance, unless you want to. You should be able to subscribe from another instance - I just tested it and it works. Visit them at [email protected] and hit subscribe.
Is this the correct one cuz it has only one post and doesn’t seem active plus no links to their wiki so I assumed it’s a fake one but if I just go to https://lemmy.fmhy.net/ there are multiple recent posts and it seems active.
Oh, I didn’t really check the community out tbh, was more interested in the subscriptions working or not, but I think you could be right! lol. Thanks for the heads up.
deleted by creator
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: [email protected]
