brokenparser

Fuck you. I'm out.

You have no idea how depression works

Doesn't make sense because Squirrelmail is also written in PHP and it's pretty solid. The next version will use HTTP-only cookies to further harden against attacks.

Spiritual sequel to SL, so this time the flying dicks are to be worshipped?

Then they should call it Opera 3.24, or -1 and count backwards from hereon.

I'd tell them how horrible the "modern" laptop is and how we'd have to turn things around in order to prevent wasting away all that research for decades to come.

I'd show them this video: http://vimeo.com/71278954

Does it still come with mail and bit torrent clients?

Windows actually supports using / as a path delimiter. If a program is (following the robustness principle) liberal in what it accepts (both / and \\) and strict in what it sends (just /), it'll work (barring any other issues).

There exists "gjs" and "js" ("smjs" in Debian), both of which are being maintained.

What are these so-called "fast lanes"?

> The really amazing thing here is that they've disentangled IE from the base Windows

Calling bull. MSIE has never been "entangled" with the OS and this has in fact been proven in court ( http://www.justice.gov/atr/cases/f2600/2613g.pdf pages 283 through 288 are especially noteworthy). The integration was merely a scam to defeat Netscape.

Here's a bunch of standalone versions from 1996 to 2002 (made by MSFT themselves) which can all run side by side: http://browsers.evolt.org/browsers/archive/ie/win32/

On the same site, you can find MSIE for HP-UX and Solaris.

Say "Torvald" one more time.

I'm eagerly waiting for Scientific, but there's no word on when to expect it that I know of

This wouldn't happen if those ISPs didn't have local monopolies. Networks should be opened by selling traffic wholesale to other companies so that they can compete for subscribers on those networks. The network owners would have more than enough money for upgrades and if they don't, downlevel ISPs will sue them.

I thought there should be a Gulp plugin, and then I found this: https://www.npmjs.org/package/gulp-uncss/

What could possibly go wrong?

> These are gold.

But not English, I can't make sense of them.

From the video:

> There's also a rich syntax highlighting

> invokes vim

Durrrrr

> Why did that fridge even have code that allowed it to send email?

If it has a remote code execution vulnerability, it's trivial to make it send spam (or do all kinds of things) whether a MUA was already present or not.

> especially when GitHub lives on top of a tool designed to avoid SPoFs

You're saying it as if it were a bad thing.

Imagine that, being able to sell each addy in a ::/32 for a cent each. You'd practically be the entire economy at that point.

I love Duck and the focus on privacy it has, but lately I've been using searx and had more success with it than ddg given the same queries. You can find running instances here: https://github.com/asciimoo/searx/wiki/Searx-instances

If you can mount it (w/ write permissions), you can push to it. Most companies already have a networked storage place.

Web dev here. There should be a gulp plugin for that.

You can at the very least send each other a zip file containing the .git directory. When you extract that directory into a separate directory, you can add it as a remote and fetch/pull from it (because that's the entire repository right there).

What I usually do is I copy the .git to another name before running zip, so it doesn't extract as .git :)

This is also one of the reasons you shouldn't commit binaries, especially large ones.

> Colocating equipment at head ends isn't a solution, because 1) not every provider will colocate, so if you can't preference colocated streams over non-colocated streams from other similar services, there's much more impact on other users

I've read this 10 times but I can't follow. In particular, who is this "you" exactly? And what kind of impact?

2) it might not be feasible to offer third-party colocation in every part of your network where there is bandwidth oversubscription.

This is not a concern for net neutrality but rather the individual ISPs. No ISP is obliged to offer any kind of hosting whatsoever.

> Terms like "net neutrality" and "reform" are often used to trick an audience into agreeing with the speaker by having the listeners fill-in-the-blank with their own favourable definitions.

That would be a sad state of affairs.

> So, when it comes to state action, "net neutrality" will mean whatever the government says it means

I'm no expert, but I don't think this accurately depicts how the legislative branch works.

> Your definitions won't matter once the bill is passed and/or the regulatory interpretation is promulgated.

Chillax, you appear to have a very grim view of your nations governance. That's fine and all, but it doesn't change what net neutrality is about so I'm not really sure how this is relevant. TFA opposes the FCC in the interests of net neutrality and more often than not, people have wildly varying ideas about what that means for service providers, content providers, and subscribers.

Yes, there's no one true definition of a free market but to say there's a logical contradiction rather strikes me as a jump to conclusions. What I meant was, impeding the flow of packets to or from competing networks prevents free trade on the Internet. It's easy to get the two mixed up, but the parallels between net neutrality and the rise of free trade in the 18th and 19th century seem realistic imho. I'm no historian though, merely biased by being on the content provider side of the fence.

There may be some misconceptions here, so I'll clarify a few things just in case:

1) Net neutrality doesn't mean everyone gets the exact same speed. ISPs are free to offer a plethora of offerings each with their own price, speed and extras (if any). There are also no new guarantees to subscribers, i.e. if the wiring is crap deal with it.

2) CDNs have nothing to do with net neutrality. A typical large ISP will offer co-location services and content providers may use the service the same as any other customer. There can even be other arrangements as they see fit, but the important thing is that no one messes with the tubes.

3) Again, just in case because this is brought up a lot, ISPs can still offer filtered subscriptions. There's a market demand for filtered subscriptions and catering to that demand is fair game.

4) ISPs are still free to apply filters on traffic in the interests of maintaining their network. This is important for example when dealing with (D)DoS attacks or worm outbreaks.

Net neutrality levels the playing field for content providers, so if you get VoIP from your ISP the service may still be better than that of a given competitor by virtue of having less latency. But what the ISP cannot do is artificially inflate their advantage, as doing so would be in violation of a free market on the Internet.

EDIT: disambiguated things

Luckily, Javascript is always allowed in PHP projects and it can do a lot more today than it could a decade ago. Also, using it will often lead to having NodeJS on the server even if it's just for compiling assets initially.

And NodeJS is bad ass rock star tech: http://www.youtube.com/watch?v=bzkRVzciAZg