@abucci@anthony.buc.ci Hmmm you raise a good point 👌 Signal/Noise is important in any design and I tend to agree here with you. Makes git-bug far more appealing in that regard because of the way it stores data…

https://github.com/driusan/bug <– cool way to handle/manage project issues/bugs

@justamoment@twtxt.net I found another cool little tiny Git forge “thingy” honza/smithy: A tiny git forge written in Go which the author runs himself at https://git.pokorny.ca/ if you want to take inspiration from to help me do some kind of cool nice UI/UX for something yet to be named 😅

@abucci@anthony.buc.ci Whoa that looks mighty cold 🥶 How thick is that ice/snow on the ground? 🤔

Bruder EXP-6 EXPEDITION TRAILER - YouTubeWhoah! 😳 This thing is a massive ~$230,000 AUD 😳

It’s All FAKE | The Dead Internet Theory - YouTube– This is kind of scary but kind of somewhat has a lot of truth to it… 🤯 #RiseOfTheMachines

@marado@twtxt.net Yeah so @lyse@lyse.isobeef.org and I are talking on IRC right now about an idea I had about this… I realise I could use the same git patch/diff format(s) but skip the Email parts. I was even thinking of using Twtxt itself as a sort of “notification” and some kind of easy-to-use web-based push/pull system for managing the patches and applying them to your repo(s).

@justamoment@twtxt.net Yeah, not only that, but one of the “issues” I have with the whole Git+Email patch workflow in general is that you have to basically “give up” your identity, email address and personal information in some way. I find that a bit bothersome really. – I’m sure we can come up with a proper “decentralised” way of collaborating on software with git as the primary backend for revision history and patches, but hmmm 🤔

@justamoment@twtxt.net Well what I mean to say is that git itself basically just houses some client-side “Metadata” about the repository and a bunch of objects that make up the contents and revision history. For example, there is a special file called .git/description that you can edit and there’s even git branch --edit to edit a branch’s description. But none of that is useful beyond a local client. That is to say, if you git clone or git push none of that information is published anywhere or made available to anyone else.

So Git’s “distributed data” is limited to well basically its revision history and series of objects I guess? 🤔

@justamoment@twtxt.net Hmmm so there isn’t a lot you can do with plain Git itself. Even patches sent via email are basisally out-or-band at that point.

@justamoment@twtxt.net From the maitainrr side you just end up having to copy the raw contents of the emails and pipe them into git am - in the right order. It’s a bit tedious 🤦‍♂️

@justamoment@twtxt.net Hmmm not sure 🤔

@justamoment@twtxt.net No the command compares your branch and automatically formats a patch containing your changes compared to the branch you specified.

@movq@www.uninformativ.de @lyse@lyse.isobeef.org LOL 🤣 Isn’t this the same as what @codebalion@twtxt.prismdragon.net posted in #5yvkoeq ? 🤔

@justamoment@twtxt.net Technically if you setup your ~/.gitconfig “just so” the steps are really just one.

$ git co -b feature
# hack hack hack
$ git ci -m "blah bla hblah"
$ git send-email main

@justamoment@twtxt.net I agree, the patch workflow is a bit complicated (especially for new users) and I find it a bit unfriendly too. Having to switch from an Email client to Command-line just to manage reviews and applying patches kind of sucks IMO. – Some nice way to manage incoming changes and communicate reviews and easily applying those changes would be nicer. – I even had this stupid idea of pushing patches to a special endpoint that create a new Twt in a per-repo Twtxt feed with a link to the “patch” (via a Web UI) and then you can communicate feedback over your own feeds 🤣 – Finally a “patch” is either #approved or #rejected and patch manager can look for those tags in the thread and deal with the UI appropriately.

@justamoment@twtxt.net So I’m still “mucking around” with my forked version of legit, and haven’t decided what to do yet… I’m not keen on the name “MacGitter” 🤣 Next option/idea? 🤔 – Feel free to muck around with what’s there, built it, run it, muck around with the HTML/CSS 👌 – Right now I’m trying to get git push to work over SSH so I can have some kind of push + auth support…

@justamoment@twtxt.net Haha, although I have written many a programming language or two, I probably won’t ever fork Go itself 😅

Learn to use email with git! Patch Workflows - Ry’s Git Tutorial - RyPress – Another good blog post on working with Git patches via Email as well as applying them. – The key point (I think) is that you need to grab the entire contents of email email in order in order to pipe the contents into git am - – Hmmm 🤔 – I think we can do better than this…

Learn to use email with git! – Interesting read of how to use the “Git Email” workflow for sending patches to a project 🤔 Not sure how I feel about it though 😅

@codebalion@twtxt.prismdragon.net Very old and very interesting clip 👌 I find many of the points actually quite relevant today, especially the “naming” things.

Hmmmm kind of sounds complicated 🤔

@logout@i-logout.cz How does it work? 🤔

@justamoment@twtxt.net Okay… How do you want to do this? 🤔 Should we hard fork at this point and rename? (If you read the linked Github discussion, we are already on divergent paths) Shall we dogfood from the start and use it for development/collaboration from the start? 🤔

No thanks. Even if you pay me to share my personal data, behaviour and activities, nope 😅

@movq@www.uninformativ.de Same here, except without the “drinking” 🤣

@xuu Oh man, this guys has written so many words, and there are so many “patterns” (many of which I never knew!) 🤦‍♂️ Q: Isn’t most of what he’s talking about effectively the same as what we do in “good” Go using interfaces and making the zero value useful? 🤔

@justamoment@twtxt.net That’s pretty cool! 👌 You wrote Vector Pass? 🤔 How does it work? 🤔

@justamoment@twtxt.net it sure did! 😅 Would you at all be interested in hacking on this wth me? I’m thinking you basically do all of the UI/UX. The HTML/CSS right now is pretty clean so its bd pretty much “greenfield” 😅

@bender@twtxt.net living in the past man living in the past!

What y’all doing this fine Xmas day? 🤔

My daughter said it would look cooler if the crayon wasn’t there and it would look like a 3D sun 😆

@codebalion@twtxt.prismdragon.net Hope you have a great day! 🤗

@abucci@anthony.buc.ci that’s pretty cool and recovery use of toothpicks 😅

@logout@i-logout.cz No I mean I don’t actually know what this thing is 🤣

@in-laws@twt.nfld.uk You’re living in the past man 😅

@logout@i-logout.cz Huh? 🤣

Merry Christmas! 🎄

@abucci@anthony.buc.ci Well you live longer living in the cold anyway 😅

@abucci@anthony.buc.ci It is.

@abucci@anthony.buc.ci Ooof gawd that’s cold 🥶

@abucci@anthony.buc.ci Fair 😅 The only exception I personally find the Go language itself, not really a Google™ product/project, but one created by Rob Pike Ken Thompson and Robert Griesemer.

@abucci@anthony.buc.ci Like most things, this is unlikely to be an actual “Google” product or project, just someone yet another Google™ engineer wrote in his/her spare time… Which is a good thing, we should use/contribute/collaborate and share such things as they really are great engineers many of them 👌

@lyse@lyse.isobeef.org I wonder whether we can represent this data format as the result of a query? 🤔

@marado@twtxt.net Yeah it does seem cool, and yeah @lyse@lyse.isobeef.org its dependencies does seem pretty nice and short, but what I don’t like about it is how it stores the data as JSON files in a “special branch”. I much prefer the way git-bug stores the data, however I’ve run into a problem with even getting gith bug push to work in the first place 🤦‍♂️

Hmmm not sure if I like the way this is done… 🤔

google/git-appraise: Distributed code review system for Git repos – Interesting way to do code reviews, kind of very similar to git-bug 🤔

@abucci@anthony.buc.ci Ahh 🤗 Well stay safe 🤞

I posted this issue to the upstream author I forked this from to see what/where the discussion may go and how our goals may or may not align 🤞

@justamoment@twtxt.net We are however considering making it possible to publish said lists, providing an option for users to have private/public lists and probably just a simple text file format.