No Stupid Questions
No such thing. Ask away!
!nostupidquestions is a community dedicated to being helpful and answering each others' questions on various topics.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules (interactive)
Rule 1- All posts must be legitimate questions. All post titles must include a question.
All posts must be legitimate questions, and all post titles must include a question. Questions that are joke or trolling questions, memes, song lyrics as title, etc. are not allowed here. See Rule 6 for all exceptions.
Rule 2- Your question subject cannot be illegal or NSFW material.
Your question subject cannot be illegal or NSFW material. You will be warned first, banned second.
Rule 3- Do not seek mental, medical and professional help here.
Do not seek mental, medical and professional help here. Breaking this rule will not get you or your post removed, but it will put you at risk, and possibly in danger.
Rule 4- No self promotion or upvote-farming of any kind.
That's it.
Rule 5- No baiting or sealioning or promoting an agenda.
Questions which, instead of being of an innocuous nature, are specifically intended (based on reports and in the opinion of our crack moderation team) to bait users into ideological wars on charged political topics will be removed and the authors warned - or banned - depending on severity.
Rule 6- Regarding META posts and joke questions.
Provided it is about the community itself, you may post non-question posts using the [META] tag on your post title.
On fridays, you are allowed to post meme and troll questions, on the condition that it's in text format only, and conforms with our other rules. These posts MUST include the [NSQ Friday] tag in their title.
If you post a serious question on friday and are looking only for legitimate answers, then please include the [Serious] tag on your post. Irrelevant replies will then be removed by moderators.
Rule 7- You can't intentionally annoy, mock, or harass other members.
If you intentionally annoy, mock, harass, or discriminate against any individual member, you will be removed.
Likewise, if you are a member, sympathiser or a resemblant of a movement that is known to largely hate, mock, discriminate against, and/or want to take lives of a group of people, and you were provably vocal about your hate, then you will be banned on sight.
Rule 8- All comments should try to stay relevant to their parent content.
Rule 9- Reposts from other platforms are not allowed.
Let everyone have their own content.
Rule 10- Majority of bots aren't allowed to participate here.
Credits
Our breathtaking icon was bestowed upon us by @Cevilia!
The greatest banner of all time: by @TheOneWithTheHair!
view the rest of the comments
You bring up some good points. I agree on the risk, even though I'm a fan I find federated tools harder to get started with.
I agree git is decentralized, but services like GitHub are not. They're more than just hosting code. They're issues, wiki's, CI/CD, peer reviews, etc.
I'd image it's the same as now. Except now you could say @everyone@that-server is cool and can contribute, or @those-guys@over-there shouldn't even be allowed to see this code.
How do you do this on GitHub?
I feel like this is the root of fediverse problems. It's easy to send your first tweet, but that first toot takes some effort (I just learned they're called toots).
Btw I appreciate the fediverse and decentralization as much as the next guy, heck I'm even writing software for the fediverse. But I feel like there's a handful of people out there that want to try and apply the fediverse concept to everything. Similar to what happened with Blockchain. Everyone and everything had to be implemented via Blockchain even if it didn't make sense in the end.
IMO though, GitHub is just one "instance" in an already decentralized system. Sure it may be the largest but it's already incredibly simple for me to move and host my code anywhere else. GitHub's instance just happens to provide the best set of tools and features available to me.
But back to my original concerns. Let's assume you have an ActivityPub based git hosting system. For the sake of argument let's assume that there's two instances in this federation today. Let's just call them Hub and Lab....
Say I create an account on Hub and upload my repository there. I then clone it and start working... It gets federated to Lab... But the admin on Lab just decides to push a commit to it directly because reasons... Hub can now do a few things:
Similarly if Hub was to go down for whatever reason. Let's assume we have a system in place that effectively prevents the above scenario from happening... If I didn't create an account on Lab prior to Hub going down I now no longer have the authorization to make changes to that repository. I'm now forced to fork my own repository and continue my work from the fork. But all of my users may still be looking for updates to the original repository. Telling everyone about the new location becomes a headache.
There's also issues of how do you handle private repositories? This is something that the fediverse can't solve. So all repos in the fediverse would HAVE to be public.
And yes, if GitHub went down today, I'd have similar issues, but that's why you have backups. And git already has a solution for that outside the fediverse. Long story short, the solutions that the fediverse provides aren't problems that exist for git and it raises additional problems that now have to be solved. Trying to apply the fediverse to git is akin to "a solution in search of a problem", IMHO.
I would like to add that git is a pretty good example of data people have backups for. I don't care if Github blows up tomorrow because I have repos on my disk. Even if my disk also dies, my friends have my repos cloned so I wouldn't lose much