Fine-tuning Akamai permissions via ABE

[dhouwn]

btw, IMHO, I disagree strongly with the "Release early. Release often" philosophy, which too often amounts to doing beta testing on (non-tech-savvy) consumers.

In the case of Firefox, feature patches for a version are just accepted in a certain time frame (six weeks in that case), and then there are two testing stages each lasting about the same amount of time, so you can't really say that any feature would reach the public untested (of course it should be in the interest of Firefox to have advanced users use the versions in one of the testing stages). What is more important about this strategy is getting feedback on introduced features and changes earlier.

[Giorgio Maone]

The FAQ entry has been updated.

[Tom T.]

The FAQ entry has been updated.

Thanks, Giorgio.

One more small request: The "syntactic sugar" comment in the revised FAQ 5.4 cleared up some lingering uncertainties regarding the necessity of

Code: Select all

friend.com *.friend.com

vs. now, just

Code: Select all

.friend.com

Any chance of adding that to the basic template, FAQ 8.10, as it would shorten and simplify the ACCEPT list?

It's done the shorter way in the INCLUSION rule beneath, but the longer (x and *.x) way in the first rule, the G-A one.
Some uses have been unsure, as in this thread. Here is an opportunity to resolve that topic.
Same with the ABE Rules, 1.3, where the example uses *.some, but the definition cites just "." (no asterisk)

Many thanks for bringing Akamai up-to-date.