I would beg to differ on this. For CI, you can easily use spot instances which are dirt cheap. We pay $0.07/hr for ours. Assuming we had a build running 24x7x365, that's $613.20 per year costs. You'd be hard pressed to find a decent box for that price. Additionally, builds are not happening 24x7x365, but rather only when changes are made so your costs are even better than hardware, which is sitting idle and using power and rack space during the interim.
We're using OnDemand for CI of everything and CD for some. We use spot instances for the workers because we don't mind waiting a bit for the test to happen. We typically have to wait ~3.5 minutes to get an instance but are only paying $0.07/hr for that instance. It's ridiculously cheap for us to do it this way.
Thank you. So, I can think of QAM in the same way as a PRI and Comcast would be setting aside one or more channels for Apple (or other) traffic.
There's no 'separate pathway' over a single line. Are they talking about QoS?
Good, it's public now. I don't have to RTFS because I was there when they announced and described this and had a chance to ask questions about it. It is brand new as of last Thursday and it is not an ARF based FBL. It is a single daily report that will give ESPs an idea of how their emails are being handled by the Google classifier. It will not be useful as an unsubscribe mechanism as it will not include any recipient specific data. Only ESPs are eligible and even then it will be limited as they roll it out and get feedback about the new service.
So, no, they still don't have an ARF based FBL.
Maybe legally but for most ISPs these days: spam is that which that their customers do not want to receive. I've heard it directly from postmasters at the majors. It doesn't matter if they opted in, have a relationship or any of that. If the customer no longer wants to receive it, it's spam. That's the base operating premise at this point.
But Google doesn't have an FBL (I.e. ARF based reporting) so that isn't possible.
This actually doesn't work like that. At the same presentation they announced this new feature at they said that the spam filtering was very specific to individuals. Using seed addresses isn't very effective for determining delivery.
Their postmaster team, historically, has been very difficult to contact for this kind of information. That appears to be changing given some further, as yet unannounced, changes they are making.
Why do you assume that because its on GitHub that its public? Many companies and individuals have private repos on GitHub.
The OSS movement shouldn't care about what other people think. Software is created and put out in the wild in the hope that others will benefit. Whether a particular class of people use it or not is typically irrelevant (unless they are the target of the software). The only people who are likely to greatly care about this are the people trying to make money off of open source software.
If this were another era.... This book did wonders for me -- http://www.commodore.ca/manuals/c64_programmers_reference/c64-programmers_reference.htm
I guess everyone is missing the part that we haven't actually confirmed the composition of the atmosphere and whether it corresponds to one of their simulated atmospheres to such a degree that their results are applicable *or* that the simulated atmosphere is actually usable by life of any kind.
For all we know, it has an atmosphere made entirely of nitrogen or one that doesn't have sufficient carbon dioxide to sustain a greenhouse effect and has substantially frozen out.
This is purely hype of a simulation based on mostly made up stuff to determine what compositions *could* work to sustain a temperature-habitable environment. Mars is nearly temperature-habitable but no one would ever claim that it is 'habitable'. The only really interesting bit is the ability to, in the future, spectroscopically analyze the atmosphere and plug the values into their simulation to get results based in reality.
1) If you're being blocked then you're hosting your mail server on IP space that Comcast and Verizon have designated as dynamic. Don't do that. Either get them to properly classify your block as non-dynamic _or_ make sure that you're really on non-dynamic space.
2) Ensure that you have proper reverse DNS configured for your server. If you have business class service, they should be completely understanding of your need to change PTR names for the IP's you use.
3) If you really are running on dynamic IP space and have no way around that (that's not painful to you), you always have the option of smarthosting your mail through the Comcast or Verizon mail servers. That's what they're there for.
DCC does something very similar, and has been in use for years.