Forgot your password?
typodupeerror

Comment: Re:Lacking Credibility (Score 1) 149

by segedunum (#48149285) Attached to: ISPs Violating Net Neutrality To Block Encryption

It means you've routed out your ISP through a peering point that isn't Level3, and that the peering point between your VPN provider and L3 is less saturated than your ISPs. That's all it proves.

I'm afraid that possibility has been discounted. Netflix has paid up. Didn't you get the memo?

Thus, if you are connecting to tcp/25, it is safe to assume, in this day and age, that you *are* an MTA.

Nope, it isn't safe to assume that. If that was the case then this traffic would be blocked completely, but it isn't, and what's more it is being modified. Do read the article.

Comment: Re:Lacking Credibility (Score 1) 149

by segedunum (#48142899) Attached to: ISPs Violating Net Neutrality To Block Encryption

When the original article cites as its first example of network tinkering the already thoroughly debunked "faster Netflix through my VPN" video, the level of technical credibility to the article is already set at "abysmal". There's no argument that the VPN tunnel was faster (obviously), but the alleged reason (which many sites, including this fine establishment, got on the bandwagon for, even though they should know better) was horseshit.

It's really quite simple. If you have a download speed topping out far lower than your maximum and you then connect through a VPN and get more available bandwidth then there is a rabbit away somewhere. Netflix have already now paid up anyway to get rid of this 'issue' for their users, so that debunks this bit of dog shit.

Second, the article demonstrates the problem with a connection to tcp/25. Unless the customer is running a mail *server* on their residential ISP line, they should be connecting to tcp/587. The wireless provider in question here is absolutely within their bounds to say "they don't want you running an SMTP MTA on the wifi", but that running a normal MUA is fine. Is there any evidence that this problem also exists for connections to tcp/587?

Connecting to something on port 25 and allowing inbound connections to something you have running on port 25 are two entirely different things. If you don't know that then you really don't know anything at all and frankly aren't qualified to comment.

Comment: Re:Systemd (Score 1) 993

by segedunum (#48105791) Attached to: Lennart Poettering: Open Source Community "Quite a Sick Place To Be In"
I'm afraid it's become clear that Lennart has a lot of very serious personal and possibly mental issues that mean he just isn't suited to working with others. The progress of systemd will mean that eventually there will be a serious conflict with the kernel developers, amongst others.

Comment: Re:it solves some unicode issues (Score 1) 763

by segedunum (#48100701) Attached to: Systemd Adding Its Own Console To Linux Systems
It's exactly the kind of misdirection and smoke-and-mirrors you get from the systemd crew every time a serious shortcoming is brought up. It's a pretty serious mental issue. Oh, and yes, having to deal with a corrupted Windows Event Viewer is exactly like this is going to be. Something you should just not have to deal with.

Oh, and I can already search my text logs in a 'fine grained' and searchable manner thank you very fecking much. I know that might come as a big fricking shock, but a lot of people are.

Comment: Re:Is this a troll about systemd or is this real n (Score 1) 763

by segedunum (#48097669) Attached to: Systemd Adding Its Own Console To Linux Systems
It's a Lennart Poettering meltdown and accurately exemplifies the problems people have with him, those around him and why people are justifiably concerned about the software he is being allowed to write. This guy simply has 'issues'.

If he believes he's going to take on Linus and the kernel developers, stamp his feet and take over the Linux landscape he's going to lose badly.

Heuristics are bug ridden by definition. If they didn't have bugs, then they'd be algorithms.

Working...