News for hackers. Stuff that matters.
Re:GitHub Incident by mulmen on Tuesday May 16, 2023 @05:50PM (#35968223)
Someone should invent a decentralized version control system so we can avoid these kinds of widespread events.
Re:GitHub Incident by dchnshA on Tuesday May 16, 2023 @06:36PM (#35968706)
BTW: There is work in progress to decentralize modern git based workflows by https://nlnet.nl/project/ForgeFed/ (paid for by the European Union), by decentralizing git not at the client level, but also on the code forge level.
Re:GitHub Incident by morelisp on Tuesday May 16, 2023 @06:48PM (#35968795)
> ForgeFed aims to define a vocabulary

Aw yeah there’s the good EU grant milking shit.

Re:GitHub Incident by legohead on Tuesday May 16, 2023 @06:39PM (#35968727)
How do decentralized networks deal with illegal content?
Re:GitHub Incident by jeroenhd on Tuesday May 16, 2023 @06:42PM (#35968752)
The joke is that Git is decentralized already. Many people pick a single master host, but it's absolutely possible to use multiple servers (or to use Git over email, like the Linux kernel does).
Re:GitHub Incident by mulmen on Tuesday May 16, 2023 @06:55PM (#35968861)
Same as everyone else. With law enforcement.
Re:GitHub Incident by legohead on Tuesday May 16, 2023 @08:51PM (#35969929)
So law enforcement contacts everyone on the network and says please delete these illegal photos?
Re:GitHub Incident by mulmen on Wednesday May 17, 2023 @03:12PM (#35979849)
Yep. Not complicated. They actually only have to contact the people hosting illegal photographs so it's easier than you describe.
Re:GitHub Incident by lionkor on Tuesday May 16, 2023 @05:55PM (#35968282)
git itself is not enough for teams to work together - you need to asynchronously communicate for the whole thing to come together. Thats what GitHub/Lab/ea bring in value.
Re:GitHub Incident by TimTheTinker on Tuesday May 16, 2023 @06:02PM (#35968355)
Someone should write a local git+ssh service (+ email client) that simulates an upstream by hosting git repos locally, emailing all pushed commits/branches/tags to other team members, and keeping the hosted repos up-to-date via the emailed updates from others.

Bonus points for a local HTTP service that provides an optional GitHub-like experience in the browser, with comments/ branch reviews/etc. federated through emailed messages (and represented as commits on meta-repos).

With that data model, the primary remaining challenge would be setting up repos on a new machine -- perhaps BitTorrent could help :)

Re:GitHub Incident by zamnos on Tuesday May 16, 2023 @05:58PM (#35968306)
I feel like "communication" isn't descriptive enough. It's right, but eg Slack (or Microsoft Teams, or maybe both) isn't the right shape of communication.
Re:GitHub Incident by unboxingelf on Tuesday May 16, 2023 @05:56PM (#35968288)
good idea. let’s call it “git”
Re:GitHub Incident by whynotmaybe on Tuesday May 16, 2023 @06:18PM (#35968531)
Not quite sure, the name should imply that the Source is Safe and provide some Visual tools.
Re:GitHub Incident by rlytho on Tuesday May 16, 2023 @06:58PM (#35968882)
DNS and git are decentralized; anyone can set up a node

Human agency tends to normalize on the brands with biggest marketing budget who collude with politicians to create a moat for themselves. There’s your real problem.

Of course none of the propaganda research that made its way from military after world wars to corporate advertising and marketing college programs has any influence on lizard brains. No sir.*

* this comment is paid placement