durin42

22 ms·

151.
by durin42 16y ago
End-users aren't who you need to tell. Just site owners. Posting this to HN before it was fixed constitutes (IMO) completely irresponsible disclosure.
152.
by durin42 16y ago
That actually sounds like an awful way to report an XSS. Honestly, as someone that maintains a web service I have to say I'd prefer private disclosure than even the rickroll approach. All it takes is one "genius" doing some copy-paste actio
153.
by durin42 16y ago
See also http://news.ycombinator.com/item?id=2001565
154.
by durin42 16y ago
Wow. I've had nothing but great experiences with the no-contract option on T-Mobile. Signup was completely trivial, have had no complaints about the service. It's been a very real savings. What do you mean, you can't sign up for a contract?
155.
by durin42 16y ago
I heard the same thing said about the atrocious security theatre at airports, especially the really busy ones like O'Hare. It was going to be temporary, I heard, because there was no practical way it could be permanent. It's been 9 years. F
156.
The Case Against Data Lock-in(queue.acm.org)
6 points by durin42 16y ago|2 comments
157.
by durin42 16y ago
He's defending against None with the assert l and len(l) bit, or at least that's what I'd assume.
158.
by durin42 16y ago
I'd recommend pretty strongly against the AGPL. I know it sounds good when you want to "screw $megacorp," but it actually has all sorts of legal wrinkles in it that make ensuring compliance almost impossible in some cases. The end result is
159.
by durin42 16y ago
AGPL does have some pretty deep flaws. See [0] for a description of some of the problems. I can't say I'd ever touch AGPL code with a 10 foot pole, simply because I've talked to lawyers about it and it's unbelievably messy (add to that the
160.
by durin42 16y ago
I use unison for my code repositories (I use dropbox for other things) and I don't bother with it in cron. It's been fast enough in my experience that I don't mind waiting, and it sometimes (rarely) requires manual conflict resolution.
161.
Google Application Utilities for Python(code.google.com)
2 points by durin42 16y ago|0 comments
162.
by durin42 16y ago
Honestly LTS releases are only viable for 3 years if you're OK with 3 year out of date versions of software. They never import new major versions of anything , so you're stuck with whatever (eventually old and crufty) version you got. Hard
163.
by durin42 16y ago
Agreed about battery life. If I turn off data syncing and don't use my Nexus One as a smartphone, but rather just a normal phone (eschew browsing and so forth other than a quick "where's my stop on this unfamiliar public transit?") I get mo
164.
by durin42 16y ago
Is that open-source anywhere? That's actually pretty slick.
165.
by durin42 16y ago
Personally I still use Etherpad more than Wave through the open source implementation.
166.
by durin42 16y ago
YouTube still uses Python extensively.
167.
by durin42 16y ago
I'm not sure I understand the obsession with speed here - at some point isn't the RPC latency going to be the dominator rather than the encode/decode time? Shouldn't we be really close to that already for well-designed applications without
168.
Experimental libdispatch mpm for Apache(libdispatch.macosforge.org)
1 points by durin42 16y ago|0 comments
169.
by durin42 16y ago
I still think you need to be much clearer here. _Nothing_ about Mercurial is unsafe - mq has dangerous edges, and we're aware of that. I'm trying to design something that's more flexible and safer than mq, but these things take time. Le
170.
by durin42 16y ago
With respect to his claim hg lost data for him, he was using mq without really understanding it or using a versioned queue. mq is disabled for a reason, and he enabled it without fully understanding the risks and ways of mitigating those ri
171.
by durin42 16y ago
On my FreeBSD 8 machine, grep is still GNU grep. Last I knew, bsdgrep wasn't quite finished, but was close. diff is from GNU diffutils, but patch appears not to be a GNU variant. bc/dc are GNU. Getting really close though. The compiler was
172.
by durin42 16y ago
I'm wondering if we can't capture some of what C4 was without the Mac focus and keep some of that magic alive, but I'm not yet sure. It really was a great thing - I'll miss it greatly if nothing rises from the ashes.
173.
by durin42 16y ago
Yeah, mixed-rev working copies are a huge pain in the rear. They make a lot of problems for conversion tools when you commit from them, I can't imagine writing a server to deal with them even remotely sanely. What does the Git DAG end up lo
174.
by durin42 16y ago
This is decidedly not the same as the internal guide. 2-space indents are the norm, and functions_like_this are supposed to be spelled FunctionsLikeThis (yes, with the leading capital). Those are the two big differences from PEP8 that I c
175.
by durin42 16y ago
Many have said so, and I don't know if you'll check this thread, but many many thanks for this library. I've only ever used it on internal tools (and the ones worth sharing belong to my now-former employer), but it was really a joy to work
176.
Scalr - automatic scaling for ec2(code.google.com)
18 points by durin42 17y ago|1 comments
177.
by durin42 17y ago
Yeah, that objective-c extensions (and objective-c++ even moreso) thing went so well for FSF too. Apple still ships a forked version of GCC (and binutils for that matter) because FSF never actually took all the patches, so I fail to see
178.
FreeBSD built with clang now selfhosting - testers wanted(permalink.gmane.org)
87 points by durin42 17y ago|20 comments
179.
by durin42 17y ago
wakelocks solve a very specific power management concern. Historically power management in Linux hasn't been tightly integrated with apps, which is desirable on a smartphone.
180.
by durin42 17y ago
I think DiBona's position was and is eminently reasonable. As I understand things, the Android team tried to upstream wakelocks, and the kernel maintainers basically said no, but without any proposal for something better. To my mind, that's

More ›