ldmud warnings

[Aloy]

someone willing to do the ldmud warnings? are from current linux mit and debian.

[Croft]

Can you please be more specific?

On Wed, 26 Aug 2026, 21:33 Aloy, <al...@fantasywelt.net> wrote:

someone willing to do the ldmud warnings? are from current linux mit and debian.

--
You received this message because you are subscribed to the Google Groups "LDMud Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ldmud-talk+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ldmud-talk/1a292a96-ec19-4499-bba5-752afb8bff82n%40googlegroups.com.

[Aloy]

there isn't somethin to more specifiy. all deets attached in file.

[Croft]

Well referring is a start. Why should someone look at attached stuff? 

To view this discussion visit https://groups.google.com/d/msgid/ldmud-talk/90914c6a-08ee-49a6-aa30-e1a9836b03ffn%40googlegroups.com.

[Aloy]

alter, was ist dein prob...echt ey. wundert euch nicht, dass sich niemand für dach muds interessiert. nen scheiß.

[Croft]

Easily triggered. Relax.

To view this discussion visit https://groups.google.com/d/msgid/ldmud-talk/0dc2bf02-9b19-4f88-8235-43867813310en%40googlegroups.com.

[Stephan Weinberger]

Hoi Aloy,

Croft hat nicht unrecht. Heutzutage hängt an jeder 2. Mail irgendein Attachment dran, von Firmenlogo bis zu wasauchimmer sich Ausguck und Gemehl einbilden anhängen zu müssen.

Prinzipiell sind Attachments in Mailinglisten eher unüblich (außer solchen die den expliziten Zweck haben Binaries auszutauschen). Ein Problem ist z.B. dass Attachments in aller Regel weder durchsuch- noch zitierbarbar sind.

Dazu hast du's auch noch ohne Dateiendung und/oder korrekten Mimetype angehängt, wodurch die meisten Mailprogramme auch nix damit anfangen können. Abspeichern + in externem Editor aufmachen (ohne zu wissen was drin steckt) ist dann einfach eine unnötige Hürde.

Also: durchatmen, in sich gehen (da hat man's ja nicht weit), Text einfach in den Mailbody schreiben.


Die meisten dieser Warnings scheinen auch recht trivial zu sein (oder schlicht und einfach egal), also könntest Du ja auch selber drangehen sie zu fixen ;-)

lg
  Invis (die imposante Helferrolle auf diese Liste erweiternd)

To view this discussion visit https://groups.google.com/d/msgid/ldmud-talk/0dc2bf02-9b19-4f88-8235-43867813310en%40googlegroups.com.

[Aloy]

löscht den thread einfach. ich machs bei zu selber, brauch ich mich nicht mit menschen rumärgern...

[Nico Kammel]

Okay, this was what is called a failure of communication!

I think we should take a moment to reflect on what happened, what we can learn from it, and what we could improve in the future.

1. A participant who was relatively inexperienced with using this mailing list pointed out potential issues in the core product. Unaware of the unwritten rules, she phrased some things rather unfortunately and placed the relevant information in an attachment to avoid making the email excessively long. This was certainly not ideal, but it was hardly a reason to react so strongly.

2. She was dismissed in one of the most unnecessarily unfriendly ways I have read in a long time—and professionally, I deal with very frustrated customers on a regular basis. Instead of explaining the issue in a kind and constructive manner, the response was needlessly harsh.

    

   Something along the following lines would have been far more helpful:

   “Thank you for reporting this. I’ll take a look when I get the chance; perhaps we can investigate it together.

   That said, please be aware that attachments are generally discouraged here for several reasons—especially when they are not correctly MIME-encoded, do not have a file extension, and the email itself does not explain what the attachment contains. In the future, please include a brief description of any errors or warnings directly in the body of the message. It is perfectly fine if the email becomes quite long; that is what the mailing list is for.

   You should also take a look at the netiquette guidelines: ”

3. This led to a brief but intense outburst from all sides, ultimately resulting in the original poster leaving the mailing list.

What can we learn from this?

1. We should not assume that everyone reading the mailing list is familiar with its unwritten rules.
2. If someone unknowingly violates one of those conventions, we should respond constructively, explain the expectations, and help them understand the established practices.

3. Before replying, we should read the message, step away for a moment, take a breath, read it again, and then draft our response. After that, we should step away once more, take another breath, reread what we have written, and ask ourselves:

    

   Would I be comfortable if the recipient’s partner, parents, children, or employer read this message?

    

   If the answer is no, start again. If the answer is yes, send it.

Unfortunately, incidents like this are precisely what cause the DACH MUD community to be viewed in such a negative light. Similar situations also occur within individual MUDs when people fail to follow unwritten rules.

I was told—although I was not present—that one MUD administration once insulted and forcibly removed a player who had returned after several years away simply because he used umlauts in everyday communication, while that particular MUD proudly refuses to support them. He was driven away almost immediately. Unfortunately, reports of this kind are not uncommon.

If we drive people away even from a public mailing list, we should not be surprised when newcomers decide not to engage with the community.

I have relatively little direct experience with other MUDs these days, and I usually hear about such incidents only indirectly because running my own MUD already keeps me more than busy. However, I do remember similar behavior from the time when I played extensively on several different MUDs.

I think we should all take this as an opportunity for improvement: we should treat newcomers more kindly, point out mistakes in a constructive way, and offer suggestions for improvement. That is what helps everyone move forward. Kindest regards Nico

To view this discussion visit https://groups.google.com/d/msgid/ldmud-talk/ec47c757-7927-4a97-970b-711d1f6f5cd4n%40googlegroups.com.

[Simon Lundmark]

I think most, if not all, of these warnings were solved in: https://github.com/ldmud/ldmud/pull/151

Simon

To view this discussion visit https://groups.google.com/d/msgid/ldmud-talk/cad6d412-6b1a-4d71-90a8-b4690b0ab8e4%40googlemail.com.