Why not hop onto https://libera.chat/ ? If you’re into self-hosting, check out https://thelounge.chat/ so that way you don’t miss any goings-on while not logged in.

Same thing is happening to me. I am assuming it has to do with the amount of traffic the instance is getting. Wonder what can be done to help alleviate the issue as it’s been happening to me since I joined a few days ago.

Anything you do cross-origin will have to be done in a server-like environment instead of in the browser.

You have to search for the community you wish to subscribe to from on your server’s search page. You’ll navigate to it from within your server’s instance and give you the ability to subscribe to it that way. For example, if you go to the lemmy explorer: https://lemmyverse.net/communities You’ll note that each entry there has a link to the community, as well as an identity listed below it that you can copy. Like so: !selfhosted@lemmy.world This is the identifier url to the selfhosted community at lemmy world. If you navigate directly to it: https://lemmy.world/c/selfhosted but you don’t have a lemmy world account, then you’d have to sign in to lemmy.world to subscribe. But if you are on another server, and you search !selfhosted@lemmy.world, you should be taken to it from within your instance and you can subscribe from there. The same url would also be: https://lemmy.world/c/selfhosted@lemmy.world So if you get the identifier of any community, you can navigate to it from within lemmy.world with that url scheme: https://lemmy.world/c/<identifier>

Hope that helps.

@Yoru@lemmy.ml - it has to do with CORS (says in the error message) - You generally can’t make cross-origin requests in the browser unless it is explicitly allowed. This is purely a browser limitation, which is why it works in your node environment. But if you open the console on any random website and try to call fetch() to that API, it’s going to fail on any site other than lemmy.world.