I loved the literate programming style and the cleanliness of the FFI also.
Org-mode is even more useful than I had previously thought, the http://orgmode.org/worg/org-contrib/babel/intro.html Babel addition also has a wonderful introduction and looks like an extremely powerful way of presenting code and commentary.
Part 4 is probably the most fascinating piece, as it discusses how their technical choices were different from their competitors and how the leveraged those differences.
I've had to up the maximum simultaneous connections, but otherwise I've been able to log extremely large volumes of data from 1,000s of machines, with syslog-ng. I'd assume the same is true with rsyslog.
Looking at limits on open files, and considering tcp timeouts and cookies were all we needed. Total volume was in the order of high 10s of GB.
If you want to unpack offline, contact details are in my profile.
Regular expressions are my favourite secret weapon; So many problems are made simple by regular expressions and so few people (outside of IT) know of them.
Enterprise extensibility and inter-operativity or inter-dependency is extremely complex to get right.
Multiple standards exist for just about anything, and most implementations of something are broken in one way or another. I've seen obvious and subtle breakage in things that ought to be simple:
* timestamps (not unambigious, not including timezone data)
* mac addresses (within SNMP, in a variety of formats in different places on the same kit)
* integration with LDAP (group membership only looking at primary membership)
* etc.
An application is a software product which fulfills a useful purpose (performing a task, storing data, etc.)
An enterprise application is an application which is suitable for use in a wide variety of environments seen in companies. (for example, as a point of difference, an enterprise application might support a wider variety of platforms or data, or at greater scale than a non-enterprise application)
supporting the fork with updates to the opt outs is good, but the change to the add-on seems gratuitous.
a more user friendly approach would have been to give them the 'downgrade' update, and opened a tab offering the 'enhanced' abine privacy add-on. the update behaviour feels more appropriate for a scammy toolbar, than a useful privacy extension. among their target audience wouldn't this be a turn off?
How do you know that IT pros are less likely to implement a workaround than hackers are to exploit it?
How prevalent is deploying workarounds and mitigations versus deploying patches? I don't know of any research in this area; it would be very interesting to know.
The important questions are how much value is derived from:
- Privacy
- Limited Sharing
- Unlimited Sharing
for both Facebook and the user. This can then be counterbalanced by the costs experienced by the user and Facebook, such as loss of privacy or spam from applications or adverts (a cost of attention/time)
If you do not derive a greater value from sharing your information than the cost, then do not share. It doesn't really matter to this whether Facebook is deriving value, only if you are incurring costs greater than the value received. I don't see how this is sharecropping.
Interesting technique, although I think a domain specific extension of Haskell for analysing log records might be more useful.
I'm sure there are more complex examples, but all the tasks in the screencast could be done easily with Splunk. It might, if you want to develop the idea of log analysis further to look at their search cheatsheet. http://www.splunk.com/base/Documentation/latest/SearchRefere...
It's questioning the idea of work for wages, not the idea of producing in order to consume.
An alternative system could be co-operatives or contract working, for example.