sramov

Shenanigans.

I am not using it personally but administer and maintain a cluster, among other people. Magento is brain dead.

As for high hosting bills, build your own equivalent version and then share your own hosting bill data.

Why do you think so? Not all sites are created equal. And Pinboard is definitely on the lean side.

Try hosting a cluster of Magento 'daily deal' sites on Amazon infrastructure, with shared storage and isolated RDS instances for each region. You end up with 15-20k $ per month for god damned bloated magento installs.

I wanted to make an opposite `gmailintervention.com` site, it appears they registered it with MarkMonitor Brand Protection™ :)

No, I've set up Route 53 on my own domain (ramov.com) and queried the results via DNSCog (http://www.dnscog.com/).

I've used NSD once, it was good. Other than djb 'non standard' conventions and installation procedures, I see no other issues with his software and am happy Amazon opted for djbdns, especially since I don't have to manage it :)

  DJ Bernstein TinyDNS 1.05

Anycast djbdns, nice :)

Finally! We can now all use colors! And perky styles! And images!

Excellent! I am seriously considering just dropping all HTML email. Want your email to be received and read? Use the god damn plain text. You now, just write the email.

I can only imagine the horror of running a hosting company. If you want to do it properly, there is no end to complexity. Not to mention the money part.

I've always dreamed about running my own niche hosting business, running on dead-stripped Slackware custom boxes for actual serving/hosting and OpenBSD for routers/firewalls/spamd daemons (actually I would not deal with email at all as it is a separate business in itself) etc. All it takes is few seconds thinking about it and then realizing what a crazy talk that is.

So hats off to providers with a clue! As for the 99% of cookie-cutter companies/resellers, do a favor to everyone and close your doors.

Linode/Slicehost are always a safe choice.

But if you want cheaper, take a look at http://arpnetworks.com/vps -- they start at $10. Heard good things about ARP.

Might want to visit http://lowendbox.com/ too, but it is something I do not recommend if you don't know which of the gazillion hosts featured there are reputable.

Validator is having hiccups ATM. It is valid, trust me. Try later. If you don't believe me, try some other pages, including the W3 one itself, they all come out as invalid.

Edit: The validator works now.

Those are just tools. A means to an end. The end result is minimal. In essence, it is only one small Makefile, which calls various external scripts.

Much like in life, where minimalism often involves more work. It is harder to design something simple, then something complex.

Feel free to put it through W3 validator, it is perfectly valid HTML5 (but the same can be done with 4 too).

AFAIK there is not.

I've just touched a favicon.ico. Zero byte, but at least it's not 404. I might do the same for robots.txt. Thanks.

I don't have any JavaScript, CSS is small, there is only one tiny image which is very small even base64 encoded. So I don't think this applies in my case.

For bigger advanced sites, yes, you are right.

Up to certain point, this is 'better', from the certain point, it is not.

The one more step is the same as in Jekyll or any other static site generator. You have content on disk, (re)generate the site and then upload it. In my case I edit an article or write a new one, type 'make all', preview the result locally in the browser, if it is fine, I type 'make live' and off it goes to a server -- with only differences from the last time uploaded.

It can also be integrated with DVCS post-hooks.

You are right. It takes a certain structure, quite a bit of adjusting etc.

But the result is what it makes all worthwhile.

BTW, I was doing all the optimization you were doing on some of my sites, but I always missed some nice ways to automate. Imagine the happiness when I stumbled on your hg.diveinto* repositories. A candy shop.

So, thank you.

There is a distinction to be made here. Inefficient in page load times and performance or inefficient in the unnecessary complication? I was talking/responding about performance.

The bigger the site, lesser the point in all of this (and harder). It is a small personal site and I enjoyed the process of doing all of this. Makefile is nice to have in the end, which means it was a one time investment.

I can see being it received like that. But the issue is deeper. Take a regular thousand line site and strip the newlines. It is not a same thing. A fact that buildout depends on so many utilities and little scripts and glue makes it clear the result is something a majority of people would not bother messing with. I bother because I really do care about the little differences. There is also no body, html, head, any divs or optional end tags etc.

On the website, it is clearly stated I am a minimalist and perfectionist. The URL slug of this article also reveals something :)

As for the title, it might be perceived as catchy. But I like nice titles on my sites and the fact I self publish entries (because of the HN blog comments experiment -- which I am happy with) makes it even harder.

Is it not a one-line website? :) Short and accurate title I would say.

Do a test proving it this way is more inefficient.

BTW, everything is separated before publishing. CSS is one file, reset CSS is in another, there is a HTML template etc. Easy maintenance off line, online and published does not matter. It is similar with dynamic publishing.

As for the inefficiency we all know HTTP requests are the biggest enemy. All my pages are exactly one request. With everything being minimized, gzipped and unused CSS selectors stripped I do not see how this can be more 'inefficient'.

Added a note about nginx http_gzip_static_module which doesn't get used as much as it should.

One tip on the gzip parameters, I use -9cn. The 'n' flag is important as your gzipped files will not appear corrupted by many gzip online checking tools. E.g. everything is green: http://redbot.org/?uri=http%3A%2F%2Fsimeramov.com%2F2010-07-.... Took me a while to figure it out. I believe it also benefits rsync.

There is one serious downside to all this reckless optimization -- I don't even notice the bandwidth RRD graphs changing if some page hit the HN front page or get featured elsewhere. The pages are so small the graphs almost always look the same, i.e. basically flat :) All the bandwidth is from me backing up my home dir to server.

Considered, but I like the bottom-up approach, putting content dead first. First you read something and then if you like it look up the author etc... Seen it on couple of sites and immediately liked it.

Also, my name is in every page title.

I've put title attributes on links ('Send me an email' and 'Go back to front page').

Minimalist trade-offs :)

Like I said, it is not that simple. The best would be to make a copy of the page, de-minify it and try for yourself. Then tell me the results ;) Focus on top and bottom parts of the page. If you don't see it, try a page with more content, so it will scroll.

All kinds of issues will arise.

I have. Click on my name. If you are on the article it will take you home. If you are home, it will send me an email.

Maybe has some usability issues but it was a minimal and elegant solution to a problem.

It is not that simple. Initially I used that method. But then you have to put:

    html, body { height: 100%; }

After which you end up with padding issues which you need to workaround with some stupid methods.

Got tired of it, put background image instead and simplified the CSS further :)

As for the RSS feed, it won't have any.

I am mainly interested in providers with EU presence because of the latency which is a reason I've never tried prgmr.com. Are you able to install Slackware there?

Would be nice to have a directory of Slackware friendly providers...

That is correct. They just wrote data over the whole damn disk. ATA SECURE ERASE as I believe directs the controller/firmware to bring the cells to a factory state, which takes a little time because the cells only need to be marked clean, not rewritten or anything like that.

The method I use on my SSD when reinstalling:

    hdparm --user-master u --security-set-pass 12345 /dev/sda
    hdparm --user-master u --security-erase 12345 /dev/sda

No idea. Try going to nokia.com and then look through locations to buy from, or online stores.

I believe the Nokia C1-00 has the ability for two SIM cards (on demand, not simultaneously) and 1616 does not. Otherwise, they are the same.

This phone is around 30 euros before taxes, unlocked and free. I don't think the battery is particularly larger than in other models, it's just that the phone itself is quite economic in its use of it, I guess. There are few features and it uses simpler software.

Batteries are getting better all the time so this should be a case of the new, modern battery and simple technology which gives it prolonged use. If they really wanted I would bet they could make it to hold even longer before charges. It is a matter of tradeoffs as you say.

I have a bigger issue with the fact many people consider such phones are for poor people or for developing countries. I for the fact, want such a phone on purpose. Hell I wouldn't even mind the colorless screen. This is what irks me. Such phones are becoming increasingly rare and difficult to buy. I do not want a camera, mp3 player, FM radio, browser, apps, MMS and gazillion other gimmicks. I want to make calls and send/receive SMS without charging it every few damn days.

nginx. And I've heard a bunch of good things about Perlbal, too.