SoylentNews

Regarding grouping of digits (outside of specialized fields); do _not_ use either "," or ".".
During my hiatus I did have reason to look into this and found a nice little thing issued by NIST(warn: pdf)

To cut-and-paste sections 10.5.2 and 10.5.3 from it:

10.5.2 Decimal sign or marker
  The recommended decimal sign or marker for use in the United States is the dot on the line [3, 6].

For numbers less than one, a zero is written before the decimal marker. For example, 0.25 s is the correct form, not .25 s.

10.5.3 Grouping digits

  Because the comma is widely used as the decimal marker outside the United States, it should not be used to separate digits into groups of three. Instead, digits should be separated into groups of three, counting from the decimal marker towards the left and right, by the use of a thin, fixed space. However, this practice is not usually followed for numbers having only four digits on either side of the decimal
marker except when uniformity in a table is desired.

Examples:
76 483 522 but not: 76,483,522
43 279.168 29 but not: 43,279.168 29
8012 or 8 012 but not: 8,012
0.491 722 3 is highly preferred to: 0.4917223
0.5947 or 0.594 7 but not: 0.59 47
8012.5947 or 8 012.594 7 but not: 8 012.5947 or 8012.594 7

Note: The practice of using a space to group digits is not usually followed in certain specialized applications, such as engineering drawings and financial statements.

On a personal note I'm fond of doing the groupings the way that Ada (the language) encourages, by an underscore (i.e.: 10_000 , which would make a US-decimalized number be like 10_000.00 and in comma-countries 10_000,00)

Considering the eternal discussion of whether to filter the ACs or not...

It would be nice with a set of filters that would allow for boolean filtering and for that matter having a chain of filters.

For instance*:
if Friend and Flamebait then ignore; -- Rose-tinted glasses
if Friend then accept; -- Show remaining friends regardless
if AC and 1 then ignore; -- To skip all non upmoded ACs
if FOE and 4 then ignore; -- To skip most from Foes
if not AC and 1 then ignore; -- To skip people that should know better
if KarmaModifier and 3 then ignore; -- Ignore regulars without upmoding
if not KarmaModifer and not AC and 2 then ignore; -- To ignore occasionals without upmodded
if Self then ignore; -- I tend to remember what I write

Also, allow one to set up multiple named chains and allow to select one where one choses the threshold and such anyways - it would allow one to easily switch between showing everything in a post with only a few comments and only see the goodies in a post with 200+ comments.

* = Collapse would probably be the behaviour rather than ignore, but the wording "ignore" would have the advantage of not implying that it will mess with what comments are expanded/collapsed in the normal mechanics. However the use of ignore would probably at some point cause a request for "hide" or "obliterate" to not even see the headers.

The new "reply to" and "parent" buttons - I just can't seem to get used to them, probably since I associate buttons with forms and there really isn't a form associated to them.

The new gradient in "Title-bars" is too steep for two-line-headers, when setting the gamma to be proper to show the first line the second line feels "washed out" and the text becomes slight blurred, when setting the gamma to be pleasant for the second line the contrast becomes harsh on the first line... However I can see why this causes an issue since the gradient for single-line-headers are just right.

Just my own musings about this..