priteau
Anyway, a better known implementation (in Bash) is probably https://github.com/holman/spark, which was developed by Zach Holman, one of the first GitHub hires.
Investigating - We are investigating reports of degraded performance for Pull Requests Feb 09, 2026 - 16:19 UTC
Investigating - We are investigating reports of impacted performance for some GitHub services. Feb 09, 2026 - 15:54 UTC
But I saw it appear just a few minutes ago, it wasn't there at 16:10 UTC.
As I suspected, poisoning most likely includes drug overdose. They have this comment about the 2023 data:
> #1: Poisoning: 100,304 deaths
> Largely due to the opioid epidemic affecting millions of people in the United States
You can see more recent data than 2004 in their interactive charts. It is interesting to see that deaths from road accidents has much reduced for teenagers and young adults, compared to the rest of the population.
It has been around for at least 15 years! https://news.ycombinator.com/item?id=1728592
I sold my Nintendo DS since then, but I still have somewhere the Supercard that I would use to store and boot Linux, which looks like this: https://wiki.gbatemp.net/wiki/File:SuperCard_CF_V2.jpg
Most of credit for the amazing work that made this possible goes to a few individuals, in particular Malcolm Parsons (pepsiman), Stefan Sperling (who later became an OpenBSD developer), and Amadeus: http://dslinux.org/wiki/ContactingDevelopers.html
About us: The Nimbus team is a pioneer in infrastructure cloud computing having developed what is now recognized as the first open source Infrastructure-as-a-Service implementation. Since 2014, we have been running Chameleon, a national experimental testbed for cloud computing research (https://www.chameleoncloud.org).
About the job: The job will focus particularly on the development and operation of phase 2 of the Chameleon testbed (mainly built using OpenStack software), as well as cloud computing platforms supporting High Performance Computing and Big Data applications and systems.
Visit http://www.nimbusproject.org/jobs/ for the full job description and how to apply.
About us: The Nimbus team is a pioneer in infrastructure cloud computing having developed what is now recognized as the first open source Infrastructure-as-a-Service implementation.
About the job:
The job involves participation in two Nimbus projects. First, it will involve contributing to building and operating the Chameleon experimental infrastructure for cloud computing (www.chameleoncloud.org). Specific tasks might involve: working with OpenStack to provide additional features or troubleshoot problems, help operate the testbed working closely with our system administrators, and respond to user requests.
The second project involves participating in development of infrastructure that combines cloud computing and HPC capabilities for resource management and container optimization. Specific tasks will involve enhancing or developing infrastructure-as-a-service system (e.g., Openstack), exploring or orchestrating their interaction with HPC tools (such as e.g., batch schedulers), and performance evaluation.
Visit http://www.nimbusproject.org/jobs/ for the full job description and how to apply.
The Nimbus team is a globally recognized pioneer in infrastructure cloud computing. We created the first ever open source Infrastructure-as-a-Service implementation, and are constantly evolving and thriving on the leading edge of cloud services technologies.
We work closely with scientific application communities to develop innovative solutions in cloud computing infrastructures and platforms, with particular focus on High Performance Computing and Big Data systems. To facilitate cloud computing research on a national scale, we also operate an experimental testbed supporting cloud computing research.
Our overall mission is to develop innovative technical solutions that create new opportunities in science. The Nimbus team provides a friendly, collegial environment where you will be challenged to help create these groundbreaking new cloud technologies.
We are looking for a software developer specializing in cloud computing. More details are available at http://www.nimbusproject.org/jobs/
The government didn't want to allow pardon to the dead because they said that in some cases they couldn't know that these homosexual acts were consensual and not under age. The Lord presenting the bill is advocating for rehabilitation of the dead if there is enough evidence available, and he hopes the Turing bill (which will pardon only Alan Turing) is a first step towards allowing pardon for the 59,000 convicted who are now dead.
In the case of Amazon, when some sales staff is in the UK (evidence coming from whistleblowers, for instance http://www.guardian.co.uk/technology/2013/may/16/amazon-whis...), when warehouses are in the UK, and Luxembourg seems to be used only for signing the official contract, how is that not tax avoidance?
http://en.wikipedia.org/wiki/C_dynamic_memory_allocation#Ope...
Having been using Growl for years, I mechanically went to buy it on the Mac App Store when 1.3 was released. To make sure the upgrade was clean, I first uninstalled the 1.2.2 version I had on my system… only to realized I could not install the new version, since I am still running Snow Leopard.
I did not reinstall Growl, and I am very happy with my system as it is. I had already disabled some notifications before, such as Adium messages showing up on my screen, but I still had some, like the name of the new song playing. All this noise is now removed and it is great.
I can see how Growl can have its uses though. Sometimes, you need to wait for a long process to finish in order to perform the next action (e.g. wait for a long download, deployment, or software build). Or for alerts of a monitoring system, where you would really like to be interrupted. I may reinstall it when I have such use cases, but enabling only the minimum number of notifications.
Work in progress to replace /etc/security, not yet linked to the build.
Main design goals: 1. Safely handle untrusted file names and file content. 2. Output compatibility with current security(8) to please people parsing the output with scripts (except when improving functionality right away saves considerable implementation effort). Substantial functional enhancements are for later.
Prodding to do this in Perl by deraadt@. Using some feedback from espie@.
http://www.openbsd.org/cgi-bin/cvsweb/src/libexec/security/s...
Many OpenBSD developers are used to CVS and don't see a strong reason to change to another system. However, they are aware of the deficiencies of CVS, and OpenCVS is supposed to fix some of them. For instance, atomic commits was on the roadmap (but I don't think it is implemented yet). You can also regularly see commit messages complaining about problems with CVS.
I know some OpenBSD developers use Git locally to track their patches before committing them to the official repository.
One comment though: there are very few details on radishapp.com explaining how Radish works. The blog post describes a bit more: there is a daemon running besides Redis that sends statistics to Radish.
A little 'About' page on radishapp.com, with the most important information from the blog post, plus a list of supported platforms (does the daemon run only on Linux, or on all platforms where Redis runs?), would be very nice.