@Craig
antifeatures are a type of warning.
Why keep it around when it looks more like a mark rather than a solvable
warning for the userbase?
- It can be seen as a form of criticism that is not actionable;
- its aggressivity implies malice rather than design choices;
- it is a "technical" term, easy to misunderstood outside USA;
- quite dismissive, could alienate/discourage the developers.
Imagine being a developer, and the FSF puts an "Anti-feature" marking on your
app.
It doesn't exactly convey the idea of "collaborating to solve a potential
issue".😬
I think it would be wise to limit the usage of the term Anti-feature in
FSD-related terminology.
@David
I suggest that we
renamehttps://directory.fsf.org/wiki/Free_Software_Directory:Antifeatures
tohttps://directory.fsf.org/wiki/Free_Software_Directory:UserNotifications.
No, mind that notice and notification have two different meanings. I wrote "User Notice",
not "Notification".
Notice conveys a sense of formal or official information written with careful
thought, rather than just any random alert or message produced automatically.
In particular, I've suggested the term Notice because it prevents confusion
withhttps://directory.fsf.org/wiki/Template:AdministrativeNotification, which I've created in the
past to leave visible tracks of the most important administrative actions toward users and entries.
It also prevents confusion with the existing user alert system internal to MW, which has been
renamed from "Echo" system to "Notifications" system.
To prevent any kind of present and future confusion, pick "UserNotices" in place of
"UserWarnings" or "UserNotifications".
~Lorenzo