It wasn't because the Spitland Internet Gestapo (SIG) has release Flickr! back into the open but rather of the fact that I found a Firefox addon that could get around this block.
For guys with similar problem, here is the Firefox addon at https://addons.mozilla.org/en-US/firefox/addon/4286. It was developed by an Iranian as Flickr was blocked there. Fortunately, the nature of the block over here in Spitland as well as other tightly controlled countries like Saudi Arabia is similar and as such this addon works over here.
Score one for Firefox over Microsoft Internet Explorer. However, that would mean that I would also have to revert back to Firefox from Sea Monkey as my default browser. What that means is that I may end up with the CPU leak problem on Firefox (which would require frequent Firefox restarts) but I think it is a small price to pay to get back my Flickr!.
Anyway, my suspicion was confirmed as to what caused the suddenly locked down of the site. Apparently, the pictures (that people were uploading to Flickr!) covering the pr0test in X1amen over the building of the P.X. plant earlier in the month triggered the lock down by the SIG.
For those outside of Spitland, check this out. http://flickr.com/search/?w=all&q=xiamen+px&m=text.
G1oba1 Voices has also covered this Flickr! disapperance act. Read it at http://www.globalvoicesonline.org/2007/06/07/china-flickr-filtered/
- Voxeros
1. lancerlord left...
I feel the latest Firefox seemed to be able to tahan the leaky problem better. Still memory sucking but not as intense as before.
Wednesday, 13 June 2007 7:58 pm :: http://lancerlord.blogspot.com
You try searching the net. Many tips to improve the memory leak problem in FF. I feel the latest Firefox seemed to be able to tahan the leaky problem better. Still memory sucking but not as intense as before.
2. JayWalk left...
Speaking of which, I have 10 tabs opened right now as I am typing.
Thursday, 14 June 2007 9:30 am ::
Lancerlord: I am refering to CPU leak where Firefox can suck up to as much as 97% of your CPU resources rendering your entire PC/Laptop to a crawl. No problems with memory leak as 230 mb of ram allocated to Firefox alone is a common fare given that I have many tabs opened concurrently. Speaking of which, I have 10 tabs opened right now as I am typing.
3. lancerlord left...
Monday, 18 June 2007 10:48 pm :: http://lancerlord.blogspot.com
97% means can pack bag, go home liao. Everything will be like standstill. Pek chek. :) Tuesday, 19 June 2007 3:33 pm ::
Lancerlord: Well, it happened again last night when I realised my laptop was taking its own bladdy sweet time to recover from Standby Mode. Task manager indicated the Firefox was again sucking up to 97% of the CPU resource which prompted me to forced shut down to kill the process.
No comments:
Post a Comment