I didn't feel I was being unreasonable asking for free use of their product for a year (after which I would obviously have to pay), for a web app I am writing which currently has practically zero traffic. As bug bounties go, it wasn't a bad deal I thought.
It is a real shame. I went to Plausible because they had posted on here, and I'm all for supporting people that show up on HN and seem to be decent human beings. They did not reply to my Tweet to them, I only got support through e-mail, which they weren't that quick about. I'm bummed because the software seemed to be what I wanted, but they've lost my trust now.
@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.
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.
Now, of course, products have bugs and once you have thousands of users there will be edge cases if it not working. Obviously, they should have handled the interaction with you differently.
Out of interest, can you expand more on when the bug occurs? Btw, if you have a fix for it, you can also create a PR.