#@mleibovicToday our engineering team did an audit of all git repos and started renaming any master branches to main. Embarassed we didn't make this move earlier, but proud of how quickly the team took action to fix this (with zero debate) once it was raised. (twitter.com/_/status/1271625826237366273)
#vilhalmerKartikPrabhu: new core branch: grayskull
#gRegorLoveI first thought of it as the master copy, a la audio mastering, so it made sense to me. In favor of renaming it, though.
#KartikPrabhuall this sounds similar to how I have never understood "foo/bar/baz" stuff
#aaronpkgRegorLove: if everyone used it that way I could see that, but it turns out there are different ways of using git yet the default branch is still called master
#gRegorLoveTotally, just mentioning why it wasn't confusing to me initially
#aaronpkBut yeah sending and receiving webmentions are pretty different tasks. If anything id go with the way pine.blog did and make receiving webmentions part of a reader
#aaronpkwebmention is just plumbing, receiving comments and sending comments are the user facing features and it turns out they have very different considerations even tho they both use webmention
#jackybut I also understand that bit w.r.t receiving comments; I wonder if allowing a reader to add a hook to listen to incoming Webmentions could give that same feel / vibe
#jacky_or_ allowing a particular feed to be flagged as the "incoming" one so the reader would know to take and handle entries of that feed according
#jackythat said, I'm like 70% done with this move to lighthouse. might mess around with it against the staging instance before sending it live (trying to keep the dev-staging-prod habit down even if it's only me testing it)
#jackyside-note: it's kinda terrifying how much information JWTs can hold
#jackyI'm using https://jwt.io to debug them and like I _understand_ why people would use them; just too much
#jackyhmmmmm tbh now I'm curious about what you mentioned aaronpk re: pine.blog accepting Webmentions
#jackybecause then I can just add a compatible reader as a relay whenever I get a webmention in lighthouse and I'll get that interactivity for free
#[LewisCowles]Is the desire to provide them one to save typing, get analytics about link-usage or something else. I don't like the extra hop, so I try to think of the reasons why anyone wants to use a shortener. To my strange brain it's another potential point of failure between me and the resource I am linking to.
#Loqishortlink is the use of a short-domain to create a link that redirects to (often much) longer link, popularized on Twitter, and used in permashortlinks for indieweb POSSEing https://indieweb.org/shortlinks
#Loqishortlink is the use of a short-domain to create a link that redirects to (often much) longer link, popularized on Twitter, and used in permashortlinks for indieweb POSSEing https://indieweb.org/shortlinks
#jackytbh everything on permashortlinks could be linked from a region on short domains
#nekr0zOh no, now there's something wrong with git master branches? Do we stop mastering audio, too? Do I give up my master's degree? Do I burn my The Beatles "Past Masters" set? Do I stop using MasterCard while I'm at it?
#jackynekr0z: did you read into the material/content around it or are you just reacting for the sake of it?
#nekr0zjacky: I did. And git master branch is exactly the same as audio master tape - the master branch. There's no other way to call it. It is created by default when you git init and git commit to an empty repo (so no, it's not the matter of "blatantly copying some age-old tutorial"
#jackyyou're saying there's no other way to call it but as others have shown online; there's _many_ ways
#jackyI tend to use names like `mainline` or `production` when I remember to rename things
#nekr0zLanguage matters, but sanity and common sense matter, too. We went through the stupidity of renaming everything because it didn't sound right and reminded of past oppressions twice last century in Russia, and it was stupid both times.
#@lgarronOur team at @GitHub just changed our project's main branch to `main`! We're not the only ones, and there's growing momentum to change the default across the company. 😱 It's no defunding the police, but it's nice to see progress against such entrenched practices. (twitter.com/_/status/1271212268294823938)
#nekr0zI'm totally with you if it makes sense for you to have "prod" instead of "master", but spending time thinking what to rename master to just because you shouldn't have master?
#jackythere's also very smart people who've highlighted that it's in fact not common sense to use "master"; that's more cargo culting than anything else
#jackyat this point, it reads a bit more of a resistance to what the community is moving to and more about wanting to stick to provably oppressive language
#jackythis isn't really dev-y so I won't continue on that here
#nekr0zYeah, I remember reading that some time ago and thinking that in a sane society the metaphor should long be gone and little childred should know "master-slave" from tech, only later getting the historical meanng from history classes.
#nekr0zBut then someone told me I should not be using the word "sane" either.
#[Murray]Interesting to log in and see people discussing master/main/others. Just changed my main site to "trunk", largely to see how hard it would be (I chose "trunk" because it fits the "branch" metaphor and was what originally made sense when I was learning Git). Turns out (for me at least) it was super easy, so will just go with that from now on
#[Murray]Do wish that I could set git init to something other than master though too
#aaronpkmaybe this is a good saturday morning project
[tantek] joined the channel
#[tantek]really hope GitHub makes this a one button click for repo owners rather than requiring everyone to do all this command line businesses
#ZegnatI think in GitHub you could do it completely through their UI. Haven’t created a fresh repo in a while, not sure if they just default a branch or not
#ZegnatOh, interesting, GitHub repos created through the site actually start branchless
#ZegnatAnd the first branch you push will be the one displayed in your repo by default, even if you were to push a branch called “master” directly after.
#ZegnatSo looks like GitHub is pretty name agnostic. They could change some of their git commandline instructions around and it’ll be gone from their platform
#aaronpkthey do have a way to create repo contents on the web, like if you use the button to create a README file. what happens then?
#willnorrisit looks like the above link I referenced causes some problems when cloning. Apparent git template is not just used when calling `git init` but also `git clone`. Maybe? Anyway, I'd suggest testing it pretty well if you make that change
Midasse and [Murray] joined the channel
#[Murray]willnorris++ thanks will take a look over and keep the potential issues in mind
geoffo joined the channel; nickodd left the channel
#aaronpki feel like there are some nuances to this
#aaronpki'm trying to script as much as possible but it's tricky
#aaronpkfor example, this bumps the repositories to the top of the list on my github profile, so i should actually do them starting with the oldest otherwise my old repos will be on top
#aaronpkmight as well take this opportunity to delete some real old ones too
#@m_ott↩️ Hey Jeremy! Just fixed a bug in my Webmention plugin. It didn’t check correctly if a photo is present in the h-card. After fixing this, I was able to add the Webmention using the little form at the bottom of the article. (twitter.com/_/status/1271928989783916545)
#aaronpkwell i only have 157 repos on my github now