Arch Linux and OpenWrt projects have successfully used Software in the Public Interest http://spi-inc.org to resolve their problems. I recommend it to use by Void too.
> Furthermore, we’re in contact with a non profit organisation that helps open source projects to manage donations and other resources. We hope that we can announce further details in a few weeks.
I've been watching the Google SERPS view of his website tank since he switched to his JavaScript stack a few months ago.
It's a eye-watering example of what happens switching from a static website to a client-side generated one. There's basically nothing on the first page of a site:scripting.com search anymore.
Even the Google Sitelinks view lists the RSS feed as the most important page after the homepage.
Maybe your google is broken, but on mine, I get plenty of hits. If you do a view source on the page you'll see why it works, there's a static copy of the full text just for google to index. Try this search:
I get all the hits in the first page. This is something that was just posted recently so you can see they're still indexing the site regularly.
Now the page rank might be hurt by the fact that Scripting News is http and they say that they're downgrading http sites. That's fine with me. The web is not owned by them, as far as I'm concerned. YMMV.
Is mirror.scripting.com really the most important page on scripting.com (and it's currently unavailable). That's what's turning up as the top result, more important than the scripting.com homepage.
> Good thing is we can load old microcode on Linux
You cannot load old microcode anywhere. The CPU won't let you.
The OS feeds the CPU a blob, the CPU checks that it's signed by Intel (to prevent modifications), and it additionally checks that the version number is newer than the currently-running code. If it's not, it won't be loaded.
If you have a CPU with the old microcode versions, you can keep it around, but if you update your BIOS you'll find it will bring the new microcode in and you can't downgrade after boot. If you're lucky the BIOS manufacturer wasn't too careful with signing their BIOS and you can replace the microcode blob, but that's a huge hassle.
Microcode is not written to the CPU, it gets loaded on every boot. This can happen during the BIOS POST, during the OS bootloader or even while the OS is booting. Therefore, yes its possible to run older microcode (at least on Linux), since you just have to not write the newer version on boot. If the BIOS contains the new microcode, you can flash the previous version of the BIOS.
> Microcode is not written to the CPU, it gets loaded on every boot. This can happen during the BIOS POST, during the OS bootloader or even while the OS is booting. Therefore, yes its possible to run older microcode (at least on Linux), since you just have to not write the newer version on boot. If the BIOS contains the new microcode, you can flash the previous version of the BIOS.
Did you read the last paragraph of my message? Because you're not really disputing anything I said. (to clarify, when I say "You cannot load old microcode anywhere", I define "old" to mean "older than the currently running microcode", I.E. you cannot downgrade it at runtime after it's gotten a new one loaded to RAM.
If you're willing to run outdated system firmware (with associated bugs, security vulnarbilities, etc), you can do it - just like I said in the message you're replying to. But that's not what I'd call a good solution.
The CPU has a burned-in microcode. It can be updated after the CPU is booted, but the updates are only written to RAM and lost on shutdown.
Usually the system firmware will include a recent-ish microcode and automatically update on boot. Many OSs also bundle microcode updates and install them on boot.
"2012-03-29 18:20:33, 2 years ago: Free accounts not accessed at least once every 6 months will be considered dormant and unloaded from memory."
What does "dormant" mean here? Do they delete your DNS records? It might not be as draconian as what DynDNS was doing, but certainly a barrier you should consider.
Your account at freedns.afraid.org has not been visited in at least 5 1/2 months.
User: Xxxxx Xxxxx (xxxxxxx)
Last visited: 2013-09-21 (169 days ago)
Unless you visit the site anytime in the next 2 weeks, your account will be considered dormant. "Dormant" consists of unloading any stale DNS records from memory which you may have set up in the past.
This stale entries optimization will free up several gigabytes of memory, making it available for active users. This will allow a DNS server to do a cold configuration boot, and load in new zones in a fraction of the time and space.
Users supporting freedns.afraid.org with a premium plan of any kind (even the smallest) will not be affected.
What does "not accessed" mean? One could write a script that would log in every month or so, click around (very carefully of course ;) ) and logout. How would they know the difference?
As a matter of fact, that's what I was doing to bypass DynDNS limitations: running a PhantomJS script via cron once every week to login, click around and logout. But it is a tiny hassle anyway. Much better to stick around with a service that does not have these annoyances.
Somewhat sadly, it was my github project that seemed at times to garner the most interest from outside, even though it was just a shoddy python script thrown together in a 10 minute cigarette break at work.
