Hacker News new | ask | show | jobs
by es3n1n 395 days ago
This is a somewhat useful feedback, however I am not too sure how this can be fixed given the structure of my blog post. Do you think if I just add a line `*WSC is short for Windows Security Center` in the first paragraph this will be enough?
4 comments

My suggestion:

In this post I will briefly describe the journey I went through while implementing defendnot, a tool that disables Windows Defender by using the Windows Security Center (WSC) service API directly.

thank you! i changed the first paragraph to include these changes
Ah that makes sense. I saw this subthread and was quite confused because WSC was clearly and obviously defined in the first sentence.

Now I see why. Thanks for incorporating the feedback! It had a positive impact for me coming later to this article.

Appreciated, thank you!~ \( ̄︶ ̄*\))
Or use the abbr (and its title attribute) that was designed for that purpose; no extraneous "flow" breaking required. Mobile people can long press on the indicator to read more, everyone who magically knew what WSC gets to continue to know what WSC means

https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/...

The typical solution, is to include the expansion in brackets after the first use.

Simple rule I learned on my Electronic Engineering degree (where we're guilty of many, many acronyms): When you write an acronym/initialism in a paper (or anywhere for others to read reall), assume the reader doesn't know what it stands for and include the expansion in brackets immediately after the first use.

EDIT: As my sibling comment also suggests, writing it in full the first time, and using the acronym/initialism in brackets is also acceptable.

Just wondering is this Slack? Just wondering what kind of logging flow you’re using.

https://blog.es3n1n.eu/posts/how-i-ruined-my-vacation/pics/p...

Looks like Discord.
this is discord in "Compact" theme