Hi fellow tilders !
I'm 'erxeto' at IRC, this is the email account I use the most, so I changed my subscription.
So, I wanted to talk a little bit about netiquette and basic mailing list behaviour.
I don't know many of you and I have no clue of your background, so if you find this too basic or that "insults your intelligence" please forgive me, I don't mean to be disrespectful in any way.
Mailing lists are old. Some of us have been subscribed to mailing lists for many years. What this means is that mailing lists have a basic set of rules that has been developed over the years. It works, and it makes all the "experience" more smooth.
A good place to start is here: https://man.sr.ht/lists.sr.ht/etiquette.md
If you don't want to follow links, basically:
* post in plain text. Never, ever send html to the list. Some of us use MUAs that don't play well with html. Besides, the html engine of the mail readers is really broken. (And there's other issues, this topic is huge). * don't do top posting. Please, is really annoying and disrupts the flow of the conversation. * related to the previous one, reply inline AND remove the parts of the email you're replying to that are not relevant. In other words, keep just the context that makes sense and remove the rest. That makes cleaner emails and is easier to read. * wrap lines. The link I sent says 72 columns. If you're curious, that's because a 'regular' terminal has 80 columns, and 8 chars less gives you some room for the '> ' response prefix, making the threads with nested replies more readable. * the link talks about gpg inline, I think that's less of a concern given the amount of people that actually uses gpg. I personally don't sign any email going to a mailing list, but that's personal preference. * I may add, don't send attachments to the list (or if you do, they have to be really small). Think about the people with bad internet connections or limited resources. It's better to send a link to a download site. If you do this, remember to say what it is and it's size. Something like https://foo.com/mylink (pdf, 3.5MB)
I think that's it, IMHO those are really basic things to do, and make all the difference. You may encounter some mailing lists that are really strict with this. I think that just "doing your best" is enough. No need to ban anybody ;-)
Have a nice day !
Looks like a fair set of rules, to be honest. I wasn't aware of the 'top posting' rule, though now that I think about it I've seen the inline commentary and the bottom- posting behavior on mailing lists that I've read in the past.
Luckily, neomutt+gpgme doesn't do inline signatures, but does do attachment signatures by default when you choose to sign a message (press p on the send/review screen). If you're using it to view a signed message, neomutt will attempt to verify the authenticity of the message by itself. It will "appear" inline because of neomutt+gpgme's behavior, but it is in fact an attachment. I'm not sure if the same things apply to vanilla mutt.
On Fri, 14 Dec 2018, ahriman wrote:
Luckily, neomutt+gpgme doesn't do inline signatures, but does do attachment signatures by default when you choose to sign a message (press p on the send/review screen). If you're using it to view a signed message, neomutt will attempt to verify the authenticity of the message by itself. It will "appear" inline because of neomutt+gpgme's behavior, but it is in fact an attachment. I'm not sure if the same things apply to vanilla mutt.
Well, those are not really intrusive, and I'm pretty sure can be deactivated/modified. Mutt/neomutt is really configurable.
What's kind of annoying is a block of base64 encoded text that does not have anything to do with the email content itself.
Cheers,
What's kind of annoying is a block of base64 encoded text that does not have anything to do with the email content itself.
Yes, I can see why having inline signatures would be distracting and will detract from the general flow of conversation. I hope everyone who chooses to participate in the mailing list abides by these standards.
~ahriman
On Fri, 14 Dec 2018, ahriman wrote:
What's kind of annoying is a block of base64 encoded text that does not have anything to do with the email content itself.
Yes, I can see why having inline signatures would be distracting and will detract from the general flow of conversation. I hope everyone who chooses to participate in the mailing list abides by these standards.
On low volume mailing lists, just a friendly reminder when somebody "breaks the rules" is usually more than enough.
We could have a page on ~team website to direct people to, or even add it to the "list signature". If you think that's useful I can create one with a more polised version of the contents of my original email.
Cheers,
On December 14, 2018 5:52:52 AM Paco Esteban paco@onna.be wrote:
On low volume mailing lists, just a friendly reminder when somebody "breaks the rules" is usually more than enough.
This is definitely reasonable. I don't anticipate any of these lists becoming high volume.
We could have a page on ~team website to direct people to, or even add it to the "list signature".
How about both options? Feel free to grab the source of the sr.ht wiki, adjust, and then make a PR to our wiki: https://tildegit.org/team/site/src/branch/master/wiki
I can add a link to it in the footer.
I should probably add a link to the web archives as well.
If you think that's useful I can create one with a more polised version of the contents of my original email.
On Fri, 14 Dec 2018, Ben Harris wrote:
How about both options? Feel free to grab the source of the sr.ht wiki, adjust, and then make a PR to our wiki: https://tildegit.org/team/site/src/branch/master/wiki
done.
Cheers,
December 14, 2018 9:51 AM, "Paco Esteban" paco@onna.be wrote:
On Fri, 14 Dec 2018, Ben Harris wrote:
done.
It's now live at https://tilde.wiki/?page=mailing_lists for those interested.
Time to figure out how to add stuff to the list footer!
Not sure exactly what I'm working on, except trying to learn Nuxt.js
On December 14, 2018 3:58:59 AM Paco Esteban paco@onna.be wrote:
So, I wanted to talk a little bit about netiquette and basic mailing list behaviour.
Thanks for bringing this up. I mentioned it a bit on irc but it's far better to have it here on the list.
A good place to start is here: https://man.sr.ht/lists.sr.ht/etiquette.md
This is one of the links I posted on irc :) I really like that write-up.
If you don't want to follow links, basically:
- post in plain text. Never, ever send html to the list.
Mail clients can be configured to do this. research it or holler in irc and someone might be able to help.
- don't do top posting. Please, is really annoying and disrupts the flow of the conversation.
- related to the previous one, reply inline AND remove the parts of the email you're replying to that are not relevant.
- wrap lines. The link I sent says 72 columns. If you're curious, that's because a 'regular' terminal has 80 columns, and 8 chars less gives you some room for the '> ' response prefix, making the threads with nested replies more readable.
I'm not sure how wrapping will work from my mobile client here... sorry if it comes out too wide!
- I may add, don't send attachments to the list (or if you do, they have to be really small). Think about the people with bad internet connections or limited resources. It's better to send a link to a download site. If you do this, remember to say what it is and it's size. Something like https://foo.com/mylink (pdf, 3.5MB)
An easy way to get a download link is to use https://ttm.sh or drop it in your ~/public_html
Another thing I'd like to add is that your reply needs to be sent to the list itself (reply all usually cuts it)
Happy listing!
-- Paco Esteban https://onna.be/gpgkey.asc _______________________________________________ tildeteam mailing list -- tildeteam@lists.tildeverse.org To unsubscribe send an email to tildeteam-leave@lists.tildeverse.org
tildeteam@lists.tildeverse.org
-
ahriman -
Ben Harris -
Paco Esteban -
rgdrake＠tilde.team