= 27d567bc2d48d9f40e9ccc20ea370b15)
falenas108 comments on Creating a Text Shorthand for Uncertainty - Less Wrong Discussion
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (29)
While this sounds like it would be useful, it would also turn a lot of people off to the site ~i4
I'm not suggesting that we make this a mandated LessWrong policy, but I think it may be fun to play with personally ~i4. I imagine that something more sensical would be created after some thought and work ~i2.
Also it could make a lot of sense for an organization to accept a standard like this rather than a blog community. For instance, many startups or EA orgs already use a lot of internal jargon ~e3i2, so something like this doesn't seem like a clear negative in that light ~i2.
Concerning the appearance aspect, it may be possible to hide the phrases (similar to the markdown mention earlier) with a small symbol that one could "inspect" when interested.