Account
HN Best Comments

HN Best Comments

Comments from https://news.ycombinator.com/bestcomments Source code: https://github.com/border-radius/hn-best-comments

Username
@hn_best_comments
Category
Technologies
Created
, 7 years
Subscribers4,393+23 in 1 day
Avg views per post, 7d528last 7 days
ERR12.03%last 7 days

Subscribers, 30 days

Nov 15 – Nov 16+23 (+0.5%)

Show as table
DateSubscribers
Nov 15, 20264,370
Nov 16, 20264,393

Average views per post by day

By publication day

Show as table
DateAvg views per post
Nov 14, 2026696
Nov 15, 2026545
Nov 16, 2026190

Most viewed this month

  1. 01

    Re: LibreOffice actually works 365 days a year Well, OpenOffice wouldn't print on Tuesdays: “ What a fascinating bug!! My wife has complained that open office will never print on Tuesdays!?! Then she demonstrated it. Sure enough, won't print on Tuesday. Other applications print. I think this is the same bug. Here is my guess: Print to a postscript file. Observe the line: %%CreationDate: (Tue Mar 3 19:47:42 2009) Change "Tue" to anything else: %%CreationDate: (XTue Mar 3 19:47:42 2009) Save the file and it prints. Tools like evince work because they simply omit the "CreationDate" tag to begin with. Now something odd happens when my cups script (I am using the Brother MFC420CN) copies the file to a temp file. Some of the code is rearranged, not sure how or why, but it uses a command called "file" to identify the file as "PostScript". This check would work on the original file you printed, but by the time it runs the check on the temp file, it misidentifies. Normally it would return: PostScript document text conforming at level 3.0 But there is another check that happens before the PostScript check. If it finds "Tue" at the fourth byte of the file, it identifies it as: Jan 22 14:32:44 MET 1991\011Erlang JAM file - version 4.2 So it's not a problem w/ openoffice.org, cups, or the brother printer drivers. It is a bug in the `file` utility, and documented at https://bugs.launchpad.net/ubuntu/+source/file/+bug/248619. ” https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/255161... fweimer, 23 hours ago

    Link preview
    Views1.62K
    Forwards24
    Reactions—
    Comments—
  2. 02
    Views757
    Forwards5
    Reactions—
    Comments—
  3. 03
    Views756
    Forwards8
    Reactions—
    Comments—
  4. 04
    Views697
    Forwards1
    Reactions—
    Comments—
  5. 05
    Views684
    Forwards7
    Reactions—
    Comments—

Latest posts

#34845Link preview
Views121−77%vs avg
Forwards1
Reactions—
Comments—
#34844Link preview
Views166−69%vs avg
Forwards2
Reactions—
Comments—
#34842Link preview

Re: Microsoft 365 outage leads to chlorine gas poisoning of 15 hotel guests I personally operate a fairly advanced closed-loop chlorination system, and this is beyond screwed up. These systems can easily fail, and they tend to fail in a way that causes them to measure low or zero chlorine and thus overdispense chlorine. More below on why. First, this means that an operator must always ensure safety, both against excessive chlorine and against insufficient chlorine. In a commercial context, that means that a real human (or maybe a totally different sensor design, e.g. a colorimetric sensor) need to measure the pool chlorine level, preferably with a high quality titration (drop test) every day before opening the pool. They should probably record the result in pen on water resistant paper, but this part is icing on the cake. Second, hoping that an email gets noticed is ridiculous. If you do not have positive confirmation that the pool is safe to open, don’t open it. Third, the systems should be sized so that they cannot overdose quickly. The maximum dispensing rate should be such that hours of continuous operation would be required to reach an uncomfortable level, let alone a dangerous level. (Hot tubs are sort of an exception here.) Fourth, everyone should be using a reasonable amount of CYA in their pool. Even at a lowish level of 30ppm CYA it takes a lot of chlorine to become dangerous unless the operator has also lost control of pH. I realize that some codes are confused about this. Fifth, chlorine is smelly. Someone should have noticed, even just casually. Admittedly, lots of swimmers may be conditioned to stinky pools, and checking for safety isn’t their job. But the staff should notice. Sixth, the systems I’ve seen beep when there’s an alert. It’s easy to add flashing lights, too. (In fact, the system I’m familiar with automatically shuts down if it feeds for more than X minutes without reaching the setpoint, and you cannot turn this feature off. You can, however, defeat it by switching the power to the whole controller.) —- sensors —- Actual free chlorine sensors intended for pools use an amperometric probe immersed in iodide solution or gel, separated from the pool water by a fancy membrane. Free chlorine oxidizes iodide to iodine, and the sensor measures the iodine concentration. If the membrane fails (or general wear and tear or excessive pressure swings) cause the iodide to be lost, then the chlorine can’t react and the sensor reads zero (or low if there’s tiny bit of iodide left). Interestingly, these sensors are rather expensive devices that appear to mostly come from France and Germany. The Chinese vendors seem to be rebranding European parts (!), and the major US vendor is very clearly reselling a French company’s product. There are some vendors who sell a cheap (or absurdly marked up) potentiometric ORP-based closed-loop system. In my considered opinion, these are worse than useless. amluto, 4 hours ago

Open in Telegram
Views203−62%vs avg
Forwards2
Reactions—
Comments—
#34840Link preview
Views191−64%vs avg
Forwards1
Reactions—
Comments—
#34839Link preview
Views192−64%vs avg
Forwards4
Reactions—
Comments—
#34838Link preview
Views220−58%vs avg
Forwards1
Reactions—
Comments—
#34837Link preview
Views252−52%vs avg
Forwards0
Reactions—
Comments—
#34836Link preview
Views302−43%vs avg
Forwards4
Reactions—
Comments—

All posts

Connections