skysight-inc/HackerNews huggingface dataset:
http://www.infoxchange.net.au/crm4nfp

CRM solution that has been developed specifically for ‘Not for Profit’ organisations in Australia and the Asia Pacific.

What is CRM4nfp?

Infoxchange has worked with Microsoft and foundation partners the Benevolent Society, Greatconnections, Impact Support Services, Jobs Australia and Travellers Aid Australia to develop a CRM solution specifically for the NFP sector.

The solution is based on Microsoft Dynamics CRM 2011 Online and provides sector specific functionality for:
I would recommend the Java language and platform. It's as mature as it gets, has strong crypto libraries, is quite popular (especially in banking, which I believe is the target domain) and has adequate type safety and static checking features. For a high-volume web service API I would recommend the Dropwizard framework. It may not be as sexy as, say, Node, but it is a very solid choice.

As a second alternative I would recommend still the JVM and its ecosystem, but with the Scala language and Typesafe's platform. It offers an (arguably) better language, the actor model (which may help with high-volume processing), a modern web framework and may be more attractive to developers, but the ecosystem is not as mature as pure Java.
I still think the most interesting thing about gray codes is the relationship to hilbert curves. It's really useful for figuring out locality with a cheap calculation (axes to/from transpose).
The feature was added in 2012 or something, whenever the log support came.

The DNS issue affects not just systemd but any stub resolver.
I don't agree with the assumption that you fit one mold or the other. I do believe there is a market of people that would be willing to play an MMO if the rules were different (as mentioned below, Eve is evidence of this).

Blizzard did an excellent job solving MMO problems that were major problems at the time, and they solved it so incredibly they completely dominated the market and squeezed out any room for new concepts.

Not everyone needs or wants the hand holding and artificial barriers that are put up between players and see some see that as a detriment to the experiences that could be created in this type of game.
FreeBSD is a concrete project in the same way Debian is.

Comparing a full system like FreeBSD to a kernel like Linux doesn't really get us anywhere. You can't really talk about the desktop experience comparisons when Linux can't even boot without a userland. If you tried to do it in an abstract sense, you'd be guaranteed to get responses of, "yes but Mouse Rat Linux supports ZFS and is also run by an elected core team!"; since there's pretty much a Linux distro for everything imaginable.
I didn't say FSS was a step backwards or wasn't useful. You completely ignored the content of my post. When the project founder tells people "hey, you don't need external syslog servers" it shows an absolute ignorance of WHY we have external logging servers. And that kind of ignorance is dangerous in a project leader. ESPECIALLY when his solution to being called out on his ignorance is to ignore the person who was critical.
Consider Sendmail as a cautionary tale. One more than one occasion I have seen a busy sysadmin manually edit a .cf file and forget to backport the edit to the .mc file. The next time someone regenerates the .cf from the .mc you have a vanishing edit.

Yes, the sysadmin was clearly at fault. No, this is not a deal breaker, as seen by the longevity of Sendmail. But a config file that gets pushed through a preprocessor has a more complicated life cycle than a "static" equivalent.

If your organization has comprehensively embraced ansible/chef/puppet/etc this may be a non-issue, because all of your configs might be generated. Just food for thought.
Log signing is nice to have, but ultimately not that reliable. Systemd has quite a broad attack surface, and if the attacker has root, you're fucked anyway. It might be a useful tool for poking local sysadmins.

compromising systemd, forcing it to re-sign the logs (assuming that practicable.)

Potentially you can have an alert that checks the signature, which might be useful. However you can do something similar now, but comparing log files (local vs remote) although its not that easy or elegant.

I've yet to use systemd in anger. I'm sure when we update all 25k machines to it next year we'll become intimately familiar with all its pains.
Your comment is an amazingly crap comment. Provide details and/or links to details. Also, does your “crap” assessment also apply to kdbus?
Thank you for advocating this practice! This kind of 'deep linking' seems to be the norm even among scholars, and I've never understood why.
The problem seems to be that everybody wants to avoid breaking anything. You should just serve webp to browsers that send an Accept:webp, and if those browsers get broken images that's their problem, and not the rest of the internet's problem. Website operators keep compensating for the brokenness of browsers, and then the browser vendors have no motivation to fix their shit.
> Point is, thus far they have not

This has been possibly through forwarding to rsyslog right from first release.
Ideas About a New Programming Language for Games
works fine for me in Chromium 38.0.2125.122 but as mentioned in other comments the site is a disaster on firefox
The thing I learned that blew me away is that with their new networking stack, the cross-AZ communication within a region is "always <2ms latency and usually <1ms".

As mentioned in the slides, that's the same latency usually associated with SSDs and 100X better than the latency typically associated with cross-region networking. This suggests to me that running distributed databases in multiple AZ's has almost no latency penalty (e.g. you won't even paying eventual consistency / replication lag taxes that you might think are a danger). That's pretty damn cool.
I think the systemd complaints really boil down to two very real problems:

1. The authors of systemd aren't dealing with criticism well. They've allowed it to turn into a PR nightmare. Agree or disagree with them on specific issues, but they've allowed this to grow out of hand. There are nearly daily popular posts on HN, Reddit, etc. Most of these are bikeshed arguments, but if you have so many bikesheds that it becomes a daily issue on news aggregators, then you have yourself a culture problem.

2. Perhaps as a result of the above, there haven't been any limitations of the scope of systemd. This means that there is a lot of feature creep as stuff gets added in, and criticism gets swept away without considering it.

Unfortunately, I don't see an easy way to fix the culture problem. But it needs to be addressed.

EDIT: formatting
You make a good point. FSS isn't an IDS, it's a metric to be used by an IDS.

However, that raises the question of what the hell it's doing in the init system, and not implemented by the IDS. That's a SOLID violation.
I haven't watched this talk for several years now, so my memory may be faulty.

That said, I highly recommend watching this talk. I think the most insights regarding cons v. conc lists are worth thinking about.
> There’s also a right fold, foldr, which does the same, but right-to-left.

No. There's also a left fold, foldl, which does the same, but left-to-right. The fold definition in the article is foldr.
Reanimate the Ruins Results – PARALLEL PROJECTIONS
Even removing"Mozilla/" could break UA detection that uses hardcoded string indexes to version numberz. :(
> Source?

Experience. I've set up SELinux, AppArmor, etc. For example back near 2000 a lot of Apache servers I worked on were running as root, now few are, and better still many have limited permissions even as their user/group.

The same can be said for many Linux services today. And better still the few that HAVE to run as root often come shipped with some level of permission controls to limit exposure.

I can link you to a random book on Linux access controls and security if you want an actual third party source. Or be a total dick and link to a man-page.

> intercept where?

It depends which system you're using to send logs remotely (and how it is configured). Sometimes the filesystem, sometimes IPC, etc.

e.g. http://www.rsyslog.com/doc/queues.html

>> Most attackers have to start outside and fight their way in which will generate plenty of logs for either external logging or FSS.

> Source?

Source on, what? That attackers who break into systems generate logs? You REALLY need a source on that, REALLY? Come on now.

> Point is, thus far they have not, and their first choice was not what the author views as more secure.

Alright, and then criticise them for that. If the article had been about systemd's lack of remote logging that would have been one thing, but it was complaining that FSS was bad because systemd lacked remote logging. FSS existing is irrelevant.

Also, again, open source. Go implement shit.
> Yes, the sysadmin was clearly at fault. No, this is not a deal breaker, as seen by the longevity of Sendmail. But a config file that gets pushed through a preprocessor has a more complicated life cycle than a "static" equivalent.

Er, only if the application doesn't run the preprocessor itself.
For people wondering about GTK,this was posted on Reddit

http://www.reddit.com/r/Android/comments/2mzqy5/xpost_from_r...

>Evolve OS reached out to them, we started with a chrome OS esque environment, and we started a material gtk theme. This uses qt, which is good for new apps, but not existing. Evolve is implementing a new lib for animations, that'll work with gtk, and existing apps. We've got dreams for it, check out the live stream on YouTube!
He presumed those things because the terms you used, “looter and griefer”, actually mean exactly those things.
Internet Explorer (of all things) already had the right
idea with its "previous IE" mode: if the renderer emits
standards errors while parsing the site, offer to retry
with an older renderer (and send that renderer' original
UA.)

IE dropping into various modes to interpret your document can be wonderful when it works, but can also be a huge pain. I work on PageSpeed, an open source optimizing proxy, and this IE behavior keeps us from making a lot of optimizations on IE. Consider this code:

<link rel=stylesheet href="main.css">
<!--[if IE 7]>
<link rel=stylesheet href="ie.css">
<![endif]-->
<link rel=stylesheet href="more.css">

Combining multiple CSS files into one is a great way to speed up page load times because most of the time in loading these resources is waiting for the round trip. We would like to issue:

IE7:
<link rel=stylesheet href="main+ie+more.css">

Other browsers:
<link rel=stylesheet href="main+more.css">

But IE's impersonation keeps us from doing this. When we process a page requested with an IE UA, we don't know which version of IE it will decide to be when interpreting the page. Yes, it claims to be IE10, but if it sees something to drop it into IE7 mode then we shouldn't have removed ie.css.

My favorite part of this announcement is the link [1] to where MS says this detection is going away:

The next major version of IE will still honor document
modes served by intranet sites, sites on the Compatibility
View list, and when used with Enterprise Mode only. ...
Public Internet sites will be rendered with the new Edge
mode platform.

[1] http://blogs.msdn.com/b/ie/archive/2014/11/11/living-on-the-...
Thanks for everyone's answers. I now have a bunch of reading/learning for the weekend.
>>arent sent instantly so an attacker could intercept or alter them

With Reliable Event Logging Protocol [0], interception is somewhat mitigated. You can configure and white-list certificates on the client and server so that even if a network attacker inserts a syslog relay with a certificate that's signed but isn't the one expected, you can't intercept the messages. Though, if you have that much control of the network, you can just drop syslog packets entirely. Having a dedicated management NIC and network helps mitigate that.

And I think there's a big difference between 10 seconds, and any delay inherent in to external syslogging. 10 seconds is enough time for an automated exploit to penetrate multiple layers of the security onion, but external logging should be able to squeak out a few messages between pwnage and syslog clobbering in the same situation (YMMV).

[0] http://www.rsyslog.com/doc/relp.html
> compromising systemd, forcing it to re-sign the logs (assuming that practicable.)

This is completely unfeasible. The point of FSS is that you sign the logs, create a new key using your old one, and then permanently throw away the old key. Once this is done, no matter what control you have on the system, you cannot re-sign the logs without the tampering being obvious.
I thought your original comment was misguided. I think there are cool and interesting things happening with blockchain technology that are related to ownership, and that are based on locks. But the fact that some new technology touches both doesn't mean that traditional locks do.

"Ownership" is a legal concept. A lock doesn't prove ownership in any way. The person with the keys to a car or a house isn't the owner of it. The person listed on the pink slip/deed is.

I started out saying that locks are just about access control, then remembered the old "locks keep honest people out" adage, and added "intrusion detection" to the list.
Oh totally. ZFS gets a lot right but even ZFS can't make deduplication practical for all bar a few fringe cases.
I should point out that $1.60 revenue/user/month is really high, unless you are addressing a marketable niche like engaged women.

Facebook has half that revenue per user, and that's with powerful targeting options and a userbase that spends a lot of time on the site/app.
NixOS got this right.

Declarative configuration is great in theory but it doesn't scale well. See Amazon's CloudFront configuration files for what configuration in JSON looks like. (For example, https://s3-us-west-2.amazonaws.com/cloudformation-templates-...) It quickly gets hard to manage the syntax and balance all the quotes, parentheses, braces and brackets, with careful use of whitespace being critical for even a hope of understanding it. When you add in semantics, it gets even worse. Take the "Ref" construct in CloudFront to work around the fact that JSON doesn't have a way to name something and refer to it elsewhere.

As the amount of configuration grows, you have to introduce abstractions to encapsulate common patterns, break out of deep nesting, name things etc. I guess it's possible to do that declaratively, but that leads to things like XSLT. (Or, open the CloudFormation JSON linked above and search for "Fn::". It makes me shudder).

S-expressions would indeed be better than JSON, but they still wouldn't scale without macros. So either all programs would have to know lisp, or you need a dedicated program for executing the configuration.

That's what NixOS has. It does all configuration via "nix expresssions" which are written in a lazy, functional language. The functional bit allows for the abstraction necessary to make large amounts of configuration readable and maintainable. The lazy bit makes executing large configurations efficient, given that you're usually only interested in certain parts of it at any one time.

The result is that you can write a configuration that describes a cluster of machines from top to bottom: from how many app servers to put behind the load-balancer to which version of zlib to link node.js against.

It takes a bit of effort to learn nix, and for many, the functional paradigm will be strange and scary. But's so worth it.
There is plenty wrong with the systemd concept.

Apart from your own list of things wrong with it, it is also monolithic, which goes directly against the Unix Philosophy,[1] which when concisely expressed is:

Write programs that do one thing and do it well.
Write programs to work together.
Write programs to handle text streams,
because that is a universal interface.

Systemd is an application that more properly belongs on Microsoft Windows and MacOS, because of their own tendency towards centralization and control. But I'm not surprised that many popular Linux distros have chosen to adopt systemd, as they suffer from a bad case of Windows and Apple envy.

[1] - https://en.wikipedia.org/wiki/Unix_philosophy
You know what would be a great idea? get a Window Manager that everyone is hating because the usability and customization that took years to achieve is being throw out of the window by the new maintainers just to copy Apple's UI, and let's use that and add Google's latest UI mumble jumble, and instead of just releasing as a window manager, let's call it a new distro.
(Not OP, but I'll reply anyway.)

>Source?

You need a reliable kernel exploit, which isn't always easy to download and compile within 15 minutes (or 10 seconds, or whatever you set the interval to). But I agree that this is not a very good mitigating factor.

>intercept where?

If you have root on the box and logs are being sent to another server via syslog, you can intercept the traffic in all sorts of ways.

>Source?

Read any incident response book or blog.

>Point is, thus far they have not, and their first choice was not what the author views as more secure.

Yeah, I side with the blog author in this case.
Isn't this what cyanoacrylate (crazy glue) was invented for? Battlefield wound stitching?
Sometimes you have a lot of throughput, and it simply isn't feasible. Could potentially saturate your network, or overload your remote aggregator. Of course, all of this is fixable, but often times when every node just pushes logs out, it's hard to throttle that.
If it takes context to know what was said and you are saying that we do not know the context, how on earth are you making the claim that you know it was intentionally misrepresented, or in fact misrepresented at all?

For one thing, the response from Uber has not given the indication that this story was misrepresented, but rather has reinforced its reliability:

---

"I wanted to apologize to you directly — I am sorry. I was at an event and was venting, but what I said was never intended to describe actions that would ever be undertaken by me or my company toward you or anyone else. I was definitively wrong and I feel terrible about any distress I have caused you. Again, I am sorry."

---

"The remarks attributed to me at a private dinner — borne out of frustration during an informal debate over what I feel is sensationalistic media coverage of the company I am proud to work for — do not reflect my actual views and have no relation to the company’s views or approach. They were wrong no matter the circumstance and I regret them."

---

There is no indication there that the reporting was false and those quotes are direct from Emil.
nonsense!

these are still tests just as much as if they'd been written first, it's just a different methodology.
So much negativity in these comments. Instead of saying "why?" or "MD is for mobile screens," present your opinions in a factual matter to support your arguments.

I personally don't prefer the MD/Metro look design philosophy. This stems from the fact that I believe in designs that help accomplish a task, not prettify it for the sole of prettifying it.
Openshift and Go – Teaching Old Dogs New Tricks
People screw up. The people working on Chrome for iOS didn't mean to break WebP support, and when they discovered this they fixed it in the next revision. They're already plenty motivated and on top of things.

It doesn't make sense to punish visitors for the mistakes of browser makers, even if browser makers need more pressure, which they don't.

(And the situation with Opera is even trickier. They did support basic WebP and no one was even doing Accept-based detection yet. More communication would have been helpful between Chrome and Opera to coordinate what "Accept: webp" would mean, but it's not a situation punishment would improve.)
I live in a ski town, this might explain why my family tends to sleep so much. I try for 10+ hours per night, which would make sense if I need extra time to replenish seratonin.
I think Amazon is just riding the tiger here. One thing to remember is back in the day they were massively over provisioning just to support their peak loads during Thanksgiving and Christmas. All that spare capacity became AWS. I bet their utilization rates aren't any different today ...quite possibly worse.
Because sending logs has a lot of overhead. Much of that overhead can be mitigated by waiting even a few seconds, packaging several logs together, and sending a batch.

On a LAN where the sender and receiver are close this type of overhead is much lower than over the internet. It is also worth noting that on some systems several logs can be generated each second, several hundred a minute, so even modest overhead can become costly 24/7/365.

It is also worth noting that some people have remote logging configured NOT for security reasons (primarily) but for system health monitoring. In this scenario the speed isn't as vital as keeping the overhead low.
> increasing connascence

Well, you're trading connascence of position for connascence of name, which in this case is much better because you are providing context for the argument data.
If the special effects can be turned of and it will be as efficient as the Blackbox Window Manager I may give it a try.
Thanks! Those do look nice. But I think I could do the same as you with GNU make and rule pattern matching (I use a Makefile library for compiler detection and some useful functions, but stop short of including automatic rule generation, in case I want to customize things.)
systemd Services for Selenium Grid
That's not much. Our baseline config HP DL380s come with 64GiB RAM (!!)
The wolf among us is fantastic!
That's a fair point. When I wrote "centralization" I mainly meant components rather than development model. Systemd is very "centralized" in that a single package does a lot, but Linux as a whole is very decentralized in development model. BSDs are "centralized" in the sense that they have a single tree in source control, but the main result is a rather small, very configurable base system. (Then you deal with ports and packages on top, which feels more like a Linux distro: scripts that pull distfiles from lots of different sites and apply patches; not unlike the experience of building a .deb from source.)
Best Android Resources for Designers (?)
I'm a product designer wanting to contribute to Android. We've had a really difficult time within my team on the Android-front (in both finding good Android developers, but then also the devs we have worked with have no concept of being able to reproduce what the design looks like).

I conceptually know nothing about Android so this probably sounds stupid, but my intention would be to build the "front-end" of the apps (colors, fonts, spacing etc) & work with our lead Android developer who would hook up the backend.

Are there any resources for this kind of thing? Or do I have to get my hands dirty & dive into the whole Android ecosystem?
Spoken like an engineer but not a business owner.

That only works until your customer spit in your face yelling "I don't want your excuses and just make it work."
> Yet there are traces of human life there dating back at least 20,000 years BP (Before Present, Present being defined as January 1, 1950, as used in radiocarbon dating).

What's wrong with writing '20,000 years ago'? Seriously, 'BP' instead of 'ago'‽
Samsung asks the US government to block Nvidia 's chips
Can someone explain bit about "trying really hard not to suggest launchd?" He's right, it does seem like an obvious fit, but he takes it as obvious FreeBSD wouldn't use it. What am I missing?
I see people riding them all the time. I wouldn't let this stop you if you're actually interested. It would be great if the law always reflected the reality on the ground, but when it doesn't I favor pragmatism.