And what happens when Ireland, the UK, the EU etc pass laws which specifically prevent Microsoft et al from responding to such warrants when they are issued from countries where the data does not reside?
Microsoft would be between a rock and a hard place.
And how does any of that contradict or correct what I said?
One route may be less congested than another. But that doesn't mean Comcast are deliberately doing anything negative to the more congested route, so it cannot be used as a smoking gun.
The problem with treating that as a smoking gun, as the other reply does, is that you are taking the end observation and assuming that the sole cause is what you need it to be in order for it to fit your view point.
For example, its entirely possible that the peering between Netflix and the data center and then the data center to the Comcast end point is less congested than between Netflix and the Comcast end point directly.
Change the routing to something other people generally aren't using and contention for that bandwidth goes down. Its the same as taking a different route to get to work during rush hour - avoid the big roads, use the rat runs and you might cut time off your commute.
Germany, France, and the UK all decided they would do away with nuclear power.
Huh? Germany might be in a panic about it, but the UK just gave the go ahead for several new nuclear reactors in the UK, and France continues on as normal.
This all sounds very very similar to the whole BitKeeper fiasco, where Andrew Tridgell watched the traffic between a real BitKeeper client and the server in order to determine the procotol used, with an eye to creating an open source client.
BitKeeper found out and withdrew the free client licences, which was a problem since the Linux kernel project used BitKeeper at the time - due to Trudgells involvement, BitKeeper refused to supply gratis licenses to anyone working for OSDL, which included Linus Torvalds...
The shitstorm that ensued resulted in Linus starting the Git project.
You don't have to accept anything as the "truth" without supporting evidence either way, or is reasoned thinking beyond people these days? An accusation has been made, and now counter claims are coming out. No evidence either way, so its a PR exercise for all parties involved.
The typical "he said, she said". Just happening via the media.
Every story has two sides and for several weeks now Julie Ann Horvath has decided to share only the details of her side of her experiences at GitHub and the circumstances around her departure.
A few of us, those who knew Julie and the events that occurred, have decided that if Julie wants to share this story so publicly then everyone should at least have all of the story.
Here are some details that may help explain this story a little differently.
The Engineer Julie calls out an engineer in her story. The engineer she alleges harassed her was in fact an ex-boyfriend that she was still friends with at the time, not a random coworker she barely knew. They had dated prior to working at GitHub and were on good terms at the time.
The project he “ripped out” code from was a small css refactoring on an internal side project that he was helping her with. At the time of the incident, she was not upset about it and it was quickly fixed. At the time of her departure, she was not on great terms with him and her public story changed.
The Cofounder and His Wife Around the end of 2012, Julie started dating a close male friend of the cofounder’s wife and didn’t like that they were close. She asked them to stop being friends and when they would not end their relationship, Julie started telling coworkers that the wife had affairs and that the cofounder’s newborn child was not his. She told this to multiple coworkers directly and also to the wife through her boyfriend.
This is where the wife reached out to her and the rest of her story starts. All of Julie’s story involving the cofounder’s wife occurs only after Julie was spreading vicious rumors about him to even new employees.
Three months later, the first Passion Projects talk was held at GitHub. It’s difficult to know if this was a concession by the cofounder for her to stop threatening his family and undermining him to his employees, or perhaps just a way for him to try to get on her good side so she would not want to hurt his family.
We share this because reading through the TechCrunch article with this in mind changes the story for us. It seems less like a story of gender issues and more like a story of the problems that arise when employees date coworkers and cannot separate work and personal life.
We dislike that she is taking advantage of people’s trust in her in order to craft a message for which she wants to be the symbol. Good people are suffering for a story she knows is not fully true and she does not seem to care.
As the other poster says, OpenSSL isn't an OpenBSD project - what is going on here is a full blown fork of OpenSSL by the OpenBSD team, who are putting their money where their mouths are because when the heartbleed bug came out it was noted that the issue could have been mitigated on OpenBSD if the OpenSSL team had used the system provided memory allocation resources.
So this is less OpenSSL and much more OpenBSD SSL being created.
Theres a lot of evidence linking the Israelis to the South African nuclear weapons program with a lot of people thinking it was a "legitimatised" nuclear program that would only get SA into trouble internationally while Israel could walk away with a lot of improvements scot free, so if US technology and material ended up in Israeli hands, then I have no doubt equally that some of it then made its way on to apartheid South Africa.
There are also non-ASP.Net MVC frameworks based on.NET, like NancyFX, so the.NET category seems to very very wide. At a guess I'm going to assume the same for Java, as its really the same situation.
If the NTIS cannot charge for their service any longer for particular documents, they should stop providing those documents - or are they legally bound to supply the service regardless?
I think many people get stuck in thinking "one single database, thats it, my initial decision condemns me forever", when in-fact theres no shame in having many databases.
Stick the raw data into one database, choose the database that suits that.
Transform the data from the raw database into something you can use day to day, thats well structured etc, choose the database for that.
Transform the data from the day to day schemas into something that more suitable for archiving and long term reporting, again choose the database for that.
You don't have to have one single database type, every particular one has its strengths, so use them!
Theres probably an element of multithreaded access that needs to be taken into consideration here - writing to a single text file may get you into issues if the receiving webserver is multithreaded, meaning the threads will either have to queue for write locks, or write to a different file.
Database engines don't have this issue, so while it may be overkill, there may be reasons to have one irregardless.
The four freedoms are *your* ideal to aspire to, never forget that:) I'm all for people releasing their source code, if they want to - however, I don't feel people should be vilified purely because they choose not to.
Why "full" copies of Visual Studio? What does the Express editions lack that kids would need? They have access to the full capabilities of the.Net framework, a full C/C++ environment and more - the Express editions really lack the surrounding IDE features that would be lost that early on in the developer learning curve, stuff like profiling etc.
And yet on my Xbox360 I've been able to play games, movies, TV shows, access streaming services and live video for five years. How is that late to the game?
The issue with AF447 is that they disregarded *all* instrument readings, not just the ones they were trained to in the event of an air data mismatch. So they never even realised they were in danger, because they didn't think the rapidly declining numbers were true - remember that the descent was 1G, so they didn't even have any feeling of descent, which added to their mistrust of the data they had infront of them.
So as the other poster said, there was nothing to call someone about other than they didn't know what was going on, and they weren't about to admit that to everyone listening.
You must be so warped with hatred, because your posts are starting to become incoherent.
The legal issue of "reasonableness" is well tested, and it doesn't go your way (fortunately). Software cannot wear out, but the Sales of Goods Act is not about forcing an entity to support anything until it wears out, its about ensuring the product lasts for a reasonable period of time - so your car doesn't die catastrophically in two years time, so your fridge doesn't stop working a year from now, so you know that when you invest a significant sum of money into something, it can last a reasonable period of time.
13 years is a reasonable time, as is 6. And the software doesn't stop working after the EOL date, it just won't receive updates, so it hasn't even "worn out".
Its also worth noting that software does not necessarily fall under the Sales of Goods Act, or its amendments - case law in the UK provides for it as a per-case consideration, and not a standard entitlement.
I'm afraid its actually *you* who is full of shit in this case, as the Sales of Goods Act 1979 and its amendments are precisely what I am referring to, and as I have intimate knowledge of that act and its various legal successes, I can safely say that you are full of bollocks.
The Sales of Goods Act is not meant to cover a product for all eternity, for an indefinite period, until the product actually wears out or for any other purpose than to require a manufacturer to provide a reasonable life span for the product in question. The Sales of Goods Act is not even intended to require a manufacturer to fix bugs or issues past the reasonable period of support, just provide a reasonable period of support.
So lets see what other Operating Systems have endured longer than Windows XP...
Red Hat Enterprise Linux 2.1 - released in mid-2002, died in mid-2009. Red Hat Enterprise Linux 3 - released in late-2003, died at the start of this year. Red Hat Enterprise Linux 4 - released in early-2005, dies at the end of this year.
Ubuntu 6.06 LTS - released mid-2006, died mid-2011. Ubuntu 8.04 LTS - released mid-2008, died mid-2013.
OSX 10.1 - released late-2001, died mid-2002. OSX 10.2 - released mid-2002, died mid-2003. OSX 10.3 - released late-2003, died mid-2005. OSX 10.4 - released mid-2005, died late-2007. OSX 10.5 - released late-2006, died late-2009. OSX 10.6 - released mid-2009, died late-2011. OSX 10.7 - released mid-2010, died late-2012. OSX 10.8 - released mid-2012, death TBD.
Hmm, I can't see any other consumer or corporate desktop OS that has been supported as long as XP has.
So out of all other reasonable time periods for Operating Systems, XP's support length is definitely an outlier and you would get laughed out of court if you tried to force Microsoft to support it beyond its current and well known EOL date.
If you are giving any sort of legal advice based around the Sales of Goods Act, please fucking stop as you have proved that you know shit about the topic.
Slashdot Mirror
And what happens when Ireland, the UK, the EU etc pass laws which specifically prevent Microsoft et al from responding to such warrants when they are issued from countries where the data does not reside?
Microsoft would be between a rock and a hard place.
And how does any of that contradict or correct what I said?
One route may be less congested than another. But that doesn't mean Comcast are deliberately doing anything negative to the more congested route, so it cannot be used as a smoking gun.
The problem with treating that as a smoking gun, as the other reply does, is that you are taking the end observation and assuming that the sole cause is what you need it to be in order for it to fit your view point.
For example, its entirely possible that the peering between Netflix and the data center and then the data center to the Comcast end point is less congested than between Netflix and the Comcast end point directly.
Change the routing to something other people generally aren't using and contention for that bandwidth goes down. Its the same as taking a different route to get to work during rush hour - avoid the big roads, use the rat runs and you might cut time off your commute.
Germany, France, and the UK all decided they would do away with nuclear power.
Huh? Germany might be in a panic about it, but the UK just gave the go ahead for several new nuclear reactors in the UK, and France continues on as normal.
This all sounds very very similar to the whole BitKeeper fiasco, where Andrew Tridgell watched the traffic between a real BitKeeper client and the server in order to determine the procotol used, with an eye to creating an open source client.
BitKeeper found out and withdrew the free client licences, which was a problem since the Linux kernel project used BitKeeper at the time - due to Trudgells involvement, BitKeeper refused to supply gratis licenses to anyone working for OSDL, which included Linus Torvalds...
The shitstorm that ensued resulted in Linus starting the Git project.
You don't have to accept anything as the "truth" without supporting evidence either way, or is reasoned thinking beyond people these days? An accusation has been made, and now counter claims are coming out. No evidence either way, so its a PR exercise for all parties involved.
The typical "he said, she said". Just happening via the media.
You also cannot verify the credibility of the original accusation, so where does that leave us?
No idea as to the credibility of this blog, but worth a read anyway:
https://medium.com/p/d96f431f4...
As the other poster says, OpenSSL isn't an OpenBSD project - what is going on here is a full blown fork of OpenSSL by the OpenBSD team, who are putting their money where their mouths are because when the heartbleed bug came out it was noted that the issue could have been mitigated on OpenBSD if the OpenSSL team had used the system provided memory allocation resources.
So this is less OpenSSL and much more OpenBSD SSL being created.
South Africa gave up its nuclear program after the fall of the apartheid regime.
Theres a lot of evidence linking the Israelis to the South African nuclear weapons program with a lot of people thinking it was a "legitimatised" nuclear program that would only get SA into trouble internationally while Israel could walk away with a lot of improvements scot free, so if US technology and material ended up in Israeli hands, then I have no doubt equally that some of it then made its way on to apartheid South Africa.
It stood up where there was an actual contract or financially backed transaction in place, not just off the back of a random click on a website.
Classic ASP doesn't run on .NET, it was pre-.NET.
There are also non-ASP.Net MVC frameworks based on .NET, like NancyFX, so the .NET category seems to very very wide. At a guess I'm going to assume the same for Java, as its really the same situation.
If the NTIS cannot charge for their service any longer for particular documents, they should stop providing those documents - or are they legally bound to supply the service regardless?
I think many people get stuck in thinking "one single database, thats it, my initial decision condemns me forever", when in-fact theres no shame in having many databases.
Stick the raw data into one database, choose the database that suits that.
Transform the data from the raw database into something you can use day to day, thats well structured etc, choose the database for that.
Transform the data from the day to day schemas into something that more suitable for archiving and long term reporting, again choose the database for that.
You don't have to have one single database type, every particular one has its strengths, so use them!
Theres probably an element of multithreaded access that needs to be taken into consideration here - writing to a single text file may get you into issues if the receiving webserver is multithreaded, meaning the threads will either have to queue for write locks, or write to a different file.
Database engines don't have this issue, so while it may be overkill, there may be reasons to have one irregardless.
The four freedoms are *your* ideal to aspire to, never forget that :) I'm all for people releasing their source code, if they want to - however, I don't feel people should be vilified purely because they choose not to.
Why does everyone in the world have to conform to your ideology? Those freedoms are part of your ideology, nothing more.
Why "full" copies of Visual Studio? What does the Express editions lack that kids would need? They have access to the full capabilities of the .Net framework, a full C/C++ environment and more - the Express editions really lack the surrounding IDE features that would be lost that early on in the developer learning curve, stuff like profiling etc.
We still have to work around issues in newer browsers, and not just IE either :(
And yet on my Xbox360 I've been able to play games, movies, TV shows, access streaming services and live video for five years. How is that late to the game?
The issue with AF447 is that they disregarded *all* instrument readings, not just the ones they were trained to in the event of an air data mismatch. So they never even realised they were in danger, because they didn't think the rapidly declining numbers were true - remember that the descent was 1G, so they didn't even have any feeling of descent, which added to their mistrust of the data they had infront of them.
So as the other poster said, there was nothing to call someone about other than they didn't know what was going on, and they weren't about to admit that to everyone listening.
You must be so warped with hatred, because your posts are starting to become incoherent.
The legal issue of "reasonableness" is well tested, and it doesn't go your way (fortunately). Software cannot wear out, but the Sales of Goods Act is not about forcing an entity to support anything until it wears out, its about ensuring the product lasts for a reasonable period of time - so your car doesn't die catastrophically in two years time, so your fridge doesn't stop working a year from now, so you know that when you invest a significant sum of money into something, it can last a reasonable period of time.
13 years is a reasonable time, as is 6. And the software doesn't stop working after the EOL date, it just won't receive updates, so it hasn't even "worn out".
Its also worth noting that software does not necessarily fall under the Sales of Goods Act, or its amendments - case law in the UK provides for it as a per-case consideration, and not a standard entitlement.
http://www.mablaw.com/2011/03/...
So even "sticking to legislation" shows you to be full of crap.
I'm afraid its actually *you* who is full of shit in this case, as the Sales of Goods Act 1979 and its amendments are precisely what I am referring to, and as I have intimate knowledge of that act and its various legal successes, I can safely say that you are full of bollocks.
The Sales of Goods Act is not meant to cover a product for all eternity, for an indefinite period, until the product actually wears out or for any other purpose than to require a manufacturer to provide a reasonable life span for the product in question. The Sales of Goods Act is not even intended to require a manufacturer to fix bugs or issues past the reasonable period of support, just provide a reasonable period of support.
So lets see what other Operating Systems have endured longer than Windows XP...
Red Hat Enterprise Linux 2.1 - released in mid-2002, died in mid-2009.
Red Hat Enterprise Linux 3 - released in late-2003, died at the start of this year.
Red Hat Enterprise Linux 4 - released in early-2005, dies at the end of this year.
Ubuntu 6.06 LTS - released mid-2006, died mid-2011.
Ubuntu 8.04 LTS - released mid-2008, died mid-2013.
OSX 10.1 - released late-2001, died mid-2002.
OSX 10.2 - released mid-2002, died mid-2003.
OSX 10.3 - released late-2003, died mid-2005.
OSX 10.4 - released mid-2005, died late-2007.
OSX 10.5 - released late-2006, died late-2009.
OSX 10.6 - released mid-2009, died late-2011.
OSX 10.7 - released mid-2010, died late-2012.
OSX 10.8 - released mid-2012, death TBD.
Hmm, I can't see any other consumer or corporate desktop OS that has been supported as long as XP has.
So out of all other reasonable time periods for Operating Systems, XP's support length is definitely an outlier and you would get laughed out of court if you tried to force Microsoft to support it beyond its current and well known EOL date.
If you are giving any sort of legal advice based around the Sales of Goods Act, please fucking stop as you have proved that you know shit about the topic.