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.

I like it so far. It is pretty convoluted how you subscribe to communities across instances. I figured it out eventually, but I am seeing the question pop up all over the place across lemmy.

People say using the Android app makes that easier, but it needs to be solved in the webapp first and foremost.

I also have major concerns about scalability. Folks are calling out for the community to grow, but the servers are already struggling. Lemmy is built ontop of Rust which is an incredibly performant language. Lemmy.world also just migrated to a new, more beefy server. Why are there still scaling issues? I’m naive to the inner-workings of Lemmy, and I’m not saying this in a negative way, I just don’t know enough about the architecture. I am a software engineer though and know a lot of infrastructure and scaling, so these are the types of questions that pop into my head when I see my posts hanging infinitely (but are there on refresh.) Am curious to also know what the long-term storage requirements are for a Lemmy instance. If I were to self-host my own instance for example, what do I expect to need at the 1 month mark? 6 month mark? In terms of storage requirements. How big does the postgres db get?

Overall I am liking the new system and am bullish on Lemmy’s future. As with any sort of hyper growth, there are pains and I’m sure it’ll all get sorted with time. Nothing like a good forcing function such as a reddit exodus to show a light on any weak spots :)

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/[email protected] 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> (minus the exclamation point).

Example of navigating to a non-lemmyworld community from lemmy world: https://lemmy.world/c/[email protected]

Hope that helps.

@[email protected] - 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.