Mindfury [he/him]@hexbear.net to chapotraphouse@hexbear.netEnglish · edit-28 days agoShould we try to do a 'hexbear history' post to try to clue the new arrivals in on any bits, emojis or other intracacies?hexbear.netexternal-linkmessage-square138fedilinkarrow-up1100arrow-down10file-text
arrow-up1100arrow-down1external-linkShould we try to do a 'hexbear history' post to try to clue the new arrivals in on any bits, emojis or other intracacies?hexbear.netMindfury [he/him]@hexbear.net to chapotraphouse@hexbear.netEnglish · edit-28 days agomessage-square138fedilinkfile-text
minus-squareGucci_Minh [he/him]@hexbear.netcakelinkfedilinkEnglisharrow-up38·8 days agoYes, the image was corrupt in some way and it took down the entire site. I had a copy from that time and opening it on my computer instantly shot my cpu temp to 85C and took up something like 4GB of RAM
minus-squarePaulSmackage [he/him, comrade/them]@hexbear.netlinkfedilinkEnglisharrow-up37·8 days agoThe image resolution size was absolutely massive and processing it was the reason the site crashed
again, amongst other things
Yes, the image was corrupt in some way and it took down the entire site. I had a copy from that time and opening it on my computer instantly shot my cpu temp to 85C and took up something like 4GB of RAM
The image resolution size was absolutely massive and processing it was the reason the site crashed