Follow

Suggested to a source forge that gets flack for being inaccessible/elitist that they simply use the plain text part in a multi-part email instead of rejecting it on their discussion list as some folks are limited in their ability to send text-only email.

Response: we consider that a bug in your email service provider.

Context: there’s a tool I use and want to contribute to but I can’t without jumping through arbitrary hoops. I’m emailing with the author directly now because it’s easier.

*smh*

· · Web · 6 · 7 · 12

There’s a fine line between having principles and being arrogant/elitist/inaccessible. I believe folks in the world aren’t always aware of where that line is and that hurts the whole movement.

When I’m feeling a bit better (hopefully later this week, still taking it easy as I recover from COVID), I’m going to put up the recording we did with @gabek (hope you’re feeling better too, btw… also COVID) where we go into this in the context of small web.

@aral

I’m emailing with the author directly now because it’s easier

To be fair, being able / encouraged to do that is a good thing imo. Directly emailing the author is good for the Git network (regardless of the format of the email), and its something that popular forges often make very difficult to do.

@robby I disagree. When a conversation is had in the open and there’s a record others benefit from it also.

@robby (And anyone can place their email address on their profile on ~ any service. As far as I’m concerned, that’s a last-try contingency. When all else fails.)

@aral That's true, they can. I've tried contacting authors of projects hosted on GitHub, and it's usually not an easy thing to do. Lots of people don't put their email on their profile, and the only way to find their email is to clone a repo of theirs, and look at the git log. It's possible to find their email by completely circumventing the forge, but the fact that I usually need to put effort into circumventing the forge to find what I want is not a good thing IMO.

I think encouraging the use of email from the start is a good thing, because it makes contacting the authors a non-issue. Contacting the author *publicly* is a different problem, and it's about as much of an issue on GitHub as <unnamed forge> (our way or the highway + git commit messages).

@robby Oddly, I’ve never had a problem opening an issue on GitHub/GitLab/Gitea, etc. In fact, it’s never something I’ve had to think about.

@aral Because you use their interface with an account on that service to do it. On <unnamed forge> you can open an issue without using the web interface or any tool specifically designed for the forge, and without having an account at all.

I don't have a GitLab account, and my GitHub account is essentially dead, and I'd rather not use it. I have no pressure to create an account on <unnamed forge> because I can interact with it entirely over email (I'm lucky enough that my email setup handles plain text fine).

To be clear, I think your idea for simply keeping the plain text part is an interesting one. I'm thinking there is more of a reason to their decision against it than they shared, and I'm curious why. Modifying emails to format them for a mailing list does seem like it could cause trouble.
@ar.al🌻 Perhaps unless it's a security issue and you don't want it to be in the open until the project has had a chance to fix it. Some allow you to submit a private issue only visible to the project members, but not all of them.

And that's only after you have registered on their platform of choice to begin with.

As a security researcher I sometimes spend way too much time to track down a safe contact for a vendor so that I can submit information about vulnerabilities in their software to them in a responsible way.
@aral The commit messages can and should record information that is important to log

@robby I’m talking about emails sent to a project’s discussion list. Not patches :)

@aral until ~25 years ago i used a popular text-based e-mail client and agreed with the "down with html email" "wrap your lines at 79 characters" "don't top-post" crowd. because someone might be using an old system or software that can't do html?

but then i realized how ridiculous it is to spend a lifetime whining at everyone for not adjusting their behavior to suit my software

if free software is as great as we say, we should be able to adjust its behavior to suit people instead of vice-versa

@aral (email embedded in proprietary microsoft word documents is a different story but nobody attempts to do that anymore)

@ar.al🌻 Tbh, I see the rationale for both positions here. The problem is that the plain text part of html email often are not a good representation of the html part. Often it's just a "Click here to read this email in your erb browser", or even the extremely rude variant "Use a different email program."

Others at least try to render the html part as something readable in the plain text part, but with varying success. More often than not the result is difficult to decipher in any meaningful way, or even completely unreadable. (I've got emails where the plain text part had all the correct letters, but no whitespace, for example.)

Neither of this is anything you would want to clutter up your discussion list.

Tbh, I think the only way to do it is to pass the html part along so that the client can decide which part to render and how.

@aral yeah, I ran into that recently while trying to submit an issue on a sourcehut project

it's borderline impossible to send a plain text email from gmail on a mobile device

you have to go in the browser, enable desktop mode and manually put in a URL to be put on the full desktop frontend, which is the only one that allows setting an email as plain text

(even an email without formatting is otherwise considered HTML)

but also, maybe sourcehut should just strip the formatting from HTML mails, instead of completely rejecting them and dumping the problem on the user.

@LunaDragofelis @aral this email client for android I use.
In theory you could use any client that supports sending plaintext but this is one I know of that has this switch

@dhfir @aral does it work with gmail (as in, gmail will not deny it access)?

I'm too depressed to bother with switching email providers, especially when I already plan to switch to my own domain at some point.

@LunaDragofelis @aral I cropped out the bit with Via:[Legal.Name[number]]@gmail.com, but this is with gmail.
@LunaDragofelis @aral I mean, gmail uses some kind of thingy that requires google play services, but beyond that, should work?

@aral What is "a source forge?" I've never heard of that as a generic term. Is it a generic term for a SVN repository or something?

@n8chz @aral A Source forge is where people typically host their projects.

GitHub, GitLab, Gitea and Savane are all source forges.

@n8chz @aral The source forge mentioned in this post is SourceHut, a source forge notorious for using Email to communicate with developers and not requiring an account to collaborate.

@n8chz @aral Back in the day, we even used one called sourceforge. Generally not a good idea to use sf.net anymore, they quit putting viruses in generated zips but my trust is gone.

@mdhughes @aral I never much liked Sourceforge, but I could never quite put a finger on why. I remember the rumors (apparently w. receipts) about malware in binaries. Long before that, I recall noting the forced wait for downloads and thinking "that's a pretty brazen monetization tactic, even for the commercial web."

@mdhughes @aral I'm proud to say at this point that I'm not just a member of Codeberg, but also a donor. I hope it stays the way it is for as long as possible. But if there's something you know about that that's problematic, by all means, let me know.

@n8chz @aral Early on sf were the only public open source hosting, they did a lot of things right. The bad years chased everyone good off.

MS buying github made me delete my account there.

Now I use gitlab if I want public visibility, or just self-host on my blog. Trust no-one.

@mdhughes @aral I'm very sold on the self-hosting philosophy, in my case probably a little more PESOS than POSSE, although I'm trying to migrate to the latter. Big downside to that is much of the very best content in the history of online has been lost to the sands of time due simply to someone not being able to pay their hosting or domain name bill. So Internet Archive is near the top of my to-do list of donations.

@mdhughes @aral "Trust no-one" is something I've also learned the hard way, and yes, I also don't trust the non-commercial sector to remain non-commercial (Mozilla being a whopper of an example there), but I've also concluded that, for now, donor-funded activities are the only viable alternative to monetization, which is to say, predatory behavior.

Sign in to participate in the conversation
Aral’s Mastodon

This is my personal Mastodon.