HackerTrans
トップ新着トレンドコメント過去質問紹介求人

craftyguy

no profile record

コメント

craftyguy
·7 年前·議論
They would be screwed if google decided to actively cut off downstream chromium projects by making breaking code changes, licensing changes, etc.
craftyguy
·7 年前·議論
The ext4 folks are working on adding case-insensitive support... https://lwn.net/Articles/784041/
craftyguy
·7 年前·議論
It's not silly. Google 100% controls upstream chromium, and they can afford to make decisions about it in a vacuum.
craftyguy
·7 年前·議論
chrome has far more ads, they are just more subtle.
craftyguy
·7 年前·議論
IMAP is fine. It's likely your email provider's fault.
craftyguy
·7 年前·議論
.. what does this comment have to do with the actual article other than keying off of 'fastmail' in the title?
craftyguy
·7 年前·議論
I think the point OP was trying to make was that they should invest in MUA support for this feature.. mutt was merely an example.
craftyguy
·7 年前·議論
And here we have a great example of an obvious, uh, violation of this HN guideline:

> Please submit the original source. If a post reports on something found on another site, submit the latter.

Clickbait blogspam, right to the top! Nice work HN!
craftyguy
·8 年前·議論
> does this make you consider switching back at all

No. I'm old enough to remember the way Microsoft operated for most of their history, and do not trust them.
craftyguy
·8 年前·議論
Well, you cannot patch the vast majority of the software in your computer (assuming you are like the vast majority of users using proprietary crap for everything). That does not mean it is all unpatchable. If supermicro care, they could release a BMC update, for example.
craftyguy
·8 年前·議論
> You can't patch it.

Sure you can. OEMs regularly release patches for platform BMCs.
craftyguy
·8 年前·議論
Yes, I know, but commas!
craftyguy
·8 年前·議論
Wait, you must kill John Romero, or John Romero must kill you? Commas are awesome!
craftyguy
·8 年前·議論
Thank you for not breaking the non-JS use case, and thanks for elaborating on your point!
craftyguy
·8 年前·議論
> We use an express server to pre-render our text

That's silly. Unless your users are on throttled dial-up inet, and you're trying to feed them several volumes worth of text (a MB or so?), pre-rendering text on the next page is not a good enough excuse. This must mean you are using some large framework to deliver text and present your website. HN seems to be able to deliver tons of text to users without javascript bullshit, why can't you?
craftyguy
·8 年前·議論
> It is not.

That's why I put 'required' in quotes, indicating that they think it is (for the reasons you pointed out) but it's obviously not.
craftyguy
·8 年前·議論
Sending the pihole admin password in a non-https url query string seems like a bad idea. You might argue that your network is 'trusted', but then I'd remind you that this pihole device is designed to intercept all dns on your network, and would be used quite maliciously if compromised.
craftyguy
·8 年前·議論
> which is their loss

Exactly what my stance is towards sites that 'need' crap to work. My favorite are news sites/blogs whose primary content is text, but display a completely white blank page when the adblocker is up. (some even do this when you disable JS too. why JS is 'required' for displaying any text is beyond me)
craftyguy
·8 年前·議論
How did you resolve that snapchat problem?
craftyguy
·8 年前·議論
The key piece is whether curl performs hostname verification of the cert, or not. Their ssl certs page is unclear[0] (they go off into the weeds about self-signed certs). If they are not verifying the hostname, then your argument is completely off base since it's basically "you trust a person who signed a thing" vs "you trust a thing you got from someone who has a cert that is trusted by a CA on your system" (and that's pretty trivial to get considering how many 'trusted' CAs distros/OSes ship by default).

https://curl.haxx.se/docs/sslcerts.html