147
Lemmy.world is too big, use other instances
(hackertalks.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 May 2024
147 points (89.3% liked)
Unpopular Opinion
6216 readers
27 users here now
Welcome to the Unpopular Opinion community!
How voting works:
Vote the opposite of the norm.
If you agree that the opinion is unpopular give it an arrow up. If it's something that's widely accepted, give it an arrow down.
Guidelines:
Tag your post, if possible (not required)
- If your post is a "General" unpopular opinion, start the subject with [GENERAL].
- If it is a Lemmy-specific unpopular opinion, start it with [LEMMY].
Rules:
1. NO POLITICS
Politics is everywhere. Let's make this about [general] and [lemmy] - specific topics, and keep politics out of it.
2. Be civil.
Disagreements happen, but that doesn’t provide the right to personally attack others. No racism/sexism/bigotry. Please also refrain from gatekeeping others' opinions.
3. No bots, spam or self-promotion.
Only approved bots, which follow the guidelines for bots set by the instance, are allowed.
4. Shitposts and memes are allowed but...
Only until they prove to be a problem. They can and will be removed at moderator discretion.
5. No trolling.
This shouldn't need an explanation. If your post or comment is made just to get a rise with no real value, it will be removed. You do this too often, you will get a vacation to touch grass, away from this community for 1 or more days. Repeat offenses will result in a perma-ban.
Instance-wide rules always apply. https://legal.lemmy.world/tos/
founded 2 years ago
MODERATORS
As a DevOps Architect, let me make it simple:
With a single front-end, you have a bottleneck. If you have one domain (website) that everybody goes to to get to the front-end, that means that domain is the single point of failure.
In my line of work, we use load balancers and sub-domains to divide the work and provide resilience (High Availability), but at the end of the day, if the DNS for that site goes down, we're down.
Also, as Jet mentioned, ~~whomever~~ whoever controls the domain (website) controls the content. You can't have multiple groups controlling a single domain. Whomever buys it controls it. If they don't like content, they could easily block access to it.
I'm oversimplifying the inner workings, so if you want more details, let me know.
EDIT: subtext called me out on my crap English. Have nobody to blame but myself. English is my first language.
I just want to let you know that “whom” is only ever used as an object. In your sentences, I think you should have used “whoever”.
The easiest way to remember which you should use is to think about the difference between s/he==who and her/him==whom.
She gave the ball to him Who gave the ball to whom
She controls the domain Who controls the domain
The domain is controlled by him The domain is controlled by whom
Updated the comment with your recommendation. Yeah. I suck at writing.
In this case the solution, as I mentioned in other comments, is to make the back end the decentralized database that's accessible to anyone so the people developing a front end don't host the data and you can use any of the available front ends to connect to your account as it's not attached to any specific front end (your info is in the database).
Front end devs would be competing to provide the best UI/UX, but in the end everyone would have access to the same data and front end devs couldn't get in the way of the data or if they did then people could just go to another website without losing anything.