u801e

98 ms·

961.
by u801e 6y ago
Some websites accept them when creating an account, but not when trying to log in with that account.
962.
by u801e 6y ago
> Yes, but python packages are not for distributing that kind of software. Where is that documented? The fact that setuptools and distutils.core supported building RPM packages from a setup.py file indicates that python intended to supp
963.
by u801e 6y ago
> Wheels don't, and shouldn't, replace RPM or deb packages Part of the motivation for using wheels in our case was to allow for pulling in later versions of certain python packages as part of the dependency resolution process w
964.
by u801e 6y ago
> Today I spent at least an hour fighting with Python packaging. The more I think about it, the more I feel that self-contained static binaries are the way to go. Trying to load source files from all over the filesystem at runtime is hel
965.
by u801e 6y ago
> Is it desirable for a distributed Python package to write files to a hardcoded absolute path? The established behavior of python setuptools when creating an RPM spec file via the bdist_rpm command was to create a spec file that would i
966.
by u801e 6y ago
One thing I found when converting our python application packaging from RPM to wheels is that wheels don't properly handle the data_files parameter in the setup call. That is, it places files under the python library directory instead
967.
by u801e 6y ago
> However, startups don't fail because the codebase is ugly, or convoluted, or not following best practices. Could they fail because they fail to meet deadlines due to convoluted or buggy code or having to invest more money and time
968.
by u801e 6y ago
On some platforms, the emoji is so small that is difficult to determine what it is, let alone what it's supposed to represent.
969.
by u801e 6y ago
How does that compare with https://old.reddit.com ?
970.
by u801e 6y ago
> The wetware component enforcing some line length - some old maintainer stuck in his ways You need to be more specific about what you're referring to when you bring something up. I already stated that email clients can be set to u
971.
by u801e 6y ago
>> there's nothing in git commits or the code itself that forces wrapping at 80 characters > Very clever leaving out the third component here that does force it. Which component is that? The SMTP protocol? According to [1],
972.
by u801e 6y ago
> How? That workflow assumes a 80-char b/w terminal for the most part. There's nothing stopping you from using a gui text editor to edit the code and there's nothing in git commits or the code itself that forces wrapping a
973.
by u801e 6y ago
I'm pretty sure that most people would prefer their code hard-wrapped at a certain line length.
974.
by u801e 6y ago
> I don't like the process because it has so many issues And you still haven't described any of them. > It's just hostile in so many ways if you aren't using a VT-100 That's a strawman. At some point, you&#x2
975.
by u801e 6y ago
> About your "for email all I need to do is": this looks simple and neat (and even then, does it really?) when you already know how it works At one time, I didn't know how it worked, but I read through the documentation (m
976.
by u801e 6y ago
> that process is obsolete, cumbersome, finicky and convoluted. It just sounds like you don't like the process since you apparently aren't able to express a specific issue with it. Here's what I don't like about Githu
977.
by u801e 6y ago
> As I said above, if your code is loaded down with tons of long lines of code, it's likely a symptom that something else is wrong. If code is difficult to read, it's bad code. Isn't perceived difficulty of reading code co
978.
by u801e 6y ago
> so bad it locks most people out. Could you specifically describe why it locks most people out? > I did contribute to Git, and the experience was horrible. What was bad about it? > The amount of time spent on the mailing part was
979.
by u801e 6y ago
Github provides an email to Github comment gateway. So he was composing his replies in his email client.
980.
by u801e 6y ago
The C128 did have a 80 character mode[1]. [1] https://www.c64-wiki.com/wiki/Commodore_128
981.
by u801e 6y ago
This is what Linus has said in the past regarding soft-wrapping: https://github.com/torvalds/linux/pull/17#issuecomment-56611...
982.
by u801e 6y ago
Well, the C64 had a 40 column display width for the BASIC interpreter, but I think it was possible to have statements that wrapped and could go up to 80 characters (I may be wrong about that though).
983.
by u801e 6y ago
I find as I get older that I need to use bigger fonts in order to easily read code. Based on my terminal font, I can fit two windows side by side with 90 character line lengths, but if I have 3 windows, it would go down to 60 characters (t
984.
by u801e 6y ago
> I think you're imagining some kind of TLS framework that simply doesn't exist currently. It's not clear if you're misunderstanding what exists now, or you're alluding to a different possibility without clearly
985.
by u801e 6y ago
I realize that now. One way to mitigate it would be to have the browser somehow tie a given client certificate with a particular website. That is, the client cert for news.ycombinator.com, would only be presented if I try to connect with
986.
by u801e 6y ago
> That is not how TLS works. A server can trust a client based on the certificate the client presents. A client can't distrust a server based on the certificate the client presents. You're correct; I posted inaccurate informati
987.
by u801e 6y ago
~~It wouldn't work because the phishing site would lack the private key needed to validate your client-side certificate and the TLS connection would not be established. This is assuming that the legitimate website itself signed your c
988.
by u801e 6y ago
> The URL bar is helpful to fighting phishing attacks It would have been nice if client side TLS certificates were more popular. Then your browser could warn you that you're not using your client cert when connecting to a certain w
989.
by u801e 6y ago
Unless you're talking about a protocol other than SMTP, all message headers and the body are sent during the DATA phase.
990.
by u801e 6y ago
I was thinking more about encryption at rest as opposed to in transit, but you do make a good point.

More ›