The case of "dead end" closed topics becoming dangerous

How is this handled?

I was looking for something today related to wiznet w5500 chips and stumpled on this thread, the top result actually.

The last post before the topic got closed is absolute drivel yet the thread can't be reopened to add something about it to warn people about it.
The person though probably being well meaning shoves an IP instead of a mac in the ethernet.begin() method , then reads the mac address from the ethernet object and is convinced he's reading a hardware mac.

This kind of information is plain dangerous. Either he's reading leftover junk in that piece of memory or what he reads is something fixed based on the IP he gave as a parameter.
People thinking "oh cool, i can extract the mac from a w5500 this way will either be using junk data as a mac or will be creating duplicates.

How is people writing some drivel before an auto closure to a thread handled?

1 Like

By asking a moderator, politely, with properly worded reasons, to open the thread so you can add an explanatory post. One. With no hyperbole, no criticism, just the facts.

If you want a topic reopened then flag it for the attention of a moderator as "Something Else" with a brief reason. If it is felt reasonable then the topic will be reopened and you can add to it

Implying it's me that "wants" something?
I need to be wearing kid gloves and knock quietly wearing socks at mom and dad's bedroom door?

Ok. Thank you for the clarification.

This seems reasonable. I'll give it the one go.

1 Like

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.