What is the plan to make communities between instances easily accessible? I feel like with mastodon and now lemmy that is the part that concerns me, namely community reach/discoverability
External communities are just searchable, subscribable and browsable from here. Sometimes you need to change a search filter or default view from Local to All. Or is there something else you feel is missing? I think 90% of the issues people are having are UX related and not a core issue with federation or decentralization.
I think my concern for adoptability is that a technology community could exist with the same name on lemmy.world as well as on another instance. I think theirs some benefit to creating a user and community pool of names and communities to allow genuine growth. it would also prevent fakes and phishing.
I think of it like [email protected] instead of just selfhosted. Sure there may be duplicate communities on different instances but over time I think there will be more people gravitating to a particular community and people will just sub there from then on and the others will become more dormant. When I refer to a community I’ll just use the full name ([email protected]) and not just the community name (selfhosted)
I like the concept
But it feels very much like its been designed by nerdy developers and has had little to no-input on user friendly design.
The federated idea can work but it needs to be more seemless than this.
Communities with the same name should be merged when viewing it from any instance, so you can see all the posts from these communities, they can be moderated seperatley and for advanced users you should be able to select which communities make up the merged community.
By default you should see all of the merged communities in a central place and be able to subscribe to them easily, at the moment its handled different per instance but you have to seek out these communities to subscribe or follow them.
I strongly believe there should be a centralised log-in system, so you can log into any instance with an account from another instance, this means if your instance goes down your account is centralised and is safe.
Regarding point three: I want to be able to migrate my profile to another instance if my current instance has performance issues or admins going rogue.
Because of how fragmented this platform is, there isn't a universal answer. Some links will work in one client but not another. Fixing this will require a lot more coordination than is currently happening.
I woke up to a load of noise downstairs, went to investigate assuming it was my cat… who I couldn’t see. No problem, I thought.
Stood in the kitchen making a cuppa and I hear a very sorry meow, so obviously assumed my poor boy was hurt!
No. Completely wrong. Some random cat is sat on the windowsill in my living room. Dead lovely little thing that enjoyed a bit of fuss before I let it back out into the world!
I think it depends heavily on how much storage you’re allocating, if you allow uploading media that is. From what I’ve understood most of the bottlenecks are in DB operations so CPU and memory definately play a role.
I have somewhat of a similar setup. I use Nginx Proxy Manager and AdGuard Homes rewrites to do the same thing as you.
As for Question 1: Creating self-signed certs is pretty straightforward. I followed this tutorial by Christian Lempa: youtu.be/VH4gXcvkmOYHe also has a good writeup on his GitHub: github.com/ChristianLempa/…/ssl-certs.mdHow to import the certs into Nginx, I don’t know, but I think that’s easy to lookup online.
Regarding Question 2: My understanding is that all traffic goes through the Reverse Proxy.
I hope I could help, let me know if you have any more questions.
kbin.life
Newest