Three things I would suggest:

First off, the timer should be long enough that people who don't play every day (many of us have real lives) can still defend the POS. A week sounds more reasonable to me than 24h, with 72h being a bare minimum of what I would see as reasonable.

Second, attacking the hacking unit should NOT flag the defending corp towards the attackers.

I think this should be a "get rid of unused/unwanted POSes" not a "anchor something and make the defenders either come out and DiaF or lose their POS". Nothing stops the attackers from wardecing the defenders though.

Third, the thing shouldn't have more EHP than a BC can chew through in an hour or two. You shouldn't need to bring 50 friends or capital ships to take one of the things down in a reasonable amount of time.

Providing for those things, I think it's a reasonable compromise between cleaning up dead POSes and allowing people who still want to keep their POSes to have them.

Oh, and I don't think they should be crazy cheap either, I would say 20-50M minimum to keep them from being spammed all over the place (though the number might be less depending on how much of a pain they are for defenders to get rid of).

Yes, I know what I proposed would favor the defenders, but it seems to me that if a corp worked to pay for a POS and grind the standings to put it up, they should get a home-field advantage if they're willing to come out and stop someone from taking it down. I see this as a "Get rid of unused POSes", not a "Tear down all POSes that aren't defended well enough".

Once the suggested 7 day timer is up could you give the target POS owner, or anyone, the option* to salvage the now offline hacking module and score some nice salvage or even to counter hack it and take ownership.

Three things I would suggest:

First off, the timer should be long enough that people who don't play every day (many of us have real lives) can still defend the POS. A week sounds more reasonable to me than 24h, with 72h being a bare minimum of what I would see as reasonable.

You should have at least a weeks fuel loaded into your tower at any given time and I think the OP is talking about PoS' that have run out of fuel.

+1

I agree. My point is that there should be sufficient time to respond if someone is trying to hack your POS. Even if you forgot to refuel your POS (sometimes you know you need to refuel but forget or put it off a bit too long, stupid but understandable), you shouldn't come back to the game a day or two later to find your POS just gone.

Anyone who logs onto the game every couple days and doesn't want to lose their POS should be able to defend it if someone tries to hack it, that is the point of all of what I had posted.

to be fair to the pos owner, it should be a week. Afterall, it could be...

And what if you were in a car wreck and in a coma for two weeks? Where do we draw the line?

Don't forget that the POS has to be offline first. Which means either you weren't keeping it fueled, or you were gone long enough for it to run out of fuel, be found offline, and hacked for 3 days. I don't care if you were marooned on a desert island with just a volleyball for company for a week, it's your failure to be prepared that costs you the POS...not a three-day timer.

Don't you be bringing in stanely into this.

What if there was a module you had to anchor that "hacked" the pos, forcing an offline pos to un-anchor?
...I think the hacking module should be invulnerable while the pos is offline ...