The Firing Line Forums - View Single Post

LBussy · December 24, 2017, 07:06 AM

<removed attachments>

... hrm ... now it works. I wonder if I was running a bugged version of Chrome previously? You never know since it updates itself. I was on 63.0.3239.84, now on 63.0.3239.108.

Thanks for the replies. I hate when that happens. It's like when you bring your car to the mechanic.

Just a comment then: Isn't the user quota a little bit of a negative? While I understand the need to limit things somewhat (someone is paying for the hosting space) it fosters deleting images from threads which might have once had useful images. I guess you have to make compromises somewhere.

ETA: I also noticed there seems to be a timeout to editing posts. I went back to try to inline an image that was previously uploaded.

December 24, 2017, 07:06 AM	#5
LBussy Senior Member Join Date: February 26, 2012 Location: Kansas City, MO Posts: 296	<removed attachments> ... hrm ... now it works. I wonder if I was running a bugged version of Chrome previously? You never know since it updates itself. I was on 63.0.3239.84, now on 63.0.3239.108. Thanks for the replies. I hate when that happens. It's like when you bring your car to the mechanic. Just a comment then: Isn't the user quota a little bit of a negative? While I understand the need to limit things somewhat (someone is paying for the hosting space) it fosters deleting images from threads which might have once had useful images. I guess you have to make compromises somewhere. ETA: I also noticed there seems to be a timeout to editing posts. I went back to try to inline an image that was previously uploaded. __________________ -- Lee Bad decisions make good stories. Last edited by LBussy; December 24, 2017 at 07:17 AM.