5 ms·

Curious - so what was the problem with their server configuration?

by cuu508 5y ago

kingcharles 5y ago
What's weird is that your comment here caused some sort of weird bug in HN that I've not seen before (no reply button): https://kingcharles.one/weird-hn-bug.png https://kingcharles.one/weird-hn-bug.png @dang - any ideas on this one? The issue with Plausible's server: I didn't want to put it out there because then they get the fix for their commercial product for free after I spent the time doing all the work for them, but I feel like the same bug might actually exist all over the Web, so I'm going to write it up and post it online.
- forty 5y ago
  I think HN somehow limit the pace of answers in fast threads to let people the time to think before they post (so the reply button appears with a bit of delay)
  - sokoloff 5y ago
    If you really must blow through the delay, click on the timestamp of the post you want to reply to and the reply box will show there.
    - kingcharles 5y ago
      That's what I did to reply, but I've never seen one person's reply link missing when all the others are visible.
- johnchristopher 5y ago
  > The issue with Plausible's server: I didn't want to put it out there because then they get the fix for their commercial product for free after I spent the time doing all the work for them, but I feel like the same bug might actually exist all over the Web, so I'm going to write it up and post it online. Yeah, no. So far, you only say there's a bug in their server configuration that prevents logging in some cases. I self host plausible and I'd be very much interested in what misconfiguration I could have triggered. Is it a TCP pool connection problem ? A pre-flight request thing ? Wrong CORS headers ? On one hand you could be doing FUD, on the other there is a gunfoot problem that could impact self hosters but the knowledge doesn't come out. I suppose it's a problem that can be pinpoint from the outside, without knowing the proxy stack running at plausible so it should be observable with HTTP sniffer/wireshark.

Curious - so what was the problem with their server configuration?

by cuu508 5y ago

Curious - so what was the problem with their server configuration?

What's weird is that your comment here caused some sort of weird bug in HN that I've not seen before (no reply button): https://kingcharles.one/weird-hn-bug.png https://kingcharles.one/weird-hn-bug.png @dang - any ideas on this one? The issue with Plausible's server: I didn't want to put it out there because then they get the fix for their commercial product for free after I spent the time doing all the work for them, but I feel like the same bug might actually exist all over the Web, so I'm going to write it up and post it online.

forty 5y ago
I think HN somehow limit the pace of answers in fast threads to let people the time to think before they post (so the reply button appears with a bit of delay)
- sokoloff 5y ago
  If you really must blow through the delay, click on the timestamp of the post you want to reply to and the reply box will show there.
  - kingcharles 5y ago
    That's what I did to reply, but I've never seen one person's reply link missing when all the others are visible.
johnchristopher 5y ago
> The issue with Plausible's server: I didn't want to put it out there because then they get the fix for their commercial product for free after I spent the time doing all the work for them, but I feel like the same bug might actually exist all over the Web, so I'm going to write it up and post it online. Yeah, no. So far, you only say there's a bug in their server configuration that prevents logging in some cases. I self host plausible and I'd be very much interested in what misconfiguration I could have triggered. Is it a TCP pool connection problem ? A pre-flight request thing ? Wrong CORS headers ? On one hand you could be doing FUD, on the other there is a gunfoot problem that could impact self hosters but the knowledge doesn't come out. I suppose it's a problem that can be pinpoint from the outside, without knowing the proxy stack running at plausible so it should be observable with HTTP sniffer/wireshark.