This is great for small one-off projects, but I don't know why anyone would want to promote the usage of mailing lists in general. The industry moved on to more centralized solutions like github for a reason - mailing lists are clunky, intuitive, and simply horrible for large discussions. Because old and large projects are using them doesn't mean it's a good reason for new projects to use them today. If anyone has pr…
Small, one-off projects like Linux, postgres, git? What makes mailing lists worse for large discussions? Decent mail readers support threaded conversations and decent mailing list participants know how to quote properly. This has been around for decades and I don't think github discussions add anything except more noise maybe.
Show HN: Learn to use email with Git
61–70 of 76 posts
Re: Show HN: Learn to use email with Git
#62I wanted so much to like this. The evolution of SirHat (better name :) is entertaining, and never leaving the cmdline would be great! And I was on board until encountering this type of tedium: Find the message ID to reply to. Don't stress too much about getting this step right, but it's a nice Courtesy for the people receiving your patch. On the mailing list Archives, look up the latest email In your thread and expan…
Re: Show HN: Learn to use email with Git
#63This is great for small one-off projects, but I don't know why anyone would want to promote the usage of mailing lists in general. The industry moved on to more centralized solutions like github for a reason - mailing lists are clunky, intuitive, and simply horrible for large discussions. Because old and large projects are using them doesn't mean it's a good reason for new projects to use them today. If anyone has pr…
Small, one-off projects like Linux, postgres, git? What makes mailing lists worse for large discussions? Decent mail readers support threaded conversations and decent mailing list participants know how to quote properly. This has been around for decades and I don't think github discussions add anything except more noise maybe.
the first is rare(in that no one bothers using mail readers) and the latter is non existent in the current generation - which you do have to interact with.
Re: Show HN: Learn to use email with Git
#64Earlier quoted context omitted.
The idea is that in order for multiple people to collaborate, most of the time you will need a service like Github, Bitbucket or perhaps something you can run yourself. This is a different workflow. Instead of staying in sync via a hosted service, people stay in sync and send 'pull requests' via email.
Thanks, this response starts to remove some of my confusion. So it's git without the server, communicating pushes over email instead. (I guess you automatically pull whatever is in the emails you get?)
Re: Show HN: Learn to use email with Git
#65One thing a lot of email providers (at least gmail and fastmail) do is let you create application passwords that you can use for specific purposes. So if you're at all queasy about having your password in plain text on the hard drive, you can create a special password just for git. Edit: you don't have to set up a terminal email client at this point, but if you figure out how to use git-send-email, you're just inches…
The Google implementation of application specific passwords is horrible . There's nothing application specific about it -- it's valid for at least mail, calendar, and contacts, with no way to limit the scope. It ends up being a password that effectively bypasses all MFA on your Google account. Where do you store such a password? That's a powerful credential to be regularly unlocking. I should be able to create a cred…
Re: Show HN: Learn to use email with Git
#66This is great for small one-off projects, but I don't know why anyone would want to promote the usage of mailing lists in general. The industry moved on to more centralized solutions like github for a reason - mailing lists are clunky, intuitive, and simply horrible for large discussions. Because old and large projects are using them doesn't mean it's a good reason for new projects to use them today. If anyone has pr…
But email lists (and newsgroups) have one thing that even HN and reddit do not. That is, the ability to quickly see new posts. In HN, I have to search through the entire thread to find new posts when I refresh the page. It's the same issue with reddit unless you're a subreddit moderator or have a reddit gold subscription.
Re: Show HN: Learn to use email with Git
#67Re: Show HN: Learn to use email with Git
#68Earlier quoted context omitted.
Isn't it better to nest the checkbox inside the label? Then you don't need the for attribute nor an id.
You still have to do the complementary for= and id=, but I am also a proponent of nesting, though I have not solicited public opinion on it until just now. Here is how I started doing it: display alphabet
Re: Show HN: Learn to use email with Git
#69Earlier quoted context omitted.
The Google implementation of application specific passwords is horrible . There's nothing application specific about it -- it's valid for at least mail, calendar, and contacts, with no way to limit the scope. It ends up being a password that effectively bypasses all MFA on your Google account. Where do you store such a password? That's a powerful credential to be regularly unlocking. I should be able to create a cred…
That magic password is somewhat restricted as in you can only link an application with it once (which then should get an infinite token). It's mildly better. Last time I used it there were scoping options, but I might be mistaken
The magic password is the token. The "scoping" options are just a label (I suppose this might have recently changed), mostly targeting folks who are looking at using legacy mail/cal/card clients with only user/pass support, and are unsure what's going on.
edit: Just triple checked -- the 16 character string returned when creating a "Calendar on iPhone" password works perfectly for SMTP via PLAIN over TLS.