News for hackers. Stuff that matters.
Re:Google's CardDAV server isn't standards compliant (2014) by sanderjd on Monday February 19, 2018 @05:10PM (#16416164)
I know nothing about these RFCs, but this seems trivial to clear up with a reference to the text. Here's RFC6409 section 8.8: https://tools.ietf.org/html/rfc6409#section-8.8. There is exactly one "MUST NOT" and it looks like it only prohibits what your parent said it does.
Re:Google's CardDAV server isn't standards compliant (2014) by leephillips on Monday February 19, 2018 @05:46PM (#16416376)
There seems to be an idea floating around that anything at all is permitted under the RFC for MSAs unless it is specifically prohibited using the phrase "must not", regardless of context and other guidance in this RFP and the other RFPs that refer to it. Perhaps this is true. I have a sincere question for anyone holding this opinion: would Google be in compliance if their software altered the message body by adding the sentence "Google is the best search engine ever." here and there, at random? If not, why not, exactly?
Re:Google's CardDAV server isn't standards compliant (2014) by daurnimator on Monday February 19, 2018 @06:22PM (#16416581)
yes they would be compliant.

They wouldn't be a good server to use, but they'd be one compliant to the specification.

--> What this tells you is that abiding by the spec is not everything, it just sets minimum interoperability guarantees.

Re:Google's CardDAV server isn't standards compliant (2014) by leephillips on Monday February 19, 2018 @06:28PM (#16416606)
Thanks for this reply. It's food for thought.
Re:Google's CardDAV server isn't standards compliant (2014) by zamber on Monday February 19, 2018 @07:34PM (#16416954)
In Poland it was standard to add ads as mail footers among homegrown free providers. Some still do. If they don't have sold ads they just advertise themselves.

Made me hate pretty much all footers, especially the bloated corporate ones.